Develop Bugs

Guide to restoring factory Image that works?

There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
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 oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.

I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
I appreciate the reply. RSD doesn't detect, but ADB can. I can send fastboot commands via the bootloader, so I think drivers are OK. What got me in this mess was flashing the Chinese TWRP posted on the root guide here on XDA so I think the drivers are installed ok. I think it's a Windows thing.
I found that page you're referring to last night and read up on it. I found the retail US stock firmware image posted by another here on XDA and proceeded to go through the steps. After looking, the batch file immediately closed and did nothing. Then I went into the XML file and removed the m in mfastboot. After runnng manually, I found that it kept saying mfastboot.exe is not found. Then it went through every step as I've seen before, but every time a command was finished it would say "Image not signed or corrupt". I believe if I could somehow get RSD lite to work that I would be OK. I'd love to get this thing booting again.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
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 oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.

- You are restoring the firmware without wiping the device, i'd try fastboot erase userdata first before flashing the rest, could be worth a try.
- I get "Image not signed or corrupt" when flashing a modified kernel too, but it is flashed regardless.
- I got root with the chinese twrp, the others gave me bootloop.
Good luck.

I too have a freshly-bricked EU dual-SIM Z Play that gives "Image not signed or corrupt" errors when I try to flash recovery and boot. Seen by fastboot, but not by RSD.
edit: more of my saga is here http://forum.xda-developers.com/moto-z-play/help/identifying-firmware-required-phone-t3517360/

yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
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 oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
joesee said:
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...g-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
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 oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.
Click to expand...
Click to collapse
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin

Milly7 said:
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
Click to expand...
Click to collapse
You just saved my phone. Can I buy you a beer or something?

theodric said:
You just saved my phone. Can I buy you a beer or something?
Click to expand...
Click to collapse
It's all good. Just helping out. Glad it helped.

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
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 oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
I had the complete restore section reversed when you saw it on my thread, someone pointed it out and it's been fixed now.
Edit: I see someone's done it here too.
You also don't need to restore fully, just do the restore for ota and it should be enough if you've not flashed over the other stuff.

well i forgot to boot and set up a pin before installing TWRP, soft bricked myself for hours, this thread helped me return to stock so i could set a pin so TWRP would work, THANK YOU!
also if anyone else ends up here, and is having trouble finding the US retail stock image, i used the one from https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/

Is that an official signed image?
Can i use it to relock bootloader?
Thanks!

dyonissos said:
Is that an official signed image?
Can i use it to relock bootloader?
Thanks!
Click to expand...
Click to collapse
None of the images are signed and won't relock the bootloader.

Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.

IncendiaryPyro said:
Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.
Click to expand...
Click to collapse
Yep if you have the right factory image for your device.

Leraeniesh said:
Yep if you have the right factory image for your device.
Click to expand...
Click to collapse
Thank you. I've never had issues doing stuff like this before, but for some reason it scares the hell out of me with this phone. Maybe because I haven't had it for very long, lol. Downgraded to Marshmallow successfully. Hopefully I don't run into any issues in the future that would require an RMA, but out of all the phones I've had over the years, I've only had to RMA a Nexus 5 due to a problem with the screen.

Hi everyone. Is this guide is okay for reteu dual sim? And please point me if there is a firmware for reteu nougat. I softbrick my device and my imei is 0. I want to restore it please guide me as i am a noob in fastboot commands and steps. Thanks in advance

Vitxlss said:
yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy
Click to expand...
Click to collapse
do you have rooted device with twrp (maybe) ?
also, is the boot.img you got from Android 7 or 6.xx ?
Thanks

I use the DOWNGRADE script found here :
https://drive.google.com/file/d/0B134drJ4-Ed0MHQ5aE1wUmp5eFk/view
The original discussion here :
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Note that the original script is not ideal. The actual script came from @-=MoRpH=- on comment #4

How to restore to stock?

I am using a rooted Z Play XT1635-02 and would like to un-root the device and restore it to stock. Can someone recommend a thread for me to follow. Thanks

[email protected] said:
I am using a rooted Z Play XT1635-02 and would like to un-root the device and restore it to stock. Can someone recommend a thread for me to follow. Thanks
Click to expand...
Click to collapse
download ROM from here[1] ( select appropriate country/region )
[1] https://mirrors.lolinet.com/firmware/moto/addison/official/
for flashing instructions ..go here [2]
[2] https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486

jatinkhatri said:
download ROM from here[1] ( select appropriate country/region )
[1] https://mirrors.lolinet.com/firmware/moto/addison/official/
for flashing instructions ..go here [2]
[2] https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.

Euroter said:
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Click to expand...
Click to collapse
You'll never relock your bootloader , it's over and I can't understand why people think it makes a difference, moto has given you the unlocking key by asking for that key you are unlocked and unlock forever.
Read the unlocking agreement page from moto. You signed off on it.
You'll never ever see signed firmware from moto anyways , they keep them in house, all you'll ever see is unsigned firmware packages.

https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118

