THIS IS NOT FOR DROID TURBO 2 I REPEAT DONT DO THIS FOR DROID TURBO 2
How to Manually Official Firmware on any Motorola Device
Requisites:
Unlocked Bootloader if you want to flash firmware from another country or locked bootloader to flash the official firmware from the country/carrier of your device
Android Studio or Minimal ADB and Fasboot (i personally recommend Minimal Adb and Fastboot because thats all we gonna need and its lighter than Android Studio 2 Mb vs 800Mb)
Official Firmware you want to flash
mFastboot (motorola Fastboot) i uploaded it for you: https://mega.nz/#!pI9iVZwS!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
RSD LITE is the fastest way if you want to install the official firmware of your phone, download latest RSD lite, download the firmware of your phone carrier/country, open rsd select the .zip and start flash, your phone will reboot when done, thats all, RSD lite doesnt work if you want to flash firmware from another country, just your phone default carrier/country firmware
Installation:
1.- Install MAaF
Install Minimal ADB and Fastboot
2.- Install mFastboot
Copy the contents of mfastboot.zip and put them on Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
Now you have working Fastboot AND mFastboot
3.- Copy Firmware
Copy the contents of your desired firmware to Minimal ADB and Fastboot Folder like this:
Now you are ready to flash!
First turn off your device and Put it on fastboot mode (Power and volume down for 2 seconds with your phone off)
4.- Get Detected
type
Code:
fastboot devices
on minimal adb to see if your pc detects your phone on fastboot mode
if you get some numbers and letters like the picture you are ready to go.
if not, you are missing drivers, looks for Motorola Device Manager
5.- Install
Copy and Paste these commands on Minimal ADB and Fastboot:
If you are upgrading to Marshmallow use this:
Code:
mfastboot flash bootloader bootloader.img
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem fb_mode_clear
mfastboot reboot
If you are installing a different firmware use this:
mfastboot flash bootloader bootloader.img
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 erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
check the amount of system.img_sparsechunk. your firmware has, if it has 10,12 or 15 add the extra lines required.
And thats all, as easy as copy from here and paste on cmd.
when your phone finishes flashing just press enter to execute mfastboot reboot and you will boot the new firmware.
Tip:
you can remove/skip the line
Code:
mfastboot flash recovery recovery.img
if you want to keep your custom recovery like TWRP
remember:
Flashing another firmware will erase all your information
i know that you can flash without erasing anything but that causes many many errors and inestability i've seen it a lot of times so i encourage to erase everything every time you flash a different firmware, better start fresh.
FAQ
i have a X Force and i want to flash Verizon (or another Firmware) will it work???
Flashing different Kinzie phones firmware will work and boot, however getting signal its another history, all x force are unlocked and there is no problem with them but if you flash droid turbo 2 firmware on moto x force you likely wont get any signal and have wifi issues.
Why i can't just flash it using RSD LITE?
Because somehow it detects the firmware you are on, so you can only flash your original firmware
Why did you not include gpt.bin in the flashing???
Because if you were on marshmallow, installed brasil or another firmware back to lollipop your gpt.bin version will be greater than the one you'll try to flash and it will FAIL TO FLASH, dont worry just skip that line.
Why If i flashed UK/Mexico/Brasil Firmware it says the name of my original Firmware???? did it failed??
Motorola Somehow stores in a separate partition your original firmware name, even if you flash another from another country it will say the name of the original firmware you had, dont worry it doesnt affect anything.
Can i go back to lollipop if i flashed the Mexico or Brasil stock marshmallow???
Yes you can flash back to lollipop without risk of brick if you flashed the mexican or LAT firmware using the method of this thread.
Where i can get my official firmware???
you can get it in another thread i have: [All Kinzie][Official] Stock Firmware Moto X Force / Droid Turbo 2
Im in mexico or brasil Lollipop or marshmallow how can i get root?
Just boot or flash TWRP and flash Super SU for android 5.1 or 6.0.1 by chainfire.
Protip: (my view on flashing soak test on locked devices)
DONT YOU EVER EVER EVER FLASH A SOAK TEST IF YOU HAVE LOCKED BOOTLOADER OR DONT WANT TO UNLOCK, GPT.BIN AND SOME OTHER BOOTLOADER FILES WILL BE UPDATED AND WILL FAIL IF YOU TRY TO FLASH BACK TO OLDER VERSIONS YOU'LL HAVE TO WAIT FOR THE FIRMWARE TO GET OFFICIALLY RELEASED AS A FULL (NOT OTA) AND EVEN THAT ITS NOT A GUARANTEE THAT YOU'LL HAVE YOUR PHONE BACK WORKING, BE CAREFUL WHAT YOU DO TO YOUR PHONE, UNLOCKED BOOTLOADER ITS BEST TO TRY FIRMWARE.
this is a Q&A thread, so if you have any questions just post them here!
i took my time to upload and write this guide for you, so...
If this was useful Press Thanks and if you have $1.00 spare on paypal, i can always take it
Click Donate to me below my name
I see few mistakes in flash commands:
mfastboot flash motoboot bootloader.img - are you sure - motoboot?
mfastboot flash radio radio.img - stock soft don't have radio.img
These brainless peoples will do copy/paste, and write questions "hey i do step by step and don't work" etc.
damkol said:
I see few mistakes in flash commands:
mfastboot flash motoboot bootloader.img - are you sure - motoboot?
mfastboot flash radio radio.img - stock soft don't have radio.img
These brainless peoples will do copy/paste, and write questions "hey i do step by step and don't work" etc.
Click to expand...
Click to collapse
Agreed......Change radio.img to NON-HLOS.bin and change motoboot to bootloader
mFastboot link is dead.
damkol said:
I see few mistakes in flash commands:
mfastboot flash motoboot bootloader.img - are you sure - motoboot?
mfastboot flash radio radio.img - stock soft don't have radio.img
These brainless peoples will do copy/paste, and write questions "hey i do step by step and don't work" etc.
Click to expand...
Click to collapse
it was motoboot because im actually mfastboot not regular fastboot but i'll change it anyway, should be the same.
if there's no radio and you put the command it just continues, theres no danger on keeping it there.
maroof.saeed said:
Agreed......Change radio.img to NON-HLOS.bin and change motoboot to bootloader
Click to expand...
Click to collapse
im avoiding flashing NON-HLOS.bin because it bricks your device if you reflash a older version and has compatibility issues with some firmware, it doesnt affect anything.
Zeljko1234 said:
mFastboot link is dead.
Click to expand...
Click to collapse
fixed.
Jaocagomez said:
it was motoboot because im actually mfastboot not regular fastboot but i'll change it anyway, should be the same.
if there's no radio and you put the command it just continues, theres no danger on keeping it there.
im avoiding flashing NON-HLOS.bin because it bricks your device if you reflash a older version and has compatibility issues with some firmware, it doesnt affect anything.
fixed.
Click to expand...
Click to collapse
Wifi is not working after flashing any idea?
---------- Post added at 10:59 PM ---------- Previous post was at 10:44 PM ----------
Flashed UK Moto X Force XT1580 Android 6.0, Wifi not working, now roll back to 5.1.1, all working
cfw950116 said:
Wifi is not working after flashing any idea?
---------- Post added at 10:59 PM ---------- Previous post was at 10:44 PM ----------
Flashed UK Moto X Force XT1580 Android 6.0, Wifi not working, now roll back to 5.1.1, all working
Click to expand...
Click to collapse
I am sharing a post with all you guyz by uploading a nandroid backup....this will definately solve your issues of not working wifi and so on......
maroof.saeed said:
I am sharing a post with all you guyz by uploading a nandroid backup....this will definately solve your issues of not working wifi and so on......
Click to expand...
Click to collapse
I am just following the guide, unlock oem -> mfastboot -> reboot -> wifi issue (in marshmallow)
With all my respect to OP, but considering people having issues with WiFi after manual flash, it makes me think, that the key for successful upgrade is in the list of commands. When I did it on my device ,I flashed every single command from flashfile.xml , starting from line
<step var="max-sparse-size" operation="getvar"/>
Click to expand...
Click to collapse
and all the way down to
<step var="fb_mode_clear" operation="oem"/>.
Click to expand...
Click to collapse
After this flashing I have zero issues with my phone whatsoever.
I have European version from England.
evgeny71 said:
With all my respect to OP, but considering people having issues with WiFi after manual flash, it makes me think, that the key for successful upgrade is in the list of commands. When I did it on my device ,I flashed every single command from flashfile.xml , starting from line
and all the way down to
After this flashing I have zero issues with my phone whatsoever.
I have European version from England.
Click to expand...
Click to collapse
i think you're right, marshsmallow should have newer modems and im not including modems, thats why wifi its failing.
everyone having wifi issues flash this way:
Code:
mfastboot flash bootloader bootloader.img
mfastboot flash radio radio.img
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst1
mfastboot flash bluetooth BTFM.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem fb_mode_clear
mfastboot reboot
and you will be good to go, this is only for upgrading to marshmallow
edit: added it to main thread.
Jaocagomez said:
i think you're right, marshsmallow should have newer modems and im not including modems, thats why wifi its failing.
everyone having wifi issues flash this way:
Code:
mfastboot flash bootloader bootloader.img
mfastboot flash radio radio.img
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst1
mfastboot flash bluetooth BTFM.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem fb_mode_clear
mfastboot reboot
and you will be good to go, this is only for upgrading to marshmallow
edit: added it to main thread.
Click to expand...
Click to collapse
Correction: there is no radio.img in the list of flashable files. For newbies sake, please remove it from your guide.
Sent from my XT1580 using Tapatalk
evgeny71 said:
Correction: there is no radio.img in the list of flashable files. For newbies sake, please remove it from your guide.
Sent from my XT1580 using Tapatalk
Click to expand...
Click to collapse
it doesnt stop the flashing if theres no radio, but i'll remove it to clean the codes.
Jaocagomez said:
it doesnt stop the flashing if theres no radio, but i'll remove it to clean the codes.
Click to expand...
Click to collapse
You said i cannot flash UK firmware on my Turbo2? Why? My phone is Unlocked Verizon device
Sent from my XT1585 using Tapatalk
zeidof said:
You said i cannot flash UK firmware on my Turbo2? Why? My phone is Unlocked Verizon device
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
What do you mean by "Unlocked Verizon device"?
Anyway, don't even try to flash any Force firmware. Turbo 2 and Force are very similar but not exactly the same. Radio/modem is different, Turbo 2 has locked and unlockable bootloader, some additional apps for Verizon, etc.
If someone find exploit to unlock Turbo 2 bootloader then you may get custom rom or modified Force rom for Turbo 2.
Moto X Force is with me
Zeljko1234 said:
What do you mean by "Unlocked Verizon device"?
Anyway, don't even try to flash any Force firmware. Turbo 2 and Force are very similar but not exactly the same. Radio/modem is different, Turbo 2 has locked and unlockable bootloader, some additional apps for Verizon, etc.
If someone find exploit to unlock Turbo 2 bootloader then you may get custom rom or modified Force rom for Turbo 2.
Moto X Force is with me
Click to expand...
Click to collapse
Dude my device is Unlocked & im using the phone with another carrier in Iran, i've bought it from Moto maker site without any sim
Sent from my XT1585 using Tapatalk
zeidof said:
Dude my device is Unlocked & im using the phone with another carrier in Iran, i've bought it from Moto maker site without any sim
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Dude, read again or search and educate yourself. Turbo 2 is sim free, sim unlocked or whatever you wish to call it but has LOCKED bootloader. That's not the same thing. I was using Turbo 2 with non Verizon sim in US on At&T.
Compare your and mine sig. xt1585 vs xt1580, Turbo 2 vs Moto X Force.
Btw, why you didn't order Force instead? Much better device for any non Verizon network.
P. S.
If you insist to flash Force firmware on Turbo 2, good luck but don't cry after
Sent from my XT1580
Ps
---------- Post added at 02:27 AM ---------- Previous post was at 02:25 AM ----------
Zeljko1234 said:
Dude, read again or search and educate yourself. Turbo 2 is sim free, sim unlocked or whatever you wish to call it but has LOCKED bootloader. That's not the same thing. I was using Turbo 2 with non Verizon sim in US on At&T.
Compare your and mine sig. xt1585 vs xt1580, Turbo 2 vs Moto X Force.
Btw, why you didn't order Force instead? Much better device for any non Verizon network.
P. S.
If you insist to flash Force firmware on Turbo 2, good luck but don't cry after
Sent from my XT1580
Click to expand...
Click to collapse
Mine is xt1585, yeah dude Force was the better choice and this is my mistake
Sent from my XT1585 using Tapatalk
Sent from my XT1585 using Tapatalk
Yeah, that's why I returned Turbo 2 and bought Force
However Turbo 2 is great device.
Sent from my XT1580
zeidof said:
Dude my device is Unlocked & im using the phone with another carrier in Iran, i've bought it from Moto maker site without any sim
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
The fact that you bought Turbo 2 from Moto web site without a sim card from Verizon doesn't mean that the device has unlockable bootloader. The majority of Verizon devices are compatible with GSM carriers (so-called world phones) and can be used on their networks , but their bootloader remains locked, unless your device is XForce, which is GSM only and has unlockable bootloader.
Sent from my XT1580 using Tapatalk
evgeny71 said:
The fact that you bought Turbo 2 from Moto web site without a sim card from Verizon doesn't mean that the device has unlockable bootloader. The majority of Verizon devices are compatible with GSM carriers (so-called world phones) and can be used on their networks , but their bootloader remains locked, unless your device is XForce, which is GSM only and has unlockable bootloader.
Sent from my XT1580 using Tapatalk
Click to expand...
Click to collapse
So if i can unlock my bootloader it will be possible to flash another firmware?
Sent from my XT1585 using Tapatalk
Related
DISCLAMER: i'm not responsible of damage you can apport to your phone following this guide
First of all you need a UNLOCKED BOOTLOADER then of course motorola driver for your pc and fastboot/mfastboot.
The Hardware of Chinese Moto X Force XT1581 is the same of Mexican one, 64Gb dual sim so I flashed MX ROM 6.0 with Chinese firmware file
I used a script to flash, paste it in a notepad and then save as script.bat in the same folder cointein firmware files and fastboot/mfastboot:
@ECHO OFF
ECHO.
ECHO. Script by @evogp ...
ECHO.
ECHO.
ECHO. Flashing Bootloader ...
ECHO.
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
ECHO.
ECHO. Flashing System ...
ECHO.
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
ECHO.
ECHO. Flashing Modem SW ...
ECHO.
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
ECHO.
ECHO. Wipe Cache and Data ...
ECHO.
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
ECHO.
ECHO. Installation Complete!
ECHO.
PAUSE
mfastboot reboot
EXIT /b 0
Click to expand...
Click to collapse
POWER OFF YOUR DEVICE then press power+vol down for about 2 seconds so you are in recovery mode, launch script.bat, wait you phone should automatically reboot in a couple of minutes.
Often flashing modem fail the first time so the script repit the operation...
if you want a "ready and working ROM" go here:
https://drive.google.com/file/d/0B8xKzkQTdRcVWGQ0dVFnZV9vNTg/view
it's the modified MX rom with Chinese modem
source: http://4pda.ru/forum/index.php?showtopic=752644&st=680
Have fun!
Hi, i think your link points to the wrong rom. The Mexican rom should be a XT1580 file...
help
I've put it and now I get a poster with the warning warning bootloader unlocked!Certainly not the one from Mexico is verizon USA to see if you can put the right one so that I can fix it thank you very much
jose lito said:
I've put it and now I get a poster with the warning warning bootloader unlocked!Certainly not the one from Mexico is verizon USA to see if you can put the right one so that I can fix it thank you very much
Click to expand...
Click to collapse
Sorry guys! My mistake, I corrected the link
here the correct one:
https://drive.google.com/file/d/0B8xKzkQTdRcVWGQ0dVFnZV9vNTg/view
Thanks
Everything ok now, I put the room and the phone revived .android 6 running on xt1581. Thanks again
You are great for me its works just fine
fine job!
Works fine. Does anyone know if the mexican android does get otas or security updates in general?
lorissuper said:
Sorry guys! My mistake, I corrected the link
here the correct one:
https://drive.google.com/file/d/0B8xKzkQTdRcVWGQ0dVFnZV9vNTg/view
Click to expand...
Click to collapse
If i used this file, should i do that script again ? Or this file is already merge with suitable modem for xt1581? Btw any link for unlock bootloader ?
lorissuper said:
ECHO.
ECHO. Flashing Modem SW ...
ECHO.
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
Click to expand...
Click to collapse
What's the purpose of all of this?
- Flashing modem partition
than:
clearing modem parition 1
clearing modem parition 2
Flashing modem (again)
Flashing modem (again, and again)
Flashing modem (again, again and again)
check the bootloader log, first time modem flash fails. So all is necessary except the last line, which is included just to be sure. You are free to remove as you wish!
just to inform, i've tried to flash my chinese XT1581 with "XT1580_KINZIE_RETLA_DS_6.0" firmware just keeping the "fsg.mbn" file from this topic, and it works fine wifi and 4g signals are ok.... maybe that will work for another firmwares
undrtkrr said:
just to inform, i've tried to flash my chinese XT1581 with "XT1580_KINZIE_RETLA_DS_6.0" firmware just keeping the "fsg.mbn" file from this topic, and it works fine wifi and 4g signals are ok.... maybe that will work for another firmwares
Click to expand...
Click to collapse
So this firmware works too for xt1581 ?
Please give me link right then
Thanks
frey.derico said:
So this firmware works too for xt1581 ?
Please give me link right then
Thanks
Click to expand...
Click to collapse
yes, i've tested on my XT1581 and its working since yesterday with no problems... i'm sorry but i can't post links on XDA because i'm new user
but you can do like me and download any XT1580 dual sim firmware from "firmware.center" website then extract and replace the "fsg.mbn" file of original firmware with "fsg.mbn" found in the firmware of first post of this topic
flash the original firmware with replaced "fsg.mbn" file, and it will work
Thank you for your awesome work!
It is working fine for me! My china Kinzie XT1581 arrived yesterday and i've followed your tutorial. Modem failed to install at first attempt like you said but it installed just fine at the 2nd one! tested almost everything and its perfect! all SIM cards from Brazil that i have are working fine.
Regards,
Queiroz
Hi from Germany,
today I get my XT1581 from China it works well, but with android version 5.1.1....and it gets no updates
I understand I can update it with aDual Sim FW (may from Mexico). Should I unlook the bootloader first?
Will then work the App "Moto" with any language ?
Thanks
crash64 said:
Hi from Germany,
today I get my XT1581 from China it works well, but with android version 5.1.1....and it gets no updates
I understand I can update it with aDual Sim FW (may from Mexico). Should I unlook the bootloader first?
Will then work the App "Moto" with any language ?
Thanks
Click to expand...
Click to collapse
Dude, YES first of all you have to unlock BL!!
# PC: install MOTO drivers & minimal ADB & mfastboot
# unlock BL
# remove 'unlocked BL warning'
# flash firmware as told in OP (1st page)
# be happy
if you want Root/Xposed..too, flash TWRP for kinzie and SU 2.62-3
search for tut's on XDA - read carefully!!!
App "Moto" will work with GER language.
may the force with you!
Good Morning,
thanks very much. I will try. I hope it will work. Will then work updates via OTA too?
Best regards
crash64 said:
Good Morning,
thanks very much. I will try. I hope it will work. Will then work updates via OTA too?
Best regards
Click to expand...
Click to collapse
i think thats no OTA updates for unlocked bootloader
Hello one more question,
if I flashed my China Xt1581 with the Mexiacan Stock Rom, is it then possible to lock the bootloader and get updates via OTA?
Thanks
crash64 said:
Hello one more question,
if I flashed my China Xt1581 with the Mexiacan Stock Rom, is it then possible to lock the bootloader and get updates via OTA?
Thanks
Click to expand...
Click to collapse
Hi, FYI!
https://mobilesupport.lenovo.com/us/en/Solution/MF91999
Here you go, Android 7.1.1 Stock ROM for Moto Z Play.
https://www.androidfilehost.com/?fid=673368273298986785
Official ??
ROM_HUNTER said:
https://www.androidfilehost.com/?fid=673368273298986785
Click to expand...
Click to collapse
Is it official or wot ??
LovinVEVO said:
Is it official or wot ??
Click to expand...
Click to collapse
It's stock rom but not signed by Motorola.
ROM_HUNTER said:
It's stock rom but not signed by Motorola.
Click to expand...
Click to collapse
How can I update? Using RSD normally like another Stock ROM?
Fabio Magalhaes said:
How can I update? Using RSD normally like another Stock ROM?
Click to expand...
Click to collapse
Yes, or save this as a batch file and execute it.
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 flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Is it safe to flash gpt.bin? With other images there was a risk of hard-bricking if something went wrong there.
I only want to update my bootloader and firmware, so for that I'd do:
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 oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Question is if I should exclude the gpt.
Also: Is this compatible with reteu, or for what variant is it? I have XT1635-02 reteu.
BtbN said:
Is it safe to flash gpt.bin? With other images there was a risk of hard-bricking if something went wrong there.
I only want to update my bootloader and firmware, so for that I'd do:
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 oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Question is if I should exclude the gpt.
Also: Is this compatible with reteu, or for what variant is it? I have XT1635-02 reteu.
Click to expand...
Click to collapse
Just a headsup, updating only the GPT, bootloader and parts of the firmware is risky - unless you're already on the same patch level of the firmware. This is likely because only a partial flash may result in a mismatch between your system and your bootloader in terms of patch level. I don't recall the GPT causing hard bricks, it's more the bootloader that's a big cause of bricks because of having the aforementioned mismatch.
Thus, if you accept OTA updates, the OTA update will attempt to patch your device thinking that your system and bootloader are on the same patch level. As you've only done a partial update, the OTA will either fail or successfully patch, only to corrupt your mismatched bootloader, leading to a hard brick. We've seen this behaviour with downgrading a device's system (but not bootloader), so it'd be a similar state to your device if you updated like this and then accepted an OTA, and this bricking behaviour has been observed on partially updated Moto G4/Plus, Z Play and X devices, to name a few. Of course, you may receive an OTA update that may bring you to the same patch level as your updated bootloader/GPT, which may work, but it's a gamble.
Thus, if you're gonna update, fully update to the same patch level (that includes modem as well), do not mix and match parts of different builds (or if you do, remember not to update via OTA).
As for whether this build is suitable for EU devices, hopefully those who uploaded the stock ROM can comment.
echo92 said:
Thus, if you're gonna update, fully update to the same patch level (that includes modem as well), do not mix and match parts of different builds (or if you do, remember not to update via OTA).
Click to expand...
Click to collapse
I'm running LineageOS and am only looking for a way to update my bootloader and modem firmware.
What confuses me about this: It says NPNS, instead of just NPN or MPN. What's the meaning of those abbreviations?
The listed baseband version ends in an R. The one of other people ends with an e. It this just a typo?
BtbN said:
I'm running LineageOS and am only looking for a way to update my bootloader and modem firmware.
Click to expand...
Click to collapse
Hmm, I don't know if it'll work - in theory, it could as Lineage OS only affects your system/data. Of course, you'd have to remember that if you were to revert back to stock, to reflash at least the same stock ROM as your bootloader patch level.
Still would be better to completely flash the same stock ROM onto your device (of course this would wipe Lineage and TWRP off your device). What do you hope to gain from updating your bootloader/GPT and modem compared to your existing firmware?
As far as I know:
MPN - Marshmallow firmware
NPN - Nougat firmware
NPNS - Nougat firmware with added security patch updates
Usually your baseband, from what I've seen, ends in R (e.g. for Moto G4, our latest basebands end in 62.01R). If it ends in e, it's either a typo or something has gone wrong with the underlying firmware, I've not noted working modem firmware working if ending in anything other than R.
echo92 said:
Usually your baseband, from what I've seen, ends in R (e.g. for Moto G4, our latest basebands end in 62.01R). If it ends in e, it's either a typo or something has gone wrong with the underlying firmware, I've not noted working modem firmware working if ending in anything other than R.
Click to expand...
Click to collapse
My current baseband ends in an e, according to the Phone Status page in my settings. See attached image.
Just want to be up to date with what LaOS expects. As it declares 7.1.1 to be the target, and my device has not gotten any firmware updates since the first 7.0 firmware which it updated to when I got it.
On another note, putting the filename into google ends up with this link: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Looks pretty official to me. The sha1sum of that file is e94b9690de5417b4499d8995726ccaf5d0492d5e
So whats are the correct steps?
Should I flash gtp or not?
---------- Post added at 08:52 PM ---------- Previous post was at 08:52 PM ----------
So whats are the correct steps?
Should I flash gtp or not?
Hi, hyoga68. I´ve updated my Moto Z Play using RSD, but you can do by prompt. I think you´ll be in trouble if you downgrade ROM, but in this case we´ll be updating, with the newest ROM avaible.
Fabio Magalhaes said:
Hi, hyoga68. I´ve updated my Moto Z Play using RSD, but you can do by prompt. I think you´ll be in trouble if you downgrade ROM, but in this case we´ll be updating, with the newest ROM avaible.
Click to expand...
Click to collapse
Thanks, will try to get a PC with Windows, and try with RSD ...
Did anyone try to re-lock the bootloader with this image?
Thanks!
New Stock ROM with September Security Patch: upped by Rickk182440 - https://androidfilehost.com/?fid=889964283620757667
Fabio Magalhaes said:
New Stock ROM with September Security Patch: upped by Rickk182440 - https://androidfilehost.com/?fid=889964283620757667
Click to expand...
Click to collapse
Can I clean flash this over a custom ROM on my reteu MZP?
MZP with unlocked bootloader?
Fabio Magalhaes said:
MZP with unlocked bootloader?
Click to expand...
Click to collapse
Hint: Custom ROM is not possible without.
Deleted
tag68 said:
Hint: Custom ROM is not possible without.
Click to expand...
Click to collapse
So... Go on
I am currently running 7.1.1 and the more I read in these forums about hard bricking my device due to some weirdness with the bootloader the more worried I get. Can someone please verify that I can safely flash the image ADDISON_NPNS26.118-22-2-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip using the following commands?
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
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 system system.img_sparsechunk.10
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase cache
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear
Used those exact commands to restore mine to stock. Just make sure when you extract it you flash the correct amount of superchunks. Like if it has 12 flash all 12. Other than that as long as you're not trying to get back to 6.0 you won't brick
justsomeguy007 said:
Used those exact commands to restore mine to stock. Just make sure when you extract it you flash the correct amount of superchunks. Like if it has 12 flash all 12. Other than that as long as you're not trying to get back to 6.0 you won't brick
Click to expand...
Click to collapse
1. Would it be of any concern if I had TWRP installed before doing this process?
2. Is there a way to do this flashing without losing my user data too?
Brutal_Master said:
1. Would it be of any concern if I had TWRP installed before doing this process?
2. Is there a way to do this flashing without losing my user data too?
Click to expand...
Click to collapse
1) TWRP usually will get overwritten by the stock recovery in the flash recovery step, thus it shouldn't affect the flash. You will have to reflash TWRP after you've updated.
2) you can try to save your data by omitting the 'mfastboot erase userdata' command in fastboot. Either skip this command or delete it from the flashing script. I would still caution you back up your data(either in TWRP or copying your files) and transfer the back up off your device, in case you have to factory reset if your device becomes unstable.
Usually, you only experience hard bricks or serious risks of hard bricking if you downgrade your firmware (without downgrading your bootloader) and then attempt to install OTA updates. The OTA update may corrupt your newer bootloader, and generally bootloaders block attempts to downgrade the bootloader patch level. Thus, if you do downgrade, generally do not use OTA updates. Motorola only appears to have designed their firmware and their OTA patches for upgrading.
Does anyone have the unlocked variant on Verizon? I'd love to know if WiFi calling works like the Verizon variant.
Thanks so much.
I do. No issues. Popped in sim from Moto X Pure Edition and set it up.
I have not used wifi calling.
I don't even know how to use wifi calling.
What are the advantages of wifi calling?
WiFi Calling Only on Verizon Variants
I have the 64 GB Unlocked Z2 Play on Verizon and no, there is no WiFi calling.
That option can only be enabled via settings options that are specific to Verizon's software. It is the one feature I really miss.
I have the unlock 1710-01. Put Verizon software on it and enabled wifi calling. Can't get video calling to work though.
bear263 said:
I have the unlock 1710-01. Put Verizon software on it and enabled wifi calling. Can't get video calling to work though.
Click to expand...
Click to collapse
Which Verizon software?
The firmware?
pizza_pablo said:
Which Verizon software?
The firmware?
Click to expand...
Click to collapse
Yes. Verizon firmware. You can't update it through the phone with a unlocked bootloader. Use Verizon's software upgrade assistance to update. It'll say it failed but it doesn't.
bear263 said:
Yes. Verizon firmware. You can't update it through the phone with a unlocked bootloader. Use Verizon's software upgrade assistance to update. It'll say it failed but it doesn't.
Click to expand...
Click to collapse
Thanks, but I'm not interested in VZW firmware.
You wrote "software" so I was thinking a Verizon app.
bear263 said:
I have the unlock 1710-01. Put Verizon software on it and enabled wifi calling. Can't get video calling to work though.
Click to expand...
Click to collapse
did you just flash system.img or all the firmware
bear263 said:
I have the unlock 1710-01. Put Verizon software on it and enabled wifi calling. Can't get video calling to work though.
Click to expand...
Click to collapse
Just curious, did you go to MY Verizon, Log in, My devices, My Plan and Services, Manage Products & Apps, Free Products and see if your line is compatible, if so click the Git It Now button. See attached
Then, on your phone go to settings, Network & Internet, Advanced Calling and enable it there.
BTW, HD Voice vonly works (is noticeable) when you're calling another VZW phone with HD Voice (using the HD Codec).
pizza_pablo said:
I do. No issues. Popped in sim from Moto X Pure Edition and set it up.
I have not used wifi calling.
I don't even know how to use wifi calling.
What are the advantages of wifi calling?[/Q
Hello brother, you unlocked the bootloader of your z play 2 of Verizon is not supposed to be done but if you succeeded you could say how you managed to do it in mine you would be grateful for the help
Click to expand...
Click to collapse
pirana1920 said:
Hello brother, you unlocked the bootloader of your z play 2 of Verizon is not supposed to be done but if you succeeded you could say how you managed to do it in mine you would be grateful for the help
Click to expand...
Click to collapse
My Z2 Play is not the Verizon version XT1710-02, but the US Unlocked version XT1710-01.
mrhodes19904 said:
did you just flash system.img or all the firmware
Click to expand...
Click to collapse
Complete firmware using fast boot. After that, you can use the software upgrade assistant.
---------- Post added at 05:14 AM ---------- Previous post was at 05:06 AM ----------
wanb1i said:
Just curious, did you go to MY Verizon, Log in, My devices, My Plan and Services, Manage Products & Apps, Free Products and see if your line is compatible, if so click the Git It Now button. See attached
Then, on your phone go to settings, Network & Internet, Advanced Calling and enable it there.
BTW, HD Voice vonly works (is noticeable) when you're calling another VZW phone with HD Voice (using the HD Codec).
Click to expand...
Click to collapse
Yes. HD voice is activated. Just can't use the video calling with Verizon built in dialer. Have to use google duo.
bear263 said:
Complete firmware using fast boot. After that, you can use the software upgrade assistant.
---------- Post added at 05:14 AM ---------- Previous post was at 05:06 AM ----------
Yes. HD voice is activated. Just can't use the video calling with Verizon built in dialer. Have to use google duo.
Click to expand...
Click to collapse
bear263 so you flashed in this order right
@Echo off
@ECHO ALBUS_VERIZON_7.1.1_NDS26.74-36 Firmware on Moto Z2 Play XT1710-01
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
bear263 said:
Yes. Verizon firmware. You can't update it through the phone with a unlocked bootloader. Use Verizon's software upgrade assistance to update. It'll say it failed but it doesn't.
Click to expand...
Click to collapse
Do you mean "Verizon Software Upgrade Assistant for Motorola"? I can't get past not having the "Software Installation mode" for the USB connection. Does my XT1710-01 (Android 8.0.0) need to be unlocked/rooted for this to work? Whatever it takes, I would really like to get this working.
Yes you will need a unlocked boot loader. You first have to install the firmware via fastboot. Then Verizon software can be used.
---------- Post added at 05:39 AM ---------- Previous post was at 05:33 AM ----------
mrhodes19904 said:
bear263 so you flashed in this order right
@Echo off
@ECHO ALBUS_VERIZON_7.1.1_NDS26.74-36 Firmware on Moto Z2 Play XT1710-01
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I am not sure what order was used. I use houseofmoto that will unpack the firmware and create a batch file. I just run the batch file it creates.
WARNING: if the gpt.bin flash did not work, please stop and do not continue with the rest of the commands. It has been brought to my attention that software upgrades to the phone has changed the gpt and may not allow you to go back to the original stock firmware.
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Outstanding. Thank you for the post. I'm sure this will get used quite a bit. I did do a backup but it's always nice to have contingencies at the ready.
Sent from my Nexus 10 using XDA Premium HD app
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
glockman4519 said:
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
Click to expand...
Click to collapse
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
aj2333 said:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you very much. You sir are an awesome person.
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
glockman4519 said:
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
Click to expand...
Click to collapse
Did you remember to do an fastboot OEM fb_mode_clear?
no I didn't do that. I will go back over your instructions and re-do it. Thank you again for your assistance. I usually don't bug people for help and try to fix things on my own so I really appreciate you help.
Sent from my G3223 using XDA Premium HD app
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
glockman4519 said:
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
Click to expand...
Click to collapse
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Code:
fastboot oem fb_mode_set
fastboot flash gpt 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
doodalydoo said:
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Click to expand...
Click to collapse
You Sir are the man. I can't thank you enough for your help.
Update: Awesome.... It worked like a charm. I have everything copied now in case I hit the wall again. Thank you once again.
So I have used this and it worked great. However does anyone know when the firmware in that download will be updated to the latest version?
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Cool miner malware that pops up on firmware.center.
mattleft said:
Cool miner malware that pops up on firmware.center.
Click to expand...
Click to collapse
I haven't had that problem. Have you scanned your PC for virus/malware?
I would like to relock my bootloader but on this firmware it says the boot is not signed. Can I relock it after I do the ota as they should be signed then right?
bcrichster said:
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Click to expand...
Click to collapse
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
mindstream98 said:
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
Click to expand...
Click to collapse
I read in another thread that it was possible by using a Custom ROM but haven't tried it myself..
Although the Custom ROMs should work on several Carriers, this is a "Completely Back to Stock" thread..
Running an Xp3r!meπt with my XT1776
zerogun said:
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Click to expand...
Click to collapse
I used this to go back to stock, now my phone wont even turn on, at all.