Database Info

[Solution - NO SIM DETECTED] [CM13-based ROMs] - XT1562 Single SIM EU

Hi all.
If you are here, then you have likely experienced issues with custom ROMs not detecting SIM, or you are still experiencing this issue.
I have a XT1562 UK Single-SIM model and have had this problem with EVERY ROM I have tried and it was getting so frustrating.
Over the last few weeks, I have flashed custom ROMs based on CM13 and all have presented the SIM not detected issue. A simple fix was to pop-out the SIM module and reinsert - more often than never, the SIM was detected. Then I would restart (as is often the case with a custom setup) and alas, the SIM was not detectable.
After trying various suggestions from developers, nothing was working until I happened to flash a dualSIM firmware and I haven't looked back. I can now flash EVERY CM13-based ROM with successful SIM detection BUT it takes a few extra steps to get to that stage.
Here are the things you need:
This firmware
This fix
A custom ROM of your choice (Highly recommend crDroid or Temasek)
GAPPS of your choice - I would recommend this
TWRP
Okay - the solution (confirmed working and reliable):
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot​
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
Voila! You can now confidently flash ANY CM13-based custom ROM with the added assurance of SIM detection. IF, however, you flash a ROM and SIM is NOT detected, then simply reflash the DualSIMFix.
If this solution works for you, please give credit where it's due - thank me using the thumbs-up icon below AND vote in the poll at the head of this thread

So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?

perfectsense72 said:
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
Click to expand...
Click to collapse
It has worked for me and I have tried everything that has been recommended. Just by determined trial-and-error I have found my solution.

Just to reiterate
and my intention is to generate enough interest to further assist developers of the CM13 custom ROMs.
Click to expand...
Click to collapse

Can you write a sequence of actions? What nuances?

perfectsense72 said:
Can you write a sequence of actions? What nuances?
Click to expand...
Click to collapse
I fastboot flashed XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1 (here ); flashed ROM; flashed GAPPS and then flashed DualSIMFix (from here)
I've tested reboots and SIM is detected each time.
I am assuming you know how to flash a stock image - if not let me know.

I am assuming you know how to flash a stock image - if not let me know
Click to expand...
Click to collapse
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?

perfectsense72 said:
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
Click to expand...
Click to collapse
Follow this:
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
13. Enjoy - but please let me know if not quite right.

@perfectsense72 - once you are able to confirm fully working, then I'll amend the OP to reflect necessary details for successful detection, etc. Thanks for trying this.

Thank you, i'll try tomorrow.

I can't confirm your problems with single sim modem.
I have german single sim and had problems after flashing french dual sim stock image and then flash cm13 roms.
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
After flashing back a single sim stock and completly boot the stock then flash again crdroid no problems appeared again. All fine with detected sim on every boot.

For now I'm using Pac-ROM (LP) and have no problem, I'll try CrDroid soon and I'll let you know.

Jeso said:
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
Click to expand...
Click to collapse
This is what I'm aiming to avoid for those with issues such as this. Every firmware flash produced an error on flashing bootloader. The only one to not present me with the error is the 18.1 DS retasia.
This has, I believe, been the key to my issues as well as other users. I can flash any official firmware and use it perfectly well, it's just the custom MM ROMs that are problematic.

moozer said:
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Does it lock the bootloader?
(Sorry for noob question)

axxx007xxxz said:
Does it lock the bootloader?
(Sorry for noob question)
Click to expand...
Click to collapse
No - this just re-introduces the stock bootloader for the firmware

So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.

perfectsense72 said:
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
Click to expand...
Click to collapse
You're welcome. Checked rebooting the phone? SIM remains?
You can now flash custom ROMs to your heart's content. No need to fart around with firmware flashes. All that you need to check is SIM detection on setup and if necessary flash the SIMfix.

^^

Yes, SIM remains after reboot, everything is OK

Thanks a lot! Worked perfectly for me aswell. Currently running ResurrectionRemix and I've had no problems with the sim card since.

Motorola Moto G 4G (XT1040) Bootloop Problem

