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
Related
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
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.
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?
*Update: I finally was able to get a hold of someone at sprint who actually took the time to take care of me. My phone was indeed unlocked, but she submitted the unlock request again. After restarting my phone on, wifi with a sprint sim, it unlocked!!!! Finally! Btw sprint doesn't like you walking into stores without a mask on and they'll give you the corporate # immediately to get you out of the store. 877-365-6413 Hope this helps someone since it took me 6 sprint community chats, 3 phone calls and a store visit to handle.
About 2 years ago I bought 2 Boost Moto G plays for $49. We activated them on Sprint and used them for a year. Sprint Sim unlocked both phones after 6 months and I have confirmed it twice. I gave my old moto g6 play to my mother in law with Verizon. Popped the sim card in and it worked no problem. My wife continued to use her moto g6 play but wanted Android 9, so I unlocked the bootloader, downgraded and then flashed the stock sprint update from here: https://forum.xda-developers.com/g6-play/development/ota-moto-g6-play-aljeter-t3921877
Phone worked fine and wife used it for 6 more months until we upgraded to g7 powers.
The issue I am having is that the only sim card this phone will read is the sprint one. Tmobile=Nothing. Verizon=No. At&t=No.
I know for a fact that the other phone works on Verizon, so this one should too. I tried flashing RetUS on this phone (which actually worked for my metro g7 power to work on Verizon) and still no luck. I figure something is messed up, or not flashed properly to see the other sim cards.
Anyone have a clue? Thanks in advance!
This is how i flashed it:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I skipped boot.img on purpose, gpt.bin, adspso.bin, logo.bin
shawndak said:
About 2 years ago I bought 2 Boost Moto G plays for $49. We activated them on Sprint and used them for a year. Sprint Sim unlocked both phones after 6 months and I have confirmed it twice. I gave my old moto g6 play to my mother in law with Verizon. Popped the sim card in and it worked no problem. My wife continued to use her moto g6 play but wanted Android 9, so I unlocked the bootloader, downgraded and then flashed the stock sprint update from here: https://forum.xda-developers.com/g6-play/development/ota-moto-g6-play-aljeter-t3921877
Phone worked fine and wife used it for 6 more months until we upgraded to g7 powers.
The issue I am having is that the only sim card this phone will read is the sprint one. Tmobile=Nothing. Verizon=No. At&t=No.
I know for a fact that the other phone works on Verizon, so this one should too. I tried flashing RetUS on this phone (which actually worked for my metro g7 power to work on Verizon) and still no luck. I figure something is messed up, or not flashed properly to see the other sim cards.
Anyone have a clue? Thanks in advance!
This is how i flashed it:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I skipped boot.img on purpose, gpt.bin, adspso.bin, logo.bin
Click to expand...
Click to collapse
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Thank you for reaching out!!! Tried it with no luck. When flashing the modem file it says: not found? Not sure if that's a normal error or not.
Also the phone simply says, sim status: unavailable. So it knows it's in the phone but doesn't know what to do with it.
I think you're on the right track though! It's something simple that didn't flash properly at some point.
Hello, how are you? My Name Is Cristian and I'm from Argentina.
I've had a Moto G5 for a while and a lot of custom roms were installed on it. However, there were many problems in the process. The roms had bugs, performance issues, and some didn't even boot.
So i made the decision to go back to the factory rom and close the bootloader forever. But it couldn't. Something prevented it. Something was causing the phone to not start properly.
Therefore, after doing so many laps, i was able to do the whole process.
And today i publish this topic so that you can do it too. I hope you can come out triumphant in the process just like me. Have lucky!
1) The first thing you should do is download Rescue & Smart assistant. Install on your pc and create account (if you not) or login in.
Code:
https://support.lenovo.com/es/es/downloads/DS101291
2) You will need to find the official firmware of your device. Search for the exact device SKU (model of your phone) and exact region. For example the SKU of my device is XT1670 the region is RETAR (from Argentina). If you are from United States (and try to install RETAR) Rescue & Smart assistant will not recognize the SKU of your device, and will not be able to continue.
Find the exact firmware corresponding to your mobile phone.
Code:
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Unzip the rom in the place that you prefer.
3) Now put your device in bootloader mode and execute the following commands (ignoring any errors in the process)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot erase cache
fastboot erase userdata
fastboot reboot
4) Once the above process is finished, start your phone normally. Go to the developer options and activate usb debugging. Plug the phone into PC.
Open "Rescue & Smart assistant" and accept usb debugging on your phone. The app installs some control app, dont worry.
Go to Rescue & Smart assistant and select "Rescue". The program will recognize your phone's SKU if you downloaded the correct firmware. Otherwise, if a wrong sign appears, you will have to repeat step 2 and 3 with the correct firmware.
Click on "Rescue now" and the program will download the firmware corresponding to your phone. After this, the firmware installation will begin.
Why do all this process?
The Rescue & Smart app is official from Motorola. When the official firmware is installed, the signed firmware files are also installed with it. The firmware is official because is delivered directly by Motorola, specifically for your mobile phone, and not by unofficial sites.
5) Hey, wait! the bootloader needs to be blocked. True.
Go to C:\ProgramData\LMSA\Download\RomFiles and you will find there the official rom downloaded by "Rescue & Smart". This rom is unique, signed and official. Only for your phone, only for its hardware. Do not lose it. It will save your ass from many inconveniences, if one day you want to continue experimenting with your phone.
Copy the whole directory in other site and open cmd in it. Now shutdown your phone and start it in bootloader mode.
Now put these commands (ignoring bla bla bla errors):
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
And that's it. Your mobile phone is now official and with its bootloader locked. almost factory-made.
So thank you for reading all this and I hope the information has served you a lot. Any questions about it (about this) do not hesitate to consult.
Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:
R1ffR4ff said:
Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:
Click to expand...
Click to collapse
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.
He.Art said:
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.
Click to expand...
Click to collapse
It's a great little program that I had to use Yesterday on a Moto G3 as the normal ADB way as per your post wouldn't work for whatever reason and I've used ADB loads
I was my own fault on that phone as I,"Soft Bricked" it using the latest version Magisk uninstall option so NEVER use this option in Magisk. I returned the phone to Stock and then upgraded it to my favourite Custom roms