Database Users

How to Root with Minimum Impact

Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?

You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312

So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.

mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium

mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274

i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.

phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.

threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.

phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.

phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.

ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688

phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.

clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium

Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium

ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2

VZW Software Update inside

Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
It does "fix" the bootloader unlock exploit though
http://www.droid-life.com/2013/07/1...the-kernel-exploit-for-unlocking-bootloaders/

scoobaspeaz said:
Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
Click to expand...
Click to collapse
So, stock recovery to install this?

I would assume you would need to be 100% stock, including the recovery, to install this.

scoobaspeaz said:
I would assume you would need to be 100% stock, including the recovery, to install this.
Click to expand...
Click to collapse
hmm put it on my internal storage and its not found, I think stock recovery wants to see it on a sdcard.

If your boot loader is unlocked before the update, it should stay unlocked. You just will not be able to unlock with methods out there now.
Sent from my Razr HD using xda app-developers app

I received the OTA today on my Max HD. It was build 9.18.79.
Sent using xda premium

A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!

LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1

Thanks for the reply! A few more questions if you don't mind (would hate to do something wrong... like I did last time... luckily I was able to revert back to an original version and fix the install... sigh...):
4) With protecting root, I need the SuperSU Pro version, yes? To be able to use the survival mode, yes? Will Voodoo OTA Rootkeeper do the same thing? Is it possible to use both "to be sure"?
5) I have everything backed up with Titanium Backup. Should I bother getting the pro version and backing everything up using the cloud backup and hypershell? Or won't this matter since if root doesn't keep I won't be able to use Titanium Backup?
6) I also have performed the VZW Wireless Hotspot hack using SQLite. Am I going to have to undo the hack in order for the OTA update to work?
Thanks again for all your help!

Update - I decided to attempt the update and hope for the best. System update 9.18.79.xx updating from 9.16.6.xx.
I purchased the SuperSU Pro from the Play Store, and used the survival mode in SuperSU. I also used the Voodoo OTA Rootkeeper and protected root. I figured if one didn't work the other might... Voodoo worked to protect and re-install root access (not sure about SuperSU as I tried Voodoo first to restore root after the install).
I am unsure if the bootloader is still unlocked, but from what people have said there doesn't seem to be a reason to believe it is re-locked. I haven't tested it out to know for sure though.
It appears that the entire update installed correctly. No errors, and the baseband version was updated to the new radio (xxx.15P).
I did not undo the VZW Wireless Hotspot hack prior to installing the update.
Hopefully this post helps others out there.
My final question... what does updating the radio/baseband do exactly?

i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options

rodmc123 said:
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
Click to expand...
Click to collapse
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny

KachowPow said:
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Click to expand...
Click to collapse
So any idea how one might fix this?

LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
I tried to take the 9.18.79 update I protected the root (I'm not unlocked) before I did so I also temporarily un-rooted (I've always been told to do this before and update) Now I an no longer rooted and it can't find any SU binary codes. Gonna have to flash back to 9.6.16 and try it again I guess or stay on 9.6.16 in order to maintain root for now. If you find a solution please share.

IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
I agree with Lenny. This same thing happened to me when I tried to take the liquid smooth ROM. Follow his instructions above. You'll lose all your pics, vids, files, etc. But at least you'll have a working phone again.

Went smoothly here
All my devices except this one are rooted and some are rom'd. I thought long and hard about whether to void this warranty but decided one day it would be out of updates from VZW and I would want to flash something. I have been denying the OTA for the last day so I figured now or never.
Here are the simple steps:
Download and install Moto device manager (for the USB drivers) here
Enable USB debugging in developer options on the phone
run motochopper here
run motoapocolypse here
install voodooOTA root keeper from Play and backup root
apply OTA
It went error free. The phone has the 15P radio update, unlocked BL and root.

larsdennert said:
It went error free. The phone has the 15P radio update, unlocked BL and root.
Click to expand...
Click to collapse
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?

