[ROM][STOCK][RETAIL] Official Stock Pie 9 [updated March 6th] - Moto G6 Plus Guides, News, & Discussion

Hi guys,
Did not see anyone here on XDA who uploaded recently leaked OFFICIAL PIE fastboot image ROM for Moto G6 Plus, so I decided to do it for you all. :highfive:
This is a RETAIL release so it should work on all variants of our device (I have XT1926-3 (this is RETEU, Europe, Poland) and flashed it without any problems, phone works flawlessly).
06.03.2019, THE NEWEST PPW29.116-20 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1Axk870qsui9w3TnnRQM9pt618CQ0CnHz
MIRROR: https://mega.nz/#!0ZUyTAqI!XXPwj0mcsGs0wLFwxwX8V0OeFXgCe-NXf-2VbDvr5Nc
OLDER BUILD: PPW29.116-16 FIRMWARE DOWNLOAD (RETAIL) - BE CAREFUL, IT BREAKS SAFETYNET ON EUROPEAN G6+ VARIANTS!
DOWNLOAD: https://drive.google.com/open?id=1F0SFwVyXgy3ZixL36W6xwxjqPJAwiDus
MIRROR: https://mega.nz/#!VJ8xEYRT!rb476WxlV099PVJrLwbFIr1Z3XNjo89sO5MU-HfPzMQ
OLDER BUILD: PPW29.116-11 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1shkeHg_jxsCTLgcDjwcCgecMLJKC4EB0
MIRROR: https://mega.nz/#!MQ8BBYwJ!KpwfgunwBONWlwAYFmFUEt4UsRPpjn34jJo1GHY66fo
Flashing scripts (G6PlusFlashPieOfficial.bat from the attached .zip file can be also used, it contains the same commands as below):
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything:
--- If you don't want to erase all your phone data, use script from G6PlusFlashPieOfficial_NoErase.zip. This will upgrade your G6+ to Android Pie without erasing data. ---
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 logo logo.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_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 oem fb_mode_clear
fastboot reboot

It works, indeed, flawless, though I used the version Vache shared on telegram. I assume it's the same file you used for this tutorial. I think it's important to mention that there are 2 possibilities to update:
1. The way you describe here
2. Use the update file (Blur_Version.29.11.11.evert.retail.en.US.zip) and place in the root of the internal storage. Then check for updates (though I think this only works when coming from a specific build).

Screenshots.
PS. Digital Wellbeing installed via Magisk.

My brother has a Moto G6 Plus (bought in Europe) without root, will he be able to update it without loosing his data?
Thanks in advance guys.

Is it also posible to use this zip, extract it and then use Fastboot to update without losing enything? So like this:
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 logo logo.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_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 reboot
This is normaly how i update my G6 Plus and never expierence problems......

cdfreak said:
Is it also posible to use this zip, extract it and then use Fastboot to update without losing enything? So like this:
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 logo logo.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_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 reboot
This is normaly how i update my G6 Plus and never expierence problems......
Click to expand...
Click to collapse
Exactly like this. 
 @cyberon these commands are for your brother.

rafikowy said:
Screenshots.
PS. Digital Wellbeing installed via Magisk.
Click to expand...
Click to collapse
So you were able to upgrade without getting the "Verity mode is set to disabled" on the boot screen or having your System Updates disabled due to the unlocked bootloader?

thump said:
So you were able to upgrade without getting the "Verity mode is set to disabled" on the boot screen or having your System Updates disabled due to the unlocked bootloader?
Click to expand...
Click to collapse
"Verity mode is set to disabled" is still present on boot screen - I don't care.
System Updates were disabled at the begining - there was some information about System Integrity. After flashing Magisk 18 this information dissapeared as you noticed.

smitharro said:
It works, indeed, flawless, though I used the version Vache shared on telegram. I assume it's the same file you used for this tutorial. I think it's important to mention that there are 2 possibilities to update:
1. The way you describe here
2. Use the update file (Blur_Version.29.11.11.evert.retail.en.US.zip) and place in the root of the internal storage. Then check for updates (though I think this only works when coming from a specific build).
Click to expand...
Click to collapse
which file i need to do the 2nd method and where can i download it?

