Related
Hi guys,
Im from the UK and I have a Moto G XT1032 device which was running Cyanogenmod 12 up until yesterday when I decided to re-install the stock rom. Unfortunately, I have well and truly botched it. The current situation is that I have TWRP set up as the recovery image, so I can get into 'AP Fastboot Flash Mode (S)' OR into TWRP.
I accidentally wiped the 'system' via TWRP which seems to have caused most of my problems. I have tried to install the stock rom using a flashable zip (which failed) and I have also tried around 10 times to install the stock rom using the fastboot commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
When I try to do a basic wipe using TWRP, this is what shows up: hxxps://s27.postimg.org/r1dax21mb/falcon.jpg (change xx for tt, I don't yet have 10 posts so I cannot post links)
I just cannot seem to get the stock rom installed and booting no matter what I try. Can someone please work with me to get this sorted?
I would very, very much appreciate the help.
Thank you
Ok so i've managed to fix the 'unable to mount storage' issue via TWRP. I changed 'data' to EXT4 and I don't get any errors now.
But the problem is, for whatever reason, I am just unable to install a stock rom. I've used tutorials and still cannot seem to get a stock rom to load/work.
I used fastboot to install the rom files is this zip: XT1032_FALCON_TESCOGBSL_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
When I do a normal boot it gets stuck on 'Warning bootloader unlocked'
When I go to 'recovery', it boots up to a dead android which says 'no command'
When I go to factory restore, it gets stuck on the 'Warning bootloader unlocked' screen
What am I doing wrong?
edit: I even tried sideloading cyanogenmod and it said it was successful, but then it boots up to TWRP. Totally confused! In desperate need of help.
EDIT: I have now made progress. Here are my basic instructions:
put all the files from the zip file in a folder
put mfastboot.exe files into the same folder
install TWRP, erase
run bat file (add/remove sparse depending on files)
reboot and wait. Should work
I have managed to install the OS but wifi isn't working. And i'm now learning about a file called persist that I need to look into regarding wifi.
TRY THIS AT YOUR OWN RISK! MAKE A NANDROID BACKUP BEFORE MAKING ANY CHANGES!
So, you have rooted The phone flashed EX kernel and then Rooted via SuperSU/Phh's Superuser/Magisk v 12.0
Find the stock Kernel of the version you are on, since this OTA needs you to be on 25.93-14, therefore, you can find the boot.img of the stock kernel. here and stock recovery here
Next would be to un-root the phone,
ANY FLASHING HERE NEEDS TO BE DONE IN CUSTOM RECOVERY. ( I know you know it, but Just a reminder)
1. SuperSU - use the un-root option,
2. Phh's Superuser - just uninstall the apk and then flash the stock boot.img
3. MagiskSU - Use the magisk uninstaller here
3 simple Steps to follow: (Please follow the order, as flashing the stock boot.img on the rooted phone can bootloop it! And nothing will help then except flashing the stock ROM.)
1. Make sure you redo any changes done to the System. (cannot guarantee if the OTA will succeed after this). The changes done by Magisk will be reverted as soon as you flash the uninstaller, so nothing to worry about that.
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important) IGNORE IF ROOTED BY SUPERSU. USE APP UNROOT OR RESTORE THE NANDROID MADE BEFORE ROOTING
3. Connect the phone Via PC and then in bootloader mode flash the stock boot.img and recovery.img
Take the OTA of approx 40MB and then u can root the phone again!
Done!
I have also replaced the boot warning picture with a custom one. Wonder if I need to reverse this... I don't have the stock warning pic.
Maybe I should flash the system and logo completely, keeping the user data.
SoNic67 said:
I have also replaced the boot warning picture with a custom one. Wonder if I need to reverse this... I don't have the stock warning pic.
Maybe I should flash the system and logo completely, keeping the user data.
Click to expand...
Click to collapse
Yess, that needs to be brought back to stock... flashing the logo file in the stock firmware should do the trick... I have never tried it though!
I have re-flashed the 93-14.4 with the file that I have received. Well... it seems that the retention is gone. Again.
I uninstalled the root, flashed the stock recovery and removed any root apps on the phone. Still the update wouldn't work and I won't go as far as re-locking my bootloader in order to install a update that only patches some vulnerabilities that this device has been vulnerable to for at least 6 months. When I tried to install the update it would fail every time.
I did use the fastboot to re-flash the system and logo, keeping my data untouched. The "noerase.bat" file contains:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 erase cache
fastboot reboot
j0nas_ said:
I uninstalled the root, flashed the stock recovery and removed any root apps on the phone. Still the update wouldn't work and I won't go as far as re-locking my bootloader in order to install a update that only patches some vulnerabilities that this device has been vulnerable to for at least 6 months. When I tried to install the update it would fail every time.
Click to expand...
Click to collapse
How did u root the phone?? SuperSU? U don't really need to uninstall the the root apps as after unroot they do not function!!
Did u alter the system? Like made any user app as system app??
SoNic67 said:
I did use the fastboot to re-flash the system and logo, keeping my data untouched. The "noerase.bat" file contains:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 erase cache
fastboot reboot
Click to expand...
Click to collapse
What's the error that u are getting after this??
Ideally, u should flash only system file!! Recovery and System 1-7!
abhi212b said:
How did u root the phone?? SuperSU? U don't really need to uninstall the the root apps as after unroot they do not function!!
Did u alter the system? Like made any user app as system app??
Click to expand...
Click to collapse
I rooted with superuser.zip with phh's superuser app. Got it somewhere here on xda and it has worked fine. Some root apps caused a bootloop, either gnuroot or root essentials or both. I just remove most root apps that may interfere with the bootup when I unroot even if they can't do anything after the unroot.
j0nas_ said:
I rooted with superuser.zip with phh's superuser app. Got it somewhere here on xda and it has worked fine. Some root apps caused a bootloop, either gnuroot or root essentials or both. I just remove most root apps that may interfere with the bootup when I unroot even if they can't do anything after the unroot.
Click to expand...
Click to collapse
Ohkay! did u flash EX kernel? Did u bring back that to stock??
abhi212b said:
Ohkay! did u flash EX kernel? Did u bring back that to stock??
Click to expand...
Click to collapse
Yes, I backed up the stock one before I flashed it for the first time.
j0nas_ said:
Yes, I backed up the stock one before I flashed it for the first time.
Click to expand...
Click to collapse
If everything's stock, there should not be any problems in taking an OTA!
You can go here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
And download the stock rom and flash only system files, just in case any messing up to the system was done.
Make a nandroid 1st.
Just flash systemsparse 0-7..
If that doesn't help...Flash all of these!
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 erase customize
fastboot erase clogo
This should do the trick.
abhi212b said:
If everything's stock, there should not be any problems in taking an OTA!
You can go here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
And download the stock rom and flash only system files, just in case any messing up to the system was done.
Make a nandroid 1st.
Just flash systemsparse 1-7..
If that doesn't help...Flash all of these!
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 erase customize
fastboot erase clogo
This should do the trick.
Click to expand...
Click to collapse
Do I need to re-lock the bootloader? Because that was the only thing missing from complete unroot. When I tried to install the update it got to like 40% before crashing or something, don't know what causes that.
j0nas_ said:
Do I need to re-lock the bootloader? Because that was the only thing missing from complete unroot. When I tried to install the update it got to like 40% before crashing or something, don't know what causes that.
Click to expand...
Click to collapse
Nope, relocking is not mandatory to take the OTA! It fails because the device doesn't look like stock! if u uninstalled any system app, or removed the bootloader unlocked warning message or used any custom logo, or even added any folder to the system folder, it fails!
abhi212b said:
Nope, relocking is not mandatory to take the OTA! It fails because the device doesn't look like stock! if u uninstalled any system app, or removed the bootloader unlocked warning message or used any custom logo, or even added any folder to the system folder, it fails!
Click to expand...
Click to collapse
It still fails and it's as a clean install as it can be apart frombeing connected to my wifi and my google account, nothing else is installed. When I try to install the update this time it got to ~30% and then displayed a dead android and "Error!" below it.
j0nas_ said:
It still fails and it's as a clean install as it can be apart frombeing connected to my wifi and my google account, nothing else is installed. When I try to install the update this time it got to ~30% and then displayed a dead android and "Error!" below it.
Click to expand...
Click to collapse
I have no idea if everything is stock why is it failing OTA! Then you will have to install stock rom again.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Go here and follow the instructions! If u are rooted then make a titanium backup of all the apps and user data and then do this function! That way after taking the OTA u can root again and use the titanium backup app to get all the data back!
Newbie here. I hope to receive my Moto G4 Plus (xt1644) tomorrow! I don't understand this step:
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important)
When rooting my G4 Plus, I will be using SuperSU. It seems that to unroot this app it's not done within custom recovery, which step 2 seems to require? Am I misunderstanding something?
Also, you speak of a 40MB OTA update. Does this change the Android version or is it just some type of security patch? Thanks
flroots said:
Newbie here. I hope to receive my Moto G4 Plus (xt1644) tomorrow! I don't understand this step:
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important)
When rooting my G4 Plus, I will be using SuperSU. It seems that to unroot this app it's not done within custom recovery, which step 2 seems to require? Am I misunderstanding something?
Also, you speak of a 40MB OTA update. Does this change the Android version or is it just some type of security patch? Thanks
Click to expand...
Click to collapse
You use custom recovery to recover your bootloader and system before making any changes.
---------- Post added at 11:23 AM ---------- Previous post was at 11:18 AM ----------
abhi212b said:
I have no idea if everything is stock why is it failing OTA! Then you will have to install stock rom again.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Go here and follow the instructions! If u are rooted then make a titanium backup of all the apps and user data and then do this function! That way after taking the OTA u can root again and use the titanium backup app to get all the data back!
Click to expand...
Click to collapse
I used titanium backup to restore my apps after installing linage os. I felt the trouble of installing linage is less than acquiring that security update. So far so good Except all sms are lost and a few games lost their saves.
abhi212b said:
What's the error that u are getting after this??
Ideally, u should flash only system file!! Recovery and System 1-7!
Click to expand...
Click to collapse
I guess the bootloader didn't want to be re-written, but the logo also needed to be reverted (I had a custom one).
However, the above procedure worked fine for me, the installed applications where maintained.
j0nas_ said:
You use custom recovery to recover your bootloader and system before making any changes..
Click to expand...
Click to collapse
Sorry, I don't know what that has to do with step 2 which refers to unrooting SuperSU. As near as I can tell, one does the uninstall of SuperSU within the SuperSU app on Android, not custom recovery. Hope you can elaborate. 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
NOTE: I am not responsible for anything that might happen to your device while doing this. (it most likely is not).
EDIT: RE-DOWNGRADING TO 7.1.1 IS POSSIBLE WITH THIS!
I noticed there was no clear tutorial on how to do this yet so I have decided to make a guide explaining how to install the Oreo update on the Moto Z. This should work on most unlocked models (excluding Verizon). I have tried this on my Moto Z RETUS and it is working fine. I believe you should also need an unlocked bootloader, I haven't tested it on a device with a locked bootloader. Please download all the files from the bottom of the post.
Run the following commands with fastboot to install this version of 7.1.1 (download below) (hold power + volume down to get into bootloader mode):
Code:
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
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
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
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Once the device reboots into 7.1.1, turn the device off, and hold power + volume down to get into the bootloader again, and keep pressing the volume up key until you can select recovery. Press the power button to boot into recovery and once in recovery, keep pressing power and volume up buttons (do not hold them) to access all the options. Once the options appear, use the volume down key to scroll down to "apply update from ADB".
Now, open a new command prompt window, and rename the "Blur_Version.27.11.58.griffin.retail.en.US.zip" file to "ota.zip". Run "adb sideload ota.zip", and it should sideload the oreo update.
Note: If you have any issues sideloading the OTA (example issue: * cannot read 'ota.zip' *) then download this and move the adb.exe and dlls to the same folder as the ota zip. This version of ADB should be able to sideload the zip without the "cannot read ota.zip" issue. In terminal, make sure to run "adb.exe sideload ota.zip" instead of just "adb".
Finally, use the volume keys to scroll down to "Wipe cache" and press the power button. Then scroll up to reboot and hit the power button again and you should be good!
------------------------------
All Downloads:
7.1.1: 7.1.1 Firmware Download
Flashtools zip: Moto Flashtools ADB / Fastboot Download
Oreo update: Download Blur_Version.27.11.58.griffin.retail.en.US.zip (Oreo)
Want to root Oreo? Follow this guide, should work for the normal Moto Z:
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
thanks.. I m install Oreo last week.. but thanks to you for complete guide for who faced error or they don't know how to sideload Oreo Ota ..
sorry my ignorance. Why it shouldn't work on Verizon's version?
Elsnakes said:
sorry my ignorance. Why it shouldn't work on Verizon's version?
Click to expand...
Click to collapse
Because the firmware is for the unlocked Moro Z not the Verizon Moto Z and the Verizon Moto Z has a locked boot loader.
If applied on 7.1.1 Moto Z (RETEU), with TWRP, custom kernel and Magisk, but otherwise stock, will this method erase or preserve user data/apps/settings?
Is there a way to upgrade rooted stock 7.1.1 to Oreo without loosing data?
ethanscooter said:
Because the firmware is for the unlocked Moro Z not the Verizon Moto Z and the Verizon Moto Z has a locked boot loader.
Click to expand...
Click to collapse
So there's no way to unlock they phone's bootloader if it's Verizon version?
I didn't know that. My only option is to wait ?
Hey, @ethanscooter I have a question regarding applying update from adb part. I'm on stock reteu ROM/recovery. And when I boot into recovry two things happens
- adb doesn't see device (nor lsusb)
- I have no options like -- select apply update from adb, actually nothing except of droid on the screen.
Any suggestions?
Try holding the power button, then shortly pressing volume up and then releasing both buttons.
I am trying to install an update, but I think it is stuck. On windows command prompt window there is:
serving: 'ota.zip' (~47%)
Click to expand...
Click to collapse
and on the phone screen last message is:
Patching system image after verification
."
Click to expand...
Click to collapse
It's like 15 minutes now. Is it normal? Should I wait more?
EDIT
OK, so It's normal. It is going further now.
kooocko said:
Try holding the power button, then shortly pressing volume up and then releasing both buttons.
Click to expand...
Click to collapse
WHOA! Thank you very much! It worked.
You're welcome
Let us know if the update was succesful.
Went smoothly. Anyone else having issues with Approach and Moto Display not working?,
I installed over my locked bootloader and it went well btw
I did a factory reset and everything is fine now.
I have a suspicion that Oreo + MotoApproach/MotoDisplay + Immersion Mode is broken.
kooocko said:
You're welcome
Let us know if the update was succesful.
Click to expand...
Click to collapse
Actually it was. Additionally I've done wipe for cache just to be sure. All other thing migrated successfully. ROM that I've used was not from post. It came from Efran's OTA Tool.
Is your phone reteu? What parameters did you use in the OTA tool?
Please help!
stivenus said:
I am trying to install an update, but I think it is stuck. On windows command prompt window there is:
and on the phone screen last message is:
It's like 15 minutes now. Is it normal? Should I wait more?
EDIT
OK, so It's normal. It is going further now.
Click to expand...
Click to collapse
in my case my phone shows
Finding update package...
opening update package...
Verifyng update package...
And in terminal in windows is not going more than 16%, please anyone can helpme?
i use this XT1650-03_GRIFFIN_RETUS_7.1.1_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Its ok?
Sorry for my bad english
Edit: Its ok, i can install
Anyone can root this version?
ethanscooter said:
NOTE: I am not responsible for anything that might happen to your device while doing this. (it most likely is not).
EDIT: RE-DOWNGRADING TO 7.1.1 IS POSSIBLE WITH THIS!
I noticed there was no clear tutorial on how to do this yet so I have decided to make a guide explaining how to install the Oreo update on the Moto Z. This should work on most unlocked models (excluding Verizon). I have tried this on my Moto Z RETUS and it is working fine. I believe you should also need an unlocked bootloader, I haven't tested it on a device with a locked bootloader. Please download all the files from the bottom of the post.
Run the following commands with fastboot to install this version of 7.1.1 (download below) (hold power + volume down to get into bootloader mode):
Code:
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
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
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
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Once the device reboots into 7.1.1, turn the device off, and hold power + volume down to get into the bootloader again, and keep pressing the volume up key until you can select recovery. Press the power button to boot into recovery and once in recovery, keep pressing power and volume up buttons (do not hold them) to access all the options. Once the options appear, use the volume down key to scroll down to "apply update from ADB".
Now, open a new command prompt window, and rename the "Blur_Version.27.11.58.griffin.retail.en.US.zip" file to "ota.zip". Run "adb sideload ota.zip", and it should sideload the oreo update.
Note: If you have any issues sideloading the OTA (example issue: * cannot read 'ota.zip' *) then download this and move the adb.exe and dlls to the same folder as the ota zip. This version of ADB should be able to sideload the zip without the "cannot read ota.zip" issue. In terminal, make sure to run "adb.exe sideload ota.zip" instead of just "adb".
Finally, use the volume keys to scroll down to "Wipe cache" and press the power button. Then scroll up to reboot and hit the power button again and you should be good!
------------------------------
All Downloads:
7.1.1: 7.1.1 Firmware Download
Flashtools zip: Moto Flashtools ADB / Fastboot Download
Oreo update: Download Blur_Version.27.11.58.griffin.retail.en.US.zip (Oreo)
Want to root Oreo? Follow this guide, should work for the normal Moto Z:
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Click to expand...
Click to collapse
Can anyone root this version of android, i tried the metod in the description but is not working for me, i want to disable navbar and i need root, ¿can anyone please help me?
I upgrade my RETEU Moto Z following a German Guide, roughly the same as this guide, not first installing 7.1.1. (was already on that). I installed the RETUS version, but the Moto Z still says RETEU, so the update seems to be softwarechannel independent.
Works flawlessly!
modem
I want to just upgrade the modem, any suggestions on how to apply?
this wont install with the February update
I am presently on erfan v4 stock rom 7.1 and when i try to downgrade to the stock os u have provide with all the fastboot command it boots in to 7.1 stock but every time i lost my imei no ...so have to install twrp and restored it from my backup..any solutions
Story: I bought US version Z3 Play open market model from B&H. I could unlock the bootloader according to Motorola Developer site, but I encountered problem to root and I have struggled half day to make root done from booting TWRP to patching boot.img.
Eventually, I bit the bullet and make a step up to update to Pie bu downloading RETAIL ROM instead of RETUS. This time I patched the updated boot.img and I got success.
Prerequisite:
Full RETAIL Pie ROM
https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
Bootloader unlocked
It's recommended to flash in Linux (I used Ubuntu) as I didn't have luck with Windows
Main battery should be full and supplied battery module should be at least 50% (you can charge battery module with 9V PD charger)
Some typing (all fastboot commands typed as ./fastboot)
Be aware some components will be flashed in b partition. Failure to do it will cause bootloop
./fastboot erase userdata is optional, but it is recommended to avoid unexpected trouble
Steps:
1. Download the Pie ROM and extract to somewhere you know (you can drag and drop the file into terminal window).
2. Copy the boot.img to the phone and let Magisk Manager to patch it, and copy the patched_boot.img to where you can locate.
3. Backup your personal data just in case
4. Prepare USB C cable
5. Enter bootloader. Turn the phone off, press and hold both volume down and power button together, and connect you phone to host computer. (You phone should show USB conmected)
6. Enter the following commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
7. After the phone has booted up, wait until it completed the update process. Now you have to go back to bootloader for rooting.
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Booting process takes much longer, but it's one process until you update ROM and regain root again.
8. Run Magisk Manager to check root status
This is what I did to manually update to Pie and root it. Your milage may vary.
Good luck
Will this work on the amazon version?
CrimsonSaber5G said:
Will this work on the amazon version?
Click to expand...
Click to collapse
If the bootloader can be unlocked, it's likely
Will this still allow you to get OTAs or will it break it?
crazyjimbo said:
Will this still allow you to get OTAs or will it break it?
Click to expand...
Click to collapse
I used to flash stock on my rooted z3play, then take the OTA . For some reason that's not possible anymore. I really need the latest OTA to sideload it. I tried many different roms 8.1 and 9.0