Hi, this is my first time making a post, ok here's the thing, a couple of days ago my phone run out of battery, when i come back to charge the phone, this just get stuck in the Motorola logo and don´t turn on, i never make nothing like root or flashing roms, the phone os was all stock Android 5.1; so i look in the internet for possible cause and i find that it was a bootloop, i try to get in to the fastboot flash mode to make a reset with the factory option but just get directly to the motorola logo and dont do nothing, so a try with the recovery option and gets in to the android system recovery <3e> and try the wipe data/factory reset but doesn´t work. I try even via computer using the minimal adb and fastboot to erase the cache and the userdata with the commands and doesn't work, still appearing the motorola logo. so i found that i have to install the original rom again but first ill have to unlock the bootloader for my device, so i did it, i unlock the bootloader and now appear <Device is UNLOCKED. Status Code: 3> and now appear the poster WARNING BOOTLOADER UNLOCKED instead of the motorola logo; then i search for the stock rom for my device and i find this one XT1040_PEREGRINE_RETBR_5.1_LPB23.13-8_cid12_CFC.xml.zip (i know that my device is peregrine because i remember saw it before in the settings but not remeber the hole name), so i make the installation with adb tools like the post say and make this 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 its over i press fastboot reboot, but then appears again the WARNING BOOTLOADER UNLOCKED poster, i try to make it again, bus still appearing, i try more than 10 times, but still appearing.
sorry if the post is too large but i try to explain everything so you guys can help me because im desesperate with this, thanks.

HanSolo97 said:
Hi, this is my first time making a post, ok here's the thing, a couple of days ago my phone run out of battery, when i come back to charge the phone, this just get stuck in the Motorola logo and don´t turn on, i never make nothing like root or flashing roms, the phone os was all stock Android 5.1; so i look in the internet for possible cause and i find that it was a bootloop, i try to get in to the fastboot flash mode to make a reset with the factory option but just get directly to the motorola logo and dont do nothing, so a try with the recovery option and gets in to the android system recovery <3e> and try the wipe data/factory reset but doesn´t work. I try even via computer using the minimal adb and fastboot to erase the cache and the userdata with the commands and doesn't work, still appearing the motorola logo. so i found that i have to install the original rom again but first ill have to unlock the bootloader for my device, so i did it, i unlock the bootloader and now appear <Device is UNLOCKED. Status Code: 3> and now appear the poster WARNING BOOTLOADER UNLOCKED instead of the motorola logo; then i search for the stock rom for my device and i find this one XT1040_PEREGRINE_RETBR_5.1_LPB23.13-8_cid12_CFC.xml.zip (i know that my device is peregrine because i remember saw it before in the settings but not remeber the hole name), so i make the installation with adb tools like the post say and make this 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 its over i press fastboot reboot, but then appears again the WARNING BOOTLOADER UNLOCKED poster, i try to make it again, bus still appearing, i try more than 10 times, but still appearing.
sorry if the post is too large but i try to explain everything so you guys can help me because im desesperate with this, thanks.
Click to expand...
Click to collapse
If your goal is to re-lock the bootloader: try the command: fastboot oem lock
However, I don't see that solving your problem and may compromise your ability to restore to stock. Instead check this link and follow the install directions EXACTLY:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
eg. for Canada choose: XT1040 (Note: for Rogers/Fido - confirmed)
Retail Canada 5.1 ROM (Untouched) (531mb) [Download]
i.e., you want the untouched version for your specific region.
Good luck. S

Problem with unlock boot loader in motorola x force

Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.

Rasah97 said:
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Click to expand...
Click to collapse
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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

TheFixItMan said:
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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
Click to expand...
Click to collapse
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same

Rasah97 said:
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Click to expand...
Click to collapse
Some phones may not have sparsechunks 0 & 4 - as long as you flash all the ones in the firmware in number order
I don't have your phone so I couldn't tell you what firmware to use
I have Motorola g5 so I can just tell you the process
And looking on that firmware thread it says you need to use mfastboot for system images - so see that thread for details
Long as everything is flashed successfully in the order I have written above including erasing user data

Sooo.... Could you tell me which comand i have to use ?

Related to no sim card issue?
I'm wondering if this is related to a problem I am having with mine phone. I flashed the official firmware (6.0) on my moto x force and everything works but the simcard. It says it's not loaded so I have no phone or cell data. My sim card works in other moto phones so its not that.

[Guide] How to install the official Oreo update!

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

Manually update Z3 Play to Pie

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