rafikowy said:
"Verity mode is set to disabled" is still present on boot screen - I don't care.
System Updates were disabled at the begining - there was some information about System Integrity. After flashing Magisk 18 this information dissapeared as you noticed.
Click to expand...
Click to collapse
Just rechecked and found my System Updates page no longer gives the "system integrity" error either. Still do get the "verity" error, but seems of no concern. Cool.

giorgis91 said:
which file i need to do the 2nd method and where can i download it?
Click to expand...
Click to collapse
This should do the trick. Remember to rename the file to Blur_Version......zip. (see my previous post).
https://mega.nz/#!RRF01QID!9QjfFmaVjWQW6ZAoqqbn-tOW9bCYgnn7IojnSgrHLJU

smitharro said:
This should do the trick. Remember to rename the file to Blur_Version......zip. (see my previous post).
https://mega.nz/#!RRF01QID!9QjfFmaVjWQW6ZAoqqbn-tOW9bCYgnn7IojnSgrHLJU
Click to expand...
Click to collapse
Will it wipe the phone ?

giorgis91 said:
Will it wipe the phone ?
Click to expand...
Click to collapse
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'

Suggestions
rafikowy said:
Hi guys,
Did not see anyone here on XDA who uploaded recently released OFFICIAL PIE fastboot image ROM for Moto G6 Plus, so I decided to do it for you all. :highfive:
This is a RETAIL release so it should work on all variants of our device (I have XT1926-3 (this is RETEU, Europe, Poland) and flashed it without any problems, phone works flawlessly).
PPW29.116-11 FIRMWARE DOWNLOAD (RETAIL)
DOWNLOAD: https://drive.google.com/open?id=1shkeHg_jxsCTLgcDjwcCgecMLJKC4EB0
MIRROR: https://mega.nz/#!MQ8BBYwJ!KpwfgunwBONWlwAYFmFUEt4UsRPpjn34jJo1GHY66fo
Flashing scripts (G6PlusFlashPieOfficial.bat from the attached .zip file can be also used, it contains the same commands as below):
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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[PHP][/PHP]
fastboot flash dsp dspso.bin
fastboot flash logo logo.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_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 oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
I place an "m" in front of fastboot to use mfastboot.
Get the mfastbootv2 it's best for flashing this way imo
Good work buddy.

What's the command erase carrier for?

smitharro said:
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Click to expand...
Click to collapse
Is that multilang or only in english?
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
giorgis91 said:
Is that multilang or only in english?
Click to expand...
Click to collapse
smitharro said:
No, it shouldn't. It's an update file. So it 'll leave all your apps and settings intact.
But if you want to be sure that you have a clean install, do a 'factory reset' prior to the update!
Oh yeah, remember to grant storage the 'motorola update services'
Click to expand...
Click to collapse
I ask because I'm italian and I see that the file as "en.US" in the name, i tried just now to rename the file but with "it.IT" and the system find it as an update. But i want to know if i can choose the language or it's just in english

giorgis91 said:
Is that multilang or only in english?
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
I ask because I'm italian and I see that the file as "en.US" in the name, i tried just now to rename the file but with "it.IT" and the system find it as an update. But i want to know if i can choose the language or it's just in english
Click to expand...
Click to collapse
All stock ROMs are multilingual. So Italian shouldn't be a problem.

what dos this mane: Verity mode is set to disabled when you boot the phone up?

cdfreak said:
what dos this mane: Verity mode is set to disabled when you boot the phone up?
Click to expand...
Click to collapse
A short explanation:
dm-verity
transparent integrity checking for block devices
read error if block integrity check fails
try to recover damaged blocks (from Android 7.0)
useful for read-only partitions like*system
fundamental part of*verified boot*on Android
Verified boot
device software integrity based on hardware root of trust
Boot chain (simplified)
verify*bootloader*using a hardware root of trust
bootloader*verifies*boot*and*recoverypartition
kernel*verifies*system*partition
uses dm-verity for the integrity checks once execution has moved to the boot partition

