[Q] Droid R2D2 Killed by Verizon OTA ?! - Droid 2 General

Hello! I have been searching through the forums and have found several similar issues to mine, but I have some questions/concerns as to whether the solutions mentioned apply to exactly my situation.
I have a Motorola Droid R2D2 edition. I Did not do anything to it. I did not root, I did not side load anything, I did not try to roll back anything. I was minding my own business and received a message regarding a firmware update OTA. I assumed this was going to fix the horrible behavior introduced by the previous OTA, (random reboots etc) So excitedly.. I let it do its thing.
Big Mistake...
I think THIS: http://support.verizonwireless.com/pdf/system_update/droid_r2d2.pdf is the update I was installing.
Now it is stuck on a black boot loader screen. Here are my concerns about the other post.
1.) A similar problem was had with a normal Droid 2, but his boot loader was version D2.35 Mine says D2.37 Can I use the same tools that were mentioned here: http://forum.xda-developers.com/showthread.php?t=849658 ?
2.) My error code is different, his says Err:A5,70,00,1F Mine says A5,70,00,00,23
What does this code mean? These kinds of things intrigue me
3.) I do not have that mem_map message.
My screen looks exactly like this:
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
Can I just do what the other guy did in the above mentioned post? Or do I have to do something else? I'd prefer not to take a 25 mile drive to the nearest Verizon store to beat them..err I mean.. ask them to re-flash it, if I can just do that myself.
P.S. Already tried a battery pull no luck :'(

That's unfortunate.
The OTA killed my root, as one would expect. I re-ran the Motorola One Click Root, but this time, it didn't root it. I wonder if Verizon blocked this exploit? I'll have to try again and report back.

One more question
IS there a precedent for installing Windows phone on a Droid 2? Can I do that since I have to flash something on anyway?

NOtanXDANoob said:
IS there a precedent for installing Windows phone on a Droid 2? Can I do that since I have to flash something on anyway?
Click to expand...
Click to collapse
no you cant install windows phone on the droid 2, when did u get this update? were you previously on gingerbread or froyo.. best bet is to use rsdlite and flash the newest r2d2 sbf or droid 2 sbf .601 in that case you just wont have all the stupid r2d2 noises ;/

merlot2k1 said:
That's unfortunate.
The OTA killed my root, as one would expect. I re-ran the Motorola One Click Root, but this time, it didn't root it. I wonder if Verizon blocked this exploit? I'll have to try again and report back.
Click to expand...
Click to collapse
I am waiting to see if/how somebody gets ROOT back on their R2-D2 before I update with the OTA 2.3.4
So far I have found nothing on it and I wonder if our precious R2-D2 is too old for people to crack it....

merlot2k1 said:
That's unfortunate.
The OTA killed my root, as one would expect. I re-ran the Motorola One Click Root, but this time, it didn't root it. I wonder if Verizon blocked this exploit? I'll have to try again and report back.
Click to expand...
Click to collapse
Is the one-click root you're talking about the same thing as 'Pete's Motorola root tools'? I know that works great on newer droids (e.g. droid pro, droid 3) I don't know if the update the R2D2 got would mess up Pete's exploit.

Related

Verizon ota failed