bananapeapod said:
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
Click to expand...
Click to collapse
Yes, the bootloader won't get locked again after it is unlocked. Moto would be shooting themselves having to reinstate warranties if they did that. Yes I wanted the option of flashing later becuase the ota will install sooner or later. I also want to stay on the upgrade path for now to have current radios.
I still have an Eris lying around that is long out of support but i have gb on it.

IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
that's what i want to do, but i cant because my power button is broken! so i cant enter to fastboot mode without the power button.. i will have to open my phone and try to fix the power button myself.

Just to make a point and to clear up any confusion, this Update will not lock the Bootloader. If you have an Unlocked Bootloader then you will have an Unlocked Bootloader after the update, regardless if it fully works or not, and even if you lose Root, the Bootloader will still be Unlocked. If Root is lost with an Unlocked Bootloader, I suggest downgrading through an FXZ of either 9.16.6 or 9.16.9 and restore Root.

Warranty Process

I have a RAZR M running on T-Mobile. All was good, but I guess I accidentally took the update last night, because I woke up my phone to be greeted with the "your device has been updated" screen. I was trying to avoid it because I was rooted and wanted to keep the possibility of unlocking the bootloader, but oh well...it's not a big deal. However, now my phone keeps rebooting itself. I haven't narrowed it down to whether it's a consistent time between boots or what, but I've had at least 4 or 5 times since last night where I either glance over and see the boot animation playing, or I've been greeted by the "SIM is from an unknown source" screen when I wake the phone.
There's no chance Verizon will just swap it out for me, is there? Since I'm not their customer, I'm assuming I'd have to go through Motorola, which probably takes forever.

Motos turn around rate is rather fast... 10 days total maybe... 2 shipping to get to them they have to have it done in 5 business days... 2-3 days shipping to get it back to you... but with root they may not fix it... either way its worth a shot if you can go without a phone that long...
Sent from my XT907 using xda app-developers app

Oh, cool, that's not too bad. I'll try going into Verizon tomorrow just to see if I get lucky, but otherwise, I'll get in touch with Motorola.
I had root before, but the update removed it, so it shouldn't be an issue. It's too bad we can't RSD back to 4.1.1. The phone was perfect until the update was installed.

Just redo the NV edit and you don't have to return the phone, you can keep using it on GSM carriers.
The same NV edit works fine under the new build and you don't need root to use RadioComm.
There is also a way to revert to the prior rootable version and then protect root and update again keeping root.

cellzealot said:
Just redo the NV edit and you don't have to return the phone, you can keep using it on GSM carriers.
The same NV edit works fine under the new build and you don't need root to use RadioComm.
There is also a way to revert to the prior rootable version and then protect root and update again keeping root.
Click to expand...
Click to collapse
Sorry, I don't think I was clear. I did redo the NV edit, and that works as expected. It's just that the phone keeps freezing and rebooting. It's done it another 2 times (make that 3...it just did it again) since I posted this thread. The only thing that has changed from yesterday to now is that it now has the update (and a factory reset, since I hoped that would solve the issues).
How do I go back to a rootable version? That would be easiest if possible, but I read that RSD doesn't allow you to downgrade unless you have an unlocked bootloader.

Ok I misunderstood then. Check this link for the reversion method. It is for the HD but the same principle applies to the M as well.
I posted an edited XML file for the XT907 in that thread but there has been more work done since then and a fully scripted tool was made up which may not have been released yet.
This was all worked out over the last couple of days, so check that thread for the most recent info.
Basically you flash back in RSD Lite with the previous full XML.zip but using an edited XML file that skips the tz.mbn and gpt_main0.bin along with the getvar lines.
The boot up and root under that version with Motochopper and use Voodoo root keeper and protect and temp unroot and update again to the current build.
http://www.droidrzr.com/index.php/t...18799201-ota-locked-bootload-razr-hd-test-it/