Euroter said:
Is this finally the SIGNED stock firmware? I've been dying to have it since I know the unsigned won't allow you to relock the bootloader.
Click to expand...
Click to collapse
Nope...

core720 said:
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Click to expand...
Click to collapse
Please help. I successfully unlock bootloader and twrp but my big mistake was i erase user data via fastboot. My phones memory is empty. I tried to adb push zip file and whenever i flash it via twrp error says unable to mount data. I want to return in stock can u help me flashing/unbricking my mzp? I have the Android N firmware from russia. Can u teach me a step by step guide how should i survive my phone pleaseeeeee... thanks in advance

Kap_Tutan said:
Please help. I successfully unlock bootloader and twrp but my big mistake was i erase user data via fastboot. My phones memory is empty. I tried to adb push zip file and whenever i flash it via twrp error says unable to mount data. I want to return in stock can u help me flashing/unbricking my mzp? I have the Android N firmware from russia. Can u teach me a step by step guide how should i survive my phone pleaseeeeee... thanks in advance
Click to expand...
Click to collapse
Download the stock ROM ...extract it and run following commands turn by turn from the extracted folder ( you must have ADB tools installed )
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 oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps

jatinkhatri said:
Download the stock ROM ...extract it and run following commands turn by turn from the extracted folder ( you must have ADB tools installed )
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 oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps
Click to expand...
Click to collapse
Hi sir one of my friend telling that i dont need to flash the bootloader.img because it will make my device brick. He means that downgrading bootloader will be a problem? Please confirm

Kap_Tutan said:
Hi sir one of my friend telling that i dont need to flash the bootloader.img because it will make my device brick. He means that downgrading bootloader will be a problem? Please confirm
Click to expand...
Click to collapse
Yeah ...that can happen if you are on newer bootloader
So Skip bootloader.img

Moto Z Play Bricked
I have Moto Z Play. My device is totally bricked. When i try to boot my device it wont boot. Even fastboot mode wont work. When I connect this device to laptop, in device manager it shows Qualcomm HS-USB QDLoader 9008 & Notification LED Beside front Camera Constantly Starts Blinking. I had tried all the methods shown on XDA but i didnt find any solution from it.
If any one of a member from XDA knows this solution then please tell me.
Contact no- +91 9970631435
email- [email protected]
name- Mohammadzain Thakur

I want LOS14.1 on my phone, but it's better to keep on stock 7.1.1? Normally you are right, because it's stupid to change the rom just because the number (7.1.1 to 7.1.2).

Is my HTC 10 another Brick for the USA-MEX wall?

Hi Guys! I appreciate any help or orientation to find out how should I proceed,
I don't know why my phone just got Brick yesterday, it was running fine for two months since the last Room's flash, suddenly I notice an estrange behavior of the system, then the capacitive buttons were not responding nor its backlit appear when I touch them, the home button and the fingerprint and everything else was working fine, so I think that with a simple Reboot it will be back to normality. For my disgrace, it enter in a Bootloop in the HTC logo screen and for my surprise when I manage to get to the Bootloader and try to enter to the Download and Recovery mode get me to the same HTC logo Bootloop!!
The principal suspect for me is that like 15 days ago a installed the TotallyFreeVPN app to see some Japanese Netflix
To complicate the things I want to make my phone thefts proof, so I disable usb debugging and OEM unlocking and installed Cerberus with the option of block usb debugging and also in security I enable the encrypted data option for every reboot or when enter in recovery.
My only hope is that you know if something can be done from the Bootloader to unbricked?
I attach the only two screens I have access right now
HTC 10
Firmware 2.41.401.4
Leedroid V3.6.1
Unlocked Bootloader
S-OFF
TWRP 2.8.4
I manage to run some fastboot commands from Bootloader, getvar all give me the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT64EBN02616

flash a stock ruu

If your phone will still power on, it's not bricked.

BrianKuo1853 said:
flash a stock ruu
Click to expand...
Click to collapse
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:

ALOMAJEMO said:
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
Click to expand...
Click to collapse
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on

Yeah and use the full version, not the NoWipe...

I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.

j to the 4n said:
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Click to expand...
Click to collapse
Sneakyghost said:
Yeah and use the full version, not the NoWipe...
Click to expand...
Click to collapse
Thank for your tips guys,
I follow exactly the order you suggest my good j to the 4n, and I download the firmware from your useful thread Sneakyghost, but still, I can not get it out of the Bootloop my friends
Dont you think my case is very strange?
If it serves for any other suggestion, I I add the following details
-The only image that is not flashing is rcdata, everything else is flashing OK
-I buy a microsd card class 10 of 32GB only to discard that the old microsd card of 3GB was not reading the RUU zip file.
-I optained the zip file, from the RUU.exe with the same version of the firmware 2.41.401.4 (the full version) and I copying it from the Temp files in Windows.
-With the microSD in FAT32 format I put the RUU zip file with the 2PS6IMG.zip name
-After flashing all the img files and rebooting to bootloader, then I inserted the card and select Download mode, where is supposed should appear the screen that jichuan89 mention to flash the RUU, but again nothing happen.
-Also I should say that I try also with the firmware and RUU version 2.41.617.3 (the corresponding for my model 2PS6500 in the back) but the last I have was the 2.41.401.4 with superCID and cidnum change it to HTC-001.
-And also among the hundreds of attempts I have executed fastboot erase userdata, erase cache, erase system, to try to clean any corrupt file.
Do you think there is any hope yet?
Once again thank you for your support guys!:good::good:

