- CrackBerry Newbie
- 2 Posts
Is Playbook 220.127.116.110 Rootable?
I am sorry if this has already been asked.. I tried a lot finding a similar problem.. but couldn't..
I have a Playbook which I upgraded to OS 18.104.22.1680. And now, I want to root it and install Android Market basically. It would also be nice to know rest of the possibilities after rooting.
The Main Question.
Is Playbook OS 22.214.171.1240 rootable? Do I have to downgrade it first? if yes, then how?
Thanks a lot!
Any help will be appreciated..
- 07-05-2012, 06:55 AM #6
A glimpse of hope?
an explosive content in a small line, because you are the only one
who stands opposite all 'no' sayer allover in this forum.
could you provide slightly more details about the direction its going (Dingleberry 4?)
lets hope the RIM empire is not striking back much quicker than they did
the last time when they became aware of root-subversives
Last edited by Anvil2k12; 07-05-2012 at 01:22 PM. Reason: shbelling
- 07-07-2012, 08:15 AM #8
malwayne66 - no reply for safety reasons?
or did you trip over the first line of
Dingleberry jailbreak where it says
"Dingleberry 4.0 is still being worked on! No ETA but i promise it's coming. Check back for updates! and follow me below on twitter"
mate, that was 3 month ago!
- CrackBerry Abuser
07-10-2012, 08:47 AM #9
- 361 Posts
CWM obviously has no more interest in the PB - his last tweet was probably a couple months ago when he said "Yeah I know - dingleberry"... sounds like damn will they forget about this soon?
I guess it would also be pretty easy to say the Playbook is too big of a challenge for any serious hackers - RIM may have scored on this one - they still lose at the end of the day though - their joke of an ecosystem is stagnant.
Last edited by RicThot; 07-10-2012 at 08:50 AM.
- 07-10-2012, 09:02 AM #10
- CrackBerry User
07-10-2012, 02:13 PM #11
- 74 Posts
A solution would probably be to get a replacement playbook, but make sure it's brand new in the box.
And then follow the guide concerning rooting a brand new playbook.
Dingleberry 4 is possible in the future, but for now there is no easy root for the public.
- 07-11-2012, 08:00 AM #12
main problem as such. its what and where without causing
a fatal outcome.
the following is a guess, but it would explain why RIM
doesn't allow current old OS's to be worked with and
you need external help like cfp to avoid an update (see attach PBguts.jpg):
the whole OS which previously replaced the flashable
content of the NAND only, is now replaced by one which sets
anchor bits within the en-circulated area to zero/close/crc or
whatever. similar to the manipulation on tunnel ions
(field electron emission ) in EEProms e.g. like telephone cards
which become less worth after money spent.
simple - it was some kind of bios flash camouflaged as
update (or can anybody confirm similar 'benefits' on that side?).
I'll try to disassemble several PB-OS and try to tell
the alleged update-disguise, which should be offset-wise
similar to the others from the from the one now which
'deals' somewhere else.
experts here - please tell me whether I am wasting my time
- CrackBerry Newbie
07-12-2012, 08:34 AM #13
- 3 Posts
- 07-12-2012, 09:45 AM #17
is it possible you just battologize what's been spread from RIM
and quoted allover in the web (google it)? that phrase is always
used from companies to calm critical users down...
if not, than there might be hope RIM, Apple and so forth will soon
extinct the bugs in their terms and conditions which forwards
our private security and vulnerability to third parties...
- 07-13-2012, 02:47 PM #18
Kk let me make a statement here, rooting is possible except the reason we can't at this moment is because we do not have the official rim signing app. if we did or found the key it hides or even make a program that does what the rim packager is supposed to do we can easily rot the playbook. the only way we are going to get rim to give us that app is when the playbook runs out of buissness. thus allowing us to do even more with the playbook, maybe even unlock the bootloader so we can install other os simultaneously. Remember the HP tablet running web os or so i remember, when they ran out of buissness they released all the software even a virtual machine of the original os and then finally they rooted and got further into compatability with android and stuff, it's just a matter of time
- CrackBerry Addict
07-13-2012, 11:17 PM #19
- 639 Posts
RIM won't release the signing app as they have a 10" tablet, refreshed 7" tablet, some sorta laptop, and the new phones coming by Q1 2013 (phones and tablets at least)... They are not going bankrupt anytime soon and if, though highly unlikely, BB10 completely flops and they lose obscene amounts of customers then the most you likely will see is a licensing of BB10 to other cell phone manufacturers."Even if you are on the right track, you'll get run over if you just sit there!" -Will Rogers
- CrackBerry Addict
07-16-2012, 11:02 PM #21"Even if you are on the right track, you'll get run over if you just sit there!" -Will Rogers
- 639 Posts
- 07-17-2012, 02:35 AM #22
I'd appreciate xsascha could give us some signs of dingleberry-life (if so)
because he signs his posts still as
Developer of ReQognise (on AppWorld), Dingleberry and other Qt apps.
unfortunately he is not responding to my recent question of old dingleberry either -
Dingleberry stubborn? - so this branch really may have dried out
if these guys from RIM are as clever as Bill Gates was at a time
they should make him an offer he can't refuse
- 07-22-2012, 02:49 AM #23
I believe Sacha mentioned that he knew a way that might work, but that it was highly likely to brick his PlayBook so he wasn't trying it... I could be wrong there.
- CrackBerry Genius
07-22-2012, 05:44 AM #24
- 2,058 Posts
Yeah there's a way to reset it to 1.0.0 but it is too dangerous for me to attempt. I need my Playbook for a project I'm working on.
Basically you need to corrupt the filesystem using cfp so that it believes it has to do a factory refresh. Then it will be at 1.0.0 and will attempt to do an activation again. Then you can use the 'new playbook trick' using resetqnxosregion to get a rooted playbook.
Someone has reported success with this.
There are other methods I could explore if I didn't want to risk bricking.
For example: after upgrade to 10.x on Playbook, can downgrade again?