Okay so Yesterday evening am prompted by OTA Update and foolishly I clicked on Update.
Code:
Version:98.72.165.XT912
Meanwhile I was trying for Ubuntu Dual Install thus Safestrap was being installed simultaneously. Long stroy short after update I lost my ROOT and all applications
i.e. Busy Box, Boot Linux, Terminal ES File Explorer while showed rooted were not having access.
Spent the whole night figuring how to accomplish as everytime I tried the Exploit I use to get the following error
Code:
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
Thus, meanwhile I came across this Post which took me good 2 hours to decipher as per logic, plus few others and this is how I achieved a ROOT on my XT912 again without downgrading (and without having to have Voodooo Temp un-root and stuff)
Code:
1) Unmount the Ext-Sdcard I basically removed it
2) Make sure your Debugging option is enabled, USB Mode change it to MTP or Camera Just don't keep Mass Storage.
3) Settings> Apps > All > SmartActions
Clear Cache
Once Above steps are done
Proceed towards the exploit, plug you Mobile, execute the Exploit
As soon as you see "[*] Rebooting device..." for the first time, and screen turns off, immediately press Vol Down + Vol up & Power Button
In it select the last option BP Only
Rest follow the process of Exploit as they come on screen.
(I personally waited 30secs after Selecting Save on Battery Saver option).
All due thanks to orignal coders who invented the exploit, took it further, XDA & Droidrzr Forum and also to [Link]http://www.droidrzr.com/index.php/topic/36187-ota-9872165-11014/#entry395166[/Link] which gave me the direction over a good nights sleep.
Hope it helps others also.
This works with unrootable after OTA
Thanks a lot bro, was driving me crazy. Posted pic to give visual reference.
I had a little trouble with this on mine. When I got to the first reboot, I selected "BP Only" from the menu, as directed. When the phone booted, it was not recognized by my PC. The PC wanted "MZ600" drivers and couldn't find them. Yes, I had installed the latest Motorola Device Manager. So, the process stalled at "Waiting for phone to reboot".
Since I was stuck, I decided to try something else. I rebooted the phone using the power and both volume buttons, then selected BP Tools from the menu. When it booted it was recognized by the exploit and everything else went as planned.
One other thing to mention, when it booted up the second time, I had to grant SuperUser root access via the standard SuperUser pop-up before the exploit would proceed. That was kinda weird, but it all worked fine in the end.
Thanks for posting this!!
Worked perfectly! Thanks! As a side note I used the full droid razr utility and then Razr blade within that instead of the razr blade file you provided.
Also, the first time i chose bp-only it froze for me at the Motorolla screen. I had to hit the power button to shut down, and then just turned it on again. I don't know if it booted into bp-only mode this time, but nonetheless the utility installed root fine after this.
JTCGiants56 said:
Worked perfectly! Thanks! As a side note I used the full droid razr utility and then Razr blade within that instead of the razr blade file you provided.
Also, the first time i chose bp-only it froze for me at the Motorolla screen. I had to hit the power button to shut down, and then just turned it on again. I don't know if it booted into bp-only mode this time, but nonetheless the utility installed root fine after this.
Click to expand...
Click to collapse
I keep getting errors.
errorrotocol fault no action no status
Any ideas?
Finally worked for me in airplane mode, "BP Tools" after the first reboot, and USB setting as "Camera". Had the same issue as in the OP with the other combinations I tried.
I installed the ota manually and there were no root, but before updating I installed voodoo root keeper. Everything is ok right know
Enviado desde mi DROID RAZR mediante Tapatalk
Worked like a charm for my first root on this phone. Thanks for the tips, It worked great!
Unable to root Razr MAXX
I stupidly updated my razr MAXX just now to 98.72.165.XT912, which I just bought and has never been rooted. Could someone please tell me, Step by step, how to root the device? the latest exploit on XDA does not work. Is there an update for this? Please help!
Thanks.
Wasn't having any luck with the instructions in the original post, though I missed the suggestion to try selecting BP Tools instead of BP only the first time around. Tried using saferoot after that and it worked with no problems. File was called saferoot-moto, found it over on droidrzr.com.
Also saw a suggestion there to disable the lock screen. Don't know if that would have made a difference with the other method but had it disabled when I used saferoot.
How does one fully unroot from this method (without losing data)? I uninstalled safestrap, and deleted \system\xbin\su , system\bin\su, & system\apps\superuser using root explorer but the darn superuser app still keeps showing up (though it no longer works properly).
Need to unroot since I got my corporate email blocked by MaaS360 due to being rooted. :crying:
I think you will need to goto Utility and perform it as far as I remeber , sorry for late reply have moved to XT1080 thus went out of touch with Motorola or there is anew update available for XT912 updated my moms phone yesterday ( it was unrooted earlier also ) that should restore your phone and probably re-unroot it.
Sent via Droid Ultra XT1080 using Tapatalk for TnP...
This works for me.
Thanks OP!
jskandhari said:
Okay so Yesterday evening am prompted by OTA Update and foolishly I clicked on Update.
Code:
Version:98.72.165.XT912
Meanwhile I was trying for Ubuntu Dual Install thus Safestrap was being installed simultaneously. Long stroy short after update I lost my ROOT and all applications
i.e. Busy Box, Boot Linux, Terminal ES File Explorer while showed rooted were not having access.
Spent the whole night figuring how to accomplish as everytime I tried the Exploit I use to get the following error
Code:
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
Thus, meanwhile I came across this Post which took me good 2 hours to decipher as per logic, plus few others and this is how I achieved a ROOT on my XT912 again without downgrading (and without having to have Voodooo Temp un-root and stuff)
Code:
1) Unmount the Ext-Sdcard I basically removed it
2) Make sure your Debugging option is enabled, USB Mode change it to MTP or Camera Just don't keep Mass Storage.
3) Settings> Apps > All > SmartActions
Clear Cache
Once Above steps are done
Proceed towards the exploit, plug you Mobile, execute the Exploit
As soon as you see "[*] Rebooting device..." for the first time, and screen turns off, immediately press Vol Down + Vol up & Power Button
In it select the last option BP Only
Rest follow the process of Exploit as they come on screen.
(I personally waited 30secs after Selecting Save on Battery Saver option).
All due thanks to orignal coders who invented the exploit, took it further, XDA & Droidrzr Forum and also to [Link]http://www.droidrzr.com/index.php/topic/36187-ota-9872165-11014/#entry395166[/Link] which gave me the direction over a good nights sleep.
Hope it helps others also.
Click to expand...
Click to collapse
Just system wipe the device 2 times. I did that and I got root access.
Tom2112 said:
I had a little trouble with this on mine. When I got to the first reboot, I selected "BP Only" from the menu, as directed. When the phone booted, it was not recognized by my PC. The PC wanted "MZ600" drivers and couldn't find them. Yes, I had installed the latest Motorola Device Manager. So, the process stalled at "Waiting for phone to reboot".
Since I was stuck, ... I rebooted the phone using the power and both volume buttons... When it booted it was recognized by the exploit and everything else went as planned.
Click to expand...
Click to collapse
JTCGiants56 said:
...the first time i chose bp-only it froze for me at the [red circle] Motorolla [boot] screen. I had to hit the power button to shut down, and then just turned it on again. I don't know if it booted into bp-only mode this time, but nonetheless the utility installed root fine after this.
Click to expand...
Click to collapse
I just wanted to report success on this as well. As the quotes above indicate, I had to make adjustments to the OP's instructions before it would work. The menu entry "BP Only" was not the last item as indicated in the OP, but instead it was "BP Tools". I chose the option "BP Only" as per the OP's instructions, but the phone locked up at reboot. After forcing a reboot the process proceeded as expected with no further issues.
Related
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
[email protected] said:
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
Click to expand...
Click to collapse
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is here. Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
jojojohnson7410 said:
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
Click to expand...
Click to collapse
When I touched the screen above the search button, I see the source of the error is "/system/app/swype.apk
so I imagine it is due to updating swype cuple of times and as far as I remember, in the first update i had to remove 2 system files to make it work.
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Eddie Bombay said:
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Click to expand...
Click to collapse
This did it for me. Left the SD card update on my SD card and as soon as it rebooted to clean 183 it found the update and installed it!
Thanks
I was rooted using ViperMod. I took the JB OTA, thinking rootkeeper would work. Wound up with the partial root issue (some apps worked, i.e. Anti, Network Spoofer, Root Explorer, but root checker and the Linux Installer for Backtrack gave no root errors), so I tried the method here: http://forum.xda-developers.com/showthread.php?t=1911261
I got through step 3. Step 4 gave me a permission denied error, so I used Root Explorer to turn on all permissions for /data/local/tmp. At that point, adb push claimed to have worked through step 6, but I noticed my Prime had frozen. Before I went any further, I decided to hard reboot (hold down power button), to be sure everything was running proper before I started in with shell commands.
Upon reboot, it now sticks at the initial splash screen. I can vol-down & get to the bootloader there, giving me the 4 standard options. Recovery gives me the dead-looking Andy with exclamation mark (I assume because I don't have a backup image, which yes, I know, was stupid not to have. Hindsight.). The OS option says it's starting from a cold boot, but freezes there and does nothing else. I can access fastboot, and at least the reboot command seems to work, but I haven't tried anything else, as I'm not familiar with fastboot, and have no idea where to go from there. I'm hoping against hope I don't have to use the wipe action, as I have a lot of time and data invested in the thing.
I'm also able to vol-up and have APX recognized on my Win7 machine, but I admittedly have no idea what to do with that.
If anyone could help me here, especially if it would include NOT wiping my Prime, I would be forever grateful. Thank you in advance for any advice.
Please, I'm begging the community for help. I have no idea where to go from here. From my view, I don't know what went wrong. I simply changed permissions for one folder and pushed three files.
I don't have anyone else to help with this. This community has always been amazing when someone needed help, and I'm asking, as a man who seems to have screwed himself, for that help for me.
Again, I offer thanks in advance for any advice.
OK, I recognize I might catch some crap on this, since you guys don't know me from Adam, but it's a crappy situation. My friend passed this on to me, because he is stumped. His brother died in a car wreck on Christmas night, and found among his possessions in the car was this Venue 8320. It's set up with a pattern lock, and of course we can't get past it.Don't have access to the email, because the guy is dead. His father tossed the cell phone that might have been linked to the email, so we can't get in the email that way. So, I'm trying to figure out how to either bypass the pattern lock, or barring that, reset it so that it's at least usable.
I've loaded the Intel Android drivers on my computer, and can get an ADB shell, or access the fastboot when booted into Droidboot, but without root access I'm still pretty limited in what I can do. Is there any way in to this thing, or is my friend SOL?
Rasilon said:
OK, I recognize I might catch some crap on this, since you guys don't know me from Adam, but it's a crappy situation. My friend passed this on to me, because he is stumped. His brother died in a car wreck on Christmas night, and found among his possessions in the car was this Venue 8320. It's set up with a pattern lock, and of course we can't get past it.Don't have access to the email, because the guy is dead. His father tossed the cell phone that might have been linked to the email, so we can't get in the email that way. So, I'm trying to figure out how to either bypass the pattern lock, or barring that, reset it so that it's at least usable.
I've loaded the Intel Android drivers on my computer, and can get an ADB shell, or access the fastboot when booted into Droidboot, but without root access I'm still pretty limited in what I can do. Is there any way in to this thing, or is my friend SOL?
Click to expand...
Click to collapse
factory reset clears all lock codes but also deletes all info.
power off, then power on while holding voume down button
you should select the option called recovery, on the recovery screen you should c da droid on his back when you are there press and hold power button and voolume up button for 2 or so seconds and you should enter recovery mode
chairsz said:
factory reset clears all lock codes but also deletes all info.
power off, then power on while holding voume down button
you should select the option called recovery, on the recovery screen you should c da droid on his back when you are there press and hold power button and voolume up button for 2 or so seconds and you should enter recovery mode
Click to expand...
Click to collapse
Hmm. When I go to Recovery, all I get is a picture of an android on it's side with a repair hatch open. There does not appear to be any way to do a reset from there, at least not that I can see.
I've been trying to root it, but SuperOneClick isn't working. I tried pushing the various included files manually and executing them, but they won't execute - the error message is "not executable: magic 7F45". I tracked down x86 versions of su, busybox, etc. and they will execute, so it looks like all I need now is an x86 binary for rageagainstthecage/psneuter/zergRush. Does anybody know where I would track one down? I haven't had any luck finding one so far.
When at then android hatch picture you can press power then vol+ same time, let go and u will have more options. Good luck.
Sent from my Venue 8 3830 using xda app-developers app
Rasilon said:
Hmm. When I go to Recovery, all I get is a picture of an android on it's side with a repair hatch open. There does not appear to be any way to do a reset from there, at least not that I can see.
I've been trying to root it, but SuperOneClick isn't working. I tried pushing the various included files manually and executing them, but they won't execute - the error message is "not executable: magic 7F45". I tracked down x86 versions of su, busybox, etc. and they will execute, so it looks like all I need now is an x86 binary for rageagainstthecage/psneuter/zergRush. Does anybody know where I would track one down? I haven't had any luck finding one so far.
Click to expand...
Click to collapse
there is a working method of rooting this tab is for the 4.2.2 version ( some 4.2.2's are not really working with root but others are) and if your tabby is the 4.3 update then that method to root exists somewhat but the creator of that method isnt releasing it till he deems its ready. so just look in this forum somewhere you'll find you root method if your on 4.2.2
also to enter recovery when at the droid on his back screen press and hold the volume up and power button simultaneously
there you can wipe stuff.
chairsz said:
there is a working method of rooting this tab is for the 4.2.2 version ( some 4.2.2's are not really working with root but others are) and if your tabby is the 4.3 update then that method to root exists somewhat but the creator of that method isnt releasing it till he deems its ready. so just look in this forum somewhere you'll find you root method if your on 4.2.2
also to enter recovery when at the droid on his back screen press and hold the volume up and power button simultaneously
there you can wipe stuff.
Click to expand...
Click to collapse
Yeah, thanks. I don't think it's 4.3, because it hasn't been on a network since 12/25, although perhaps that's why I haven't been able to root it. Kernel version is 3.4.34, which I see has been reported as present in a patched 4.2.2 version that is not vulnerable to standard 4.2.2 exploits. I guess that's what I haven't been able to get in. I'll tell my friend that he can either wait for a 4.3 root exploit to be released, or wipe it clean.
Thanks for the help chairsz.
Hey guys. A friend of mine gave me a Motorola Droid RAZR XT912 which woudln't work with GSM networks to make it work. So I went here and used DROID RAZR Utility XT912 Jellybean to gain root. After that I installed Safestrap 3.73 and flashed CM11 M9 into the Slot1. The phone was working completely fine without a single hitch.
Today my friend called me to ask about the phone and I said it's working only it has two systems (lots of not really good used memory). He said to me to remove one of them and I went back into Safestrap recovery and activated Stock. Then I wiped Dalvik cache, cache, system, android secure. After that I switched to Slot1 (CM11) and it said it was active. I thought it would work since there is still that CM11 in Slot1, right? I tapped reboot -> system and since then the phone won't boot. When I press and hold the Power button for about 7-8 seconds, Motorola logo is shown and after that only a black screen (phone turned off). I tried holding Power+VOLDN but sadly same results. I know I should have read more about removing stock, but I did it anyway. Everything was going so smoothly so I thought there wouldn't be any problems. I think I should point out that when I connect the phone to my laptop, I can see "Mot Composited ADB Interface". Does this mean the phone is not dead?
Is there a way to unbrick the phone without some special cables and/or equipment?
Thanks.
Use Matt's utility to restore things to stock:
http://forum.xda-developers.com/showthread.php?t=2192467
@mikeoswego Thanks. I actually managed to get it working a little before this post using that amazing piece of software.
The state of the phone was like this: I hold the Power button, Motorola logo pops up and then the phone turns off. I hold Power+VOLDN same thing happens (Logo is shown and then it turns off). I couldn't even get it to fast boot. It just turned off. I searched a bit here and found the solution. When the logo is shown, press and hold VOLUP+VOLDN and don't let go. The menu will be shown where you can select fastboot. After that I just connected the phone to my laptop, used matts program and resurrected the phone
I lost root, so I rooted again, installed safestrap, wiped Stock and in it's place installed CM11. Rom1 was still occupied by old CM11 install so I deleted that. Installed the GSM patch and now the phone works as a charm.
So many thanks to this great community. I usually don't post at all. I use the search function and just follow the steps, but I panicked a bit today. Sorry.
Thread can be closed.
CyberBully said:
So many thanks to this great community. I usually don't post at all. I use the search function and just follow the steps, but I panicked a bit today.
Click to expand...
Click to collapse
Thanks for letting us know that you got things working. Someone else in the future will see this thread and be helped by it!
A couple days ago, I decided to root my unlocked but running on AT&T OnePlus 3.
After a while, I was able to do it, thanks largely to the guide that naman bhalla posted here on XDA.
I tried to start snapchat, but it wouldn't let me login because I had root. Like a complete noob, I just uninstalled supersu instead of hitting "uninstall root" or whatever from inside the supersu app itself.
I then realized that was a horrible idea, and redownloaded supersu from the google play store (noob!). It said "your su binaries are not up to date. restart now?" or something like that and I selected "yes" (like a noob). It then proceeded to take ~ 20 minutes to actually update the su binaries, and then DRAINED THE BATTERY COMPLETELY TRYING TO START UP THE PHONE. The phone got physically warm to the touch while this was happening.
I've tried resetting the dalvik cache once, but the only way I was able to do that is to wait for the phone to die, then boot into recovery mode on startup.
I have two questions:
1. Is there another way to stop the phone from booting up completely? Will just holding down the power button work or something in ADB?
2. Have I significantly screwed up my phone?
kpratiik57 said:
A couple days ago, I decided to root my unlocked but running on AT&T OnePlus 3.
After a while, I was able to do it, thanks largely to the guide that naman bhalla posted here on XDA.
I tried to start snapchat, but it wouldn't let me login because I had root. Like a complete noob, I just uninstalled supersu instead of hitting "uninstall root" or whatever from inside the supersu app itself.
I then realized that was a horrible idea, and redownloaded supersu from the google play store (noob!). It said "your su binaries are not up to date. restart now?" or something like that and I selected "yes" (like a noob). It then proceeded to take ~ 20 minutes to actually update the su binaries, and then DRAINED THE BATTERY COMPLETELY TRYING TO START UP THE PHONE. The phone got physically warm to the touch while this was happening.
I've tried resetting the dalvik cache once, but the only way I was able to do that is to wait for the phone to die, then boot into recovery mode on startup.
I have two questions:
1. Is there another way to stop the phone from booting up completely? Will just holding down the power button work or something in ADB?
2. Have I significantly screwed up my phone?
Click to expand...
Click to collapse
Some more research (that I should have done before posting here) revealed that holding down the power button would allow me to boot into recovery again. I also remembered that I backed up my phone using Titanium Backup before doing everything that screwed up my phone. I saved that onto my phone's internal storage. Is there any way to restore this from TWRP?