3711 replies to this topic

[twinkyz1979]

so far so good on root using Superuser OTA survival.

[johnlgalt]

Yeah, if I had thought about it I would have delayed taking the update - but I specifically wanted to see if VooDoo played nicely with Kush's superuser and su binary so I took the plunge.

 

Upside-  it worked for me and I am rooted on JB.

 

Downside - I can't revert to test other scenarios now.  Even if Crobs were to come in here and say otherwise.

[SamuriHL]

And it doesn't help that our devoted leader lost root in the initial process........

 

Yea, sucks to be me.  See what I get for rushing in head first?  I know better.  What a dumbass.  

[johnlgalt]

You took one for the team, just say it like that.  

[SamuriHL]

Yeah, if I had thought about it I would have delayed taking the update - but I specifically wanted to see if VooDoo played nicely with Kush's superuser and su binary so I took the plunge.

 

Upside-  it worked for me and I am rooted on JB.

 

Downside - I can't revert to test other scenarios now.  Even if Crobs were to come in here and say otherwise.

 

LMAO!

[johnlgalt]

Thought you'd like that

[twinkyz1979]

Downside - I can't revert to test other scenarios now.  Even if Crobs were to come in here and say otherwise.

OMG no you didn't! LMAO

[ReservedName]

lol some kind of inside joke i'm guessing

[johnlgalt]

Oh hell yes I did.  I took one for the team that time to prove that you could not revert from ICS .235 to GB.

 

Luckily matt posted a method (I think that was either his own creation, or else from timmy's suggestions) that allowed my phone to revert to a semi-bricked state with the updated security so I could then sideload the update onto my phone and get it back in a working manner.

 

In fact, I had hoped the same method could be used to put su / su backup on the phone and then sideload the OTA so that a person could then be JB with a working su backup that culd be restored in VooDoo, but no can do.

[SamuriHL]

A very old inside joke going back to the 235 ICS update.

[SamuriHL]

That method (the unstick method) is the basis for how the House of Bionic update and reinstall functions work.

[twinkyz1979]

lol some kind of inside joke i'm guessing

You just had to be around back in the day to understand the headache known as CROBS.

[johnlgalt]

lol some kind of inside joke i'm guessing

 

Either back here, or the old Hive forums, a user who has some respect at XDA posted that my trials in trying to revert .235 to GB were unfounded b/c I could just simply install the old .905 systems over the current .235 / .238 leak and I'd have a working GB instead of having a semi bricked phone when trying to FXZ back to .905/.092 from .235.

 

It's now a recurring joke b/c he argued incessantly with Sam, myself, and a few others that were were wrong and that you could, indeed revert to GB from ICS the entire time when I proved that there was no full reversion once you went to .235 or higher.

[altspeed]

Just like the moron who was posting "you totally can go back from the 22 to the 246' that spurred my "you absolutely cannot" post on XDA

Sent from my DROID RAZR using Tapatalk 2

[SamuriHL]

You can...so long as you followed the above post.  LMAO

[johnlgalt]

Might have been the same moron lol....

[altspeed]

I mean you totally could if you wanted to totally brick your phone into needing a Timmy, or a Matt, or a Sam, or a JohnL to have to bail you out. But the point I was trying to make to them is you can flash up as many levels as you want, but you can't flash down.

Sent from my DROID RAZR using Tapatalk 2

[altspeed]

Might have been the same moron lol....

Nah. I remember CROBS from when I used to lurk over there. This moron's nick is renonakal, funny how it rhymes with moronical.

Sent from my DROID RAZR using Tapatalk 2

[Aldroid33]

Which is why now that I have this working, and pretty well, I made a backup in safestrap and loaded it in slot 1. I'll keep my stock rooted slot just in case and run on slot 1.
I do realize I may be one of the lucky ones, but I'll be damned if I'm going to screw this up now. Lol

For what it's worth, my method for the update was:

-backup with TiBu
-removed safestrap recovery (did NOT uninstall app)
-full fxz 246 using HoB
-root using HoB
-update su binary (using SuperSU)
-voodoo protected
-download OTA and update (did NOT temp unroot)
-boot JB, check root was kept
-installed TiBu from play store
-restored all apps + app data
-installed safestrap recovery
-boot into ss recovery, backup stock, rooted
-create slot 1
-restore backup to slot1
-run from slot 1 and live happily ever after (I hope)

YMMV and I'll not be responsible of you jack it up.

Sent from my DROID BIONIC using Tapatalk 2

Did pretty much the same, but I put the 22 system in slot 3, so that I can use slot 1 for CM10.1 KEXEC 4.2 builds and other fun things. I then restored my encrypted data from my encrypted Icarus HD nandroid backup and reebooted. Have encypted data now on the 22 JB build in slot 3 with root!D :

Just an update, another one that kept root.  I followed this plan:
***
 
It took some time for this to actually settle in and work, not really sure why.
 
I then installed Safestrap, backed up the stock slot, made a new slot 2 and restored the backup there.  Now running the stock rom in Slot 2 leaving the stock partition alone for now. 
 
Anybody know if most custom roms should run OK with the JB update installed or should we wait for them to be updated (if they ever are)?

The KEXEC 4.2.2 JB builds seem to run fine on 22. I have the CM 10.1 running in slot 1.

Sent from my Xoom using Tapatalk HD

[Aldroid33]

You can...so long as you followed the above post.  LMAO

Sam, I can't help you on the ICS side, but please let me know if I can help with anything on the rooted 22 JB side.

Sent from my Xoom using Tapatalk HD