I rooted my razr using doomlords method and now i cant re-root it. Everything was fine until my gmail wasnt able to reply to messages so i unrooted and now it works again. So when i tried to re-root it, it didnt complete. I originally did i from another computer and that computer broke down on me. The cpu i have now doesnt have internet access. Could that be the reason why it wont root? Do i have to do a system reset? I dont get what im doing wrong. Please help
Sent from my DROID RAZR using xda premium
I think it has something to do with the motorola USB drivers you need to install.
you can check it also with ADB. I think you computer doesn't see your phone.
I had the the same problem when trying to re-root my razr. I went through the batch file lineby line typing it in manually. Here is what I found. It was not installing superuser the 2nd time around. It looked like I was rooted as I could use astro to access the / folder. I installed superuser and it started working.
Give this a try. Hope it helps.
ok so i tried to root my phone again with my work cpu and it still wont root. it reads cannot find the specified file. when i plug the phone to the computer it reads the device because it says all drivers are installed and ready to use. i also installed super user again and still the same thing. my phone still acts like its rooted but it really is not. i un-rooted using ginger un-root. now what? im thinking about just backing up my fone again, doing a reset and then root and then put everything back the way it was. but i dont wanna get rid of my free wifi tether. thanks for you suggestions so far, any other ideas?....
Sent from my DROID RAZR using xda premium
Could you paste the errors message you occured when you try to root please?
Got it! I forgot what post i saw it in but i had the runme file in the same folder with the other programs that were un-zipped. Once i removed it, zoom....... back in business. THANK YOU FELLAS!!!!
Sent from my DROID RAZR using xda premium
Related
After flashing new moto update (the one from this forum, not the one that came over the air) using RSD Lite, it worked. Then I ran through the dock root method to root it, that seemed to work. And then I restarted the phone and get the red moto logo and it will not get past it. Should I reflash this update or do I need to flash something else like stock pudding? I will attempt to flash 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US again and hope that fixes whatever got broke. Any other advice?
Did you try a battery pull and reboot?
Sent from my MB855 using xda premium
Oh yes. The photon battery pull is well documented. It fixes many problems but it's not fixing this one so a reflash of the update is happening now but I have a bad feeling that isn't it.
Okay. It did work. Acted like it wasn't going to but then started to work. Should I redo the dock root and assume I typoed (I'm pretty sure I did not) or should I do photon torpedo? I did dock root before the OTA several weeks ago and it worked fine then.
No you don't have to buy a new photon. Mine did the same thing but I flashed like 4 times before it took. If you can get it into rsd lite to flash something your not bricked. Take the battery out for 5 minutes, put it back in and try to flash it again. It should take and boot up. Also close rsd lite then reopen it.
Sent from my MB855 using xda premium
Try the one click root method. Glad you got out straightened out.
Sent from my MB855 using xda premium
Okay. The phone didn't temp brick last time because of the root method I chose, it was busybox related. I forgot that LCD Density Changer relied on Busybox to set the default system density. The option had already been set to save it as a system default. So whatever was done to install Busybox has to do it again. If someone isn't sure, they can always uninstall any root requiring programs that also use Busybox when going from root to unrooted to rooted.
mikel719 said:
Try the one click root method. Glad you got out straightened out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I agree, try the one click root method as I was having errors and this worked for me.
Edit* glad it all worked out
Hey you all I rooted my phone a while back when I first got it. Now I want to unroot but I have a problem....My phone shows up as not being rooted, but I can't get rid of SU, can anyone help with this?
I can't remember which root method I did, I think it was called the "Forever Root" or something of the sort.
iAaronHD said:
Hey you all I rooted my phone a while back when I first got it. Now I want to unroot but I have a problem....My phone shows up as not being rooted, but I can't get rid of SU, can anyone help with this?
I can't remember which root method I did, I think it was called the "Forever Root" or something of the sort.
Click to expand...
Click to collapse
Look for mattgroffl's RAZR Batman utility
Edit: http://forum.xda-developers.com/showthread.php?t=1486718
in the development section, there is an automated unroot option in there.
Sent from my DROID RAZR using xda premium
Ronin3178 said:
Look for mattgroffl's RAZR Batman utility
Edit: http://forum.xda-developers.com/showthread.php?t=1486718
in the development section, there is an automated unroot option in there.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I tried doing this method but when I did the command prompt said "'moto-fastboot.exe' is not recognized as an internal or external command,
operable program or batch file." The Batman utility is saying the same thing.
EDIT: I got it man thanks! I used it to do a Fastboot Restore to 173. Worked like a charm.
just a thought: what if you did voodoo temp unroot then hard reset the phone?
How to get rid of su
you can re-root the phone and then install root manager, in root manager go to uninstall apps and it will show all installed apps even the system apps, find the su .apk select and reboot, you phone will still be rooted but the su app will be gone. from there you just need to unroot.
I got it guys thanks for the advice!
Very strange thing happening with my Razr. I all of a sudden noticed a number of apps force closing, including motorola and google processes. I have the Verizon CDMA Razr .181, rooted, su, busybox, etc. I have bootstrap installed but never use it, however notice that it is always granted SU permission on boot.
Anyways, when I decided to reboot my phone it booted back up but I started getting calendar alerts from Sunday 5/6 that I had already dismissed, and my gmail was only synced through about 4pm on 5/6, though my system clock and date show correctly the present. What I also noticed is any app I unstainall or setting I change (ie, debug in settings), once I reboot my Razr reverts to the 5/6 setup.
I thought I'd get into Boostrap (which I can't recall ever needing to in the past) so I click "BootStrap Recovery".. I get the "Success!" box, then click "Reboot Recovery". Only problem is it never goes into recovery, but just reboots into the 5/6 state.
I tried to reload the Verizon OTA via RSD Lite, but it always fails on 3/28 with an mbmloader.bin restriction. I tried using Motofail and Matt's Razr Utility to revert back to previous builds, but I get an read-only error on just about all the chmods.
Anyone else seen this or have any suggestions? At this point I'm looking to go back to stock so I can start fresh.
Are you sure you're using the 181 sbf?
Sent from my DROID RAZR using Tapatalk
One trick you might try to get to recovery is reboot, then manually power off before it completely boots (I think vol down and power does that). Next boot should be CWM. I haven't needed to use that method since I had a Bionic but the option shouldn't have changed. Essentially if bootstrap sees that you didn't boot successfully it'll go to recovery.
May want to make sure you have root (test a root app). Try updating su binary in Super User.
Sent from my DROID RAZR using Tapatalk
Yes, I'm positive it is 181. thanks.
joshw0000 said:
One trick you might try to get to recovery is reboot, then manually power off before it completely boots (I think vol down and power does that). Next boot should be CWM. I haven't needed to use that method since I had a Bionic but the option shouldn't have changed. Essentially if bootstrap sees that you didn't boot successfully it'll go to recovery.
May want to make sure you have root (test a root app). Try updating su binary in Super User.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
I tried your initial method, but it didn't work.. just boots me to my homescreen as usual. It's strange, I can't seem to load or get to any other recovery other than stock. I even tried to reinstall boostrap. I also tried safestrap. Nothing.
I'm getting the "granted super user permission" popups when certain apps such as JuiceDefender, VOODO keeper, SQL Lite, ec. I'm also able to go into SU and activate and delete SU permissions.. then it prompts me again when I open apps, so I'm assuming I have root. I thought though maybe it was a "soft" root or something, so I tried to root it with DroidRazr Utility Matt's app it can't write to certain files. Strange.
smgill said:
I tried your initial method, but it didn't work.. just boots me to my homescreen as usual. It's strange, I can't seem to load or get to any other recovery other than stock. I even tried to reinstall boostrap. I also tried safestrap. Nothing.
I'm getting the "granted super user permission" popups when certain apps such as JuiceDefender, VOODO keeper, SQL Lite, ec. I'm also able to go into SU and activate and delete SU permissions.. then it prompts me again when I open apps, so I'm assuming I have root. I thought though maybe it was a "soft" root or something, so I tried to root it with DroidRazr Utility Matt's app it can't write to certain files. Strange.
Click to expand...
Click to collapse
Have you made any modifications that could have caused the issues? I've been reading online trying to find the other tricks I used to use for manual bootsrap with no luck. There's a file that is deleted when you reboot telling bootstrap it's ok on your next reboot. If you can figure out that file and reinsert it with Root Explorer, it should go to recovery (just a blank file).
Also research the hack that forces CWM on every reboot. Again, sorry for not having more info, never had to use it.
Sent from my DROID RAZR using Tapatalk
joshw0000 said:
Have you made any modifications that could have caused the issues? I've been reading online trying to find the other tricks I used to use for manual bootsrap with no luck. There's a file that is deleted when you reboot telling bootstrap it's ok on your next reboot. If you can figure out that file and reinsert it with Root Explorer, it should go to recovery (just a blank file).
Also research the hack that forces CWM on every reboot. Again, sorry for not having more info, never had to use it.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
Will do!. Don't be sorry, this is something new to try and anything new is helpful! Let me know if you think of anything else and I'll keep you posted.
p.s. I find it weird though that no matter how I modify my settings / apps / etc while booted, once I reboot it reverts back to ~Sunday afternoon. Very weird.
Just throwing more out...have you tried factory reset (in settings and in factory recovery)?
Sent from my DROID RAZR using Tapatalk
joshw0000 said:
Just throwing more out...have you tried factory reset (in settings and in factory recovery)?
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
Yes, I've tried factory reset but it boots me back the same way... As if it's Sunday afternoon 5/6. And I'm trying to remember if there was anything that happened or I installed then. The only thing that comes to mind is that my phone was unresponsive for about 30 minutes, though seemed to be still on as my green LED was flashing as if I had notifications but I couldn't get the screen to come up. I then had to force power down (power + vol down).
I've also tried wiping data / cache in stock recovery, but doesn't do anything.
Im still stuck. Anyone else have any thoughts? Im to the point where I may just buy a new device, full retail, if needed...but that would set me back quite a bit. As an alternative, im happy to make a donation for anyone who can get my Razr back to a normal state.
smgill said:
Im still stuck. Anyone else have any thoughts? Im to the point where I may just buy a new device, full retail, if needed...but that would set me back quite a bit. As an alternative, im happy to make a donation for anyone who can get my Razr back to a normal state.
Click to expand...
Click to collapse
Aside from sbf'ing I don't know what else to suggest. When you sbf'ed, you had:
Good charge
Oem cord plugged to the BACK of the computer (not the front)
Moto Drivers
Latest RSD Lite
What OS are you using (XP, 7, Linux)? 32 or 64 bit?
Have you tried on another computer? That could be your problem.
If all else fails, you can send it to me (just cover shipping both ways). I kinda enjoy tring to fix phones (software issues).
Sent from my DROID RAZR using Tapatalk
Using Windows 7 64 bit.
Good charge
Plugged into side (laptop)
I may try it on my wife's desktop tonight. Hoping that fixes it.
Sent from my DROID RAZR using XDA
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
it is rare that I ever ask for help around these parts. But I just recently got my droid x2 back and wanted to try cm10 alpha 3. The problem is it doesn't seem to want to root. I have SBF'd numerous times and tried both Motorola one click root tool and Pete's Motorola root tool (which actually has worked every time when I used the DX2 as my daily driver with no problems). No matter how many times I run the programs, it seems to stay stock, unrooted gingerbread. Now remember, I have been around these forums for a long time and know what I'm doing. The only difference is that the phone has no number attached to it. Meaning its a WiFi only device. I have tried to bypass the activation which was successful. But I have not been able to root it and install the bootstrap recovery. It just goes through the process and stays the same. I have USB debugging on and checked the unknown sources box. It's been a while since I've done this so I may be missing something. All these tools are the same ones that I've always used with no problems. The only difference is that its a WiFi only device now. So is there any reason why the normal process wouldn't work now?
Have you tried zerg rush?
AKShotgun said:
Have you tried zerg rush?
Click to expand...
Click to collapse
Just tried it with no luck. Its saying it failed to copy over the files because its a read only file system.
its on 2.3.4?
try the ezSBF root option or magic md5
Sent from my XT862 using xda premium
sd_shadow said:
its on 2.3.4?
try the ezSBF root option or magic md5
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yep, I never had this phone on 2.3.5. And these same tools always worked in the past. But I will try this other method.
you check windows device manager, for missing drivers?
Sent from my XT862 using xda premium
Just to double check, after an SBF, you get the activation screen. To bypass that, you have to turn off the phone, hold volume down and power then select "boot android (no bp)"? Thats what I'm doing and I'm just wondering if thats what is causing the phone to not be able to root. Thats the only difference there is from when I had this phone as a daily driver.
sd_shadow said:
you check windows device manager, for missing drivers?
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
I'll double check the next time I do it. But I have attempted this on two different computers. Both of which I have successfully rooted on in the past.
Finally got it rooted and cm flashed on it. Don't know how. Just kept trying until it took. Lol
jsgraphicart said:
Finally got it rooted and cm flashed on it. Don't know how. Just kept trying until it took. Lol
Click to expand...
Click to collapse
sounds alot like the patch and pray method. in a way its the flash and pray.