cellzealot said:
Ok I misunderstood then. Check this link for the reversion method. It is for the HD but the same principle applies to the M as well.
I posted an edited XML file for the XT907 in that thread but there has been more work done since then and a fully scripted tool was made up which may not have been released yet.
This was all worked out over the last couple of days, so check that thread for the most recent info.
Basically you flash back in RSD Lite with the previous full XML.zip but using an edited XML file that skips the tz.mbn and gpt_main0.bin along with the getvar lines.
The boot up and root under that version with Motochopper and use Voodoo root keeper and protect and temp unroot and update again to the current build.
http://www.droidrzr.com/index.php/t...18799201-ota-locked-bootload-razr-hd-test-it/
Click to expand...
Click to collapse
Awesome, thanks! It looks like Kaos is working on a tool for the M, so I'll probably just wait for that. I'm way to tired to read and follow instructions tonight anyway. Thanks for the great work you guys do!

freak4dell said:
I had root before, but the update removed it, so it shouldn't be an issue. It's too bad we can't RSD back to 4.1.1. The phone was perfect until the update was installed.
Click to expand...
Click to collapse
I was just thinking about the root checker in the recovery menu... the "qe0/0 ,1/1 if your rooted and 0/1 if you have rooted"...
Sent from my XT907 using xda app-developers app

Is your phone still freezing and rebooting. If your phone stopped doing that, do you know what you did to stop this because I'm now facing the same problem.
Sent from my XT907 using xda app-developers app

ccdsatt said:
Is your phone still freezing and rebooting. If your phone stopped doing that, do you know what you did to stop this because I'm now facing the same problem.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Mine is still doing it. It's either just a random coincidence that it happened the same time that I took the update, or it's caused by a part of the update that was skipped by the roll-back procedure. Either way, I've contacted Motorola and will be sending the phone to them this week. I just don't feel like dealing with trying to fix it myself, and if the X turns out to be decent, I'm going to end up selling the M so I want it to be in good condition for a good resale value.
Now I need to see if the files to RSD to a completely stock version of the newest build are available anywhere.

[Q] Going in circles

I promise that I have been reading threads for 2 weeks trying to figure out how to solve my problem without posting any questions, because I know no one likes to repeat themselves! I made a little bit of progress, but now I don't know what to do.
I bought my RAZR M in February. I took it out of the box and activated it. I never rooted it - had no intention of rooting it. Everything was great until the April update (98.15.66). All sorts of apps started crashing, background, Chrome, text messaging... phone kept deleting Contacts...it was a mess. I posted in the Moto Support forum and was advised to reset, which I did. It helped a little, sometimes apps still crashed, but I was dealing with it. I know the phone took at least one more update after that, but I don't know which. Then November 8, I did the OTA to 98.30.1. Phone got stuck on the red eye during boot. Tried clearing cache, reset, no luck. Called Moto support and they said they couldn't do anything unless I paid them $120 to flash the phone, because according to their info, my phone was rooted!! I never rooted it, I didn't know anything about rooting (still don't, really). I wonder if something failed during one of these updates and triggered their root checker. After reading threads here on XDA, I was able to use RDS lite to 98.16.3. So at least the phone boots, but now it keeps wanting to do the OTA to 98-30.1.
I assume I should avoid taking the OTA, but I don't know how to do that without hitting "Later" every 12 hours. If I'm understanding correctly, since I have 98.16.3 my bootloader is locked and there is nothing I can do about that. I thought maybe Titanium Backup would help so I could at least freeze the updater, but I don't have SU/root access to be able to do that. Where do I go from here? Thank you very much for any help!

So you've never been rooted and moto said it had been... Did you buy it from Verizon? Lets check and see if that device has ever been rooted... Power of the device... Power on while holding volume up + volume down... Select recovery...when you see Android Andy hold volume down tap volume up... Now you should see QE process does it say 0/0 or 0/1... If it says 0/0 your phone has never been rooted... If it said that I would either call them back.. After taking pix of that... And inform them of that.. Or take it to a Verizon store and request a new device... Post the pic in your topic on Motorola's forum and say how they refused service because your device was rooted when it wasn't... Matt the forums manager should reply and assist then
Sent from my XT907 using xda app-developers app

