DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
Downloads:
PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Minimal ADB Fastboot Drivers size: 628.5KB
Congrats, you have completed the process to Install stock ROM in Moto X4 and successfully fixed the bootloop.
do not hesitate shared firmwares if you have for other variants of the moto X4.
wow, really good guide. a few questions though before i'll jump at it:
is this oreo from the A1 version?
has someone tested this on other variants (brazil, europe, US, etc.)?
does it play nicely with both the 32 and 64 GB versions?
THANKS for this <3
bombaglad said:
wow, really good guide. a few questions though before i'll jump at it:
is this oreo from the A1 version?
has someone tested this on other variants (brazil, europe, US, etc.)?
does it play nicely with both the 32 and 64 GB versions?
THANKS for this <3
Click to expand...
Click to collapse
I installed same firmware on my European model few hours back which is 32gb variant. Working perfectly fine. Not sure about A1 version
Sent from my moto x4 using Tapatalk
rehanraza said:
I installed same firmware on my European model few hours back which is 32gb variant. Working perfectly fine. Not sure about A1 version
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
oreo?
lohanbarth said:
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
Downloads:
PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Minimal ADB Fastboot Drivers size: 628.5KB
Congrats, you have completed the process to Install stock ROM in Moto X4 and successfully fixed the bootloop.
do not hesitate shared firmwares if you have for other variants of the moto X4.
Click to expand...
Click to collapse
Thanks for guide. Kindly add Few things in this guide.
Provided firmware is for US version or X4. There is nothing as such global version released so far.
You need a unlocked bootloader to flash it
If you require to relock bootloader assuming you flashed it on European X4 model you will get message on boot " your device got different software version" only way to get rid of this is to flash exact firmware specific to model.
Hope this helps
Sent from my moto x4 using Tapatalk
---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------
bombaglad said:
oreo?
Click to expand...
Click to collapse
Yes
Sent from my moto x4 using Tapatalk
working 100% fine on xt1900-2.
Can you put that its OREO in the original post?
Merci, lohanbarth
Is this stock or Android One? How did you do this?
What is the difference compared to this one? https://forum.xda-developers.com/showpost.php?p=75055099&postcount=8
Will I need to unlock the bootloader on my European XT1900-7 ? Since you are from France, you should own a EU version, too...
Unlocking the bootloader will prevent future OTAs, I fear. This would be far from being an ideal solution if the only way to relock the bootloader is flashing the proper factory software version...
lohanbarth said:
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in download section).
Now extract stock firmware in ADB Fastboot folder.
Now, connect your device to your PC via a USB Cable.
PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Minimal ADB Fastboot Drivers size: 628.5KB
Congrats, you have completed the process to Install stock ROM in Moto X4 and successfully fixed the bootloop.
do not hesitate shared firmwares if you have for other variants of the moto X4.
Click to expand...
Click to collapse
Wait...is it me or are there no steps here to actually flash the firmware?
worked like a charm for me too (european unlocked 64GB version) XT 1900-7, even with using regular fastboot.exe instead of mfastboot.. THANKS for the guide
another question though just to be sure - is it safe to relock the bootloader?
---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------
mightysween said:
Wait...is it me or are there no steps here to actually flash the firmware?
Click to expand...
Click to collapse
try to open the page in chrome, there is a code window showing what to type into the shell
bombaglad said:
worked like a charm for me too (european unlocked 64GB version) XT 1900-7, even with using regular fastboot.exe instead of mfastboot.. THANKS for the guide
another question though just to be sure - is it safe to relock the bootloader?
---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------
try to open the page in chrome, there is a code window showing what to type into the shell
Click to expand...
Click to collapse
Oh, I am pretty familiar the steps for flashing firmware
Just pointing out that the post itself has no text instructions... and will lead to repetitive questions from people in coming hours and days. ?
---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------
Also, unlocked bootloaders do NOT prevent OTA updates.
working 100% fine on xt1900-4
thanks.
Working great on Mexican x4.
Thx bro
Enviado desde mi moto x4 mediante Tapatalk
Is this for the regular variant or specifically for the Android One variant sold in the U.S?
Is there any particular reason you don't flash the b side /system with the four sparsechunk images with "mfastboot flash system_b system_b.img_sparsechunk.0" (and 1,2,3)?
Edit: I notice it's not in the flashfile.xml or servicefile.xml scripts either. I wonder why they included the system_b.img.sparsechunk files?
DiDGR8 said:
Is there any particular reason you don't flash the b side /system with the four sparsechunk images with "mfastboot flash system_b system_b.img_sparsechunk.0" (and 1,2,3)?
Edit: I notice it's not in the flashfile.xml or servicefile.xml scripts either. I wonder why they included the system_b.img.sparsechunk files?
Click to expand...
Click to collapse
Hmm interesting observation. May b that's y they omitted in oreo
Sent from my moto x4 using Tapatalk
Script to automatic flash
1 download the firmware
2 download the script
3 restart your phone in fastboot mode
4 plug it to your computer
5 click "clickHere.bat" file
6 wait
during the three days . working 100% fine on xt1900-2
Can this work on Xt1900-1? non Project Fi version?
olive23 said:
Can this work on Xt1900-1? non Project Fi version?
Click to expand...
Click to collapse
yes
Related
Hello all,
I currently have a Moto Z XT1650-05 SHERIDAN Dual Sim from China. I tried to install TWRP and root it but messed it all up. Now I am stuck in a bootloop. I tried to flash the stock rom in mfastboot using the XT1650-05 GRIFFIN China Stock ROM but it gets to the "Erasing" screen with a droid and keeps looping from there.
Have tried to google all over for a "SHERIDAN" ROM but not able to find one either. Could any kind soul here point me in the right direction to save my device?
Thanks so much in advance!
You can download stock firmware from there:
http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
use mfastboot to flash it.
alphaeva said:
You can download stock firmware from there:
http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
use mfastboot to flash it.
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately this list does not include the Sheridan variant, only the Griffin ones. It's okay, I managed to figure out a workaround.
how u install goggle play in china version?
...
Just flash any Griffin firmware, for safety you should first delete gpt and bootloader IMG. These variants share their firmware with each other, according to website spec info.
Sent from my XT1650 using XDA-Developers mobile app
I have the same trouble with my European version. I tried to flash a griffin version and now it is stuck in bootloop
I had the same issue awhile ago. I fixed it by using the ADB command prompts version and installing it piece by piece. It took longer but works flawlessly now. The directions are somewhere in the forums Ill see if I can find them.
Here is the command I use to flash the ROM
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash system system.img_sparsechunk.13
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
erase partition.gpt
evanxyj said:
Just flash any Griffin firmware, for safety you should first delete gpt and bootloader IMG. These variants share their firmware with each other, according to website spec info.
Sent from my XT1650 using XDA-Developers mobile app
Click to expand...
Click to collapse
hi, how can erase partition gpt?
because is the only one with errors in fastboot load rom
thanx
rvinturis said:
hi, how can erase partition gpt?
because is the only one with errors in fastboot load rom
thanx
Click to expand...
Click to collapse
Sorry. No idea about your situation, but instinct tells me you are mostly fxxked up if you mess up with gpt partition.
Sent from my OnePlus3T using XDA Labs
I try to install stock rom for motorola xt 1650-03 griffin , but was not good idea . Because is not genuine for my moto z Sheridan . Now my moto work like a charm but during the start up , remain in fastboot mode, after that must push the power button in start for continue start up process. Afterthat everything is normal. My moto z Sheridan have unlock bootloader, no Root and official firmware 7.0
---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------
I cannot find stok rom nougat for Sheridan european model. Xt1650-03.
rvinturis said:
Now my moto work like a charm but during the start up , remain in fastboot mode, after that must push the power button in start for continue start up process.
I cannot find stok rom nougat for Sheridan european model. Xt1650-03.
Click to expand...
Click to collapse
To fix stuck @ bootloader (START only) - on bootloader, run:
Code:
fastboot oem fb_mode_clear
Then restart it, tell me if it helps
i have the same problem, have xt1650-03 sheridan, i can use some roms, but i want a stock rom and lock the bootloader bsecause my bluetooth died.
fastboot oem fb_mode_clear it works.
HELP!
solitudinal said:
Thanks for the reply. Unfortunately this list does not include the Sheridan variant, only the Griffin ones. It's okay, I managed to figure out a workaround.
Click to expand...
Click to collapse
please tell me what you have done because im stuck with the same problem
help!
solitudinal said:
Thanks for the reply. Unfortunately this list does not include the Sheridan variant, only the Griffin ones. It's okay, I managed to figure out a workaround.
Click to expand...
Click to collapse
please tell what was the workaround because im facing the same problem and dont know what to do!!!:crying:
Get the Firmware Here
Flash without Locking bootloader
Code:
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 erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
fastboot reboot
Flash and lock bootloader
Code:
fastboot oem fb_mode_set
fastboot oem lock
fastboot oem lock
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 erase userdata
fastboot erase cache
fastboot oem lock
fastboot oem fb_mode_clear
fastboot reboot
Flashed on XT1710-06 Mexico ATT and it worked fine, coming from Oreo April update btw, thanks.
I've different experience...
I've XT1710-11 (ZUI bought from www.jd.com)
When I flashed from ZUI to this 8.0 without the modem - the fingerprint sensor stopped from working [I had no SIM inside so I cannot verify if the modem worked Or not]
I tried stock 7.1.1 RETAIL without modem - it worked well.
Tried going to 8.0 April without success - fingerprint still failed.
Tried 8.0 RETUS no sucess
went back to ZUI for XT1710-08 with modem everything worked well
Then tried again this stock without modem - same no fingerprint sensor
Then tried adding the modem the fingerprint sensor worked well... when inserted the sim the modem worked well - so maybe for XT1710-11 no need to avoid the modem.
saturn_frak said:
Then tried adding the modem the fingerprint sensor worked well... when inserted the sim the modem worked well - so maybe for XT1710-11 no need to avoid the modem.
Click to expand...
Click to collapse
I did that too, flashed everything and it worked like a charm, right now i have root with magisk and all is just pretty great
This is working well so far, except with Substratum?
still require signed boot.img for relock the bootloader xt1710-09
HamZusGh said:
still require signed boot.img for relock the bootloader xt1710-09
Click to expand...
Click to collapse
Please let me know, if you have a solution for flashing the newest update as I have the same version with unlocked bootloader
With pleasure
GermAndi said:
Please let me know, if you have a solution for flashing the newest update as I have the same version with unlocked bootloader
Click to expand...
Click to collapse
Ok man
Hello guys today i relock my bootloader on XT1710-09 with this firmware and tgis adb https://www.mediafire.com/file/h409ny7pa42z0j1/ and this adb
1-you download this firmware
2-download adb moto z2 play from the lik https://www.mediafire.com/file/h409ny7pa42z0j1/
3- unzip it in the same folder
4- lunch bloqear Bootloader moto z2 play.bat
The phone must reboot with locked bootloader
Sorry for my bed English and i wish this work with you guys
15mins to boot!?!
hi there,
first thx for this guide. i got my z2 last week and tried some customs roms. but no one satisfied me so i decide to go back to stock.
everything worked well with this guide.
then i got some probs with magisk but finally it worked too. then i installed xposed beta3 and luckypatcher.
with luckypatcher i tried to uninstall some systemapps and to block ads. but it didnt work. after uninstalling some apps they dont disappear from app drawer and all ads are shown on webpages.
and when i reboot my phone it tooks me up to 15mins!!! and all system apps that i updated through play store previously wants to be updated again.
so this looks like that everything get reinstalled everytime i reboot my phone.
does someone has this too?
can someone give me a hint how to solve this?
thx in advance...
:cyclops:
@rahulsnair
link for firmware is dead!?
:cyclops:
The link of the firmware is dead.
found this page: https://www.stockrom.net/motorola
latest rom there: https://www.stockrom.net/2018/05/albus.html
:cyclops:
---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------
i reinstalled this rom and now, withot xposed, its running. yes!!!
does someone installed xposed successfully?
further i tried to install adaway. when it tries to save the host files into /system/ect it has not the permissions even as supersu through magisk.
i changed the location to /data/data but then the symlink cant be created.
so i did that in twrp. but after reboot the symlink seems to be overwritten.
any ideas what can be done?
:cyclops:
After few time unsuccessful relock my Z2 play. I tried this way and everything is good.
Remember the re-lock process must be 2 steps flash with flashboot
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 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 cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Restart the phone and allow USB Debug again
Code:
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash boot boot.img
fastboot oem lock
I am wondering if anyone has successfully flashed this to a locked down, Verizon version of this phone (1710-02), via fastboot command prompt. Also, if so, had VO-LTE working afterword.
I appreciate any response.
afterlastangel said:
After few time unsuccessful relock my Z2 play. I tried this way and everything is good.
Click to expand...
Click to collapse
Hi,
After doing this, is your phone just like stock ? I mean not warning on boot logo, no N/A or Bad Key on boot logo, OTAs working fine and safety net passing successfully ?
Thanks
lcrok said:
Hi,
After doing this, is your phone just like stock ? I mean not warning on boot logo, no N/A or Bad Key on boot logo, OTAs working fine and safety net passing successfully ?
Thanks
Click to expand...
Click to collapse
Probably the warnings on boot logo will keep until you lock bootloader again
8bitcode said:
Flashed on XT1710-06 Mexico ATT and it worked fine, coming from Oreo April update btw, thanks.
Click to expand...
Click to collapse
Which one?
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 08:13 AM ---------- Previous post was at 08:08 AM ----------
afterlastangel said:
After few time unsuccessful relock my Z2 play. I tried this way and everything is good.
Remember the re-lock process must be 2 steps flash with flashboot
Restart the phone and allow USB Debug again
Click to expand...
Click to collapse
No boot.img sign required this way?
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 08:18 AM ---------- Previous post was at 08:13 AM ----------
lcrok said:
Hi,
After doing this, is your phone just like stock ? I mean not warning on boot logo, no N/A or Bad Key on boot logo, OTAs working fine and safety net passing successfully ?
Thanks
Click to expand...
Click to collapse
If bootlogo is flashed (as it is) no warning sign should be there anymore.
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Which one?
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 08:13 AM ---------- Previous post was at 08:08 AM ----------
No boot.img sign required this way?
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 08:18 AM ---------- Previous post was at 08:13 AM ----------
If bootlogo is flashed (as it is) no warning sign should be there anymore.
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
lcrok said:
Hi,
After doing this, is your phone just like stock ? I mean not warning on boot logo, no N/A or Bad Key on boot logo, OTAs working fine and safety net passing successfully ?
Thanks
Click to expand...
Click to collapse
I can confirm it went back to original state, no sign needed.
I has problem with my fingerprint reader after using in rain. So I need to go back to stock for warranty, and Moto replaced sensor with a new one.
el-Loko said:
@rahulsnair
link for firmware is dead!?
:cyclops:
Click to expand...
Click to collapse
... Very
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 08:31 AM ---------- Previous post was at 08:28 AM ----------
afterlastangel said:
I can confirm it went back to original state, no sign needed.
I has problem with my fingerprint reader after using in rain. So I need to go back to stock for warranty, and Moto replaced sensor with a new one.
Click to expand...
Click to collapse
Thanks, but download link is pretty dead anyway. Can you provide a copy for the community, please?
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 08:33 AM ---------- Previous post was at 08:31 AM ----------
HamZusGh said:
Hello guys today i relock my bootloader on XT1710-09 with this firmware and tgis adb https://www.mediafire.com/file/h409ny7pa42z0j1/ and this adb
1-you download this firmware
2-download adb moto z2 play from the lik https://www.mediafire.com/file/h409ny7pa42z0j1/
3- unzip it in the same folder
4- lunch bloqear Bootloader moto z2 play.bat
The phone must reboot with locked bootloader
Sorry for my bed English and i wish this work with you guys
Click to expand...
Click to collapse
Which device version is this intended for, please?
Sent from my Moto Z2 Play using XDA Labs
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO G5S:
Download Moto G5s Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash oem oem.img
mfastboot erase cache
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear
mfastboot reboot
Downloads:
All firmware MONTANA_OPP28.65-37 : 1.5GB
MONTANA_OPP28.65-37-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
MONTANA_OPPS28.65-37-2-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Minimal ADB Fastboot Drivers size: 628.5KB
it´s worked ! thanks
Retbr or retus? Thanks
Sent from my Moto G5s using XDA Labs
Montana XT1792 ?
Android official oreo?
Do you have petch security preference?
Touch Screen not Working!
Retbr here, no bugs or others problems
worked, thank you
Someone has tried in the XT1790?
Will this change the software channel from retin to retla? @lohanbarth
wesmat95 said:
Will this change the software channel from retin to retla? @lohanbarth
Click to expand...
Click to collapse
yes it will change your software channel so that it does not flash flasher zip kaminari.
Works on reteu?
Hi the process to unlock bootloader Is the same as android 7?, And if is the same, the twrp also Is the same forma Android oreo ?
I have a doubt. I installed the kaminari zip. Can I flash this without problems? I wanted to clean the phone and take advantage.
Adi5 said:
Works on reteu?
Click to expand...
Click to collapse
Yes
Cesarcami53 said:
Hi the process to unlock bootloader Is the same as android 7?, And if is the same, the twrp also Is the same forma Android oreo ?
Click to expand...
Click to collapse
Yes
LucasUruguay said:
I have a doubt. I installed the kaminari zip. Can I flash this without problems? I wanted to clean the phone and take advantage.
Click to expand...
Click to collapse
it's the same ROM, but yes you can flash it
Software channel not changed
Hi @lohanbarth, I flashed the ROM and works great. But you mentioned that software channel will change to retla. But in about phone it is still showing retin. I used regular fastboot( not mfastboot) on Ubuntu 18
Will this work on a retgb device running NPPS26.102-49-11? Thanks
Works on reteu,channel ofc its still reteu
I dirty flashed in my dad's phone works fine till now,if any problems will happen I will clean flash?
Just omited fastboot erase userdata
siarp said:
Will this work on a retgb device running NPPS26.102-49-11? Thanks
Click to expand...
Click to collapse
Yes
Adi5 said:
Works on reteu,channel ofc its still reteu
I dirty flashed in my dad's phone works fine till now,if any problems will happen I will clean flash
Just omited fastboot erase userdata
Click to expand...
Click to collapse
By dirty flashing you just skipped erase userdata command, yes?
Daniel936 said:
By dirty flashing you just skipped erase userdata command, yes?
Click to expand...
Click to collapse
Yes
[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.
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.