[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.
Related
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
I've tried flashing stock firmware from 6.0.1 then flashing ota through side load
Flashing other countries firmware (which always ends in fail messages)
I've tried multiple rom from the forum which just loop.
I've spent about 6 hours trying different combinations of recovery, boot and other images with no luck.
Any help is appreciated.
Sent from my iPhone using Tapatalk
criptix said:
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
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 adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
HippieFlasher said:
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
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 adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
Click to expand...
Click to collapse
Dude, you are awesome. Worked like a charm. Was missing fastboot getvar max-sparse-size andbfastboot oem fb_mode_set plus I was flashing the modem after the chunks. Thanks again!
Sent from my iPhone using Tapatalk
Anytime! Glad I could help!
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.
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
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.
Hey everyone
My motorola one deen xt 1941-4 64GB PVT1 is not starting up
its just giving error Start Up Failed
Its just starting up in bootloader mode with locked oem and AP Fastboot Flash Mode (Secure).
Not going into recovery
not going into factory mode
Can you plz help me out to solve it plz
nashi_jee said:
Hey everyone
My motorola one deen xt 1941-4 64GB PVT1 is not starting up
its just giving error Start Up Failed
Its just starting up in bootloader mode with locked oem and AP Fastboot Flash Mode (Secure).
Not going into recovery
not going into factory mode
Can you plz help me out to solve it plz
Click to expand...
Click to collapse
Are you familiar with flashing moto firmware with fastboot.exe ?
Did it install an update recently?
Sent from my mata using XDA Labs
sd_shadow said:
Are you familiar with flashing moto firmware with fastboot.exe ?
Did it install an update recently?
Click to expand...
Click to collapse
Not much familiar but know some basics.
No it did not install any update.
My wife just powered it off during a call and when tried to turn it on it showed up with the message
I have tried to unlock bootloader but it requires developer option to be turned on.
Simply I can follow the instructions if you provide some.
And thanks for reply buddy
nashi_jee said:
Not much familiar but know some basics.
No it did not install any update.
My wife just powered it off during a call and when tried to turn it on it showed up with the message
I have tried to unlock bootloader but it requires developer option to be turned on.
Simply I can follow the instructions if you provide some.
And thanks for reply buddy
Click to expand...
Click to collapse
I would start with
Motorola smart assistant
It has a recovery option
There's a link in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my mata using XDA Labs
sd_shadow said:
I would start with
Motorola smart assistant
It has a recovery option
There's a link in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Click to expand...
Click to collapse
I have already tried this LMSA. It shows its model in recovery option i.e xt1941-4. But when I try to recover it ends up with MODEL NOT SUPPORTED
Waiting for reply / solution from any expert please.
nashi_jee said:
Waiting for reply / solution from any expert please.
Click to expand...
Click to collapse
You could flash firmware but if you don't flash the correct firmware for the software channel on the device it won't work.
Usually the software channel is the named for the carrier or region.
https://mirrors.lolinet.com/firmware/moto/deen/official/
You can flash the firmware with fastboot.exe
Setting up and Using adb.exe and fastboit.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
The flashing commands should be
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
Another option would be trying to switch a/b system
Hoping that the non active partition is bootable.
Some instructions about that in my adb thread.
Sent from my mata using XDA Labs
---------- Post added at 05:58 PM ---------- Previous post was at 05:57 PM ----------
Switching active system partition is the easiest
If the bootloader will even allow the commands
It may not.
Sent from my mata using XDA Labs
Thanx to help me.
But I am confused.
Can you plz help me through team viewer or wonething like that if you dont mind
sd_shadow said:
You could flash firmware but if you don't flash the correct firmware for the software channel on the device it won't work.
Usually the software channel is the named for the carrier or region.
https://mirrors.lolinet.com/firmware/moto/deen/official/
You can flash the firmware with fastboot.exe
Setting up and Using adb.exe and fastboit.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
The flashing commands should be
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
Another option would be trying to switch a/b system
Hoping that the non active partition is bootable.
Some instructions about that in my adb thread.
Sent from my mata using XDA Labs
---------- Post added at 05:58 PM ---------- Previous post was at 05:57 PM ----------
Switching active system partition is the easiest
If the bootloader will even allow the commands
It may not.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I tried RSD Lite last night and successfully flashed the firmware but the problem still exists.
Everything gone good then why its not back into life?
One more thing I am thinking that the firmware folder does not contain any recovery file. Is it normal?
nashi_jee said:
You could flash firmware but if you don't flash the correct firmware for the software channel on the device it won't work.
Usually the software channel is the named for the carrier or region.
https://mirrors.lolinet.com/firmware/moto/deen/official/
You can flash the firmware with fastboot.exe
Setting up and Using adb.exe and fastboit.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
The flashing commands should be
I tried RSD Lite last night and successfully flashed the firmware but the problem still exists.
Everything gone good then why its not back into life?
One more thing I am thinking that the firmware folder does not contain any recovery file. Is it normal?
Click to expand...
Click to collapse
Recovery is part of the boot.img now
Sent from my mata using XDA Labs
sd_shadow said:
Recovery is part of the boot.img now
Click to expand...
Click to collapse
It finishes successfully but again comes up with same error
i face same problem you solve that problem or still not?
Same problem
Hey guys. Wait please I'm working for your blank flash for your device . Recently I worked two models before . Check this coming soon I'll add your model.
https://forum.xda-developers.com/one-vision/how-to/start-failed-motorola-one-macro-t4082275/amp/
still No luck mate.
yehison said:
Hey guys. Wait please I'm working for your blank flash for your device . Recently I worked two models before . Check this coming soon I'll add your model.
https://forum.xda-developers.com/one-vision/how-to/start-failed-motorola-one-macro-t4082275/amp/
Click to expand...
Click to collapse
Should I try this method for Motorola XT1941-4?