Hmmm. For some reason I get "Server error" in play store. And autobrightness jumps up and down every few seconds. Have tried returning to oreo and reflashing/factory resetting to no avail On reteu.
EDIT: Hmm also get the error in oreo now Anyone know whats up? Came from Lineage 16.

Related

How to manually update Moto Z2P to NPS26.118-19 (August Security Patch)

Hello all!
So I got tired of waiting for the latest update to hit my phone so I figured I would do it manually. After plenty of experience with Moto phones I gathered that the official RETAIL files should work with all of the GSM versions of the Moto Z2 Play. This is confirmed to work with both XT1710-01 and XT1710-07, but is likely to work with others (but not the US Verizon Model). For those of us who are security minded, this is flashed w/o unlocking your bootloader which means that only Motorola signed images will work, and it also means that you do not need to wipe your data. Woohoo!
As usual, you take full responsibility for anything you do to your phone, but since your bootloader is locked, this should be fairly low risk, barring some sort of power loss mid-flash.
How to:
1. Download & Install Motorola Drivers from XDA.
2. Download & extract stock rom from here.
3. Use mfastboot/fastboot to run the following commands/run the attached .bat file. (Hint: make sure fastboot files are in the same directory as the the ROM files and .bat file).
3a. If you need more help on mfastboot or fastboot, look here.
Code:
echo off
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash Start
echo -------------------------------------------------------------------------
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
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 oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo Moto Z2 Play ROM Flash End
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
4. Enjoy!
Hope this helps!
but how is obtained stock rom?
For those of us who are security minded, this is flashed w/o unlocking your bootloader which means that only Motorola signed images will work, and it also means that you do not need to wipe your data. Woohoo!
Click to expand...
Click to collapse
The file you linked to on lolinet isn't signed. You do need to unlock the bootloader to flash it.
timster01 said:
The file you linked to on lolinet isn't signed. You do need to unlock the bootloader to flash it.
Click to expand...
Click to collapse
I had no problem flashing with a locked bootloader. Didn't even have to wipe. What error did you get when you tried to flash?
I am wondering if it works on an XT1710-08 model...

[Q] Is it safe to flash another region version of my phone's stock firmware?

Before unlocking or flashing my XT1650-03 it was labelled as retapac and I haven't been able to find any retapac 7.0 images for fastboot but I've found other regions, are they safe to flash?
Yes it's safe, I have done that (I have retmx and used a retbr) and it works exactly the same
Malmarox said:
Yes it's safe, I have done that (I have retmx and used a retbr) and it works exactly the same
Click to expand...
Click to collapse
How do you changed it? You unlocked the bootloader or something like that?, Im thinking about change my reteu stock rom by retbr too.
vok01 said:
How do you changed it? You unlocked the bootloader or something like that?, Im thinking about change my reteu stock rom by retbr too.
Click to expand...
Click to collapse
I use this steps:
0. Download files
1. install motorola device manager
2. install minimal adb&fastboot
3. extract files from zip and put them in the same directory as fastboot.exe
3. boot phone into fastboot mode
4. flash via fastboot:
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
I don't know if you need to have unlocked bootloader, when I tried it, I already had it unlocked.
Variant xt1605-05
I have a doubt, I have a Chinese version xt1605-05, I do not want to use Chinese roms, can I flash an xt1605-03 retbr? deleting gpt.bin and bootloader? sorry my english is bad

[FASTBOOT ROM] OREO Retail OPS27.76-12-25 (April) using Fastboot

