Related
Dear all,
after a try to load the Chinese twp and root my z play I bricked my phone. Now the only think that I can get is fast boot screen that says:
bl:co.14
baseband: not found
product: xt1635-02 32gb p7
serial number:
.
.
.
flashing_unlocked
.
.
I am trying to load the XT1635-02_ADDISON_RETUS_6.0.1_MPNS24.104-49-4 firmware by running a bat file that I found somewhere around with the following commands:
echo off
fastboot getvar max-sparse-size
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase DDR
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
But I get a screen says erasing... and the boot loop!!!
ANY IDEAS GUYS??
thx in advance for your help!!!:crying::crying::crying::crying:
asprofridis said:
Dear all,
after a try to load the Chinese twp and root my z play I bricked my phone. Now the only think that I can get is fast boot screen that says:
bl:co.14
baseband: not found
product: xt1635-02 32gb p7
serial number:
.
.
.
flashing_unlocked
.
.
I am trying to load the XT1635-02_ADDISON_RETUS_6.0.1_MPNS24.104-49-4 firmware by running a bat file that I found somewhere around with the following commands:
echo off
fastboot getvar max-sparse-size
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase DDR
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
But I get a screen says erasing... and the boot loop!!!
ANY IDEAS GUYS??
thx in advance for your help!!!:crying::crying::crying::crying:
Click to expand...
Click to collapse
Just flash the boot.img, recovery.img , all sparsechunks.img and the OEM.img using fastboot.
After you've flashed type in fastboot erase userdata and then fastboot reboot and see what happens
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
You should never flash using a short cut or a bat file found in some obscure thread or website
Sent from my XT1635-02 using XDA-Developers Legacy app
Is the device recognized by fastboot?
Command: fastboot devices
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Luiz_Pennywise said:
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Click to expand...
Click to collapse
Oh man, the same problem here. I was updating the android for N and when restart the phone doesn't turn on, I'm crazy because I don't find anything to fix :crying::crying::crying::crying:
Luiz_Pennywise said:
Guys, I have a similar problem.
After an update of the android give error, I can no longer connect my moto z play.
Nor in fastboot and adb enters.
See video:
http://youtu.be/o8yYn0hNers
Click to expand...
Click to collapse
kaue152 said:
Oh man, the same problem here. I was updating the android for N and when restart the phone doesn't turn on, I'm crazy because I don't find anything to fix :crying::crying::crying::crying:
Click to expand...
Click to collapse
Have you guys downgraded to Marshmallow, then tried updating to N again? Particularly after installing the April update?
IncendiaryPyro said:
Have you guys downgraded to Marshmallow, then tried updating to N again? Particularly after installing the April update?
Click to expand...
Click to collapse
How should I do this? I was reading this topic https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
and they said that necessary download russian firmware, is it right?
kaue152 said:
How should I do this? I was reading this topic https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
and they said that necessary download russian firmware, is it right?
Click to expand...
Click to collapse
I'm not sure. I believe you need a blankflash file for that firmware from what I've gathered, if it was a downgrade to Marshmallow after the April update for N, then updating back to N.
IncendiaryPyro said:
I'm not sure. I believe you need a blankflash file for that firmware from what I've gathered, if it was a downgrade to Marshmallow after the April update for N, then updating back to N.
Click to expand...
Click to collapse
I'm was updating for Nougat, probabily was that April update. Honestly I don't know what to do
kaue152 said:
I'm was updating for Nougat, probabily was that April update. Honestly I don't know what to do
Click to expand...
Click to collapse
Have you ever downgraded to Marshmallow at any time before that happened?
IncendiaryPyro said:
Have you ever downgraded to Marshmallow at any time before that happened?
Click to expand...
Click to collapse
Yep, I'm was using ViperOS, I'm downgraded to stock Marshmallow and was doing the OTA updates. When the phone reboot to install Nougat this happened.
kaue152 said:
Yep, I'm was using ViperOS, I'm downgraded to stock Marshmallow and was doing the OTA updates. When the phone reboot to install Nougat this happened.
Click to expand...
Click to collapse
Ah, so it was the update to Nougat that caused it. Yeah that has something to do with a bootloader upgrader in the April update I believe. You'll have to wait for a blankflash file to surface to repair that issue, unfortunately. Only reason I was asking was because I downgraded to Marshmallow a few months ago, then OTA'd back to Nougat, then also got the March update later down the road and never had any issues. I haven't gotten the April update yet but it'll be a good reminder to me not to downgrade to Marshmallow again.
IncendiaryPyro said:
Ah, so it was the update to Nougat that caused it. Yeah that has something to do with a bootloader upgrader in the April update I believe. You'll have to wait for a blankflash file to surface to repair that issue, unfortunately. Only reason I was asking was because I downgraded to Marshmallow a few months ago, then OTA'd back to Nougat, then also got the March update later down the road and never had any issues. I haven't gotten the April update yet but it'll be a good reminder to me not to downgrade to Marshmallow again.
Click to expand...
Click to collapse
How did you fix it? I found a blankflash and another rom to install
kaue152 said:
How did you fix it? I found a blankflash and another rom to install
Click to expand...
Click to collapse
I never had to fix it. I downgraded from the January patch for N (which I had sideloaded), OTA'd from Marshmallow to N + the February patch from my carrier, then I got prompted for March's update a few weeks later, so I guess there was never an issue downgrading back then, but something changed in April's patch that causes hardbricks when you downgrade and try to go back to Nougat. I've never had the April patch installed before so it hasn't affected me. From what I've read, it's only happened to people who had downgraded after installing April's update. Sorry I can't offer any help there. :/
PLEASE ALL GO TO THIS LINK
Http://lenovo-forums.ru/topic/20594-moto-z-play-obschaya-tema-voprosov-i-otvetov/#comment-550611
WHILE MORE OF US SEE AND LEN LIKE THE COMMENT OF
* VVizard @
SAGE
THEY COULD HELP US CHECK IT
Hello there. So, after flashing the TWRP my moto z play got bricked and now it remains at the "bad key" screen at boot. I can get into the fastboot screen and the recovery. To my understanding, I need to flash some firmware. My doubts are; does it matter which one of all I flash? And, most are marshmallow: I had nougat before this happened so, will I have trouble flashing these? Thanks!
Kon22 said:
Hello there. So, after flashing the TWRP my moto z play got bricked and now it remains at the "bad key" screen at boot. I can get into the fastboot screen and the recovery. To my understanding, I need to flash some firmware. My doubts are; does it matter which one of all I flash? And, most are marshmallow: I had nougat before this happened so, will I have trouble flashing these? Thanks!
Click to expand...
Click to collapse
Flash only system, data and boot. Do not mess with the modem, efs and bootloader images.
[GUIDE] Unbrick MOTO Z Play.... work in progress! (not working yet)
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Moto z play updated blankflash
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19
Go here .. flash the files and thank god and the OP.
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.
hey
please i want help i want stock rom for moto g5 XT1676 to unbrick by blank-flashing and how do it in steps on my dead phone
sorry for bad english
my phone moto g5 rooted when i try to unroot by minimal adb past wtong stock rom in Minimal ADB and Fastboot folder when i intered command and i pasted this order :
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 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
fastboot oem fb_mode_clear
fastboot reboot
//////////////////////////////////////////// after this step ended my phone not strat or boot /just white led blinking when connected by charger
mention / my phone is moto g5 xt1676 rooted but i flashed this stock CEDRIC_NPP25.137-93_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,forMotor ola Moto G5(XT1672) but my phone Motorola Moto G5(XT1676) please help me
If you can no longer get into the bootloader to flash correct firmware via fastboot see
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
TheFixItMan said:
If you can no longer get into the bootloader to flash correct firmware via fastboot see
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Click to expand...
Click to collapse
after i did this steps and finshed the last command the phone not open
waleedzzz said:
after i did this steps and finshed the last command the phone not open
Click to expand...
Click to collapse
Did gpt & bootloader flash correctly?
Did you get errors flashing these?
Read the last few posts on that thread!
You can still boot with the sd card but to boot without it gpt & bootloader must be flashed successfully using firmware that is equal or newer to the version already installed
If you bricked your phone flashing an 8.1 soak test ota you may have to wait until 8.1 firmware is released
TheFixItMan said:
Did gpt & bootloader flash correctly?
Did you get errors flashing these?
Read the last few posts on that thread!
You can still boot with the sd card but to boot without it gpt & bootloader must be flashed successfully using firmware that is equal or newer to the version already installed
If you bricked your phone flashing an 8.1 soak test ota you may have to wait until 8.1 firmware is released
Click to expand...
Click to collapse
i soloved by this method These two files are those that are damaged when doing downgrade on your G5 bike
therefore here I leave you the most updated
so that the flashees and your phone can light up without the SD
if you flash these two you will not need to flash a complete firmware
Just open the folder that says Fastboot and click on the MAF32.exe file or START.bat
Once there you will insert the micro sd on your g5 motorcycle and turn it on in fastboot mode and take out the sd
and then connect your motorcycle g5 that is on and flash these commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
and that would be everything and you could start your phone without the micro SD
the link to slow
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Anything below Pie is vulnerable to the X-helper rootkit... we were just talking about it in another thread. It's a real nasty little bugger.
But its posible? I just want to get all the features back, even, i dont know what is that thing, if they have some to hack me i dont have to much to lose anyways, just want to downgrate to fix the fingerprint bug from oreo
Don't know. Hopefully someone with this device can help you.
iMaxwell said:
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Click to expand...
Click to collapse
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
marcost22 said:
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
Click to expand...
Click to collapse
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
iMaxwell said:
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
Click to expand...
Click to collapse
that's probably the worst available way to do it. If your phone didn't originally receive it via OTA, then you are forcing it the wrong way.
If you want to go back to nougat all you need to do is download the official N firmware, then flash everything but bootloader and gpt
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
I follow the steps on this video
iMaxwell said:
I follow the steps on this video
Click to expand...
Click to collapse
Yeah that is just terrible
iMaxwell said:
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
Click to expand...
Click to collapse
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
marcost22 said:
Yeah that is just terrible
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
Click to expand...
Click to collapse
The issues begin on official oreo, i upgrade nougat to oreo then, fingerprint option dissapear, then i upgrade to pie from oficial firmware but issues still remain
It really works? I didnt find any video or post about downgrade like that
Yes it does work, but it's not recommended, that's why you don't find much info
iMaxwell said:
It really works? I didnt find any video or post about downgrade like that
Click to expand...
Click to collapse