I lost root privileges upgrading to 2.0.0.7111
- Just from my experience:
I just rooted my device with Dingleberry 3.02. Got the nice root prompt "#".
I had some issue finding the market application in the HCL updater, and after playing around I considered to upgrade to 2.0.0.6149, mainly in order to fix the market.
But I was surprised to find that there is a newer upgrade available: 2.0.0.7111.
So I upgraded.
And then, surprise, trying to ssh with dingleberry I got the "jailbrake failed" message.
Since I had root privileges but the android market wasn't working I can't tell you will all loose root after upgrade to 7111 but I thought I should share this.
Just be aware...01-18-12 11:38 PMLike 0 - Do we have any other .7111 experiences with root yet?
I've been rooted since the original .4869 without downgrading. I flawlessly used DingleBerry 3.02 to get HuluBerry.
I'd love to check out the new predictive typing and whatever else they've changed, but I don't want to lose root.
If it wasn't for the additional functionality in the new beta, I would have suspected the timing as a fix for DB 3.02.01-19-12 12:01 AMLike 0 - Again, I don't want to mislead you. The reason I tried to upgrade to 6149 and ended up with 7111 was because I could not find the android market, no where to setup the account, etc.
So maybe I was doing something wrong and that cracked the root....
I downgraded back to 4869 in the meantime (with Dingleberry 3.02) and now I am in the middle of the process to re-root. I got the prompt, I am now Winscp-ing in.
I will post updates01-19-12 12:09 AMLike 0 - I just bought a PB and just upgraded it to 7111; wasn't aware that these new releases are conflicting with the root procedure. I'd be very interested in learning if someone with more experience is having any success with it yet.
Also, has anyone found any good PDF reader apps in the Android market that have worked?01-19-12 12:18 AMLike 0 - Again, I don't want to mislead you. The reason I tried to upgrade to 6149 and ended up with 7111 was because I could not find the android market, no where to setup the account, etc.
So maybe I was doing something wrong and that cracked the root....
I downgraded back to 4869 in the meantime (with Dingleberry 3.02) and now I am in the middle of the process to re-root. I got the prompt, I am now Winscp-ing in.
I will post updates01-19-12 01:15 AMLike 0 - What are you coming from? What is your current status? Can you SSH in? Do you have Android market? Does HuluBerry work? No offense, but "didnt get any errors" doesn't give the full picture.
Last edited by xeju; 01-19-12 at 01:50 AM. Reason: quote accuracy
01-19-12 01:49 AMLike 0 - Downgrade Core OS to 6149 and you'll have root back (no dingle required) with 7111 Android working.
You can't dingle 7111 Core OS at this stage.Last edited by xsacha; 01-19-12 at 04:32 AM.
anon(4181646) likes this.01-19-12 04:28 AMLike 1 - So whats the consensus on this? im running 2.0.0.6 rooted and would love to upgrade but dont want to lose root etc. Would be great if someone could advise a little further.
01-19-12 04:56 AMLike 0 - I am on the dingled version of 4869. When I went back to get to .6.. Blackberry had pulled it. I am stuck on the partial 4869. I really don't want to loose root or Huluberry and it looks like I will loose that if I take the .7.. update. Can someone point me to a way to get back to .6..? Thanks!01-19-12 07:38 AMLike 0
-
Overall, I'm not overly upset, however I would like to have the Google market back and access to Huluberry. XSacha, you mentioned downgrading back to 6149 core. Will DB be updated to reflect a 6149 core vs the 4869 core that's listed?
My question would be why would downgrading and rooting work then returning to 7111, when it didn't work for me now? I was already rooted prior to 7111, but the upgrade must have broke that connection.01-19-12 09:34 AMLike 0 - I figured out what I have done wrong: I used dingleberry 3.0.2 to upgrade from "stock" 1.0.8.6067. Rooting was successfull but android market wasn't there, even after sideloading sys.android.bar and sys.browser.bar but I I'm assuming there is more to it. I have to do a full upgrade to 2.0.6149 to get it all working.
Since I was "caught" by the newest upgrade 2.0.7111 I have no market.
Once I get home from work I will try the "playbook update server" to see if I can get to upgrade to 6149.
It is already confirmed in other threads that 7111 looses root.stesyl likes this.01-19-12 11:31 AMLike 1 - Good morning,
da1, you said, you have root access on ...7111 and come from .6xxx and 4xxx ; how did you get the root access to your PB ?
Tell us more please, because I think your are the only one in this fabulous case.
In my side, after some research yesterday night, Elvis editor give me a possibility to read files withe user access.
"Elvis" qnx editor, it's like Vi or Vim editor for unix system.
This editor is built inside the PB....
I don't know how to use it but it's ok to read files in shh mode on the PB.
A solution for an other hack ?01-20-12 06:10 AMLike 0 - i had root and huluberry working on 6149. lost it after upgrading to 7111, the files in the /tmp folder are gone.
Tried dingle 3.02 on 7111, payload pushed and restored settings, rebooted...but no root.
@da1
We need step by step. Should we downgrade to 4xxx, root, then go straight to 7111 to regain root?01-20-12 08:02 AMLike 0 - i had root and huluberry working on 6149. lost it after upgrading to 7111, the files in the /tmp folder are gone.
Tried dingle 3.02 on 7111, payload pushed and restored settings, rebooted...but no root.
@da1
We need step by step. Should we downgrade to 4xxx, root, then go straight to 7111 to regain root?
you can upgrade to 7111 after DB from 4xxx, but need to use core OS 6149
all other bar can use 711101-20-12 02:31 PMLike 0
- Forum
- BlackBerry PlayBook Forums
- BlackBerry PlayBook OS
I lost root privileges upgrading to 2.0.0.7111
LINK TO POST COPIED TO CLIPBOARD