Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
There is no need to relock your bootloader.
The reason the OTA-Update fails, is that one of the /boot, /system, /logo or /recovery partitions are changed.
For example the /recovery if you flashed it permanently or the /boot partition for rooting. Also the /system partition when you remove same build-in apps or install xposed and do not reverse the changes.
To restore the partitions you have to flash the stock ROM Images of the partitions.
That's all you have to do!
Most of you have the problem that they can't find the right stock ROM with the correct build-no. (or don't have access to the FileFactory folder).
In desperation you just download any stock ROM that contain "XT16xx" and flash it, without any idea what you are doing.
And that is the reason your phones lost the IMEI no.
There is also another problem with changing /system or /boot after the OTA-Update, because usually Motorola don't release a stock ROM image which include the OTA-Update when the next OTA-Update should be a major update to the next Android Version (6.0.1 -> 7.0). So when you make some changes to /system or /boot (rooting) after the OTA-Update you have no stock ROM image files of the current build-no and you have to flash the hole stock ROM image and erase all your data and take then two OTA-Updates (6.0 -> 6.0.1 -> 7.0) to get Android 7.0.
This is the reason you should make a TWRP backup of /system and /boot to restore it and then take the next OTA-Update, maybe to Android 7.0.
[GUIDE]
ONLY FOLLOW THIS GUIDE IF YOU HAVE THE CORRECT STOCK ROM IMAGE !!!
STOCK ROM IMAGE FILE NAME MUST CONTAIN YOUR CURRENT BUILD-NO AND SKU (e.g. XT162) OF THE PHONE !!!
I am not responsible for any damage or failure on your smartphone.
Requirements:
Correct Stock ROM Image for your phone -> FileFactory Moto G
Minimal ADB & Fastboot
Motorola Drivers
TWRP - Custom Recovery
1a. If you get the OTA-Update notification
If you are rooted and the OTA-Update notification pops up, download the update and hit the "later" button. Go with your fav. Filebrowser to:
Code:
/data/data/com.motorola.ccc.ota/app_download
and copy the OTA-Update "Blur_Version.2....." file to your SD-Card.
Go to 2. ↓
1b. If you don't get the OTA-Update notification because you already try to install it and get "error 7"
First option is to wait and drink some cups of tea till the notification popup again and try 1a. ↑
Second option is to go to 2. ↓, but then you have no root access till the notification popup up again.
2. Restore the stock ROM images
Extract only the boot.img, logo.bin, recovery.img, system.img_sparsechunk.0 to .7 files to the MADB&FB folder.
Connect your phone to your PC and open MADB&FB, check the connection with:
Code:
adb devices
return should include your "serial-no" and "device".
Reboot into bootloader with:
Code:
adb reboot-bootloader
and check again with:
Code:
fastboot devices
return should be "serial-no" and "fastboot".
Flash the partitions with:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
After every command should be a return with "OKAY".
Reboot your Phone with:
Code:
fastboot reboot
After reboot all your data is still there and you can sideload the OTA-Update, if the OTA-Update notification has not already appeared.
3. Sideload from SD-Card
Reboot into recovery:
Code:
adb reboot recovery
After few seconds the dead "Android" should appear with "No command."
HOLD "Power" and then HOLD "VOLUME UP" for 2-1 seconds and release. Now you are in "Android Recovery".
Select "Apply update from SD card" and choose your "Blur_Version.2..." file.
After 20-30 min you get "success" message and select "Reboot system now".
4. Make a backup of /system, /boot, /recovery and /logo
Before you can make some further changes on your /system, /boot, /recovery and /logo, you should backup these partitions for the next OTA-Update.
Follow all steps in the Guide to root systemless -> [ROOT][GUIDE] Systemless Rooting with SuperSU 2.78 , which include the TWRP backup (/system and /boot).
Then come back here and install on your rooted phone -> Partitions Backup & Restore.
Select "LOGO" and "RECOVERY" and change Settings to "Raw partitions image (img)" and save it on your SD-Card.
Now you have all partitions as a backup for the next OTA-Update. So when the next update is coming, you have to flash /logo and /recovery and then restore your TWRP backup and you are able to install the update without issues.
Have Fun and don't pay attention to my writing errors
Bender1987 said:
Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
You can root your phone again with this GUIDE after the update -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
There is no need to relock your bootloader.
Click to expand...
Click to collapse
I used this procedure a couple of days ago and it worked flawlessly. When I rebooted after flashing all of the stock files, my OTA update notification was there waiting for me to select "Install". I did and it installed without issues.
What is surprising to me is how many people try it with the wrong firmware and then are surprised when they screw up their phones.
I was so close!!! lol, didn't realize they checked /logo for modifications. Was about to completely wipe everything to get the update to apply. Glad I checked xda before doing so as all I was missing was flashing stock logo.img (restoring system, recovery and boot I had already tried). Thanks Bender1987 for the easy guide.
I have the 64GIG 4G plus (XT-1644)
Hi @Bender1987,
Thank you for your guides, they are very helpful. I've already unlocked, rooted without flashing twrp, uninstalled some system apps and flashed xposed using Flashfire on my xt1642, and eveything is running fine so far. So, when an OTA update is available (hopefully nougat!) will I receive the notification? Or does the rooting stop even OTA notifications? Thanks!
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Bender1987 said:
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Click to expand...
Click to collapse
I just got my xt1642 a week ago. It already came with build number: MPJ24.139-48 which I think is the latest, so I haven't received any OTA update yet.
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Bender1987 said:
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Click to expand...
Click to collapse
Well, I spent 2 days without touching the phone before unlocking/rooting and didn't receive this ota-update. Maybe it is not available for my version (32gb, 3gb ram, xt1642)...
If I didn't flash twrp, I guess I won't need to restore it, right? Anyway, I made the full backup following your instructions. In which partition is stock twrp included? Boot? Thanks.
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Bender1987 said:
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Click to expand...
Click to collapse
Let me know if I understood it right. I made a TWRP backup of untouched boot, system and data, rooted and installed xposed without flashing TWRP and without changing logo.bin. Then I should be able to install next OTA update if I previously restore my copies of boot and system in TWRP. Right? No need to flash stock images in this case? Thanks!
@pblasi jep you are right
Xt1644 not play nice with adb nor does it go into recovery it just reboots when I hold the buttons...or it stays on no command
All devices have stock recovery on it. I tried it again, when you see the dead Android -> HOLD POWER and then HOLD VOLUME UP for 2-3 sec. -> release VOLUME UP and still HOLD POWER
https://www.youtube.com/watch?v=SuOrl7Q4JY8
at 1:58.
When I flash the files, for the boot and recovery I get a warning that the "image not signed or corrupt". Eventually it is written... but is that normal?
mfastboot flash recovery recovery.img
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
Image not signed or corrupt
OKAY [ 0.153s]
finished. total time: 0.684s
Click to expand...
Click to collapse
@SoNic67
Maybe it is not the correct stock rom?
Hmm, it was DL from the usual place, but true, I am not 100% sure about it. However, it "works" but I don't get the OTA.
I am DL now the newer full FW.
LE: That latest full FW worked. I had to reinstall all my apps from backup but...
Weird thing is that before my imei disappeared I was getting the ota updates
Sent from my 6045X using Tapatalk
@Bender1987 I have a TWRP backup of unmodified Stock ROM XT1643, so now to install OTA do I just have to flash the nandroid backup & then flash stock recovery to get ota updates? If so then how can I go about flashing stock recovery. Thanks in advance mate
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Bender1987 said:
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Click to expand...
Click to collapse
Will try
Related
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Do a factory reset
Do NOT use toolkits!
My first advice is: Do NOT flash using toolkits! You never know what's exactly going on if you don't do it manually. There are plenty of reasons why to not use them...
Okay, now my second advice: Don't flash cache partitions. Caches are built during boot/runtime. However, as far as I know, a corrupted cache partition can lead to bootloops - so it's better to just wipe them before boot...
I don't know what the toolkit did and what not - but try to follow these steps:
1. Install fastboot and adb
Preferred method is via Android Studio command line tools from official source: http://developer.android.com/sdk/index.html - Scroll down to "Get just the command line tools". You can decide between an installer or just a zip. It's your choice.
2. Boot your phone in bootloader mode and execute these commands one by one...
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp-recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Use the proper files! Extract bootloader and radio from latest Google factory image and download TWRP from twrp.me!
3. Boot your phone into TWRP and choose wipe -> DO NOT SLIDE TO FACTORY RESET -> advanced wipe -> cache + dalvik ticked, rest unticked -> slide to wipe
4. Try to boot...
Not sure if it works - but that's the only thing I can think of right now
EDIT: @GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!
experience7 said:
@GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!
Click to expand...
Click to collapse
Then he should do all the ota's instead of flashing the factory image
Sent from my XT1562 using XDA Labs
Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?
experience7 said:
Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?
Click to expand...
Click to collapse
Because you have to factory reset the device. That's the downside of being rooted and wanting to update, especially with M
I'm sorry to say that you're terribly wrong. I hope you didn't factory reset your device every single time you did an update just because you're rooted! Actually you can use the flash-all.bat file that's provided with the factory image. Just remove the "-w" flag from the "fastboot update" command. This will stop fastboot from wiping your /data partition.
That's what the OP could use as well - however, for his better understanding I listed the commands separately.
For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Start to finish - 15 minutes, including the rebuilding of the apps. No data loss (because you haven't touched the data/userdata partition).
I don't say that every step is essential (I note the comment from experience7 about cache) - but this works fine for me.
Please feel free to amend or correct...
dahawthorne said:
For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Click to expand...
Click to collapse
Same problem again. I'm trying all 6.x.x versions but same problem. All commands running without error.
In that case all I can suggest is that you bite the bullet and run the flash-all.bat. Back up all your important stuff (photos, etc.) because you'll lose them.
I've seen it suggested often that you should always do a full wipe when upgrading between major versions (e.g. 5 to 6), so maybe this will fix your problem and give you a working phone even if you lose some data and have to set up from scratch.
P.S. Please "Quick reply" - don't repeat the entire previous post. We've all read it; we don't need to read it again.
marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Search for a full guide thread. I'm sure you will come out with something.
Sent from my GT-I9505 using XDA-Developers mobile app
"Search for a full guide thread. I'm sure you will come out with something."
Excellent advice. It's amazing that so many experienced senior members with all their years of combined knowledge missed that blindingly obvious idea...
Problem solved by unfreezing all frozen apps from Titanium Backup before upgrade.
Thank you!
Hey guys,
I was using a NXT-TL00 with Android 7.0 and EMUI 5.0 and I wanted to change to a international ROM with Nougat and EMUI 5.
My current situation:
I unlocked the bootloader.
I can boot into fastboot and flash twrp-3.0.2-0-next.img
I can boot into that TWRP and flash MATE8-TL00-EMUI5.0_B577.zip. (Thanks again, paulcl!)
I can boot into that ROM and use it.
I changed my oeminfo and custom.bin from TL00 to L29 via SRKToolHuawei. Afterwards I had to unlock the bootloader again.
I tried to:
extract various update.zip (update.app inside of the zip) via HuaweiUpdateExtractor_0.9.9.5.
flash the extracted boot.img, recovery.img, system.img via fastboot manually and SRKToolHuawei.
wipe and format data, dalvik, cache, system in- and excluding reboots in every possible variation.
use different TWRP versions.
However:
I can't boot into stock recovery (even after flashing it).
I can't boot into eRecovery.
I can't flash any update.zip oder other ROM besides the one above. Why?
Using eRecovery or stock recovery won't work since I can't boot into it.
TWRP would print this error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link typ file...
write radio image...
check_write_data_to_partition, write data error
E:unknown command [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NXT-TL00C01B575/update.zip'
I can't flash any system.img via fastboot. I would get this error:
fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (452422 KB)...
OKAY [ 13.007s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 13.045s
What I want:
A fully working TWRP so I can simple flash an update.zip
A working (stock?) L29 ROM with Android 7 or 6 and Emui 5 or 4 and preinstalled GAPPS.
A working stock recovery and erecovery
OTA support
the possibility to lock bootloader when everything else is working
What might help:
A ROM which won't touch the data partition so I can install it trough TWRP.
Maybe there is a way to put the system.img into a flashable zip-file so I can flash the partition via TWRP so there won't be the error message from fastboot. Unfortunately, I have no idea how to do that. An TWRP doesn't allow to flash system.img directly.
BTW:
My current model number is: NXT-L29
My current build number is: "NRD90M test keys"
EMUI-Version 5.0, Android Version 7.0
Thanks for reading through my text. It would be great if there is someone to help me out here!
hello i have the EXACT same problem except i was on a l29C at the beginning..
i m stuck here 2 days now
if somebody have a solution i greatly appreciated
Install stock kernel and the use hisuite
asphaltkiller said:
hello i have the EXACT same problem except i was on a l29C at the beginning..
i m stuck here 2 days now
if somebody have a solution i greatly appreciated
Click to expand...
Click to collapse
I already found a solution which is not perfect yet. First, I tried to follow the instructions from
How to install NXT-L29C432B560 (Official) Stock Firmware. (Guide with download links) by sillanwali.
Very helpful for me was post #49. I recommend to read through the first post and then coming back and follow the instructions below.
First, you need:
TWRP 3.0.3 (...3 is for Nougat)
this update.zip
MATE8-TL00-EMUI5.0_B577.zip
The procedure might be too long with redundant steps, but it worked for me. So give it a try:
Unlock bootloader
Flash twrp via fastboot(3.0.3 is for Nougat)
fastboot flash recovery twrp-3.03.img
fastboot reboot
Boot into TWRP
Copy update.zip and MATE8-TL00-EMUI5.0_B577.zip to SD.
Wipe>format Data>yes
Wipe>Advance wipe >data, dalvik, cache, system
Install this update.zip linked above.
Try to reboot into system. Mine didn't boot into system, but stock recovery and erecovery are now installed. Go on!
Flash TWRP again (since it's overwritten by stock recovery. No worries - you now can now easily flash back stock recovery).
Boot into TWRP.
Copy MATE8-TL00-EMUI5.0_B577.zip to SD Card.
Again, do a full wipe.
Install MATE8-TL00-EMUI5.0_B577.zip.
Reboot into system. It now should work, however it's the Chinese version.
Extract the update.zip and copy update.app to a new created DLOAD folder on the SD Card.
Do a factory reset.
Flash the stock recovery via fastboot (or TWRP). You will get the image by extracting recovery.img of update.app with HuaweiUpdateExtractor.
Reboot into recovery to install the update.app (automatically).
Now you should be on NXT-L29C432B560.
If you want to use the update_data_full_hw_eu.zip or SuperSu follow the instructions in the How-to-install guide.
To be clear, I still have a few problems:
erecovery would boot but when I am trying to restore via wifi I will get the error: "getting package info failed"
Bluetooth and NFC are not working.
Maybe someone has a solution for that?
sebastjon said:
Bluetooth and NFC are not working.
Click to expand...
Click to collapse
Make the installation again!
New update for Moto G4/4+ started rolling (NPJS25.93-14-8). It has 56MB and it contains the 1st June 2017 security patch.
You can download it from here and install it by flashing it from SD card or sideloading it.
https://drive.google.com/file/d/0B_CvjgZQDGNDNFNIME5XNjRubFE/view
thanks a lot, here in my country barely i received nougat.
Would it make any issue if I have my device with a different kernel than the stock one? For rooting it I had to flash Elemental-X kernel (Moto G4 Plus).
Thanks.
cesardemi said:
Would it make any issue if I have my device with a different kernel than the stock one? For rooting it I had to flash Elemental-X kernel (Moto G4 Plus).
Thanks.
Click to expand...
Click to collapse
For flashing the OTA, you must flash to stock Nougat rom (including kernel), otherwise the phone will enter in bootloop. After you install the OTA, you can flash the EX kernel and root it again.
A few other things to note about this update:
Looks to require NPJS25.93-14-4 (the March 2017 v7.0 update) to install from (that fastboot update is here if you need it: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )
Bootloader updated to B1.06 (March 2017 had B1.05) - I imagine this fixes the critical security vulnerability as noted in the May 2017 security update (CVE-2016-10277 https://source.android.com/security/bulletin/2017-05-01#eop-in-motorola-bootloader ) EDIT - it seems that once this patch is flashed, downgrading your device (especially when flashing the GPT/bootloader from an older stock ROM) may well risk bricking your device! This brick may also occur if you downgrade from this build without flashing GPT/bootloader and then install an OTA. Be aware.
Boot animation now has 'Motorola, a Lenovo company' at the bottom (not sure if that was there previously) when the logo flips from Lenovo to the M symbol.
IMEI SV seems to be changed to 9 (think it used to be 8).
New logo seems to appear when charging with the device off (before the battery gauge appears)?
Also, if your OTA download is in your Download folder, when you're in stock recovery, I had issues trying to 'apply update via SD card'. Seems that 'mount /system' allowed me to navigate to the Download directory (don't know if that applies to everyone).
I was previously rooted on the March update with magisk v13 and ElementalX. I attempted to revert back to stock by:
Booting back into TWRP
Using the magisk uninstaller (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot to bootloader
Then using the following commands in adb to flash a stock NPJS25.93-14-4 boot and recovery image.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
However, upon trying to flash the OTA in the stock recovery, I encountered an error 7 (I think it was failing to load or verify system).
Flashing the following partitions from the NPJS25.93-14-4 stock ROM allowed me to flash the OTA in the stock recovery without erasing my data (bear in mind I was already fully updated to NPJS25.93-14-4 before rooting. I've also got a TWRP backup and Titanium backups to fall back to.) This should not affect your data, but ensure you have your data backed up regardless (always good practice when flashing anything that touches your system). I am not sure if all these partitions are required to flash the OTA if you were previously rooted. As always, if you're using these commands to roll back to stock from a rooted stock system, be prepared to factory reset if your system is not stable.
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Now I'm on the June 1 2017 update on a retgb XT1642 Thanks @georgeiulian89
Now to try and root this build
Flashed the zip from stock recovery. No issues
Thanks
Sent from my Moto G (4) using XDA-Developers Legacy app
Flashed on my XT1622. Can't say any good or bad about it.
Edit: The battery statistics seem to be more detailed now, first time ever that I have seen Firefox in it.
I tried to sideload the zip from my recovery. When I select Apply update from SD Card, the screen turns blank except for the
ge 0/0
Supported API: 0
None other keys are working.
I tried many times and still has no improvement. I am on Stock NPJS25.93-14-4
arunzone said:
I tried to sideload the zip from my recovery. When I select Apply update from SD Card, the screen turns blank except for the
ge 0/0
Supported API: 0
None other keys are working.
I tried many times and still has no improvement. I am on Stock NPJS25.93-14-4
Click to expand...
Click to collapse
Sideload it from the PC.
Just need to put it out there - Do not try to downgrade after you have upgraded to the latest OTA. I did. Hard bricked my phone.
georgeiulian89 said:
Sideload it from the PC.
Click to expand...
Click to collapse
I had sideloaded it via ADB but was curious to know about the issue. Do you have any idea about how to sort this issue?
arunzone said:
I had sideloaded it via ADB but was curious to know about the issue. Do you have any idea about how to sort this issue?
Click to expand...
Click to collapse
Do you have an SD card, and if so, what card is it? Just wondering if having an SD card might allow the recovery down as it reads?
echo92 said:
Do you have an SD card, and if so, what card is it? Just wondering if having an SD card might allow the recovery down as it reads?
Click to expand...
Click to collapse
Yes. I have Samsung Evo Plus 64 GB MicroSDXC Card. I tried place the zip file in internal memory and sd card. Still no improvement.
I also tried after removing the SD Card.
Can i flash it on my Indian version of moto g4 plus build no. Is NPJS25.93-14-4
VivekBhagat said:
Can i flash it on my Indian version of moto g4 plus build no. Is NPJS25.93-14-4
Click to expand...
Click to collapse
yes, you can.
arunzone said:
yes, you can.
Click to expand...
Click to collapse
Okk thanx
echo92 said:
Now to try and root this build
Click to expand...
Click to collapse
Did you succeed?
anirudh.m said:
Did you succeed?
Click to expand...
Click to collapse
Just install Vegito 6.6/EX kernel and flash superuser 2.79SR3.
Adb sidelined update worked thanks
i flashed 93-14-4 then this ota,rooted and working fine thanks
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
1. Get your bootloader unlocked as we will require it once, to take a nandroid backup for safety.
2. Install TWRP 3.1.1.0 to make a nandroid backup on phone.
3. Once backup is done copy it from phone to PC to make it safe. It will take some time as mine was 6GB in size.
4. Before rebooting into fastboot select "Do not install TWRP" in recovery.
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
6. Reboot into recovery and clear cache and userdata partitions. Reboot normal now.
7. Phone will start the setup like after factory reset. Just skip restoring your personal data by answering No to save time. But let it complete whatever else it do. Now "About phone" will say device is Moto X Style and build is MM 6.0.1 RETEU.en. This is just fine. Phone converted (No GSM signal is no worry at this time).
8. Try System Update. If update is available fine, otherwise we do it manually to take it to MPHS24.107-58-13 (required as Nougat pre-requisite).
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
10. Again boot and skip Android setup. About phone will say your current build version.
11. Now download and copy Blur_Version.24.231.13.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
12. Boot into recovery and choose Apply the file from SDCard. WOW this is Nougat update. It will successfully complete the update.
13 Download Last official Clark MM stock ROM from Motorola website and open the zip file to extract NON-HLOS.bin and fsk.mbn and flash it from fastboot in the standard way.
14. Go into recovery and clean cache and userdata partitions
15. Boot normally to be greeted by Nougat firsttime setup.
16. Congratulations. You have Nougat and Moto X Style.
No links to files?
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
What about ota?
Bart_UA said:
What about ota?
Click to expand...
Click to collapse
There are two files I mentioned that starts with the name "Blur_Version". These are always OTAs!!! You apply through Wifi or SDCard, what is the difference?
This is my About Phone screen after the update.
jaffers said:
This is my About Phone screen after the update.
Click to expand...
Click to collapse
You can do backup with twrp and upload it for them.
Boot(before root)+system only.
Root is not required in my steps and TWRP not installed permanently (See my steps).
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Very simple. people like me don't want to loose Moto Action, Moto Display and Moto Voice. You loose all that in custom roms. I tried Lineage in my wife's Moto X 2014 a month ago. Frequent reboots, crash and reboot during video recording etc. This after several months of constant updates. Stock ROM do not have this type of issues. Atleast in the last decade not once any of my phone ever rebooted on its own. So I don't approve custom roms. If you don't mind, go ahead.
dzidexx said:
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Click to expand...
Click to collapse
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
jaffers said:
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
Click to expand...
Click to collapse
Yes. Now you shouldn't.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Stock Nougat is getting August security patch rigth now!
Dual sim
Is it dual sim supportable after updating?
NahuelMS said:
Stock Nougat is getting August security patch rigth now!
Click to expand...
Click to collapse
Blueborne is fixed in September security fix.
jaffers said:
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
11. Now download and copy Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
Click to expand...
Click to collapse
Hi, downloading the necessary files to upgrade my phone and I see you show the same file to download in steps 9 and 11. Is this file being installed twice?
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
Click to expand...
Click to collapse
I completed the steps up to this one. I want to make sure I don't accidentally flash everything.
So noob question, what files do I not fastboot? I know boot and recovery. Appreciate the help.
NON-HLOS.bin
fsg.mbn
BTFM.bin
flashfile.xml
servicefile.xml
slcf_ref_d_default_v.1.0.nvm
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
any possibility to flash custom recorvery/root on android 7? When im flashing recorvery via fastboot it says "permission deined"
nvm im dumb, misswrite a single letter in fastboot
I find this post a bit hard to read.
1). You are not really clear on exactly what to flash. You are close but not precise. If you are going to provide instruction like this you might need to be a bit more granular.
2). You mention the same file twice for both the pre-requisite patch and the nougat update. Are then both one in the same? This doesn't make sense.
I followed these instructions up to step #7. I flashed the following files:
logo.bin
BTFM.bin
fastboot flash bootloader bootloader.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
I left out the following:
boot.img
fsg.mbn
gpt.bin
NON-HLOS.bin
recovery.img
My phone is showing Moto X Style however my build # is MPHS24.107-58-5 and not MM 6.0.1 RETEU.en
System version is reporting 24.221.5.clark_reteu.reteu.en.EU retus
If I try to move forward with the MPHS24.107-58-13 update I get a digital signature error.
jaffers said:
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
Click to expand...
Click to collapse
Bricked my OP8T (unlocked bootloader, rooted) in a failed OS update attempt. I'm pretty sure I was running OS 11.0.8.12, attempted updating to 11.0.11.11 following Magisk OTA update instructions to keep root. It seemed to mess up as when I viewed OS info, 11.0.8.12 was still listed, but then phone calling, wifi, audio all were broken. So I then attempted the local upgrade option, which didn't work at all. After rebooting, found myself in Qualcomm crash boot, but was able to still get to fastboot using Vol Up + Vol Down + Power key combination.
I've attempted switching active boot slots and that didn't fix anything. My slot a seems to have considerable issues so been trying to reflash images to b slot. I've extracted all images from payload.bin from both 11.0.8.12 and 11.0.11.11. I also have magisk patched boot images for both versions of OS's on my PC. When I've attempted flashing 11.0.11.11 system image, I get errors regarding can't resize partition, not enough space. I've tried 'Fastboot delete-logical-partition product', but still received same error. So I've thought, I'll just reflash the 11.0.8.12 images and try to get my phone back to bootable.
I've ran the following commands to attempt to get back to bootable phone:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot bootloader
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot--disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot bootloader
Issue is now that whenever I attempt to reboot the phone, it automatically boots back into fastboot :/ I've attempted wiping the cache too in hopes it would help but no dice.
Curious if there is a way to recover the phone without wiping my data partition. I've got most apps and settings backed up but it's still a hassle I'd prefer to avoid. Would it be possible to boot into TWRP using 'fastboot boot twrp.img' to pull the user data partition to local pc? Then wipe the phone and install fresh OS? I've heard that twrp can't decrypt the user data partition for stock OP Roms?
TWRP have always been able to decrypt user data for stock OOS roms. The latest twrp version can even flash OOS rom (thanks to a patch by a helpful community member).
If I where you I would try to boot latest TWRP and see if that can decrypt the data (do not freak out if it can't there might still be a way to save the data).
If it can decrypt data I would perform a backup of the data partition and then copy your whole internal sd over to your computer just to be safe.
After that I would try to flash the latest OOS ota in TWRP and see if that fixes it. If not you can try to format data and reboot. If that fixes it you can just restore your data backup. If that don't work I would use the MSM tool and then unlock bootloader and restore data backup.
If TWRP are unable to decrypt the data I would sideload the OOS ota in TWRP and see if that fixes it (it did for me when I had a similar problem). If not your data is lost and you might need to use MSM tool.
I would wait to install magisk until I made sure everything boots without it.
Qnorsten said:
TWRP have always been able to decrypt user data for stock OOS roms. The latest twrp version can even flash OOS rom (thanks to a patch by a helpful community member).
If I where you I would try to boot latest TWRP and see if that can decrypt the data (do not freak out if it can't there might still be a way to save the data).
If it can decrypt data I would perform a backup of the data partition and then copy your whole internal sd over to your computer just to be safe.
After that I would try to flash the latest OOS ota in TWRP and see if that fixes it. If not you can try to format data and reboot. If that fixes it you can just restore your data backup. If that don't work I would use the MSM tool and then unlock bootloader and restore data backup.
If TWRP are unable to decrypt the data I would sideload the OOS ota in TWRP and see if that fixes it (it did for me when I had a similar problem). If not your data is lost and you might need to use MSM tool.
I would wait to install magisk until I made sure everything boots without it.
Click to expand...
Click to collapse
Unfortunately I wasn't able to get TWRP to decrypt my data :/ Tried using TWRP with stock boot image flashed as well as with magisk patched boot image.
Tried using the following guide here to see if I could make it happen while saving my data but was unsuccessful. Ah well, glad I use Swift Backup and SMS Backup & Restore. Should make restoring phone to prior state a bit easier, but still a little pain in the butt.
I'm pretty sure I've run into issues in the past with upgrades on OnePlus and new versions not being able to decrypt previously encrypted user data. Hence why I was resistant to upgrading for the last 5 months. Hopefully the upgrade to the december update goes a little smoother.
Appreciate the advice/guidance @Qnorsten!
Sorry to hear that didn't help. I never had any problems with any updates, except when I was messing around with TWRP and that was my own fault.
Older OOS versions can't decrypt data from newer versions but if you flash a newer one it should work.
Have you tried sideloading the latest full OOS ota zip in TWRP?