@sasperson
Where did you "clear cache" during your bootloop? I dont believe stock recovery has that option. Also how did you use RSDLite if you have a locked bootloader, wouldn't it just fail. Not trying to be a ****, i'm just pointing out the inconsistencies.

ATTACK said:
@sasperson
Where did you "clear cache" during your bootloop? I dont believe stock recovery has that option. Also how did you use RSDLite if you have a locked bootloader, wouldn't it just fail. Not trying to be a ****, i'm just pointing out the inconsistencies.
Click to expand...
Click to collapse
Stock recovery does have the option to clear the cache partition...you can RSD I up or to the current version...
Sent from my XT907 using xda app-developers app

ezknives said:
Stock recovery does have the option to clear the cache partition...you can RSD I up or to the current version...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok. I didnt know stock recovery had any options, never used it. Didn't he RSD Lite from 98.30.1 to 98.16.3. I thought you couldn't downgrade with a locked bootloader.

I apologize my brain saw .16 the first time I read it from where I'm not used to seeing .30
Sent from my XT907 using xda app-developers app

It does say 1/1. I don't believe it said that when I did the FDR back in April/May when I first starting having issues after the update to 98.15, but I can't say 100% for sure since I didn't even know what it meant up until a couple of weeks ago when I started reading up.
How it got like that, I don't know. I bought the phone from Amazon. Sold by Amazon, marked as Brand New. I didn't buy it from a Joe Schmo marketplace seller.
I have no idea for sure if my bootloader is unlocked or not. From what I've read, it seems that if you have 98.16.3, then it has to be. When I go into the AP fastboot screen, it says Device Status: Locked.
I did post on the Motorola forum and someone there told me how to check in the recovery menu for the root status, but since it says 1/1, someone recommended that I come over here to XDA, which is how I ended up doing the RSD lite thing to at least get my phone functional again.
All of this stuff is so far over my head...I'm not really interested in customization or removing the bloatware - I just disable or ignore it. I am only looking to get my phone back running like normal without telling it "Later" every 12 hours to avoid the update. And if I'm understanding correctly regarding the bootloader, there aren't many customization options anyway. Do I just wait to see if the 98.30 update gets added on the droid-developers.org site?

I
sasperson said:
It does say 1/1. I don't believe it said that when I did the FDR back in April/May when I first starting having issues after the update to 98.15, but I can't say 100% for sure since I didn't even know what it meant up until a couple of weeks ago when I started reading up.
How it got like that, I don't know. I bought the phone from Amazon. Sold by Amazon, marked as Brand New. I didn't buy it from a Joe Schmo marketplace seller.
I have no idea for sure if my bootloader is unlocked or not. From what I've read, it seems that if you have 98.16.3, then it has to be. When I go into the AP fastboot screen, it says Device Status: Locked.
I did post on the Motorola forum and someone there told me how to check in the recovery menu for the root status, but since it says 1/1, someone recommended that I come over here to XDA, which is how I ended up doing the RSD lite thing to at least get my phone functional again.
All of this stuff is so far over my head...I'm not really interested in customization or removing the bloatware - I just disable or ignore it. I am only looking to get my phone back running like normal without telling it "Later" every 12 hours to avoid the update. And if I'm understanding correctly regarding the bootloader, there aren't many customization options anyway. Do I just wait to see if the 98.30 update gets added on the droid-developers.org site?
Click to expand...
Click to collapse
If it says 1/1 that means your currently rooted (0/1 it has at some point been rooted) download a root checker from google play... If it is rooted I'm sure you could install a super user then freeze the updater...
Sent from my XT907 using xda app-developers app

