Rooting Update

**xsacha** · 04-02-2012, 11:12 PM

Hey guys,
I have not managed to downgrade my Playbook below 2.0.0.7111 and so have not been able to root. The newest builds run almost everything in user-space so that it is practically impossible (without hardware mods) to root the device without first downgrading the firmware.
There may be a way to downgrade the firmware through RIM's official tools such as cfp but it isn't viable for any sort of release (I can't post it on this forum, for example).

While I always knew RIM could patch this by preventing downgrades, I unfortunately never expected this to happen and had already written Dingleberry 4.0 for the official OS 2.0 release assuming downgrades were possible.

I realise there is a few people who are still rooted because they never upgraded. I will not be able to support you with future updates due to my non-rooted device. However, I can release the source code to Dingleberry (as I do with all my projects). As the code was entirely written by me there should be no issues in releasing this source. It may even help some people learn Qt/QtQuick. It could also be used as the basis of a BDM replacement application.

Thanks for the adventure, 'til next time,
- Sacha

**sushistew** · 04-03-2012, 12:18 AM

wow thats crazy news, thanks for the update. hope to hear of any other news and developments you may have or hear of yourself.

**mkaa00x** · 04-03-2012, 01:19 AM

Yeah tnx I'm stuck with you but hey awesome job!!! Also Good Luck on Joining the roots
MohammadKaa00x

**qwang** · 04-03-2012, 01:23 AM

I'm sorry to hear that.

I don't know if this will work on 7971 OS.
1.Bulid a local update server on your computer.
2.Drain your battery,then connect the playbook to your computer,and choose update
3.Choose a firmware to update.

this works on the 6149

**Bratag** · 04-03-2012, 01:30 AM

What I find interesting is while BB is locking down root access almost every android manufacturer is opening the bootloader. My playbook is really just a toy I got for ha ha's but it had such potential and RIM really screwed the pooch (again surprise) on this.

**mkaa00x** · 04-03-2012, 01:35 AM

Yeah but how can you get the OS to go towards that server it will take more than just a computer but also possibly slot of money because this should be Online right??? And then change server settings on play book then drain battery... We finally get there... Oh wait how will we do it when we have the new block name Fingerprint.dat yeah it really confusing but only one known way through... Hey xsacha maybe we can extract that data needed for root from a high priority app in bar file format and then use that in db and possibly obtain root can that work or am I missing something.

**qwang** · 04-03-2012, 02:08 AM

Originally Posted by Mkaa00x

Yeah but how can you get the OS to go towards that server it will take more than just a computer but also possibly slot of money because this should be Online right??? And then change server settings on play book then drain battery... We finally get there... Oh wait how will we do it when we have the new block name Fingerprint.dat yeah it really confusing but only one known way through... Hey xsacha maybe we can extract that data needed for root from a high priority app in bar file format and then use that in db and possibly obtain root can that work or am I missing something.

actually,it's much more easier than you think it is,everything can be done on one computer ,maybe even without a internet connection.

And like I said,this way is already working on OS under 6149.I just don't know if it will work on the 7971,cause so far,I haven't met the Fingerprint stuff.

**xsacha** · 04-03-2012, 02:37 AM

Loading the old firmware on to the device is not the hard part. You can do this using the traditional means.
The problem is that the device will reject anything older than 2.0.0.7111 from booting.

This means even if your Playbook said there was an official update from RIM for 2.0.0.4869 tomorrow, it would not work. Actually, without RIM providing a version that is 7111 or later, your Playbook would be perm. bricked.
This flag is delivered when you update to 7971.

**borceg** · 04-03-2012, 08:04 AM

Originally Posted by xsacha

There may be a way to downgrade the firmware through RIM's official tools such as cfp but it isn't viable for any sort of release (I can't post it on this forum, for example).

Well, downgrade with RIM's official tools (loader, or whatever they use) is possible. You can post release on xda-developers for example, or any other dev forum over the internet.

And PlayBook without root or any level of access higher than user1000 or devuser is simply not interesting/worthless (sorry about this, but it's true

)

**kbz1960** · 04-03-2012, 08:13 AM

Originally Posted by borceg

Well, downgrade with RIM's official tools (loader, or whatever they use) is possible. You can post release on xda-developers for example, or any other dev forum over the internet.

And PlayBook without root or any level of access higher than user1000 or devuser is simply not interesting/worthless (sorry about this, but it's true

)

For those who only purchased it to turn it into an android.

**balding1** · 04-03-2012, 09:15 AM

Thanks Xsacha for the update and all your hard work.
It's been a fun ride how Dingle went from a step by step to "press to continue"
You made rooting idi?t proof for peeps like me.
Enjoy your new endeavors.
Keep out of trouble.

**ayekon** · 04-03-2012, 09:37 AM

It was as if millions of voices suddenly cried out in terror and were suddenly silenced

**Zero-K** · 04-03-2012, 12:23 PM

Aww. That really sucks. Really wish I wouldn't have jumped so fast at updating to 2.0 when I got my playbook. I might have stood a chance to having it rooted with the marketplace.

Thanks for all your hard work xSacha, and hopefully we'll see your work on a future update

**betterwang** · 04-03-2012, 03:10 PM

This basically announced dead of PB.
With its crappy app store, no way to compete with other pads.
It is like a touchpad stuck with webos.
I have to agree that PB has a better hardware design than TP,
and also a good build of the base OS.
But the environment on top of that sux.

**404error** · 04-03-2012, 03:19 PM

thanks for all the work you have done wish there was a one click apk->bak file no needed signed just to load and test apps fast could that be done ..

**SifJar** · 04-03-2012, 03:57 PM

Originally Posted by 404error

thanks for all the work you have done wish there was a one click apk->bak file no needed signed just to load and test apps fast could that be done ..

If you install a debug token, you don't need to sign BARs to install them. But it is easier to just get the signing certificates once and setup a tool like BBH Tool, and once it is setup correctly it is pretty much one click (well, a couple of clicks - you have to get to the right part of the tool and browse for the file, then click convert) to get the app converted, signed and installed on the PB.

EDIT: What would be REALLY great would be a way to install APKs directly into the Android VM on the device, without needing to convert or sideload via PC.

**mkaa00x** · 04-03-2012, 08:26 PM

Oh wow... sigh plus Xsacha why dont we just find a way to trick the OS into thinking it's upgrading???!!!

**mkaa00x** · 04-03-2012, 08:27 PM

Imma mist themeing for nao it's a metter of time before even rooting master xsacha's out and in root again

**po8pimp** · 04-03-2012, 08:28 PM

What about changing the "update" name to reflect a number higher than the official os2 number. You might have to go through and change the files to reflect the new number as well. Basically trick the version check process. This should get you backwards, then forwards would be the issue at that point.

**mkaa00x** · 04-03-2012, 10:41 PM

yeah oh so it's ab it ahrder i see why not just trick the pb by not allowing that checker to load?

**xsacha** · 04-04-2012, 12:44 AM

Originally Posted by po8pimp

What about changing the "update" name to reflect a number higher than the official os2 number.

The version number is in the firmware update. It's signed by a RIM signature. You can't modify signed files without re-signing.
I mean, obviously, why not just change 7971 firmware if that were possible rather than bothering with a downgrade.

Originally Posted by Mkaa00x

yeah oh so it's ab it ahrder i see why not just trick the pb by not allowing that checker to load?

'Checker' is on the PB. We can't modify anything on the PB.

**papped** · 04-04-2012, 03:45 AM

Originally Posted by SifJar

EDIT: What would be REALLY great would be a way to install APKs directly into the Android VM on the device, without needing to convert or sideload via PC.

That probably isn't possible, because their Dalvik VM port likely isn't exactly the same as the one on android.

**Magnesus** · 04-04-2012, 05:05 AM

Has anyone tried opening the device to check if the SSD is soldered (if not, we could take it out and just write whatever we want to it)? I would be willing to open it, but not yet, maybe in a month or two, I have to sleep on it.
edit: I just checked some photos and it looks to be soldered.

http://www.ifixit.com/Teardown/Black...eardown/5265/1

**mr_c** · 04-04-2012, 07:13 AM

So we cant get usb otg either if on 7911?

**SifJar** · 04-04-2012, 10:15 AM

Originally Posted by papped

That probably isn't possible, because their Dalvik VM port likely isn't exactly the same as the one on android.

I didn't say it was possible, just that it'd be great

But anyway, I'd say it would be, because in the beta versions of the OS, you could install Market and then install apps directly from there on the device itself, so I see no reason why it wouldn't be possible.