I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
exhibit679 said:
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
Click to expand...
Click to collapse
You must return to stock before you attempt to install that zip. That means you cannot be rooted or have custom recovery in place
I've got a stock N5 I bought from Google on LMY48B and there's still no update for me.
Does anyone know what the roll-out timeline is for the LMY48I?
When should I conclude that I'm not going to get it OTA and resign myself to factory wipe and flashing the image?
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Nemesis02 said:
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Click to expand...
Click to collapse
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
moeREM said:
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
Click to expand...
Click to collapse
I have the same problem her as well with my nexus 5 it keeps saying error with little droid I've tried side loading manually but it didn't work also tried hard reset and wiping cache but nothing solved the problem so i just figured out the problem is the package it self
Same problem here
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
lpganesh said:
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This possibility makes me spend a lot of time, becouse i have lcd_density changed and all apps when i restore a backup are not in the main screen.
walt disney said:
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Click to expand...
Click to collapse
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Working - confirmed
cloney said:
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Click to expand...
Click to collapse
Thanks, confirmed that this method worked. Managed to update my rooted nexus 5 to LMY48I
Tried to install ota update after reverting to stock recovery using Simple Recovery Switcher app. However, also the error message, with little Android picture also appears. Please help
I assume this removed your root, though.
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Pastorelli's said:
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Click to expand...
Click to collapse
I'm with you, not going to try to flash these things, there are a few zip files out there dated a couple days ago, apparently the zips aren't tested prior to release since everyone is getting failure when flashing the zip file.
Is there really no method to apply OTA updates on rooted/modified devices (e.g. modify the update.zip itself to bypass whatever checks it performs)?
Same problem here- only had a custom recovery and root. brought back the stock recovery and did full unroot from SuperSu.
OTA update installtion stops with "Error".
Just flash the system image from the update.
Sent from my Nexus 5 using Tapatalk
Thanks, I ended up doing this http://forum.xda-developers.com/showpost.php?p=62288667&postcount=196
(flashing stock system, boot and recovery from my current version, letting OTA update install and re-rooting according to http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905)
I guess i could have flashed the new version just the same.
Related
Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
bshpmark said:
Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
Click to expand...
Click to collapse
Bootloader info plz. Unless you were using the experimental CM10.1 build (or a select few others), it sounds like you tried to flash a ROM compatible only with an older bootloader onto the "latest" build (from your description).
Hi,
today I received a security update in my Nexus 5. I accepted it and when rebooted it got stuck in the multirom menu and it didnt update anything. Last time I have to lock the device and flash the rooted image in order to proceed with the update. this time I would like to do it diferently if possible.
Is there any other way to flash the update without removing multirom and locking back the device?
where is the update.zip stored when the system automatically downloads the update? maybe I could manually flash it using the TWRP.
thanks!
Jose
I'm on the XT1540 and I got my OTA notification and went back to stock recovery (still rooted and unlocked bootloader) but it fails halfway through flashing everytime. I reflashed TWRP and captured the OTA into a zip but get an error about updating binary or something when flashing it. Is there something I need to delete from the OTA zip to allow it to flash in twrp?
Sent from my MotoG3 using xda premium
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
HelpMeruth said:
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
Click to expand...
Click to collapse
This...do a full factory image restore, then adb sideload the ota file. It's signed. TWRP can't install it.
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
nikon120 said:
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
Click to expand...
Click to collapse
This...I can't understand, for the life of me, why everyone is wiping userdata with fastboot....that wipes your android data, and internal storage in one shot. Cache erasing is another totally unnecessary step. All that's necessary, at the most, is a factory reset with TWRP to wipe the android data and both caches....but even that shouldn't technically be necessary for an update like this. It's not like this is the marshmallow update!!
arunhebbare said:
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Click to expand...
Click to collapse
@arunhebbare I've got the APAC version of the G3 as well, which ROMs are you flashing? I could only find images of the India version, did you use those?
Hi All,
I have Moto X play running on android 5.1.1 lollipop. It was rooted recently and used with cyanogen Mod 12.1 for a month. during that time i did back up of entire phone. later i restored that and at present i have been using stock Rom. Recently i got official update for Android marshmallow and i downloaded the 500+Mb file and tried to install. In that process it was going to Twrp recovery mode and not installing properly. So i did reboot system. After 5 mins i turned on mobile, it got shutdown and i again restored my backup . It was working fine. cant we update to Marshmallow with the rooted device? If so how to stop the notifications of android system updates? I tried this way but still i am getting update notification
Apps--> All---> Motorola Update services--> turned off the notification
.How to disable it so that i should not receive update notification? or any other process to upgrade to marshmallow even after rooting? Please let me know
Mkrishna89 said:
Hi All,
I have Moto X play running on android 5.1.1 lollipop. It was rooted recently and used with cyanogen Mod 12.1 for a month. during that time i did back up of entire phone. later i restored that and at present i have been using stock Rom. Recently i got official update for Android marshmallow and i downloaded the 500+Mb file and tried to install. In that process it was going to Twrp recovery mode and not installing properly. So i did reboot system. After 5 mins i turned on mobile, it got shutdown and i again restored my backup . It was working fine. cant we update to Marshmallow with the rooted device? If so how to stop the notifications of android system updates? I tried this way but still i am getting update notification
Apps--> All---> Motorola Update services--> turned off the notification
.How to disable it so that i should not receive update notification? or any other process to upgrade to marshmallow even after rooting? Please let me know
Click to expand...
Click to collapse
you need stock recovery to update to OTA mm, you cannot update from TWRP. download the lollipop stock-firmware extract the recovery file and flash it, then update.
i wanted to ask that after restoring from backup you got OTA update notification ? or you downloaded the MM update from other sources?? because i thought after rooting i wont get official OTA.
Mkrishna89 said:
Hi All,
I have Moto X play running on android 5.1.1 lollipop. It was rooted recently and used with cyanogen Mod 12.1 for a month. during that time i did back up of entire phone. later i restored that and at present i have been using stock Rom. Recently i got official update for Android marshmallow and i downloaded the 500+Mb file and tried to install. In that process it was going to Twrp recovery mode and not installing properly. So i did reboot system. After 5 mins i turned on mobile, it got shutdown and i again restored my backup . It was working fine. cant we update to Marshmallow with the rooted device? If so how to stop the notifications of android system updates? I tried this way but still i am getting update notification
Apps--> All---> Motorola Update services--> turned off the notification
.How to disable it so that i should not receive update notification? or any other process to upgrade to marshmallow even after rooting? Please let me know
Click to expand...
Click to collapse
if you have your backup just do a full flash on stock rom and start fresh. there's an Asian 6.0 rom (I believe it is Indian) on the x play github. then proceed with root again.
bablu048 said:
you need stock recovery to update to OTA mm, you cannot update from TWRP. download the lollipop stock-firmware extract the recovery file and flash it, then update.
i wanted to ask that after restoring from backup you got OTA update notification ? or you downloaded the MM update from other sources?? because i thought after rooting i wont get official OTA.
Click to expand...
Click to collapse
Actually i am not android developer or android related person. After i heard many things about rooting the devices. I just give it a try by watching the video in you tube. So i am not aware of the core technical terms you specified.
First rooted the mobile. before installing the cyanogen Mod 12.1, i took back up in TWRP recovery mode. i used that same backup to restore after my device got shutdown. Yes even after rooting i got the Update notification
pijes said:
if you have your backup just do a full flash on stock rom and start fresh. there's an Asian 6.0 rom (I believe it is Indian) on the x play github. then proceed with root again.
Click to expand...
Click to collapse
I did not understand core android technical terms as i am not android guy. You mean to say unroot the device and perform root again?
bablu048 said:
you need stock recovery to update to OTA mm, you cannot update from TWRP. download the lollipop stock-firmware extract the recovery file and flash it, then update.
i wanted to ask that after restoring from backup you got OTA update notification ? or you downloaded the MM update from other sources?? because i thought after rooting i wont get official OTA.
Click to expand...
Click to collapse
Sir, if you have time please browse through Youtube and search for the name "dhananjay bhosale". In his playlists, there will be a moto x play playlist.in the you can find how to root moto........, by this way i rooted my mobile. i dont have any knowledge in android. I just Followed that Video. i could not able to post the link here as i am a new member
Mkrishna89 said:
Actually i am not android developer or android related person. After i heard many things about rooting the devices. I just give it a try by watching the video in you tube. So i am not aware of the core technical terms you specified.
First rooted the mobile. before installing the cyanogen Mod 12.1, i took back up in TWRP recovery mode. i used that same backup to restore after my device got shutdown. Yes even after rooting i got the Update notification
Click to expand...
Click to collapse
i think if you can block/disable notifications for Google Play Services, it'll remove the update notification.
settings>>apps>>google play services>>disable all notifications
bablu048 said:
i think if you can block/disable notifications for Google Play Services, it'll remove the update notification.
settings>>apps>>google play services>>disable all notifications
Click to expand...
Click to collapse
Sir, Is it possible to unroot the rooted devices in any way? if so could you please let me know
if you want to unroot you can do it from superuser, its mentioned in the youtube video. just unroot from superuser settings.
then if you want to upgrade to marshmallow download Indian stock lollipop rom from https://github.com/motoxplay/stock. unzip it on your computer to the the folder where you kept TWRP while flashing it . you'll see a file named recovery.img.
from adb run the command
Code:
fastboot flash recovery recovery.img
i.e flash this recovery just the way you flashed TWRP.
then you can update to marshmallow.
and did disabling google play services removed your update notification???
Mkrishna89 said:
Sir, Is it possible to unroot the rooted devices in any way? if so could you please let me know
Click to expand...
Click to collapse
You just have to download the twrp flashable 6.0 zip file and restore it through twrp. No extra things.
Sent from my XT1562 using Tapatalk
bablu048 said:
if you want to unroot you can do it from superuser, its mentioned in the youtube video. just unroot from superuser settings.
then if you want to upgrade to marshmallow download Indian stock lollipop rom from https://github.com/motoxplay/stock. unzip it on your computer to the the folder where you kept TWRP while flashing it . you'll see a file named recovery.img.
from adb run the command
Code:
fastboot flash recovery recovery.img
i.e flash this recovery just the way you flashed TWRP.
then you can update to marshmallow.
and did disabling google play services removed your update notification???
Click to expand...
Click to collapse
I diabaled. But at present i dont have internet connection to my mobile and i will let you know once i got any notification again about the update.
So as you said can i proceed that above steps with my rooted mobile? i mean flashing the unzip file like i did before? wont be any problem? or i have to unroot and root again after flashing the recovery.img??
Mkrishna89 said:
I diabaled. But at present i dont have internet connection to my mobile and i will let you know once i got any notification again about the update.
So as you said can i proceed that above steps with my rooted mobile? i mean flashing the unzip file like i did before? wont be any problem? or i have to unroot and root again after flashing the recovery.img??
Click to expand...
Click to collapse
Does your phone have twrp flashed or not?
Sent from my XT1562 using Tapatalk
K.khiladi said:
Does your phone have twrp flashed or not?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Yes Twrp flashed and successfully rooted
Mkrishna89 said:
Yes Twrp flashed and successfully rooted
Click to expand...
Click to collapse
Then please download the twrp flashable 6.0 zip and restore it through twrp.
Wait I will provide you the link of the thread.
Read the first post of that thread carefully.
Edit - here is the link, go to the thread, download the Indian one and follow the procedure
http://forum.xda-developers.com/showthread.php?t=3272979
[ROM] 6.0 TWRP Flashable Stock - Brazil / India / Canada versions
Sent from my XT1562 using Tapatalk
Mkrishna89 said:
I diabaled. But at present i dont have internet connection to my mobile and i will let you know once i got any notification again about the update.
So as you said can i proceed that above steps with my rooted mobile? i mean flashing the unzip file like i did before? wont be any problem? or i have to unroot and root again after flashing the recovery.img??
Click to expand...
Click to collapse
Edit: do as the post above this mentions.[i didn't know about that thread but it'll also work]
or
nope no problem just flash the recovery. but before doing anything take a backup on your external sdcard twrp>>backup[look at bottom to change where to store the backup select sd card] for security if in case anything goes wrong, you can flash twrp again and restore.
and remember to select 'ALLOW OEM UNLOCK' and usb debugging options from settings>>developer options
K.khiladi said:
Then please download the twrp flashable 6.0 zip and restore it through twrp.
Wait I will provide you the link of the thread.
Read the first post of that thread carefully.
Edit - here is the link, go to the thread, download the Indian one and follow the procedure
http://forum.xda-developers.com/showthread.php?t=3272979
[ROM] 6.0 TWRP Flashable Stock - Brazil / India / Canada versions
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Ya i got the thread. Before i proceed i want you let you know how i rooted my mobile. please check this link and let me know whether if i do in the way specified in the thread will works for me?
https://www.youtube.com/watch?v=PzQyg9t9j6U&index=3&list=PL3yX1-A8wnSmKqZGL55-7EYPFRol3zuIA
Mkrishna89 said:
Ya i got the thread. Before i proceed i want you let you know how i rooted my mobile. please check this link and let me know whether if i do in the way specified in the thread will works for me?
https://www.youtube.com/watch?v=PzQyg9t9j6U&index=3&list=PL3yX1-A8wnSmKqZGL55-7EYPFRol3zuIA
Click to expand...
Click to collapse
Just follow the procedure as given in that thread and everything will be fine.
It has nothing to do with the way you rooted your phone.
If a phone has twrp installed, he has nothing to fear about upgrading to latest versions as the updates are made available on Xda in Twrp flashable zip.
So no need to format the stock firmware again and then update and then all the headache.
Sent from my XT1562 using Tapatalk
bablu048 said:
Edit: do as the post above this mentions.[i didn't know about that thread but it'll also work]
or
nope no problem just flash the recovery. but before doing anything take a backup on your external sdcard twrp>>backup[look at bottom to change where to store the backup select sd card] for security if in case anything goes wrong, you can flash twrp again and restore.
and remember to select 'ALLOW OEM UNLOCK' and usb debugging options from settings>>developer options
Click to expand...
Click to collapse
Sir, In your previous post you meant to say this?
1. First unroot the mobile using the super Su (settings)
2. Then flash the Stock lollipop rom mentioned in the github
3. Then update the mobile to Marshmallow
4. Then again root the device
You meant to say this?
Mkrishna89 said:
Sir, In your previous post you meant to say this?
1. First unroot the mobile using the super Su (settings)
2. Then flash the Stock lollipop rom mentioned in the github
3. Then update the mobile to Marshmallow
4. Then again root the device
You meant to say this?
Click to expand...
Click to collapse
1. correct
1.1. check oem unlock and usb debugging
1.2. Copy the original old backup which you took, to your external sdcard. [just to return to stock if anything goes wrong]
2. Just flash the recovery which is present in the lollipop rom, no need to flash the whole rom.
3. correct
4. Do NOT flash the old superuser to root. To root again follow these steps http://forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
that other post was much easier
bablu048 said:
Edit: do as the post above this mentions.[i didn't know about that thread but it'll also work]
or
nope no problem just flash the recovery. but before doing anything take a backup on your external sdcard twrp>>backup[look at bottom to change where to store the backup select sd card] for security if in case anything goes wrong, you can flash twrp again and restore.
and remember to select 'ALLOW OEM UNLOCK' and usb debugging options from settings>>developer options
Click to expand...
Click to collapse
Hi Sir, I followed the other method. downloaded the twrp 6.0 zip from the thread. extracted to sdcard/twrp/backups.
wiped the data, restored that. after that i flashed the Super Su and reboot system. but it was stuck at motorola logo. in that description this will happen if we choose install super su. But i didnt do that.but still stuck at motorola logo.
so again i tried and now with out flashed Super su and downloaded super Su from google play,. getting error binaries cannot be updated. please help me
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?