Hi all, i have found this on Motozbrasil Blogspot.
It reported XT1710-01, XT1710-02, XT1710-06, XT1710-07, XT1710-09 e XT1710-10 models as working, but my XT1710-08 works too (see details in this post).
>>>> All credits and thanks go to motozbrasil and its staff. It is not my creation, i have just shared and reported my personal experience with my XT1710-08, not listened on that site.
A special, big, superb thanks to Junior Passos @Junior Passos the op of the motozbrasil thread. <<<
Basical steps:
1) Install drivers (Win) and reboot pc;
2) Unzip firmware and ADB + FASTBOOT - MZ2PLAY in the same folder (thanks to htcmania for package);
3) Put your phone in fastboot mode (Vol down + Power) then Connect to pc, waiting for drivers if needed;
4) Double click on z.bat (edit it with your own commands or use my zips attached changing "mfastboot" voices with "fastboot", so delete "m" from every single command), press a button.
Profit.
We needed a retail fastboot Oreo rom, so here we are.
All at your own risk.
Good luck.
Due to motozbrasil site down on link posted, i linked new adb fastboot and Installer. As soon as possibile i will change and upload installers attached.
Other links for rom only, here (thanks @thedoginthewok):
MEGA:
https://mega.nz/#!Y51hDRRQ!fxS5qoi2rklgtyQP5ydpcd7nM7qIl-wbsd9zJIF6doQ
Google Drive:
https://drive.google.com/file/d/1kyr8AHFZKv5-ASmCEpGHc8CqGgJFc6YO/view
I advice you to proceed over Windows, but in case...
> On Linux
Linux doesn't need drivers.
How to install adb/fastboot on linux, macos, win (depends on your distro): https://www.xda-developers.com/install-adb-windows-macos-linux/
If you are under Ubuntu the easiest way for installing adb-tools is (from terminal):
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Command under Terminal (Win/Linux) are:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
In some cases (for example XT1710-08) is useful to skip (if you come from NPSS26.118-19-1-6):
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
If you pass directly from ZUI skip also:
fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
Those for preserving signal and data connection.
---
If you have a corrupted boot.img and you are not able to flash (like bangood or other shops do with chinese model), you first have to give that:
fastboot flashing unlock
Click to expand...
Click to collapse
Hope is useful.
Link above are for Win (1st) and Linux (2nd)**.
** if you use attached .sh remember you have to connect you phone in fastboot mode to pc and then double click on it in the same folder you have unzipped firmware. Attached .bat and .sh files evading erase modemst1 and st2, so it is good for some brand device, not for other.
Remember, all at your own risk.
Thanks @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
About Magisk, you could give a thanks to Fabio Feher:
Fabio Feher said:
It work for me:
1: Reboot into Bootloader
2: ADB Flash TWRP
3: Start Recovery (TWRP)
4: Enter in ADVANCED > TERMINAL
5: Run commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6: Flash Magisk
7: Reboot.
Click to expand...
Click to collapse
It should work. Unfortunately,I'm already using Oreo. Otherwise,I will try this fastboot ROM.
HTCDevil said:
Hi all, i have found this:
http://motozbrasil.blogspot.it/2018/05/firmware-moto-z-play-xt1710-firmware.html?m=1
All credit and thanks to motozbrasil and its staff.
I will try it on my XT1710-08, although not in the list on the site.
We need a retail fastboot Oreo rom, so here we are.
All at your own risk.
Good luck.
Click to expand...
Click to collapse
If possible , could you please upload the firmware on google Drive , because i am not able to download oreo firmware from Your given link, it downloads for about 100MB and then the download process fails.
flashnub said:
If possible , could you please upload the firmware on google Drive , because i am not able to download oreo firmware from Your given link, it downloads for about 100MB and then the download process fails.
Click to expand...
Click to collapse
I could try
I've had trouble with the download myself (hat to restart a couple of times), so I uploaded it to Google Drive and Mega.
md5 d134168fe189d187f5728a440c380442
Google Drive
Mega
I've successfully upgraded my phone (XT1710-09) to oreo with this.
My phone is bootloader unlocked and was rooted with Magisk. before this.
TWRP was overwritten with stock recovery, but after reflashing I can't get it to decrypt, so no root for now. But everything else is working fine.
Thank you
thedoginthewok said:
I've had trouble with the download myself (hat to restart a couple of times), so I uploaded it to Google Drive and Mega.
md5 d134168fe189d187f5728a440c380442
Google Drive
Mega
I've successfully upgraded my phone (XT1710-09) to oreo with this.
My phone is bootloader unlocked and was rooted with Magisk. before this.
TWRP was overwritten with stock recovery, but after reflashing I can't get it to decrypt, so no root for now. But everything else is working fine.
Click to expand...
Click to collapse
Hey thanks for Uploading it to Google Drive .
I have successfully loaded the Oreo Firmware, no hicc-ups at all, procedure went smooth.
Now my Moto Z2 Play XT1710-10 is running Oreo
thedoginthewok said:
I've had trouble with the download myself (hat to restart a couple of times), so I uploaded it to Google Drive and Mega.
md5 d134168fe189d187f5728a440c380442
Google Drive
Mega
I've successfully upgraded my phone (XT1710-09) to oreo with this.
My phone is bootloader unlocked and was rooted with Magisk. before this.
TWRP was overwritten with stock recovery, but after reflashing I can't get it to decrypt, so no root for now. But everything else is working fine.
Click to expand...
Click to collapse
Thanks, i edit first post.
Good flash guys
flashnub said:
Hey thanks for Uploading it to Google Drive .
I have successfully loaded the Oreo Firmware, no hicc-ups at all, procedure went smooth.
Now my Moto Z2 Play XT1710-10 is running Oreo
Click to expand...
Click to collapse
Nice to see, no thanks for me
Does fastboot update method wipe userdata? Also have 09 model, no root and locked boot - can i update without loosing my data, etc?
Face1ess said:
Does fastboot update method wipe userdata? Also have 09 model, no root and locked boot - can i update without loosing my data, etc?
Click to expand...
Click to collapse
Data is not wiped.
For those who were looking for fastboot commands here they are:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
HTCDevil said:
Nice to see, no thanks for me
Click to expand...
Click to collapse
hey thanks mate, you were the reason i even thought of trying to Flash the Firmware first.
Face1ess said:
Does fastboot update method wipe userdata? Also have 09 model, no root and locked boot - can i update without loosing my data, etc?
Click to expand...
Click to collapse
Users have tested it and said you don't lose your /data
I've updated my 09 successfully without loosing data.
Works for my 09 without loosing anythings. Tkx .
Vavooon said:
I've updated my 09 successfully without loosing data.
Click to expand...
Click to collapse
Great, thanks for info
Niiiicee, updated using your method and everything works nice and smooth. Haven't lost anything either! I hope it doesn't break the OTA
I can also confirm - the data and settings after the update are not touched
09 model, reteu
I have a moto z2 play 7.1.1. NPSS26. 118-22 and the XT1710-09 model. This guide work on my smartphone?
oliondo said:
I have a moto z2 play 7.1.1. NPSS26. 118-22 and the XT1710-09 model. This guide work on my smartphone?
Click to expand...
Click to collapse
It should work without any problem.
Works on my xt1710-08, i evade fastboot erase modemst1 and modemst2.

