3711 replies to this topic

[SamuriHL]

You have quite the stubborn phone. Try this... Go into voodoo and delete the protected backup, reboot, protect root again, then try temp unroot again.

Sent from my Xoom using Tapatalk HD

[matjmonk]

You have quite the stubborn phone. Try this... Go into voodoo and delete the protected backup, reboot, protect root again, then try temp unroot again.

Sent from my Xoom using Tapatalk HD

 

I'll give this a shot in a bit, have to take the GF out for breakfast before she get PO'd!

[matjmonk]

You have quite the stubborn phone. Try this... Go into voodoo and delete the protected backup, reboot, protect root again, then try temp unroot again.

Sent from my Xoom using Tapatalk HD

 

 

I'll give this a shot in a bit, have to take the GF out for breakfast before she get PO'd!

 

 

I tried this and unfortunately it failed again leaving me un-rooted. So, I guess I will try uninstalling Superuser and Voodoo and reroot via HoB and if that gives me the same result I'll uninstall both things again and reroot using MotoFail and download Voodoo to see if that makes a difference.

[SamuriHL]

You can try replacing the Superuser.apk and su binary in the HoB root directory with Koush's and see if that works any better.

 

If you grab the motochopper root exploit and copy Superuser.apk and su from that zip file and drop them into the root dir of the HoB, overwriting the existing Superuser.apk and su binary, then try rooting again and see if you have any better luck. 

[markwebb]

I was one of the lucky ones who kept root, thanks to your warnings to update BOTH su binaries and Voodoo before installing.

 

Now, not to hijack this thread, many apps wont update in Google Play. I get network error code both on wifi and 4G. If I uninstall the apps which didn't update, I can't reinstall them back: network error codes. I even installed the new Google Play issued yesterday. Don't know if others are having this issue.

 

But back to rooting: I do hope this gets solved as it may appear I will have to FXZ and possibly lose root if these app update issues aren't solved. Otherwise, this may force many of us to trade in phones sooner than later..and then I/we would lose unlimited data plans.

[SamuriHL]

Don't FXZ.  Try an FDR first.  That will clean out your data partition and leave the system partition in tact.  (I.E. root).  You'll have to reinstall your apps, but, it should make for a much cleaner experience anyway.

[markwebb]

Don't FXZ.  Try an FDR first.  That will clean out your data partition and leave the system partition in tact.  (I.E. root).  You'll have to reinstall your apps, but, it should make for a much cleaner experience anyway.

I also have SS installed with ROMS: should I delete those and reinstall as well? Funny some of the ROMS will update the Play store but AOKP won't. 

[SamuriHL]

I don't know enough about SS to be able to give you a definitive answer...You're going to erase the data partition when you FDR, so, you'll lose the safestrap app.  I have no idea if it hooks anything on data or not.  It might be safest to uninstall safestrap recovery before doing the FDR, then when you reinstall SS, you can reinstall safestrap recovery and hopefully boot all your roms.  But this is not an area I know much about so take my advice with a grain of salt.

[altspeed]

These are pretty much the same experiences I had with running the root exploit via HoB .....tried it 3 times with the same result. Verify root good, voodoo says protected, temp unroot with voodoo, root's gone and won't restore. X3. Uninstalled voodoo on 4th try, ran standalone razr's edge verified root good, installed supersu and voodoo, updated binary for supersu pro and set survival mode and backed it up with voodoo, temp unrooted checked root gone, rerooted verified root good, temp unrooted ran JB update, rerooted in voodoo, checked root good, verified supersu survival....all good. The keep data HoB fixed the radio bug that I created when I "fixed" the unbroken radio, that sure does seem to be a mad robust CDMA radio though.

Sent from my DROID RAZR using Tapatalk 2

[SamuriHL]

But people are having the same experience with doing the method that ultimately worked for you as what others are having with the HoB method, so, I have no idea.  The messed up part is that I literally do every step that voodoo does to create the su backup.  I'm at a point now where I may just put it in a /system/usr/HoB-needs-root folder as extra insurance and have people do it manually again.  In fact, I think I will do that.

[SamuriHL]

10.0 WINDOWS RELEASE

 

o) Removed many functions that were not strictly necessary

o) Removed ability to auto-rename the webtop file...you can manually change vendor.img to vendor.img.disabled if you want to retain this functionality.  I just don't do it for you anymore as too many people had problems as a result of doing this.  I will no longer help webtop related issues.

o) Removed the ability of root to create a voodoo enabled backup.  WARNING: If you want to retain root through an OTA update, you MUST use voodoo to create the protected backup!

o) Create, instead, a hob protected backup.  Consider this a "root of last resort"...you'll always have a su-backup in /system/usr/hob-needs-root now.  

 

 

So we still push voodoo ota rootkeeper for you, but, I do *NOT* try to create a protected backup that voodoo can use.  This has not been working for the majority of people.  However, I do create a hob su backup....just in case.  If, as a last resort, you completely fuck up and forget to protect with voodoo, or the voodoo one doesn't work, you can use the hob protected backup with adb to restore root manually.  Good enough.

[kc69]

The cdtbin trick fail led for me. Prolly wasn't doing it right. Seems it didn't want to stick. Every time I rezipped it would stubbornly poof back to the 22 version. Gave up, out of playtime. Back to liquid.

[SamuriHL]

I didn't post about that here for a reason.  

[kc69]

Sorry dude, just an update. When I get off this tractor I'll try again and pm you. I have a hard time pming on my phone.

[SamuriHL]

Yea, that'd be better.  I may or may not be around.  I have stuff I need to get done today.

[kc69]

Ya me too. Why I'm on the tractor.

[markwebb]

Don't FXZ.  Try an FDR first.  That will clean out your data partition and leave the system partition in tact.  (I.E. root).  You'll have to reinstall your apps, but, it should make for a much cleaner experience anyway.

Worked...and kept root. Thanks!

[twinkyz1979]

Just thought i would put this out there. With all the problems I am seeing people post on the Motorola forums about this update I have a feeling this may not be the final 1 for our phones.  Keep in mind this is my own opinion and not based on anything other than my own observations and feelings.

[SamuriHL]

Here's another observation for you.  The RAZR ICS build was a LOT worse than this build is for us and it stayed out there for 6 months.  Their JB build is crap, as well.  They aren't going to fix any OMAP4 phones.  They're done.

[shawner47]

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