Related
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.
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Sent from my Portable
PassatSport15 said:
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Click to expand...
Click to collapse
A few problems here... First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old, it's the original MM firmware from Moto's website (the one on Moto's site is very old and dated incorrectly). We don't have the 18-16 image yet, so you cannot relock or even effectively fix this.
Also, you used a tool to flash, so when pieces failed to flash, you didn't even know it... And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
When you relock a Moto device, you don't just enter "fastboot oem lock" like a Nexus device, there is a process where you start with "fastboot oem lock begin" then flash a complete, signed factory image, wipe, and end with "fastboot oem lock" in one process.
Many parts to this process went wrong... Right now you are just kind of stuck.
BTW, relocking the bootloader has no effective gains except security... You will still be able to see in a glance it was unlocked from the bootloader screen or a fastboot command and the unlocked bootloader warning screen will still be there (you have to flash a custom logo to make it go away).
Did you make a backup of your stock ROM with TWRP prior to rooting? Restoring the backup with TWRP along with stock recovery is usually going to be the simplest and easiest way to go back to full stock.
As acejavelin stated, there really is no benefit to relocking the bootloader except from a security standpoint. As long as the stock ROM and recovery are restored to preroot condition with no system mods, you can take OTAs regardless of bootloader status.
acejavelin said:
First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old
Click to expand...
Click to collapse
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
acejavelin said:
And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
Click to expand...
Click to collapse
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Sent from my Portable
PassatSport15 said:
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Click to expand...
Click to collapse
I think 18-12 is the latest we have so far, but trying to flash it would not help... Your best bet at this point is either custom ROM or wait until we can get the image for 18-16. The problem here is Moto's don't support downgrading, it can be done but it often leaves you in a mixed state.
You could try flashing the latest version we have available manually (don't use a tool) and it might be close enough to able to OTA from there. You have some though, rumor has it initial surveys for an upgrade on the Pure just went out to MFN users this week, assuming it is the Nougat upgrade trial then once it starts you have 4-6 weeks barring any problems they encounter before public release. Assuming of course that history repeats itself and Lenovo follows the same path as Moto has previously.
So basically I'm saying have patience... We don't know when (or really if) we will get the current firmware image, sometimes it's quick and sometimes it takes months.
Update on my xt1575, that I could not take an OTA, it gave me an error - unsuccessful.
My original software was MPHS24.49-18-16, December update, latest software.
Well, I went ahead unlocked the bootloader, installed TWRP, then rooted....
Days later I had decided to unroot, so I would be able to take the OTA.
While I unrooted my device, it was successful, but could not take the updates at all.
Now I reflashed again, in this order below.
Autoflash Script with MPHS24.49-18-8.
Reboot the phone, checked if it was unrooted (No root)
Now I went to software update, and the phone did it's upgrade, like last time. Did the update, device rebooted and it was SUCCESSFUL!
I am finally back to the original software MPHS24.49-18-16
Which was December 2016 update.
Sent from my Portable
I am receiving an error when trying to update to Nougat on my Amazon Moto G4. The OTA update would download, the phone would restart to install, it would go for about 30% and then display "Error!" with the killed over android. I have an unlocked bootloader and have flashed the stock rom. Any assistance would be appreciated.
More info.. Rom? Build number? 49 or 64? Root?
lerg96 said:
More info.. Rom? Build number? 49 or 64? Root?
Click to expand...
Click to collapse
I'm having the same issue! I flashed the stock recovery because the OTA update wouldn't work with TWRP. The rom is the stock amazon one with ads, the current build number is MPJ24.139-64, What do you mean by 49 or 64? and no root. All I did was follow the motorola steps for unlocking the bootloader and flashed TWRP so i could get backups.
I found this guide: laviefrugale(dot)blogspot(dot)ca/2015/05/moto-g-ota-update-error(dot)html But it says to root the phone to look at system logs and I don't know if i wanna do that. But if rooting is necessary to update to nougat then i will do it.
I appreciate your time, please respond soon!
I have the same issue. Bootloader is unlocked. Had been rooted by the systemless method. Flashed the stock back up and tried the OTA update. Getting the same error as previous posters. Build MPJ24.139-48
I got it working now. Downgraded to MPJ24.139-49 using rootjunky file using steps from here. It finished upgrading, but showed an error at the end. Rebooted the phone and saw that the firmware was applied. An upgrade was also available to go to MPJ24.139-64. Ran the update (no errors this time). After getting back in, the nougat update NPJ25.93-14 was available. Updated and now I'm up and running.
Can anyone help me?My amazon 16gb says system update.I press OK.it downloaded around 718mb and update.but it say UNSUCCESSFUL after 40%.i tried many time but still same issue.My moto g4 not rooted,locked bootloader.and still got ads and lockscreen ads
canhmeo said:
Can anyone help me?My amazon 16gb says system update.I press OK.it downloaded around 718mb and update.but it say UNSUCCESSFUL after 40%.i tried many time but still same issue.My moto g4 not rooted,locked bootloader.and still got ads and lockscreen ads
Click to expand...
Click to collapse
Build Number?
lerg96 said:
build number?
Click to expand...
Click to collapse
mpj24.139.64
canhmeo said:
mpj24.139.64
Click to expand...
Click to collapse
so weird, if you really want it try with a factory reset
lerg96 said:
so weird, if you really want it try with a factory reset
Click to expand...
Click to collapse
i also did factory reset.but after that,still fail to update
PicklesTheHamster said:
I got it working now. Downgraded to MPJ24.139-49 using rootjunky file using steps from here. It finished upgrading, but showed an error at the end. Rebooted the phone and saw that the firmware was applied. An upgrade was also available to go to MPJ24.139-64. Ran the update (no errors this time). After getting back in, the nougat update NPJ25.93-14 was available. Updated and now I'm up and running.
Click to expand...
Click to collapse
Thank you very much for this info. I was using LineageOS and was not happy with the Custom Roms. I wanted to go back to Nougat Stock and with your info, I was able to Downgrade and do the updates. Hope this helps anyone else wanting to get back to stock from custom roms.
PicklesTheHamster said:
I got it working now. Downgraded to MPJ24.139-49 using rootjunky file using steps from here. It finished upgrading, but showed an error at the end. Rebooted the phone and saw that the firmware was applied. An upgrade was also available to go to MPJ24.139-64. Ran the update (no errors this time). After getting back in, the nougat update NPJ25.93-14 was available. Updated and now I'm up and running.
Click to expand...
Click to collapse
Were you able to remove the Amazon ads, since you are rooted and bootloader unlocked?
Edit: I just went to systems apps and removed Amazon Offers.
i'm on MPJ24.139-49 but I'm rooted, bootloader unlocked and have TWRP installed. Can you updated to nougat using twrp or do i need the stock recovery?
If you are on -49, you should get a notification to update to -64.
Danny1976 said:
If you are on -49, you should get a notification to update to -64.
Click to expand...
Click to collapse
nope, just the update to NPJ25.93-14 is showing as available. however, when I tried to install it , the phone booted itself into TWRP and I got the E30002 error.
tekweezle said:
nope, just the update to NPJ25.93-14 is showing as available. however, when I tried to install it , the phone booted itself into TWRP and I got the E30002 error.
Click to expand...
Click to collapse
That must likely means TWRP is the issue. I would get the recovery.img from -49 firmware and follow the steps on this link http://www.theandroidsoul.com/remove-twrp-recovery-restore-stock-recovery/ Then try to update.
---------- Post added at 07:12 PM ---------- Previous post was at 06:50 PM ----------
tekweezle said:
nope, just the update to NPJ25.93-14 is showing as available. however, when I tried to install it , the phone booted itself into TWRP and I got the E30002 error.
Click to expand...
Click to collapse
Here is the recovery image from -49.
https://drive.google.com/file/d/0B9qV7lcdu6LmWHA5ck90Q1llZEU/view?usp=drivesdk
i tried flashing the recovery you provided and I think it was successful. when I try to run it, i get the android go lying on it;s back and no command.
am able to flash twrp 3.02 back successfully though
tekweezle said:
i tried flashing the recovery you provided and I think it was successful. when I try to run it, i get the android go lying on it;s back and no command.
am able to flash twrp 3.02 back successfully though
Click to expand...
Click to collapse
Once you flashed the stock recovery, Did you try to update to nougat?
not yet, thought i;d verify that stock recovery was installed and working first. was expecting to see a CWM style menu to come up. i will give it a shot.
edited to say, i t goes to install the update, proceeds about 20% of the way and then i get an Error! message with the android guy lying on it;s back.
has anyone gotten this to work with a rooted phone? i don;t really want to revert back to stock and lose my settings though.
tekweezle said:
not yet, thought i;d verify that stock recovery was installed and working first. was expecting to see a CWM style menu to come up. i will give it a shot.
Click to expand...
Click to collapse
When you see the Droid with no command you press the volume up and you will see the stock recovery.
Not much going on here but the G4 Plus has been finally updated to Oreo. While many of you have unlocked or rooted already, those of you that have not and are on retail should be able download and run this.
Amazon versions may never get this update.
I am curious if there will ever be an easy way for Amazon phones to get this retail update if they are not bootloader unlocked.
When you run the update you will get an error that the ro.product.name does not match (athene_amz instead of athene).
If that small hurdle was overcome and the installer proceeded I am not sure if the phone would not boot loop to recovery because of the system and bootloader mismatch. Does anybody know?
I'm curious if you ever made any progress with updating your Amazon variant? I'm in a similar situation with the Amazon version (xt1625) that is ineligible for the bootloader unlock, and I'd love to find a way to update and squeeze a little more life out of the phone.
I noticed you posed some questions about it in multiple threads but I never saw any actual replies, so thought I'd ask. I'm not knowledgeable in the area, but if there is a way to amend the update file and make it flashable on the Amazon version, I'd give it a shot and see how it goes.
Thanks for any info.
milesius said:
Not much going on here but the G4 Plus has been finally updated to Oreo. While many of you have unlocked or rooted already, those of you that have not and are on retail should be able download and run this.
Amazon versions may never get this update.
I am curious if there will ever be an easy way for Amazon phones to get this retail update if they are not bootloader unlocked.
When you run the update you will get an error that the ro.product.name does not match (athene_amz instead of athene).
If that small hurdle was overcome and the installer proceeded I am not sure if the phone would not boot loop to recovery because of the system and bootloader mismatch. Does anybody know?
Click to expand...
Click to collapse
teeterteeter said:
I'm curious if you ever made any progress with updating your Amazon variant? I'm in a similar situation with the Amazon version (xt1625) that is ineligible for the bootloader unlock, and I'd love to find a way to update and squeeze a little more life out of the phone.
I noticed you posed some questions about it in multiple threads but I never saw any actual replies, so thought I'd ask. I'm not knowledgeable in the area, but if there is a way to amend the update file and make it flashable on the Amazon version, I'd give it a shot and see how it goes.
Thanks for any info.
Click to expand...
Click to collapse
I modified the oem.prop file on the update image by adding AMZ to the athene names. I will upload that here when I get a chance. I haven't actually tried this because my bootloader is locked and I cant wipe this phone as I use it for work.
I flashed Stock Oreo 8.1 OPJ28.111-22. Very slow.
Tried both ElementalX and loonykernel with magisk root, slow, lots of changes... still slow. Whole interface lags. Very slow!
Removed moto apps, still slow.
IDK what else to remove or change...
Trying now again (full wipe and flash) but I'm going back to Nougat Stock after this.