singlemalt said:
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
Click to expand...
Click to collapse
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL

ALOMAJEMO said:
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
Click to expand...
Click to collapse
Haha...we have two bricks for the wall now...do you know if Donald would cover shipping costs from Argentina?

curious if anyone know how to view the firmware if cannout access downlad mode

venom55521 said:
curious if anyone know how to view the firmware if cannout access downlad mode
Click to expand...
Click to collapse
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........

Mr Hofs said:
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Click to expand...
Click to collapse
my bad,i was looking around for info and ideas and just had a question when i was reading it

venom55521 said:
my bad,i was looking around for info and ideas and just had a question when i was reading it
Click to expand...
Click to collapse
Please pick up a sledgehammer and smash your device....... it's the best for all of us.

Mr Hofs said:
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Click to expand...
Click to collapse
i realize you help a lot people out which is appreciated ,but being rude is pointless

venom55521 said:
i realize you help a lot people out which is appreciated ,but being rude is pointless
Click to expand...
Click to collapse
Your interpretation of the situation. I'm honest, not rude.

Stuck in bootloader and getvar all empty

Hello everyone,
I've got some trouble with my phone.
The battery was empty I plugged it with the official charger, I heard some crackling. Then it's hard to boot into bootloader, it wo'nt charge.
When I plug it it show the "charging icon" with 0% but without the green progression bar.
I can't relock the bootloader to flash a stock firmware. I'm S-ON.
You can see below my "fastboot getvar all" it's pretty empty so weird :
e_Kit_v1.0\Data>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA66TBNXXXX
all:
Click to expand...
Click to collapse
Anyone can help me ?
Thanks

That's the way the fastboot getvar all info is gonna look if you're in bootloader. It'll show when you're in download mode.

OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.

GaTeRy86 said:
OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.
Click to expand...
Click to collapse
If you're in bootloader mode you should be able to boot to download mode from there. It's the third entry from the top. Just navigate to it with the Vol- and confirm with the power button. If there post the getvar all without IMEI and serial number.
And please elaborate a little bit more which image are you trying to flash? Is the only problem that your device doesn't seem to charge or are there more problems you encounter. Did you previously flash a custom recovery or ROM?
Sent from my htc_pmeuhl using XDA Labs

I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Click to expand...
Click to collapse
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.

OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.

GaTeRy86 said:
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.
Click to expand...
Click to collapse
Try fastboot oem rebootRUU then try flashing the firmware after

xunholyx said:
Try fastboot oem rebootRUU then try flashing the firmware after
Click to expand...
Click to collapse
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging

GaTeRy86 said:
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging
Click to expand...
Click to collapse
Sadly welcome to the club , my phone is s-off with exactly the same issue, it's almost two months as a paperweight
It seems that it is difficult to understand even for the most illustrious of this forum that theres is no way to enter to recovery, download mode, RUU mode or whatever other mode in which you can do something more than flashing img in the broken bootloader.
https://forum.xda-developers.com/htc-10/help/htc-10-brick-usa-mex-wall-t3574704

You can't brick it from S-ON. It's just not possible.

tabp0le said:
You can't brick it from S-ON. It's just not possible.
Click to expand...
Click to collapse
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
GaTeRy86 said:
I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
Quote:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.
Click to expand...
Click to collapse
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972

xunholyx said:
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972
Click to expand...
Click to collapse
Good point! You're absolutely right. I wasn't even thinking about that!

I guess i bricked my only phone....:-/

Okay, so im new to this stuff and still i managed to root the phone and flash RR 7.1.2. But i tried to unroot it and this happend:
I only have access to the bootloader and thats it. No recovery, no ROM nothing....when i start ti, it says that my phoe is unlocked and its dangerous and that the phone will boot in 5 secs but it never does....plz help me..and i wanna know where can i learn about all this stuff...its freaking me out since this the only phone i have.....plz help me..

You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image

TheFixItMan said:
You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image
Click to expand...
Click to collapse
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.

Astitva_ said:
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.
Click to expand...
Click to collapse
Firmware must be the same or newer
See the link in my post above for all the firmware - choose the right one for your region
If you don't know which to choose just use this one
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands are (assuming you know how to use & have fastboot already setup as you have already unlocked the bootloader)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (only flash if newer version of android eg going from nougat to oreo)
fastboot flash bootloader bootloader.img (only flash if going to a newer version of android)
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

TheFixItMan said:
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
Click to expand...
Click to collapse
Wasn't trying to go back to stock myself (though I did have to in the end) but this was the only rom I found that worked full stop. Thanks so much for this.