[Evert] [Stock] Firmware - Return to Stock.

[Evert] [Stock] Firmware - Return to Stock.​Disclaimer
I can not be held responsible for any type of problem with your device. This information is for the sole purpose of reporting and is delivered "as is". Only the tests will confirm if everything works well or does not work at all, proceed with caution.
Recommendations.
Make sure to back up all information, device data, and (optional) persistence partitions of the device.
Always use common sense, and confirm that you do not have an error message in the console. Verify that things are done correctly.
Requirements
Make sure that the drivers and everything related to connectivity is working properly. The official Motorola drivers work fine, and the google fastboot drivers too. Look for tutorials on installing the fastboot driver if your computer is not detecting it properly, the tutorials of other moto models (eg moto g5 plus) on the drivers and others work just as well.
All this process spends time and of course the battery of your device, make sure you have a good battery (50+) and stay connected as much as possible.
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware, but it depends on each one...
All the commands and others are done from the fastboot utility, you can find it in https://developer.android.com/studio/releases/platform-tools.
Process
Download the correct firmware for your device.
Right now there are not many firmware available, as time passes the list will grow.
One of several sites is LOLINET.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAIL/
(If not already installed, make sure of ..) Install the drivers and download the fastboot utility. And of course, verify that the driver works properly. It will be done later.
Extract the fastboot utility, and the firmware within the same directory.
To verify the connection, enter the bootloader of your device, connect it with the PC. On the PC; run the console, go to the folder where you extracted the fastboot utility, and type fastboot.exe devices, you should see the listed device in the console.
If the connection works correctly and you notice nothing strange, you can start the process.
Open the console in the directory where the fastboot utility is on the firmware files, there should be no more folders inside. (In this case you should adjust the path of the files in the commands). And write the following commands, verify that you do not have errors.:
Warning,
The commands listed below as "optional" do not necessarily have to be executed, but to be completely safe, execute them all, as long as you have the right firmware.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (optional)
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1 (Optional)
fastboot erase modemst2 (Optional)
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase carrier (Optional)
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
[I][/I]
Press the Power button, and wait a bit.. It will take a few minutes to start.
If you hear "Hello moto", congratulations you are in Stock (and everything "should work fine").
Notes
If your firmware has more or less sparsechunk files (eg, sparsechunk.3 or img_sparsechunk.7), run them all.
The bootloader will remain unlocked.
If all this was helpful, I hope your thanks.
With love by iGor.
And how remove verity Mode enabled?..and a black screen saying phone flashed with different software
IGorMcLven said:
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware
Click to expand...
Click to collapse
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
rybshik said:
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
Click to expand...
Click to collapse
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Dual SIM XT1926-7: firmware and TWRP issue
lcmp said:
I have the same phone.
Before you flash your phone make sure that you have a backup of :
EFS and Persist partitions
Click to expand...
Click to collapse
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
rybshik said:
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
Click to expand...
Click to collapse
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
TWRP decryption issue
lcmp said:
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
Click to expand...
Click to collapse
for which firmware build? Pie or Oreo?
In my case, I was able to back up with twrp-3.3.1-0-evert.img before flashing Magisk. And I was able to Magisk-root with twrp-3.3.1-0-evert.img successfully as well.
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
So I tried twrp-3.2.3-42-evert.img and it worked.
Is it possible to permanently remove encryption?
rybshik said:
for which firmware build? Pie or Oreo?
Click to expand...
Click to collapse
PIE
rybshik said:
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
Click to expand...
Click to collapse
I´m not an expert, but from what i know, You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition. Then your backups will succeed.
rybshik said:
Is it possible to permanently remove encryption?
Click to expand...
Click to collapse
I read it´s possible but i´m no expert on the subject. Why would you want to remove encryption? I think its a good feature
lcmp said:
You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition.
Click to expand...
Click to collapse
Does TWRP ask for a PIN during back up?
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
rybshik said:
Does TWRP ask for a PIN during back up?
Click to expand...
Click to collapse
What I noticed is that when TWRP 3.3 boots, it asks for your pin or unlock pattern in order to use that as the credential to get the decryption key and decrypt the data partition. TWRP 3.2 won't do this ( again, in my experience ) hence the back up fails because everything is encrypted.
This is how I noticed that force installing TWRP 3.2 was useless. it doesn´t ask for your pin or your unlock pattern so it doesn´t have a way of decrypting the data partition. Again this was my experience. A more advanced android / twrp user could give a definite answer.
rybshik said:
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
Click to expand...
Click to collapse
I think so, yes. If you don´t have a pin or unlock pattern in your phone, TWRP doesn´t have a way to "authenticate" and get the decryption key and decrypt the data partition. Again, I´m assuming this out of my own experience.
Hello, can anyone share me the persist file from a xt1926-6 please?
I am having an issue with this file and I don't know what to do now
Thank you
lcmp said:
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
Hello, how did you solve the persist issue? I have it corrupt and I don't know what to do
Thanks
lcmp said:
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Toonka95 said:
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Click to expand...
Click to collapse
You can, recently I posted a solution for this issue (i believe it's the same as yours)
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t3994827
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
The following are the official firmware commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
sd_shadow said:
The following are the official firmware commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
WoKoschekk said:
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
Click to expand...
Click to collapse
Yeah man it took me all day to try to get it all working again, the fix was i downloaded an older stock rom and it restored my IMEI, it had to be the older version though because the newer one would recover it. Anyways now i'm never erasing that carrier or modem if it's not really necessary.
revert xt1926-3 to factory (2020)
IGorMcLven said:
[Evert] [Stock] Firmware - Return to Stock.​
Code:
...
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
...
Click to expand...
Click to collapse
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
tseeling said:
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
Click to expand...
Click to collapse
Needs Termux and python.

[FASTBOOT]CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAUL

OFFICIAL
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
COMMANDS
Code:
#MOTO G5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
:fingers-crossed:
Hi takoa, thanks for your efforts. What are the differences with the firmware OPP28.85-16?
security update
Is this flashable in any cedric? I have a Moto G5 XT1675 italiani TIM brand (now with pixelexperience)
Any hope for capturing OTA update? I'd prefer to flash delta update instead of factory image
Hi. I’m currently on Android 7, build NPPS25.137-72-4, reteu channel.
I can directly flash this via fastboot to get 8.1? Thanks!
xfahim Hi, of course you can directly flash this firmware to go to 8.1. Greetings
yilhernandez said:
xfahim Hi, of course you can directly flash this firmware to go to 8.1. Greetings
Click to expand...
Click to collapse
Ah so it doesn’t matter which version am I using? I thought I’d need something for the reteu channel. Thanks for the confirmation!
moto g5
hola amigo, donde puedo descarar el firmware: CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50 para el moto g5 xt1670
juan raul perez kana said:
hola amigo, donde puedo descarar el firmware: CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50 para el moto g5 xt1670
Click to expand...
Click to collapse
Code:
https://mirrors.lolinet.com/firmware/moto/cedric/official/
can't apply mfastboot commands and when applying fastboot commands.......my phone still stuck in bootloop
vaibhavsirohi91 said:
can't apply mfastboot commands and when applying fastboot commands.......my phone still stuck in bootloop
Click to expand...
Click to collapse
Get the latest firmware from
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Fastboot commands
Code:
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 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 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 oem fb_mode_clear
fastboot reboot
Note in order to flash gpt & bootloader the firmware must be the same or newer than what is on your device
If you get a security downgrade error the firmware you are trying to flash is too old
TheFixItMan said:
Get the latest firmware from
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Fastboot commands
Note in order to flash gpt & bootloader the firmware must be the same or newer than what is on your device
If you get a security downgrade error the firmware you are trying to flash is too old
Click to expand...
Click to collapse
Already got the latest one from RETIN folder (India)but still my device stuck into bootloop
vaibhavsirohi91 said:
Already got the latest one from RETIN folder (India)but still my device stuck into bootloop
Click to expand...
Click to collapse
Assuming you got no errors when flashing the firmware & all parts of the firmware were flashed correctly
Did you erase userdata?
You can also go into stock recovery mode and factory reset
Also you can try & remove any sim & sdcards from the device & see if it boots without them
TheFixItMan said:
Assuming you got no errors when flashing the firmware & all parts of the firmware were flashed correctly
Did you erase userdata?
You can also go into stock recovery mode and factory reset
Also you can try & remove any sim & sdcards from the device & see if it boots without them
Click to expand...
Click to collapse
I am getting these errors and i can't even access recovery
vaibhavsirohi91 said:
I am getting these errors and i can't even access recovery
Click to expand...
Click to collapse
Can't see any errors there but you may want to use an older fastboot version
TheFixItMan said:
Can't see any errors there but you may want to use an older fastboot version
Click to expand...
Click to collapse
Logical system not found......and i am using the latest zip from Retin folder (India)
vaibhavsirohi91 said:
Logical system not found......and i am using the latest zip from Retin folder (India)
Click to expand...
Click to collapse
I don't believe that is an error but rather an issue with that version of fastboot
I didn't say use another firmware - just use an older version of fastboot
Try versions from
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Obviously I presume gpt & bootloader flashed successfully
TheFixItMan said:
I don't believe that is an error but rather an issue with that version of fastboot
I didn't say use another firmware - just use an older version of fastboot
Try versions from
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Obviously I presume gpt & bootloader flashed successfully
Click to expand...
Click to collapse
Ok wait let me try
vaibhavsirohi91 said:
can't apply mfastboot commands and when applying fastboot commands.......my phone still stuck in bootloop
Click to expand...
Click to collapse
Sorry, but I forgot to indicate that we have to eliminate the "m" from mfastboot.
or rename fastboot.exe to mfastboot.exe :good:

Categories

Resources