When I had my Samsung Infuse, I used the "UNBRICK" method to unroot and completely restore the phone back to its original "out of the box" condition.
Is there such a thing for my Razr? I have the stock rom on the phone. It was rooted. When I tried to unroot, using superSu, then do the OTA update, the update fails while trying to install.
What can I do to fix this? I just want ICS and no root.
Thanks in advance!
And.... sorry if this info already exists. I just can't seem to find it.
Dcar777 said:
When I had my Samsung Infuse, I used the "UNBRICK" method to unroot and completely restore the phone back to its original "out of the box" condition.
Is there such a thing for my Razr? I have the stock rom on the phone. It was rooted. When I tried to unroot, using superSu, then do the OTA update, the update fails while trying to install.
What can I do to fix this? I just want ICS and no root.
Thanks in advance!
And.... sorry if this info already exists. I just can't seem to find it.
Click to expand...
Click to collapse
Fastboot .181 using Droid RAZR Utility 1.6. Then take the OTA to ICS. #
Sent from my DROID SPYDER
Try using this: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
fr0w said:
Try using this: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
Click to expand...
Click to collapse
He doesn't want a way to keep root, he's asking why the OTA fails. Besides, keeping root doesn't matter, there are root exploits for 4.0.4.
SafeStrap Recovery installed?
Do you have SafeStrap installed? I had a similar problem with the OTA update failing, but I didn't bother to unroot. When I uninstalled SafeStrap recovery, the updated worked perfectly. (Still broke my root, though.) Then all you need to do is re-root (this method should work from pedrotorresfilho), and you should be good to go. Let me know if this was helpful at all.
Leviathan26 said:
Fastboot .181 using Droid RAZR Utility 1.6. Then take the OTA to ICS. #
Sent from my DROID SPYDER
Click to expand...
Click to collapse
This worked! When I tried it the first time it failed. I had to wipe cache and then it worked. Thanks!
One last question, Now, when I power phone down and turn back on,it ALWAYS goes into AP Fastboot mode.
I have to holf vol+ and vol- and press power to turn off, do it again to turn on and then select normal boot in order to turn the phone back on. Why? Why does it not just boot up normally when I turn it back on? Is this droid utility lingering in my hpone now? Will this effect later OTA updates? IF i decide to root this new ICS I downloaded, will I have issues?
Related
I just picked up a X2 off of CL and it seems to have a partial root (if there is such a thing). It has SuperUser on it but no CWM recovery installed. Where do I go from here? I have tried to do a factory reset and the SU remains there. I would like to get the thing fully rooted with some custom recovery/ROM awesomeness....
There is no such thing. If it has SU then its probably rooted. Look for an app that says system recovery. If you wiped then it probably gone. It needs to be reinstalled. It installs like an APK with options to install recovery and a recovery mode and a charge mode. The recovery can be found in DEV section with any of the rooting guides.
Mandelbrot.Benoit said:
There is no such thing. If it has SU then its probably rooted. Look for an app that says system recovery. If you wiped then it probably gone. It needs to be reinstalled. It installs like an APK with options to install recovery and a recovery mode and a charge mode. The recovery can be found in DEV section with any of the rooting guides.
Click to expand...
Click to collapse
Superuser gets killed if your phone got an over the air (OTA) update from Verizon. Easy to fix, all you need to do is SBF to 2.3.3 or 2.3.4 and use the one click root method to root then install boot strap recovery if you want to install a custom ROM.
Search the development X2 forum for the SBF Tutorial. It will explain step by step instructions.
L2_n19h7m4r3 said:
Superuser gets killed if your phone got an over the air (OTA) update from Verizon. Easy to fix, all you need to do is SBF to 2.3.3 or 2.3.4 and use the one click root method to root then install boot strap recovery if you want to install a custom ROM.
Search the development X2 forum for the SBF Tutorial. It will explain step by step instructions.
Click to expand...
Click to collapse
He speaks the truth. Worked for me
Recommend starting on SBF 2.3.4 and use the OneClickRoot to root it afterwards. Just make sure that after flashing stock 2.3.4 to set the phone from Charge Only to PC Sync and allow debugging (Settings -> Applications -> Development) so OneClick can see your phone.
Recommend installing System Recovery afterwards. System Recovery lets you boot into a CWM recovery mode, and of course, flash unsigned .zips (ROMS) Note: Just a heads up, you can't boot into the tweaked System Recovery unless the USB is plugged in the AC outlet or a car charger. I found that... as a minor speed bumping when getting it to work.
If you are unsure how to use the SBF with RSDLite let us know and we will help you run through that.
SBF 2.3.3 then one click root
I would start off with the SBF for 2.3.3 and then the one click root. The leaked version of 2.3.4 has battery issues still as far as I know.
There is an official 2.3.4, not just the "leaked" Soak Test version.
AtLemacks said:
There is an official 2.3.4, not just the "leaked" Soak Test version.
Click to expand...
Click to collapse
now that you bring that up, let's say the OTA has a few minor fixes. Would the people who SBF'd get the latest version via the OTA?
AtLemacks said:
There is an official 2.3.4, not just the "leaked" Soak Test version.
Click to expand...
Click to collapse
That is good to know I SBF to the leaked version and then ended up flashing back to 2.3.3. I must of missed the oficcial 2.3.4 sbf. Can you let me know what link that was in? I would like to try the new eclipse at some time soon and would like to have the official sbf and not the leaked version. Thanks for the correction.
Thanks everyone!
Off to SBF something!
Travisdroidx2 said:
That is good to know I SBF to the leaked version and then ended up flashing back to 2.3.3. I must of missed the oficcial 2.3.4 sbf. Can you let me know what link that was in? I would like to try the new eclipse at some time soon and would like to have the official sbf and not the leaked version. Thanks for the correction.
Click to expand...
Click to collapse
+1 Bc EVERY link I have found seems to be expired...
Sent from my DROID X2 using XDA App
huskerstylee said:
+1 Bc EVERY link I have found seems to be expired...
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Let me know if you cant find it, I can upload it for you.
Sent from my DROID X2
Running Eclipse 1.0
RagingCain said:
Let me know if you cant find it, I can upload it for you.
Sent from my DROID X2
Running Eclipse 1.0
Click to expand...
Click to collapse
I would really appreciate it boss
Sent from my DROID X2 using XDA App
huskerstylee said:
I would really appreciate it boss
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
According to them this is the unofficial "official" SBF release of unmodified 2.3.4.
http://www.droid-life.com/2011/10/01/droidx2-2-3-4-sbf-released-guess-we-know-what-the-soak-test-is/
This is the XDA Forums Source:
http://forum.xda-developers.com/showthread.php?t=1284679
Ok... just SBF'd my X2 and did a factory reset in the recovery (to be able to activate). SU is still there.
eth3rton said:
Ok... just SBF'd my X2 and did a factory reset in the recovery (to be able to activate). SU is still there.
Click to expand...
Click to collapse
Try one more factory reset after you flash. That has happened to me before but goes away after the second factory reset.
I have the app to help keep my root by temporarily unrooting but I also have bootstrap installed and everything set up so that my Razr will boot into recovery every time it starts up/reboots as a safety net. My question is: Will I have to uninstall Bootstrap in order to successfully update via OTA? Someone recommended it on a thread here but after I did some googling I couldn't find anything confirming or denying the need to uninstall your custom recovery.
AliceInUnderland said:
I have the app to help keep my root by temporarily unrooting but I also have bootstrap installed and everything set up so that my Razr will boot into recovery every time it starts up/reboots as a safety net. My question is: Will I have to uninstall Bootstrap in order to successfully update via OTA? Someone recommended it on a thread here but after I did some googling I couldn't find anything confirming or denying the need to uninstall your custom recovery.
Click to expand...
Click to collapse
Im going stock and hoping it gets rooted and a CWM flashable zip is made.
My guess would be yes, remove bootstrap. You will be better off using rsd to get back to stock.
Sent from my DROID RAZR using XDA
sammyd253 said:
My guess would be yes, remove bootstrap. You will be better off using rsd to get back to stock.
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
I'm already on the stock ROM, I just have a custom recovery and I'm rooted.
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
SoCoolAZ said:
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
Click to expand...
Click to collapse
If you want to apply the ota, grab ota rootkeeper from the market. Open the app, save root, then go to town updating. No need to unroot. Once updated, open the app again and hit restore root, as the ota will remove root.
That's pretty much it. As it stands that is the only way to get root on the latest ota so if for some reason you run into an issue and lose root, you will have to sbf back to 2.3.4.
Sent from my MB870 using xda premium
SoCoolAZ said:
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
Click to expand...
Click to collapse
I'm sorry but are you on pre 2.3.4 on your X2? If so why haven't you had to update before now? Just curious.
SoCoolAZ said:
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
Click to expand...
Click to collapse
I made this thread just for cases like this.
Although if you search (when working of course lol) there's tons of info on this I just compiled it together
http://forum.xda-developers.com/showthread.php?t=1757854
Sent from my DROID X2 using Tapatalk 2
So i am trying to run the update to no success. It goes into shut fown mode, comes back to a box with an arrow pointing to the android guy, it gets 20% or so and the box turns to a explanation point. X2 reboots to home screen, update failed. Tried both plugged to power and unplugged to same affect.
Cant find pete root tools but installed rom manager and rootkeeper. My root is intact and stable...i just cant get it to frickin' update from 2.3.3 .
Sent from my DROID X2 using xda app-developers app
SoCoolAZ said:
So i am trying to run the update to no success. It goes into shut fown mode, comes back to a box with an arrow pointing to the android guy, it gets 20% or so and the box turns to a explanation point. X2 reboots to home screen, update failed. Tried both plugged to power and unplugged to same affect.
Cant find pete root tools but installed rom manager and rootkeeper. My root is intact and stable...i just cant get it to frickin' update from 2.3.3 .
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
Have you modified the system
Sent from my ThunderBolt using Tapatalk 2
SoCoolAZ said:
So i am trying to run the update to no success. It goes into shut fown mode, comes back to a box with an arrow pointing to the android guy, it gets 20% or so and the box turns to a explanation point. X2 reboots to home screen, update failed. Tried both plugged to power and unplugged to same affect.
Cant find pete root tools but installed rom manager and rootkeeper. My root is intact and stable...i just cant get it to frickin' update from 2.3.3 .
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
For updating to the latest release you can't have changed any of the system files (ie frozen), and if you are rooted it's best to do a temp unroot (with a Voodoo backup of course) and make sure you boot into the Stock Recovery and attempt to flash that way. Should go without saying that you have to be on the stock rom.
GL!
SlimMan said:
For updating to the latest release you can't have changed any of the system files (ie frozen), and if you are rooted it's best to do a temp unroot (with a Voodoo backup of course) and make sure you boot into the Stock Recovery and attempt to flash that way. Should go without saying that you have to be on the stock rom.
GL!
Click to expand...
Click to collapse
Slim, i have ignored the OTA upgrade notification for 9 months. If its not broken, dont fix it theory. I had tweaked the phone with root only so that i could barnacle my tablet to the internet. Since i just saw how easily i recovered my phone back to my last nandroid backup, i figured i would try to upgrade and ROM this thing as it seems ive gotten it this far. Can someone link me to an easy to follow, step by step on "flashing stock recovery mode"? I can unfreeze programs with titanium backup and then unroot with ota rootkeeper. Just lrt me know how to stock recover, ie: phone plugged in? Unzipped file locations? External or internal sd card? I appreciate the help.
if update is failing
try unrooting with rootkeeper (keeps backup) like slimman suggested
if that doesn't work it's time to flash 2.3.4 sbf
http://forum.xda-developers.com/showthread.php?t=1317707
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
a little surprised, that you made it 9 months and phone didn't try to install overnight after several notices
I know that has happened with other moto phones like D2 and D2G
Guys root has nothing to do with not being able to receive ota.
Nothing.
Lol
It sounds to me like you need to sbf back 2.3.4
Make sure your phone is fully charged.
Do you have usb debugging enabled?
Forget about guessing games, sbf back to 2.3.4.
Root your phone via Pete's. Do not use zerg.
Install recovery
Install superuser etc. If you feel the need but Pete's su. Works fine.
Install voodoo rootkeeper.
Make the back up.
Again with these phones root has NOTHING to do with receiving or not receiving ota.
If your ota is borked there's somthing else going on. You must have removed (bad idea) or froze something
Just sbf and follow my instructions again.
Hope that helps.
As I said in my guide, all updates were done with root, and I went from2.3.3>2.3.4>2.3.5
All rooted each time all retained root via rootkeeper.
Hope that helps
Sent from my DROID X2 using Tapatalk 2
temp unroot hurts nothing, and some reported success, after failed attempts to update
Sent from my DROID2 using xda premium
sd_shadow said:
temp unroot hurts nothing, and some reported success, after failed attempts to update
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Never said it did just saying it doesn't have anything to do with not receiving updates.
What ever works right?
sd_shadow said:
temp unroot hurts nothing, and some reported success, after failed attempts to update
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
I have been there, not sure why but it has happen.
freakboy13 said:
Never said it did just saying it doesn't have anything to do with not receiving updates.
What ever works right?
Click to expand...
Click to collapse
Agree, was just trying to cover all bases but if the are gonna SBF any ways then your right, just do it and go with it.
Id just sbf and be done with it personally, i dont like otas
cm7dx2
sd_shadow said:
[/COLOR]a little surprised, that you made it 9 months and phone didn't try to install overnight after several notices
I know that has happened with other moto phones like D2 and D2G
Click to expand...
Click to collapse
LOL - I ignored it almost daily for the first three months. Okay, unfroze everything and unrooted...still can't get the update. SBF time...I'll keep ya'all posted.
My point is that, the update, can install it's self
At least that is what other user have claimed of other moto phones
Sent from my DROID2 using xda app-developers app
Ok where do i start? Gonna try and be brief as possible. So today i was gonna update to ICS ota. I uninstalled safestrap first cause i was gonna reinstall the ics version using the Razr Utility ver. 1.7, as well as use to reroot. After i uninstalled the safestrap app i tried to install the ota i just took. Well it failed. I rebooted my phone and the Safestrap (SS) splash screen still popped up. I tried to reinstall the SS app using Razr Utility 1.6 (that i used to install in the first place) and it failed saying "failed to find path" or something similar. Weird caused it worked to install before. So now i cant get the SS app back to try and uninstall the actual recovery. Make sense? I was gonna try and load a Nandroid, but it was made back when i was still on .173. Can i go back to .173 and then reupdate to .181 and try again? Can anyone help me sort this out? I know its a lot to swallow Thanks in advance to anyone willing.
Edit: I am a moron. Trying to install Safestrap failed because I temp. unrooted with Voodoo before trying the update and forgot to allow root again. Thought I was past the noob stage.
Sent from my GT-P3113 using xda app-developers app
Hey guys,
I was looking forward to trying out the new JB Roms for my razr maxx and needed to update safestrap, so I went into safestrap and disabled safe system and went to restore and lo and behold, it can't find my backup. I checked the SD card and it's sitting there under "clockworkmod/backup" but safestrap just keeps telling me it can't find it. I copied over that folder to sd-ext and still no luck. Does anyone have any ideas?
Finalchrono said:
Hey guys,
I was looking forward to trying out the new JB Roms for my razr maxx and needed to update safestrap, so I went into safestrap and disabled safe system and went to restore and lo and behold, it can't find my backup. I checked the SD card and it's sitting there under "clockworkmod/backup" but safestrap just keeps telling me it can't find it. I copied over that folder to sd-ext and still no luck. Does anyone have any ideas?
Click to expand...
Click to collapse
I take it you are coming from SS 2? It is possible that the backups arent compatible. Also its possible that the safestrap folders on your sdcard and sdcard-ext are messing with the new version of SS3.
If it were me I would just remove it all and start from scratch. If something happens and you mess SS up, I would use matts droidrzr utility and fastboot back to 211, then install the newest safestrap from hashcode's website. (How to safestrap)
If you need help with the utility I can help you
That's the problem though. I haven't been able to upgrade to SS 3.x because I can't access my stock rom from SS 2 because it won't find the backup. It's the same backup I made when I installed SS 2 so it really makes no sense. If I try and access my stock rom without doing a restore, it obviously just sits at the boot animation forever.
So I guess no one has a clue? If no one can offer any sort of idea, does anyone know where I can find a SS 2.11 backup of the razr maxx ICS rom?
Finalchrono said:
So I guess no one has a clue? If no one can offer any sort of idea, does anyone know where I can find a SS 2.11 backup of the razr maxx ICS rom?
Click to expand...
Click to collapse
Someone correct me if I am wrong, but SS started using TWRP for backup at some point in place of CWM.
I would suggest using the utility to go to .211 stock. Then root and upgrade to jb.
doing so lowers the risk of loosing root when you upgrade.
And yes since he moved to 3.0 the recovery is based on TWRP since mid-October
Sent from my JellyBeaned Droid RAZR Maxx
klabit87 said:
I would suggest using the utility to go to .211 stock. Then root, then protect root with Voodoo OTA Rootkeeper, and upgrade to jb.
doing so lowers the risk of loosing root when you upgrade.
And yes since he moved to 3.0 the recovery is based on TWRP since mid-October
Sent from my JellyBeaned Droid RAZR Maxx
Click to expand...
Click to collapse
FTFY
85gallon said:
FTFY
Click to expand...
Click to collapse
Thanks. I guess I assumed he would read the instructions thoroughly when he downloaded the JB update.zip.
I guess I didn't explain clear enough. I am still on an ICS rom. I have NOT upgraded to JB at all. I have NOT upgraded to SS v3 at all. I am still on SS v2.11 and my backup was from when I first installed SS v2.11. I am trying to get back to my stock rom by disabling safe system and restoring the backup that I made. I can't do this because it keeps telling me that it can't find the backup when it is clearly in clockworkmod/backup.
Anyway, so using the utility to go back should be able to fix this issue?
Finalchrono said:
I guess I didn't explain clear enough. I am still on an ICS rom. I have NOT upgraded to JB at all. I have NOT upgraded to SS v3 at all. I am still on SS v2.11 and my backup was from when I first installed SS v2.11. I am trying to get back to my stock rom by disabling safe system and restoring the backup that I made. I can't do this because it keeps telling me that it can't find the backup when it is clearly in clockworkmod/backup.
Anyway, so using the utility to go back should be able to fix this issue?
Click to expand...
Click to collapse
yes the utility will fix it for you.
when i wanted to go back to the nonsafe side(stock side) I would only have to disable safe system and then reboot.
does that not work for you? ss2 doesnt support flashing to the nonsafe side, therefor no restoring cwm backups to the nonsafe side i believe.
Unfortunately no, it just sits at the boot animation screen. I figured it might have been taking a long time, but I let it sit for 30 minutes and nothing changed.
Finalchrono said:
Unfortunately no, it just sits at the boot animation screen. I figured it might have been taking a long time, but I let it sit for 30 minutes and nothing changed.
Click to expand...
Click to collapse
Looks like you don't have a choice.
Use the utility to fastboot to.211.
Root, then use the utility to install voodoo root keeper so you can have root when you update to jb.
Read spc hicks guide in the development section.
Sorry can't post link right now.
Sent from my JellyBeaned Droid RAZR Maxx
Hrm, just a heads up. Apparently 75% battery is not enough to use option 1 on the Razr Utility. Phone is now stuck in invalid flash mode. Ah well, working towards fixing this now.
Finalchrono said:
Hrm, just a heads up. Apparently 75% battery is not enough to use option 1 on the Razr Utility. Phone is now stuck in invalid flash mode. Ah well, working towards fixing this now.
Click to expand...
Click to collapse
75% is plenty. You have something else going on. How long did it take?
Ah, I think it was just a faulty cord. I got it back to regular fastboot and ran option 1 again and it's working fine now.