does anyone know if there is some way to flash stock pie on a sprint variant??
Yes, see page 3 of following post:
https://forum.xda-developers.com/z2-force/how-to/verizon-update-t3952591/page3
Copying Hibinoh's work here for simplicity (not my work; this is a copy of the post of the person above):
Since someone asked Sprint, to get 9.0 on your sprint, following the steps:
1, get RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest Sprint 8.0(XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
2, unzip both ROM, find a copy of mfastboot, a copy of TWRP(use nash's TWRP)
3, copy the boot.img from RETIN 9.0 to your phone's sdcard
4, wipe your phone(data + cache)
5, use mfastboot flash following files from RETIN 9.0:
Code:
Code:
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot oem fb_mode_clear
6, use mfastboot flash following files from Sprint 8.0(!!!BECAREFUL, DO NOT FLASHED FOLLOWING FILES FROM 9.0!!!):
Code:
mfastboot oem fb_mode_set
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp adspso.bin
mfastboot oem fb_mode_clear
7, boot into TWRP
Code:
mfastboot boot YOUR_TWRP_FILE_PATH
8, use TWRP to flash the boot.img(step 3) to 'boot'
9, reboot
Well, I am happy on 9.0, but not happy to lost google pay(yea I know there is magisk hide)
quadcrap1 said:
Copying Hibinoh's work here for simplicity (not my work; this is a copy of the post of the person above):
Since someone asked Sprint, to get 9.0 on your sprint, following the steps:
1, get RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest Sprint 8.0(XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
2, unzip both ROM, find a copy of mfastboot, a copy of TWRP(use nash's TWRP)
3, copy the boot.img from RETIN 9.0 to your phone's sdcard
4, wipe your phone(data + cache)
5, use mfastboot flash following files from RETIN 9.0:
Code:
Code:
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot oem fb_mode_clear
6, use mfastboot flash following files from Sprint 8.0(!!!BECAREFUL, DO NOT FLASHED FOLLOWING FILES FROM 9.0!!!):
Code:
mfastboot oem fb_mode_set
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp adspso.bin
mfastboot oem fb_mode_clear
7, boot into TWRP
Code:
mfastboot boot YOUR_TWRP_FILE_PATH
8, use TWRP to flash the boot.img(step 3) to 'boot'
9, reboot
Well, I am happy on 9.0, but not happy to lost google pay(yea I know there is magisk hide)
Click to expand...
Click to collapse
I have done this twice and it's not working i followed all the steps one by one
I'm guessing the answer is no, but, has anybody tried this with the EU version for T-Mobile or ATT? Or Verizon version, even?
I'm tempted to try, but fairly certain it won't work.
worked like a charm, I had to factory reset after flashing the boot in TWRP though
Starkiller2 said:
worked like a charm, I had to factory reset after flashing the boot in TWRP though
Click to expand...
Click to collapse
A) You did this on a US Sprint phone, right?
B) Did you do the factory reset via TWRP, through the bootloader/Recovery Mode, or through the OS?
quadcrap1 said:
A) You did this on a US Sprint phone, right?
B) Did you do the factory reset via TWRP, through the bootloader/Recovery Mode, or through the OS?
Click to expand...
Click to collapse
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Screenshot
Starkiller2 said:
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Click to expand...
Click to collapse
So it sounds like you added two extra steps to the original instructions above:
1) Factory reset in TWRP after flashing boot image in TWRP
2) As a last step, rebooting to bootloader one more time and issuing the command
Code:
mfastboot flash modem NON-HLOS.bin
(where NON-HLOS.bin comes from the Sprint image, not the Pie image, just as when it was flashed the first time).
Correct?
quadcrap1 said:
So it sounds like you added two extra steps to the original instructions above:
1) Factory reset in TWRP after flashing boot image in TWRP
2) As a last step, rebooting to bootloader one more time and issuing the command
(where NON-HLOS.bin comes from the Sprint image, not the Pie image, just as when it was flashed the first time).
Correct?
Click to expand...
Click to collapse
Yes
So I've tried the above instructions on a Sprint Z2 Force. The first time, I got into an instant bootloop. So I went through the entire procedure again, and this time, I get to about 1 minute past when the Moto M is spinning around, to where the Lenovo color blocks are supposed to appear, and the screen goes black with occasional flashes on. Eventually, it just boot loops again.
Hmmm...
I do realize that I am using for the Sprint firmware (from which a few files come):
NASH_SPRINT_OCXS27.109_48_17_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
This is a nominally different than the xml file the OP mentioned:
NASH_SPRINT_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Unfortunately, I can't find a working link to the latter...I wonder if that could be the issue? Anyone have a working link for the 48-20 version?
quadcrap1 said:
So I've tried the above instructions on a Sprint Z2 Force. The first time, I got into an instant bootloop. So I went through the entire procedure again, and this time, I get to about 1 minute past when the Moto M is spinning around, to where the Lenovo color blocks are supposed to appear, and the screen goes black with occasional flashes on. Eventually, it just boot loops again.
Hmmm...
I do realize that I am using for the Sprint firmware (from which a few files come):
NASH_SPRINT_OCXS27.109_48_17_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
This is a nominally different than the xml file the OP mentioned:
NASH_SPRINT_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Unfortunately, I can't find a working link to the latter...I wonder if that could be the issue? Anyone have a working link for the 48-20 version?
Click to expand...
Click to collapse
I used the -20 version from here
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
So I managed to get Pie up and running on a Sprint Z2 Force. Everything seems to be working. I'm using it for T-Mobile, and Visual Voice Mail and VoLTE seem to be working.
One thing I can't get to work is Netflix. It won't install. if I sideload it, it won't run.
I use the phone for work (work profile), so I can't use Magisk (and I have no other need to root).
Anyone have a trick to get Netflix installed on a Frankenstein install like this with an unlocked bootloader.
Note: I was able to get Netflix to run on the Z2 Force with the T-Mobile flash on Sprint for Oreo.
---------- Post added at 05:07 PM ---------- Previous post was at 04:58 PM ----------
Starkiller2 said:
I used the -20 version from here
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you for the link!
where can I get the two files listed in step one?
delawaresace said:
where can I get the two files listed in step one?
Click to expand...
Click to collapse
The post two above yours has the link to one,
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
That's the other
Updated Tmobile Z2 Force to Pie
Starkiller2 said:
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Click to expand...
Click to collapse
I want to report that I have followed these instructions and have updated my TMobile Z2 Force to Pie. I am not in an US network.
My steps were pretty similar:
I flashed to stock using the TMO Z2 Force 27.1.5 Flashall
Booted normally
TWRP Wipe Data, Cache and System
Followed the steps as in the Verizon Update thread making sure to follow the steps as indicated by Starkiller2 above (except Factory Reset in TWRP). Using the TMO Z2 FORCE FLASHALL files and NOT the Sprint ones
Voilà
I successfully flashed 9.0/Pie to a Sprint phone for use with T-Mobile the other day.
An update. It generally seems stable and working.
Things that do not work:
A) VoLTE: The phone drops down to "H" (HSPA) / 3G when I make/receive a call. That means that while I can use data, it unusably slow 3G. I am not sure how to fix this. It's using T-Mobile as carrier, T-Mobile US as the APN (same as a Sprint/T-Mobile Z2 Force flashed phone running Oreo I am using on T-Mobile and which gives LTE speeds during a phone call/VoLTE).
B) Netflix won't install. It doesn't even show up in the Play Store. If you try to sideload it, it will crash/stop before you can use it. This is probably related to the unlocked bootloader, although I use Netflix on the Oreo Z2 Force with unlocked bootloader with no issue.
Oh, and the Oreo running Z2 Force shows 4GLTE, while the Pie running Z2 Force shows just LTE in the exact same location. The Oreo phone gets download/upload speeds of 24.0/9.1, the Pie phone gets download/upload speeds of 28.0/9.99. FWIW.
When I make a call, I see "HD call" for the Oreo phone, I don't see it for the Pie phone.
quadcrap1 said:
So I managed to get Pie up and running on a Sprint Z2 Force. Everything seems to be working. I'm using it for T-Mobile, and Visual Voice Mail and VoLTE seem to be working.
One thing I can't get to work is Netflix. It won't install. if I sideload it, it won't run.
!
Click to expand...
Click to collapse
If I recall correctly when I flashed my Z2 I(Spring) phone to unlock it from the network and also installed Magisk for Google Pay and other stuff that did't like rootl Netflix also didn't initially. It wasn't critical since I have so many other ways to watch but out of curiosity I searched for a fix and I think it was this
'
https://forum.xda-developers.com/apps/magisk/module-netflix-enabler-enable-netflix-t3708126
I did atually take notes but they are at home and I am currently on the road so I can't confirm but it looks like what I did.
A few questions:
1. Will flashing Pie on a bootloader unlocked Sprint model require the modem from 48-20, even if the phone has only been on an earlier Oreo firmware?
2. Does using the Oreo modem mean the Sprint phone could be flashed back and forth between Pie and Oreo without issues?
3. Would there be any reason this mixed/unofficial firmware would not activate / operate normally on Sprint service?
Related
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
Hello all,
I'm a bit confused about the process of taking my current '3' ROM and changing it to the official Lenovo Rom.
I have downloaded the lenovo drivers (installed and ok) phone is in debug mode.
I have downloaded the stock rom from here: https://forum.xda-developers.com/lenovo-p2/development/7-0-lenovo-p2a42-stock-nougat-update-t3581517 and have adb / fastboot.
I know I have to use the volume rocker and powerbutton to get into the boot mode but I don't know the commands for adb or fastboot. I have changed the name of the rom to 'update'
Can someone please advise me on the commands I am meant to enter to get this onto my phone please?
Thanks in advance,
Cue
Copy all the code below, paste it to a new text file on your PC and save it as All Files instead of .txt and name it a fastboot.bat. Place the fastboot.bat in the adb/fastboot directory, also place the unpacked rom in the same path. Run it as admin. Profit.
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo pause
Hi, op here.
Firstly, thank you for responding! Your instructions seem very clear. When i had a look at the contents of the ROM (in zip) i couldn't see any of the systemchunk files you mention, are they hidden deep somewhere?
Regards,
Cue.
If your phone is stock the Rom can be updated without fastboot or a PC.
All the instructions are in that thread.
Huh. Surely just boot into recovery and install the update.zip? No need to have it connected to pc.
Hello all,
Yep. I un-encrypted the sd card copied the zip onto it and booted up that way. Very easy. Now running stock directly from Lenovo which I am very happy about! It also pushed the new 78mb update as well.
Thank you for all your input.
same way i did it too theirs no need to do it through fastboot method just like the other people i did it through the built in recovery by renaming the Nougat rom to update.zip works fine and you will get another update ota straight after t obring it right up to date.
Sounds like you guys have this sorted :highfive:
Just for completeness, can somebody upload the original 3 rom? It just helps out the person who thinks they have a hardware issue and may need to return the phone to 3.
If you try and return your phone and it doesn't have the original 3 rom, your chances of a good outcome are obviously less as you have tampered with the phone etc.
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
I did the same flashed nougat and volte is working but only shows up some times not as much as I'd like is their any way to get volte to work more often. In my bedroom where the signal is weak I don't get the volte symbol at all.
philje123 said:
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
Click to expand...
Click to collapse
How you enabled VoLte on nougat? You are on stock rom or branded?
I'm on stock unbranded.
VOLTE settings now show up in phone menu and it just works. I had to factory reset though as initially it didn't work after flashing nougat.
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?
First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.
Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
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
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?
Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.
kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?
This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!
I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Hey man, have you have any success on this?
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.I will update this thread as I get new information on potential fixes.
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
I'm facing the same here. My problems started after the "erase modemst" command. After that I never was able to use my LTE connection again. I was able to use at least a H+ connection after I flashed a stock rom WITHOUT wiping nor formating data from a Lineage install. But, still no LTE. =/
I'm afraid this is caused by wrong modem driver w/ the downloaded stock rom. Don't know if there's a different driver for the Brazillian device.
CompostKicker said:
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.I will update this thread as I get new information on potential fixes.
Click to expand...
Click to collapse
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
varun.katoch said:
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
Click to expand...
Click to collapse
Sorry to leave you hanging, I stopped getting alerts on this thread for some reason. I am on shift until tomorrow and away from my computer, and it is a lot to type for a phone, but as soon as I am able I will type out the exact steps I used to fix the LTE issue, for both LineageOS and stock ROM.
Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
HTCDevil said:
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
Click to expand...
Click to collapse
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
CHECK THIS LINK IF YOU WANT YOUR VOLTE TO WORK :
100% working
https://forum.xda-developers.com/newthread.php?do=postthread&f=6506
Rodrigo Fernandes said:
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
Click to expand...
Click to collapse
Without erasing modem1st and 2st, is it right?
HTCDevil said:
Without erasing modem1st and 2st, is it right?
Click to expand...
Click to collapse
That's right! But only after you follow the step 2. Otherwise it won't work.
Rodrigo Fernandes said:
That's right! But only after you follow the step 2. Otherwise it won't work.
Click to expand...
Click to collapse
I would like to pass from ZUI (on xt1710-08) to a retail one without flashing Lineage before. So, if the problem is about modem i should not erase them, so I would leave those present on the initial version unchanged
So, my situation is : signal is ok lte\4g bit IMEI is 0. I think i understand i must flash stock lineage rom with this commands, then backup efs (i've already had It), so flash stock nougat and restore efs and i should have IMEI. Is It correct?
Inviato dal mio Moto Z2 Play utilizzando Tapatalk
Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Try Moto lenovo smart asistant to rescue your device @CompostKicker
kevoroid said:
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
Click to expand...
Click to collapse
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Rodrigo Fernandes said:
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Click to expand...
Click to collapse
I fixed it by flashing the original -08's Oreo ROM (Chinese ROM) and then reflashing Pie without doing the "erase modemst1.." steps.
moto z2 play imei repair
Hello everyone . i have moto z2 play xt1710-6 with stock rom. i wanna change my imei coz of lost signal. i tried many softs but i was not ablet to change it. i went to some techical shops , they used sigma and miracle , they couldnt as well. overall , how may i change its imei ? are there any way ?
My friend let me have his Gold Z2 Force for around $50 since my phone broke. He never used it, like new condition. Sweet.
Anyway, I am on verizon, he's on sprint so it's the Sprint Variant. I was searching around before I bought it, and I heard that I could unlock the bootloader for this specific model of the phone as opposed to the Verizon one which has a locked down bootloader. This is great, since I would want to root it.
Here is my question, after looking around it doesn't seem that I can get a clear answer. Would I be able to unlock the bootloader and install TWRP, and flash the verizon firmware onto the phone? I've already checked, the LTE bands are supported (Bands 2,4 and 13 along with the now legacy af CDMA fallback that is probably dead.).
I know you can use the Sprint version, on Verizon as it is, so even if I can't do all of this I can still use it with no issues, which is a plus.
Edit, steps further down below
I've got a Razr HD (XT925). After unlocking the bootloader, I could flash the Verizon fw to it. Flash a variant fw to an another unlocked-bootloader one (cross-flash) is capable. I cannot unlock my ATT one so I dont know exactly. I can only guess. Dont try to kill your phone :"(
mr_5kool said:
I've got a Razr HD (XT925). After unlocking the bootloader, I could flash the Verizon fw to it. Flash a variant fw to an another unlocked-bootloader one (cross-flash) is capable. I cannot unlock my ATT one so I dont know exactly. I can only guess. Dont try to kill your phone :"(
Click to expand...
Click to collapse
I'll try not to, lol.
That said, I either suck at finding it or just can't find it, but would you be able to point me towards where I could find the Verizon FW for the Z2 Force? I've tried searching but can't find it.
KOAO said:
I'll try not to, lol.
That said, I either suck at finding it or just can't find it, but would you be able to point me towards where I could find the Verizon FW for the Z2 Force? I've tried searching but can't find it.
Click to expand...
Click to collapse
Here you are
https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/
mr_5kool said:
Here you are
https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/
Click to expand...
Click to collapse
Alright, thanks!
OP - were you able to flash verizon fw on sprint z2 force?
dementor123 said:
OP - were you able to flash verizon fw on sprint z2 force?
Click to expand...
Click to collapse
Actually, shockingly, yes. I was. And it works. I did **** up the first few tries through trial and error, but currently I am using the Sprint Z2 Force on Verizon, running Verizon firmware with everything running. Glitches and all the same from a Z2 Force that would come with Verizon. Hell, you even get their bloat! Truly the Verizon Experience with the addition of Root and an Unlocked bootloader.
Doing this, I'd assume you have sim unlocked it and unlocked the Bootloader of your Z2 Force . Also note that this wipes EVERYTHING, SO BACK UP.
Also note that considering I was stunned when it worked, it's possible I missed a step while writing this up so again, have a window of time to be free. And a backup phone of possible.
The way I did it, is first prepping to have a few hours of your time because it could take a while. Set up like 2 or so hours where no one is going to call you on your phone since you'll need your Sim in the Z2 in case anything goes wrong.
Then, you need to download the latest Verizon Z2 Force Firmware. You don't have to technically do this, but updating is going to be a pain since you aren't going to be allowed to take OTA's (more on that later.) So just get the one with the January Security Patch as that is the most recent one
Here is the Verizon Firmware. Just sort by date to the most recent one for this year, there is only one lol.
https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/
Next is download the flashall utility. You aren't going to use the flashall.bat, but adb is in there. Extract the Verizon firmware into that flash all folder. From there, assuming you have adb debugging and all, boot into the bootloader.
Once you have everything prepped, follow this guide here. The first one, with wipe
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But, if you don't want to open another tab, here are the instructions. There is an important thing to note. The Verizon Firmware has it's OEM in 2 chunks, as opposed to the single .img file the others do. In this case you would run the fastboot oem, drag oem chunk 0 into cmd and run it, then run fastboot oem again and do the same for oem chunk 1 from the folder you are performing everything from. I also think we are missing sparsechunks 6-10, so just follow the steps for what files you have and ignore the ones you don't. We also have system sparse chunk b's, two files, to flash as well. We seem to have a few files others don't.
Run these commands one by one.
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Do not forget to run fastboot oem fb_mode_clear, otherwise you will boot into fastboot at every reboot.
After that, everything should be working. It worked for me I'll try to help if anything goes wrong but I hope that doesn't happen.
That said, an important note about updates and OTA's. Our Z2 Force is not a real Verizon Z2 Force. Something internally, most likely the fact it's not certified and is the same reason it doesn't show up in Verizon's site as an offical Z2 Force, is the reason we cannot take OTA's. If an Update were to come out for our phone, we would need to download the latest firmware. Once someone can get the latest OTA from Verizon for us, we then have to use the same ADB method to update our devices.
The steps for updating without deleting data are in the link to the thread above, but here are the commands for doing so without wiping data. Again, reminder that our flash oem is in two chunks, And we don't have sparsechunks 6-10.
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase carrier
fastboot oem fb_mode_clear
fastboot reboot
Again, do not forget to run fastboot oem fb_mode_clear. I cannot stress this enough because I nearly said "**** this ****" because of this simple command that I forgot to copy in. This is what puts our phone into it's state to flash firmware. So disable it once you are done.
I would assume that this would also work for flashing the Sprint to a true unlocked version. I was tempted to test it, since the unlocked retail versions get updates first and are already on the latest March Security patch. But, I was stopped because I could not find the retail firmware anywhere. The link for the retail in this thread 404'd, so this is the next best thing.
I did encounter an anomaly once everything was said and done. The phone app wasn't showing up once I had all my apps set up. I had to find it, clear the cache, and for good measure disabled and re-enabled it and it never disappeared/stopped responding again. I did end up using Magisk to install the Google Dialer framework and am using that with no issues. Aside the issue that I can't download it from the playstore, so I had to download it from a reputable site.
Note that I never had sprint service on it, so anything related to that or battery life on the sprint rom is something I have no clue about. But, I seem to get very good battery life on it.
I posted some screen shots below.
Just trying to understand something. Does verizon block sprint phones via a whitelist or via firmware?
benphillipstn said:
Just trying to understand something. Does verizon block sprint phones via a whitelist or via firmware?
Click to expand...
Click to collapse
I'm not sure, it might be the Whitelist. Since if you check your MyVerizon account it still doesn't believe its a Z2 Force. The phone's guts are the same but not all the IMEI numbers are registered.
Here are the VZW firmware. Android 9.0 1/31/2020 appears to be the most recent:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com