Hello,
Yesterday I rooted my new droid x. I used titanium backup to backup, then remove some of the apps that I didn't need. However, then I received the ota update, and it fails to install. Im assuming it is because I have removed the city id, amazon mp3 store, and backup assistant. I try to restore, but I find I cannot restore them jacques they are non market apps. Where can I find them, then install them?
Sent from my DROIDX using XDA App
quinnteq said:
Hello,
Yesterday I rooted my new droid x. I used titanium backup to backup, then remove some of the apps that I didn't need. However, then I received the ota update, and it fails to install. Im assuming it is because I have removed the city id, amazon mp3 store, and backup assistant. I try to restore, but I find I cannot restore them jacques they are non market apps. Where can I find them, then install them?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Theres An .sbf I Used To Get The Update Easily
Just Make Sure You Back Up Everything
(.sbf Is Used By RSD Lite Just In Case You Didn't Know)
hmm...
Ok, well, im not all that familiar with what your talking about...
I soppose I kinda did the opposite when it comes to removing integral apps on the phone, but from what im reading, im mostly hosed aren't I?
How do i find this .sbf and how would i use this RSD to restore?
I apologize in advance for being such a noob.
Time to start learning about your Droid X. It's all here, in this forum and in the development forum. Check out the Wiki first. There's a link to it on the first post of the android development forum.
Your problem is easily solved btw.
http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
Download the backup there, boot into CWM and restore from that image. You'll get all the crapware back and will be able to OTA. Alternatively you can go to 928droid.com and download the clean DX image.
I called Verizon about not being able to update with the OTA and they are sending me a new phone lol!
Sent from my DROIDX using XDA App
Erickomen27 said:
Theres An .sbf I Used To Get The Update Easily
Just Make Sure You Back Up Everything
(.sbf Is Used By RSD Lite Just In Case You Didn't Know)
Click to expand...
Click to collapse
I did a little research and found that i have the 30.04 boot loader. My attempts at locating what i guess is referred to as a "system only SBF" have been futile. Is there somewhere i can find this? what is the name of the file i need, i know links cannot be posted.
I attempted at restoring the apks to the phone via adb (applied proper permissions etc). I got the apks back, and the apps running properly (backupassistantclient.apk ... etc) however, to no avail it still will not update.
hmmm 30.04. TMK only the leaked 2.3.320 SBF and the official OTA use that bootloader. Are you sure the update didn't work? Maybe your brand new phone already has the update? Settings->about phone->Android version should tell you. 2.2.1 = the OTA.
Sleuth255 said:
hmmm 30.04. TMK only the leaked 2.3.320 SBF and the official OTA use that bootloader. Are you sure the update didn't work? Maybe your brand new phone already has the update? Settings->about phone->Android version should tell you. 2.2.1 = the OTA.
Click to expand...
Click to collapse
Actually, I've had that bootloader on 2 separate X's; one I bricked on a system only leak of .320 and one I ended up using the leaks to get to .340(wouldn't OTA, possibly because I forgot to fix permissions). I know because at one point I SBFed the phone from .151 to .15 and I saw the bootloader version.
quinnteq said:
I did a little research and found that i have the 30.04 boot loader. My attempts at locating what i guess is referred to as a "system only SBF" have been futile. Is there somewhere i can find this? what is the name of the file i need, i know links cannot be posted.
I attempted at restoring the apks to the phone via adb (applied proper permissions etc). I got the apks back, and the apps running properly (backupassistantclient.apk ... etc) however, to no avail it still will not update.
Click to expand...
Click to collapse
Sleuth is correct--there is a full (as opposed to "system only") 2.3.32 SBF that works with 30.04. As has been previously suggested, all of the info on finding this file and installing it are contained in the wiki (which is located on the xda droid x dev page). It really isn't a big deal to resolve your issue. Learning to unbrick your phone with RSD will be extremely useful to you in the future, as will the time you spent screwing around with ADB.
I give you props for trying to resolve your issue yourself, rather than crying to Verizon the first time you ran into trouble
ok, so i got it to SBF finally! it worked. now i have 2.2.1. But i no longer have root access, gaaha! what gives! anyway... any good tip to restore root access?
I am glad i know how to do the SBF processes, im not so leery about installing custom roms on my DX anymore... which is my end goal now that i can do the SBF for this boot loader.
However, how to do i get root access again?
Reroot your phone however you did the first time.... I used z4root, took some time to get it work... but eventually got it to work
Sent from my DROIDX using XDA App

[Q] How can I LOCK my Bootloader?

Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
lukkypuggy said:
Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
Click to expand...
Click to collapse
Nope it's impossible to relock and once it's unlocked all your warranties are void
Sent from my XT907 using Tapatalk 2
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
lukkypuggy said:
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
Click to expand...
Click to collapse
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Coronado is dead said:
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Click to expand...
Click to collapse
thanks!
yes! it is!
lukkypuggy said:
thanks!
Click to expand...
Click to collapse
was unlocked now its fn locked and stuck in ap!!!
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
phantomsniper773 said:
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
Click to expand...
Click to collapse
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Skreelink said:
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Click to expand...
Click to collapse
Interesting theory. I personally had to RSD back to 4.1.2 (q66) to install since I had removed the Audio Level Warning apk (which just restores stock apps, kernel, boot image and boot animation but leaves data intact). I then let the update installer run on its own with the stock recovery and it remained unlocked.
Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
RikRong said:
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
Click to expand...
Click to collapse
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
phantomsniper773 said:
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
Click to expand...
Click to collapse
RSD will work, but you'll only be able to flash the most recent update.

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.

[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:

Just caught my Turbo trying to update on it's own

I was sitting in my car and looked at the screen and I noticed that the phone was downloading MotorolaOTA 4.0 Does anyone know what it is? I am currently running KitKat 4.4.4 and never did the Lollipop update.
I also stopped the download in process but it appears that the phone would love to continue the download.
Thanks
gman
The phone has an app called MotorolaOTA, which is responsible for downloading system updates. If it was a software update it'd say it's 23.11.39.
Sent from my Droid Turbo using Tapatalk
Just caught my Turbo
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
gman781 said:
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
Click to expand...
Click to collapse
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
smokie75 said:
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
Click to expand...
Click to collapse
For over a month I have been getting the update screen and I would just put it off. Now it seems like it is pushing it's way into my phone.
Motorola confirmed recently that they would be patching the Stagefright exploit for the Turbo via OTA. I wonder if they can somehow force the update since it's such an important security issue this time around. I seem to remember Samsung doing something similar with the S6 shortly after release. I would recommend disabling Motorola OTA until more is known.
Not rooted, cannot disable.
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
That's what I have been trying to figure out.
TheHolyCobra said:
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
Click to expand...
Click to collapse
CM 12.1 ROM (Lollipop 5.1.1) for our Quarks is only 390 MB.
So, yeah, Lollipop 5.1 with Verizon bloatware is probably 770MB.
But the 5.1 OTA for Droid Turbo XT1254 posted here is 1.1GB:
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Still 770MB is huge.
Just freeze it
Sent from my XT1254 using XDA Free mobile app
Not rooted and will not allow disable.
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
gman781 said:
Not rooted and will not allow disable.
Click to expand...
Click to collapse
RL_Wells said:
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
Click to expand...
Click to collapse
The debloat tool is a much easier way to disable any app on your phone. On kitkat it disables and on lollipop it hides the apps. The hide command on lollipop has the same effect as the disable command on kitkat.
---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.
[/COLOR]
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.[/QUOTE]
Yea no go on Recovery. It just goes straight to "Installing System update" Got my PC on, downloaded my mofo to my work PC, and not installing drivers and also downloading a stock but rooted version of 4.4.4. not quite ready to move on to 5.1 yet.
Thanks for the help though and tryin to help out! Now to finally jump into my Turbo after 8 months of having it. I miss the days of TWRP on my Razr HD. Funny because i had to reload an old backed up image so i could get some old wifi passwords.
UGH this damn phone. Won't power off when in Fastboot, so i just have to let it sit in fastboot and watch it and just restart everytime it starts up. got 20 minutes left of downloading an image. About ready to say F'it and just factory reset it for now and see if that fixes it or not.
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
drtweak said:
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
Click to expand...
Click to collapse
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Misterxtc said:
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Click to expand...
Click to collapse
No I had to get my phone backup asap. using the RSD Lite method actually didn't work. the program would keep freezing right after it read the zip file and then crash. Had to use Root Junky's method. I was able to restore back to stock 21.44.12 and everything was there as if nothing happened so I'm all good.

Categories

Resources