ATTACK said:
Ok. I didnt know stock recovery had any options, never used it. Didn't he RSD Lite from 98.30.1 to 98.16.3. I thought you couldn't downgrade with a locked bootloader.
Click to expand...
Click to collapse
No, the phone tried to install 98.30.1 through OTA, but failed and got stuck on the red eye during boot. Moto said the update failed because I was rooted, which I never rooted the phone. How the phone came to say 1/1 on the recovery screen root check, I'll never know, but it's water under the bridge now.
Once I came here and read how to use RSD lite, I flashed it to 98.16. I don't know what version I was running before the 98.30.1 OTA attempt on Nov. 8.
I downloaded Root Checker. For SU it says, "Not found."
Root Access: "no access"
Is this because I only flashed the VRZ_XT907_9.8.1Q-78-1_1FF.xml, which from what I understand is straight stock? Is the phone technically not really "rooted" then? Is it possible to get the Super Access at this point, or am I stuck?
Again, thank you for your help and patience!

sasperson said:
No, the phone tried to install 98.30.1 through OTA, but failed and got stuck on the red eye during boot. Moto said the update failed because I was rooted, which I never rooted the phone. How the phone came to say 1/1 on the recovery screen root check, I'll never know, but it's water under the bridge now.
Once I came here and read how to use RSD lite, I flashed it to 98.16. I don't know what version I was running before the 98.30.1 OTA attempt on Nov. 8.
I downloaded Root Checker. For SU it says, "Not found."
Root Access: "no access"
Is this because I only flashed the VRZ_XT907_9.8.1Q-78-1_1FF.xml, which from what I understand is straight stock? Is the phone technically not really "rooted" then? Is it possible to get the Super Access at this point, or am I stuck?
Again, thank you for your help and patience!
Click to expand...
Click to collapse
if your on version listed in screenshot yes you can root it ... Use motochopper 1.3
Sent from my XT907 using xda app-developers app

ezknives said:
if your on version listed in screenshot yes you can root it ... Use motochopper 1.3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok, I will give that a try. I have read about motochopper, but was confused as to whether it was the right thing for the version I'm running, I think I was reading "Build version," mixing that with "System version," and getting scared when it said it will brick the phone if not used on the right version. Since my Build Number is 9.8.1Q.78-1, the directions and links on droidrazr.com posted by livinginkaos and SamuriHL should work for me, right? (assuming I can follow the directions, that is)
I wonder if this will fix the strange random app crashes I've been getting ever since the April update. It's very inconvenient to have my text message history wiped.
Thank you for the advice, ezknives!

*Update*
I used motochopper! I used Titanium backup and froze the updater.apk! \o/
I have one more question - now that I have this super user access, is it still best to just disable/freeze the bloatware instead of removing it altogether? I read that some people have used Titanium backup to delete it, I also recall reading that some people had issues with updates if they deleted them and ended up having to reinstall them...?

sasperson said:
*Update*
I used motochopper! I used Titanium backup and froze the updater.apk! \o/
I have one more question - now that I have this super user access, is it still best to just disable/freeze the bloatware instead of removing it altogether? I read that some people have used Titanium backup to delete it, I also recall reading that some people had issues with updates if they deleted them and ended up having to reinstall them...?
Click to expand...
Click to collapse
Yes it's best to freeze it all rather then delete it.... So you don't have to do as much when the next OTA comes out...
Sent from my XT907 using xda app-developers app

ezknives said:
Yes it's best to freeze it all rather then delete it.... So you don't have to do as much when the next OTA comes out...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Everything seems to be back to normal - at least back to how it was a few weeks ago. It still has the random background app crash, but whatever. I've been living with that since the April update. I'm just happy my phone is functional again.
Thanks again for the help!
:victory:

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.

It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk

Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.

So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app

No nothing roots 4.4 at this point.

vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.

akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.

mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???

-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck

mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.

-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it

mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh: