Develop Bugs

[SOLVED] Bricked and can't find a matching RUU... please help!

Please help! I recently acquired a phone that was supposed to be an Inspire 4g (ATT, unlocked) but turned out to be a Desire HD (I know they are essentially the same) that is soft-bricked with firmwarez 3.13.161.5. It would appear based on the .161. that this is (maybe) a Vodafone branded phone.
Here are some stats from Hboot:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.52.27
eMMC-boot
sEP 7 2011,19:06:24
When I tried to run the latest vodafone RUU that I could find, the numbers were smaller than 3.13 and the RUU failed.
I thought to try and downgrade the Hboot to see if that worked, but ADB doesn't work, and being soft-brick, I can't enable USB debugging.
There is some software with the correct firmware #s on HTC's dev support page, but the downloadable files are neither RUU.exe or PD98IMG.zip format.
I'm stuck. If anybody has any methods that might help, or knows where I can get a 3.13.161.5 RUU I would be so very grateful.
Thanks,

Have you looked at www.shipped-roms.com?
Sent from my HTC Desire HD using xda app-developers app

ranger4740 said:
Have you looked at www shipped-roms com?
Click to expand...
Click to collapse
Yeah, I have but it seems the shipped-roms webpage seems to be constantly offline. I have been scouring the web, and www androidfiles org/ruu/?developer=Ace is the best resource I've found. They have nothing that will work for me.
I'm looking for a downgrade method that doesn't require a fully bootable phone, or an RUU that is 3.13.161.5 or higher. I can use fastboot, but not adb.
Is shipped-roms working for everybody else?

boot your phone to fastboot USB then just type fastboot oem rebootRUU.
Run the RUU and then go hunting in the temp folder just run in run box %temp%. there should be a file called rom.zip copy that to the same dir as fastboot if you can then simply run fastboot flash zip rom.zip then it should work. Make sure you have a goldcard though as you'll need that.

hacktrix2006 said:
boot your phone to fastboot USB then just type fastboot oem rebootRUU.
Run the RUU and then go hunting in the temp folder just run in run box %temp%. there should be a file called rom.zip copy that to the same dir as fastboot if you can then simply run fastboot flash zip rom.zip then it should work. Make sure you have a goldcard though as you'll need that.
Click to expand...
Click to collapse
Did what you said. Figured out that I needed to run the RUU , find rom.zip in %temp%, cancel RUU. I hope I did that right.
got this:
sending 'zip'
okay
writing 'zip"
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote:43 main version check fail)
I'm guessing this is a goldcard issue. I will try again with a fresh goldcard later tonight..
If anybody has any helpful comments, that would be wonderful....

umopapisdn said:
Did what you said. Figured out that I needed to run the RUU , find rom.zip in %temp%, cancel RUU. I hope I did that right.
got this:
sending 'zip'
okay
writing 'zip"
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote:43 main version check fail)
I'm guessing this is a goldcard issue. I will try again with a fresh goldcard later tonight..
If anybody has any helpful comments, that would be wonderful....
Click to expand...
Click to collapse
Sent you a PM mate.

hacktrix2006 said:
Sent you a PM mate.
Click to expand...
Click to collapse
Thanks again hacktrix2006 for all your wizardry. Got it working better than ever!
Devs, Close please?

Not a problem mate, glad to help. Maybe editing the Title to show [SOLVED] might help.
Enjoy S-Off'd phone mate. Try out CM10.1 and Sense 4+ roms when you have time.

hacktrix2006 said:
Not a problem mate, glad to help. Maybe editing the Title to show [SOLVED] might help.
Enjoy S-Off'd phone mate. Try out CM10.1 and Sense 4+ roms when you have time.
Click to expand...
Click to collapse
Great idea. I guess I just assumed that mods (not devs, silly me) read through everything... duh.
Doesn't [solved] imply that there is a solution in here somewhere? contact you, I guess was the solution. Thanks again!

[Q] Bricked phone?

Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.

pastyal said:
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.

Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.770s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.787s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.431s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.790s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.706s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.455s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.713s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.463s
Click to expand...
Click to collapse
And heres the getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

pastyal said:
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
And heres the getvar all
Click to expand...
Click to collapse
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.

Seanie280672 said:
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Click to expand...
Click to collapse
Ooops thanks for the heads up on removing the info!
Aaah thats the mistake I made by using the wrong firmware. I will locate the correct firmware and try that later on today. I did look at the Sunshine option but was unsure if it would help me at this moment in time. Think i'll try the correct firmware first.
Will update here later with good news hopefully!

Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?

pastyal said:
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
Click to expand...
Click to collapse
hold volume up, volume down and power button for about 15 to 20 seconds, phone will go off, before it comes back on quickly release all buttons and just hold volume down only, it should boot to the bootloader.

Thank you for that, that gets me into the bootloader but it won't load into fastboot now?

pastyal said:
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
Click to expand...
Click to collapse
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?

Seanie280672 said:
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Click to expand...
Click to collapse
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?

pastyal said:
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
Click to expand...
Click to collapse
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC

Seanie280672 said:
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Click to expand...
Click to collapse
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?

pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.

pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Also make sure in bootloader it says FASTBOOT USB and not HBOOT

redpoint73 said:
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
Click to expand...
Click to collapse
ssantos132 said:
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
Click to expand...
Click to collapse
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.

pastyal said:
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
Click to expand...
Click to collapse
That's right, USB 3.0 does not play well with this device.
pastyal said:
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
Click to expand...
Click to collapse
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.

redpoint73 said:
That's right, USB 3.0 does not play well with this device.
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
Click to expand...
Click to collapse
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?

pastyal said:
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
Click to expand...
Click to collapse
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5

redpoint73 said:
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
Click to expand...
Click to collapse
Thanks very much for that, the reason why i was stumbling around is because i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Could you please tell me how to restore the stock Nandroid. i promise you I am going around in circles lol

pastyal said:
i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Click to expand...
Click to collapse
Instruction on restoring a nandroid are in post #3 of the stock nandroid collection thread I linked before. Click where it says Questions & Answers, and you will see the 2nd question is how to restore a stock nandroid: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
I think you may have seen these instructions, but you only did one part, not the remaining parts of the process. The boot.img is essentially just the kernel; technically a few other things too, but either way its like 1% of what you need to have a working ROM. Namely, if you only flashed boot.img, you didn't do the steps I've highlighted in orange below:
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
* Philz touch uses - Clockworkmod\Backups\
* TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
You need to unzip the downloaded file, then place the entire folder contents to the proper location on the phone. Then boot recovery (probably TWRP) and use the restore function to install the nandroid. I actually do not think you need to extract and flash boot.img separately.
After that, install the stock recovery with the fastboot command: fastboot flash recovery filename.img
Where "filename.img" is the actual name of the desired stock recovery file.
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
pastyal said:
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
Are you currently unlocked again? The above is from your top post, but I don't know if you've changed this (unlocked again).
You can only do the above mentioned steps (restore nandroid, stock recovery, etc.) if you are bootloader unlocked.

[Q] Can't flash RUU firmware htc one m9

Hey guys, so I tried to flash RUU Firmware on my htc one m9. I downloaded the firmware, minimal adb flashboot, and htc sync manager. Problem is when I open command prompt via minimal adb flashboot and I type 'adb reboot downloader' it says:
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
Am I missing something here? What should I do?

any chance you run a virtual android, genymotion or something of the like? And I would like to think aside from the drivers for HTC, the sync manager is best tucked safely away in the garbage

MrLizm said:
any chance you run a virtual android, genymotion or something of the like? And I would like to think aside from the drivers for HTC, the sync manager is best tucked safely away in the garbage
Click to expand...
Click to collapse
alright now I can get it to works however it says failed at the end.
C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
C:\adb>adb reboot bootloader
C:\adb>fasboot oem rebootRUU
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\adb>fastboot flash zip 0PJAIMG.ZIP
target reported max download size of 800000000 bytes
sending 'zip' (61661 KB)...
OKAY [ 4.842s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14: fail to flash via downloadzip)
finished. total time: 8.598s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
any idea how to make it successful?

Have to ask, you s-off?
This line makes me wonder,
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system

MrLizm said:
Have to ask, you s-off?
This line makes me wonder,
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
Click to expand...
Click to collapse
How do i check it? Sorry I'm totally new in this kind of things

kamocheng said:
How do i check it? Sorry I'm totally new in this kind of things
Click to expand...
Click to collapse
if you boot to bootloader, should be up top there. from a booted phone just 'adb reboot bootloader' if it says s-on thats your problem. My guess is since you do not know your s-on/off you are probably s-on.

kamocheng said:
How do i check it? Sorry I'm totally new in this kind of things
Click to expand...
Click to collapse
No it says:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***

so this is your problem, S-ON is the last piece of security for you. Without S-OFF you are unable to flash RUU the way your are attempting.
There is an app, Sunshine. Cost 25$ I am pretty sure and that will get you s-off. or you can wait until your carrier pushes the OTA and do a "Back To Stock" method. Well the app is free, it runs a check and makes sure it can get s-off. then it wants money.

MrLizm said:
so this is your problem, S-ON is the last piece of security for you. Without S-OFF you are unable to flash RUU the way your are attempting.
There is an app, Sunshine. Cost 25$ I am pretty sure and that will get you s-off. or you can wait until your carrier pushes the OTA and do a "Back To Stock" method. Well the app is free, it runs a check and makes sure it can get s-off. then it wants money.
Click to expand...
Click to collapse
Good to know, any idea how to get the app for free? Kinda tight on budget here. Thanks!

kamocheng said:
Good to know, any idea how to get the app for free? Kinda tight on budget here. Thanks!
Click to expand...
Click to collapse
Okay hold on, I remember when I rooted my phone it was S-Off. So to get it back to original factory version I need to S-on it?

kamocheng said:
Okay hold on, I remember when I rooted my phone it was S-Off. So to get it back to original factory version I need to S-on it?
Click to expand...
Click to collapse
No not at all, S-OFF makes it easier to get back to stock. If you were S-OFF at some point I am not too sure why the bootloader is reporting S-ON now. I am cheap and I revert to stock to get my OTAs to get the latest roms.. this is a huge pain. S-OFF is ideal once you have it you should keep it.

@kamocheng: Since I don't have much time at the moment I'm keeping it short:
1. Your zip is corrupted (look at the output). Re-download it and compare the MD5 checksums.
2. If you're s-on you need to be relocked for running RUUs.
3. You never mentioned your firmware version nor your CID so no one can verify whether you use the correct RUU.
4. There is no free version of sunshine since its a free app with in-app purchasement. But there is no need to s-off if you use the correct RUU.

Make sure htc sync isn't running on your computer.
Sent from my 0PJA10 using Tapatalk

Flippy498 said:
@kamocheng: Since I don't have much time at the moment I'm keeping it short:
1. Your zip is corrupted (look at the output). Re-download it and compare the MD5 checksums.
2. If you're s-on you need to be relocked for running RUUs.
3. You never mentioned your firmware version nor your CID so no one can verify whether you use the correct RUU.
4. There is no free version of sunshine since its a free app with in-app purchasement. But there is no need to s-off if you use the correct RUU.
Click to expand...
Click to collapse
Hello there, thanks for replying my thread
1. I'm sorry I dont quiet understand, do you mean zip in my PC or zip in my phone?
2. My firmware version is 1.32.617.30, how do i check my CID?
Correct me if I'm wrong but there are 2 options for me to return to original stock? First, S-off my phone and flash RUU firmware? Second, relocked my phone then run original stock? Since I didnt backup my original stock, I need to find untouched one?
Sorry this is my first android phone so if I'm total noob, I'm so sorry

What if i unrooted then relocked my phone, will i be able to take OTA then?

kamocheng said:
Hello there, thanks for replying my thread
1. I'm sorry I dont quiet understand, do you mean zip in my PC or zip in my phone?
2. My firmware version is 1.32.617.30, how do i check my CID?
Correct me if I'm wrong but there are 2 options for me to return to original stock? First, S-off my phone and flash RUU firmware? Second, relocked my phone then run original stock? Since I didnt backup my original stock, I need to find untouched one?
Sorry this is my first android phone so if I'm total noob, I'm so sorry
Click to expand...
Click to collapse
I'm talking about the zip you tried to flash in post 3. If you are using firefox as a browser I would recommend using an addon like DownThemAll! to verifiy the md5 checksum after the download has finished. Files can get corrupted during a download.
No, its one and the same way. You run the RUU either way. The only difference is that you can flash any firmware version with s-off and you don't need to relock while the versions you can flash with s-on have to match your current version (that means same version or newer) and your CID. Firmware versions with x.xx.617.xx are the developers editions if I'm not mistaking. (As far as I know AndroidRUU doesn't have any corresponding files. So I assume you downloaded it from clsA's personal collection of developer edition files since google didn't find any other sources for these files.) As said before redownload the file and compare the downloaded file's checksum with the one mentioned next to the download link (428582cef691c2e37053a0e19e9d738e). If they match the file should be flashable.
I prefer flashing RUUs using the sd-card method instead of fastboot so here are some instructions how I would continue:
Be sure to backup everything important like contacts, sms, etc. (I'm using MyPhoneExplorer for this step)
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Relock your bootloader.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %).
Boot into download mode.
Follow the instructions on the screen.
Wait some minutes.
Done.

Flippy498 said:
I'm talking about the zip you tried to flash in post 3. If you are using firefox as a browser I would recommend using an addon like DownThemAll! to verifiy the md5 checksum after the download has finished. Files can get corrupted during a download.
No, its one and the same way. You run the RUU either way. The only difference is that you can flash any firmware version with s-off while the versions you can flash with s-on have to match your current version (that means same version or newer) and your CID. Firmware versions with x.xx.617.xx are the developers editions if I'm not mistaking. (As far as I know AndroidRUU doesn't have any corresponding files. So I assume you downloaded it from clsA's personal collection of developer edition files since google didn't find any other sources for these files.) As said before redownload the file and compare the downloaded file's checksum with the one mentioned next to the download link (428582cef691c2e37053a0e19e9d738e). If they match the file should be flashable.
I prefer flashing RUUs using the sd-card method instead of fastboot so here are some instruction how I would continue:
Be sure to backup everything important like contacts, sms, etc. (I'm using MyPhoneExplorer for this step)
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Relock your bootloader.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %).
Boot into download mode.
Follow the instructions on the screen.
Wait some minutes.
Done.
Click to expand...
Click to collapse
So by doing that way, I dont have to S-off my phone to have it return to original stock?

kamocheng said:
So by doing that way, I dont have to S-off my phone to have it return to original stock?
Click to expand...
Click to collapse
Correct.
Edit: I just saw that you asked more or less the same question twice. jollywhitefoot's solution works the same way as the one I described. The only difference is that you are using fastboot instead of a sd-card.

Flippy498 said:
Correct.
Edit: I just saw that you asked more or less the same question twice. jollywhitefoot's solution works the same way as the one I described. The only difference is that you are using fastboot instead of a sd-card.
Click to expand...
Click to collapse
Alright, thank you for your guidance.

kamocheng said:
Alright, thank you for your guidance.
Click to expand...
Click to collapse
So my method in your other thread didn't work? Where are you running into problems?

Difficulties reverting to stock [Help Appreciated]

First things first, this has been asked very often but no other thread helped me out.
So I'll be as precise as I can
I'm using an HTC One M8 Unlocked/International version (presumably, it's not carrier branded)
I unlocked my bootloader using the offical method from HTC Dev on Ubuntu (ADB/Fastboot sucks on Windows) After which I had TWRP and Cyanogenmod 13 Nightly running for a while. Now I would like to get it completely stock (besides the relocked flag) knowing that the ROM/Firmware has been signed by HTC.
What I did:
I could not find the stock images on HTC's website like Google provides them, shame HTC.. So at first I downloaded **some random** nandroid backup from this site. I also flashed the stock recovery that I recovered from a RUU.zip. After this I was able to receive an OTA update just fine. And I'm now currently running Android 6.0 Software number 6.12.401.4 (AFAIK that's the HBOOT version).
However, this is still a random backup from someone who might have potentially modified the system. In fact, it has been modified since the bootloader says *** Software status: modified ***
So, I would like to flash a RUU. HTC's website provides these in the form of an .exe which, are not signed and downloaded over HTTP. But that's OK since the phone verifies the signature of the zip. (I have S-ON and would like to keep it that way for this reason)
But the problem is, the RUU doesn't work. at first, it simply wouldn't run at all. because apparently you need to install a whole bunch of Visual c++ libraries as mentioned here.
After I installed all of these I managed to bring up the RUU wizard. (I did install HTC Sync Manager). I got the following error: "ERROR: 103 MODEL ID ERROR" "Please get the correct update utility and try again. To be clear, this is RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe from this website. It is my exact phone model. These are some screenshots from the utility.
Besides the RUU.exe I also tried some RUU.zips from random forums (that's ok, S-ON verifies the zip anyway) but they all fail the signature test. Like so,
sudo su
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip
...
FAILED (remote 12: signature verify fail)
So if anyone could help me get the official software back that would be greatly appreciated
P.S (why is this forum not using https? login credentials are sent in the clear now )

Jasper_ said:
First things first, this has been asked very often but no other thread helped me out.
So I'll be as precise as I can
I'm using an HTC One M8 Unlocked/International version (presumably, it's not carrier branded)
I unlocked my bootloader using the offical method from HTC Dev on Ubuntu (ADB/Fastboot sucks on Windows) After which I had TWRP and Cyanogenmod 13 Nightly running for a while. Now I would like to get it completely stock (besides the relocked flag) knowing that the ROM/Firmware has been signed by HTC.
What I did:
I could not find the stock images on HTC's website like Google provides them, shame HTC.. So at first I downloaded **some random** nandroid backup from this site. I also flashed the stock recovery that I recovered from a RUU.zip. After this I was able to receive an OTA update just fine. And I'm now currently running Android 6.0 Software number 6.12.401.4 (AFAIK that's the HBOOT version).
However, this is still a random backup from someone who might have potentially modified the system. In fact, it has been modified since the bootloader says *** Software status: modified ***
So, I would like to flash a RUU. HTC's website provides these in the form of an .exe which, are not signed and downloaded over HTTP. But that's OK since the phone verifies the signature of the zip. (I have S-ON and would like to keep it that way for this reason)
But the problem is, the RUU doesn't work. at first, it simply wouldn't run at all. because apparently you need to install a whole bunch of Visual c++ libraries as mentioned here.
After I installed all of these I managed to bring up the RUU wizard. (I did install HTC Sync Manager). I got the following error: "ERROR: 103 MODEL ID ERROR" "Please get the correct update utility and try again. To be clear, this is RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe from this website. It is my exact phone model. These are some screenshots from the utility.
Besides the RUU.exe I also tried some RUU.zips from random forums (that's ok, S-ON verifies the zip anyway) but they all fail the signature test. Like so,
sudo su
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip
...
FAILED (remote 12: signature verify fail)
So if anyone could help me get the official software back that would be greatly appreciated
P.S (why is this forum not using https? login credentials are sent in the clear now )
Click to expand...
Click to collapse
Most likely their is no .401 RUU
You will have to have S-OFF to flash the RUU you have
Sent from my SM-N920T using Tapatalk

clsA said:
Most likely their is no .401 RUU
You will have to have S-OFF to flash the RUU you have
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
As long as the version number is higher or equal to what is currently installed it should work without S-OFF. Besides, I really don't like the idea of getting S-OFF. especially since it isn't necessary.

Jasper_ said:
As long as the version number is higher or equal to what is currently installed it should work without S-OFF. Besides, I really don't like the idea of getting S-OFF. especially since it isn't necessary.
Click to expand...
Click to collapse
Nope you have .401 to change it to .1540 you need to change your mid and CID which requires s-off
Sent from my SM-N920T using Tapatalk

Jasper_ said:
sudo su
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip
...
FAILED (remote 12: signature verify fail)
Click to expand...
Click to collapse
AFAIK you can't use a generic fastboot to flash RUU.zip
It needs htc_fastboot .... as you said - (ADB/Fastboot sucks on Windows) - I don't know how to help you as I know nothing about Ubuntu
Just to give you ideas (for Windows) - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You can only install 6.12.401.4 or higher (but not available as there is none) x.xx.401.x
Using 6.12.1540.4 or any non-x.xx.401.x is totally wrong and won't work for you.

ckpv5 said:
AFAIK you can't use a generic fastboot to flash RUU.zip
It needs htc_fastboot .... as you said - (ADB/Fastboot sucks on Windows) - I don't know how to help you as I know nothing about Ubuntu
Just to give you ideas (for Windows) - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I'm actually using Windows but I run Ubuntu in virtualbox since installing adb is as simple as 'sudo apt install android-tools-adb', USB drivers work out of the box.
You can only install 6.12.401.4 or higher (but not available as there is none) x.xx.401.x
Using 6.12.1540.4 or any non-x.xx.401.x is totally wrong and won't work for you.
Click to expand...
Click to collapse
Hmm, okay I get it. I don't think it would make sense to get S-OFF and flash the xx.1540.4 since this version obviously wasn't meant for my device.
There's also this HTC_Europe_6.12.401.4_signed.zip I mentioned. I tried flashing that using fastboot which seems to work just fine regardless of the non htc_fastboot. But it doesn't pass the signature check. Again I could S-OFF but I'd rather not since a properly non-modified zip should pass the check anyway. Do you think it would work with htc_fastboot? I've tried htc_fastboot on windows but it'll complain about missing DLLs.
I also contacted my local htc live support chat, they told me the only way to get back to stock is to send it to repair service. Obviously, all they'll do is hook it up to a pc run the proper RUU and charge me $100 for it. So I asked if they could just sent me the RUU instead but that "isn't possible"

It failed signature check because of generic fastboot.
You must use htc_fastboot.
Just expand the link that I gave earlier, that's post #6, read post #4 for the drivers you need.
I can't link to you because I'm on mobile.
Or you can go to my thread linked in my signature, read the last two pages where I put a guide how to use ARUWizard to install RUU
The required drivers are linked on item 2.

ckpv5 said:
It failed signature check because of generic fastboot.
You must use htc_fastboot.
Just expand the link that I gave earlier, that's post #6, read post #4 for the drivers you need.
I can't link to you because I'm on mobile.
Or you can go to my thread linked in my signature, read the last two pages where I put a guide how to use ARUWizard to install RUU
The required drivers are linked on item 2.
Click to expand...
Click to collapse
Thanks, I read your post and downloaded htc_fastboot.exe and the RUU. htc_fastboot didn't work at first because it's missing AdbWinApi.dll but I solved that by installing minimal adb in C:\Program Files (x86)\Minimal Adb and Fastboot\ and putting the htc_fastboot.exe inside that folder aswell as the RUU.zip (renamed).
Now, I get this.
C:\Program Files (x86)\Minimal ADB and Fastboot>htc_fastboot devices
SH4BHWM04147 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 3.013 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
target reported max download size of 1826414592 bytes
error: cannot load 'RUU.zip'
Click to expand...
Click to collapse
I'm sure it's there. It's not called ruu.zip.zip either because
C:\Program Files (x86)\Minimal ADB and Fastboot>dir
Volume in drive C has no label.
Volume Serial Number is 628D-64DC
Directory of C:\Program Files (x86)\Minimal ADB and Fastboot
06/20/2016 06:52 PM <DIR> .
06/20/2016 06:52 PM <DIR> ..
04/24/2016 11:51 PM 1,474,048 adb.exe
04/24/2016 11:51 PM 97,792 AdbWinApi.dll
04/24/2016 11:51 PM 62,976 AdbWinUsbApi.dll
04/24/2016 11:51 PM 802,304 fastboot.exe
06/20/2016 06:43 PM 89,865 htc_fastboot.exe
08/09/2015 02:50 PM 29,882 MAF32.exe
06/20/2016 06:51 PM 1,727,767,223 RUU.zip
06/20/2016 06:43 PM 2,004 unins000.dat
06/20/2016 06:42 PM 719,521 unins000.exe
9 File(s) 1,731,045,615 bytes
2 Dir(s) 201,722,662,912 bytes free
Click to expand...
Click to collapse
EDIT: So I moved the adb minimal folder to my documents and now it doesn't give me the error: cannot load RUU.zip
But it still gives me:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Click to expand...
Click to collapse
EDIT 2: The non-htc fastboot gives me error: cannot load RUU.zip too. Perhaps a permission issue? I've tried running it as administrator
EDIT 3: OOPS! I'm so sorry. Forgot to reboot into RUU mode!

Oh gee! It worked! I got a little scared for a bit since it kept doing the same thing over and over. But it finished
*** Software status: official ***
*** RELOCKED ***
Thanks for all the support! I could not have done it with it.

RUU for HTC 10 : HTC__001 WWE / 2PS6200

I spend almost 6 hours to find RUU, and nothing...
S:\! Sunshine\Android\M7\HTC 10>fastboot getvar mid
mid: 2PS620000
finished. total time: 0.001s
S:\! Sunshine\Android\M7\HTC 10>fastboot getvar cid
cid: HTC__001
finished. total time: 0.002s
If you want to ask if i use this : RUU Zip (Stock Signed)
CID: HTC__001/HTC__034/HTC__A07/HTC__J15/HTC__M27/HTC__016/HTC__002 | MID: 2PS620000
1.90.401.5 (by @djluisbento)
yes i used this and i'm geting: header error 22 :C
I just want to get working RUU > install > update to nugat
Currently i'm on my TWRP Stock Backup and i can't get update, cuz i getting error.

Boot to download mode and look at OS line, download the matching RUU and flash it.
The 401 wwe versions can be easily found here in the HTC 10 subforum.
Hint :
Perform a search in the stock backup thread.....

S:\! Sunshine\Android\M7\HTC 10>fastboot flash zip 2PS6IM[email protected]60331.4_41.13_F_release_490497_combined_signed_2_4.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (208927 KB)...
OKAY [ 10.832s]
writing 'zip'...
(bootloader) HOSD CL#738269
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_N
(bootloader) 6XJwu
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 15.560s
Tested RUU's
2PS6IMG_PE[email protected]60331.4_41.13_F_release_478442_combined_signed_2_4
2PS6IM[email protected]60331.4_41.13_F_release_490497_combined_signed_2_4
2PS6IMG_PERFUM[email protected]4061226_79.07_F_release_493442_signed
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_507791_signed_2_4

Flash newer firmware then try again

ergolau said:
Flash newer firmware then try again
Click to expand...
Click to collapse
Newer firmware, like?

SunshineDude said:
Newer firmware, like?
Click to expand...
Click to collapse
https://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
get firmware matched to your targeted RUU from this thread

@ergolau i'm not S-OFF
First lines from post
FIRST THINGS FIRST:
This is for GSM PHONES which have been set S-OFF - no CDMA (Sprint & Verizon) here! S-ON people: Please refer to HTC RUU methods or "Stock Backup and OTA" method. (not provided here).

SunshineDude said:
@ergolau i'm not S-OFF
First lines from post
FIRST THINGS FIRST:
This is for GSM PHONES which have been set S-OFF - no CDMA (Sprint & Verizon) here! S-ON people: Please refer to HTC RUU methods or "Stock Backup and OTA" method. (not provided here).
Click to expand...
Click to collapse
If you do what @Mr Hofs said, you'd be done already...
Sent from my HTC6545LVW using Tapatalk

I've entered the os number and download 3 Ruu's and still error
In this post:
https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Key words iv'e used: 1.30.401.1, HTC__001 WWE

Okay i found the solution...
SDCard has not working propertly, i've used another one with 2PS6IMG_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.zip and it start flashing
This same RUU wont flash via RUU mode Fastboot... #HEADER_ERROR
On M7 i don't get these problems with RUU.
Maybe i'm doing something wrong...

SunshineDude said:
Okey i found the solution...
SDCard has not working propertly, i've used another one with 2PS6IMG_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.zip and it start flashing
This same RUU wont flash via RUU mode Fastboot... #HEADER_ERROR
On M7 i don't get these problems with RUU.
Maybe i'm doing something wrong...
Click to expand...
Click to collapse
Remake the zip to 2PS6IMG.zip and copy of te the sdcard, boot to download mode and it wil be recognized. Flash it......
Stop making it very difficult with fastboot commands, not needed at all. And stop texting all RUU files, totally a waste of time. You need the RUU with the NUMBER that is WRITTEN next to OS in the DOWNLOAD mode. Stop doing all sorts of stuff that is totally irrelevant. If the RUU.zip from here doesn't work you do something wrong.
If your OS line is 2.41.401.x you download that RUU and do as i wrote in the first lines of this post.
You try all different sorts of RUU's so that indicates to me that you didn't bother to check out your download mode

Generally i get what i want.
Sorry for shi* post, but sometimes i just dont get it.
I know that the stock roms have a os versions and phone only accept only specific one.
But sometimes like today my sdcard just trick me so hard ;d and i just trying a different method like fastboot oem rebootRUU + fastboot flash zip zipname.zip, thats all.
Thanks for your time @Mr Hofs and @santod040 (Your rom on M7 GPE
is one of the better ones) .

SunshineDude said:
Generally i get what i want.
Sorry for shi* post, but sometimes i just dont get it.
I know that the stock roms have a os versions and phone only accept only specific one.
But sometimes like today my sdcard just trick me so hard ;d and i just trying a different method like fastboot oem rebootRUU + fastboot flash zip zipname.zip, thats all.
Thanks for your time @Mr Hofs and @santod040 (Your rom on M7 GPE
is one of the better ones) .
Click to expand...
Click to collapse
"generally i get what i want" .....jeeeze that comment made me crinch for a moment. Actually the lack of proper reading our posts had you downloading all sorts of RUU files which were unnecessary. It's not your sdcard that tricked you it's your unfocused mind.
Cheers

htc 10 please help me
i have HTC 10
***UNLOCKED***
S-OFF
htc_pmeuhl
CID--HTC__621
MID--2PS620000
RADIO--1.0.U01................
OS--2.41.709.73
and twrp recovery INSTALLED and have a Viper Rom but problem is phone hang on some function and heat up and shutdown like when i make shortcut an app from app drawer to home screen phone is hang with no response and heat and shutdown and also when i download from chrome or other apps so i decided to go to the original software no matter is Marshmallow or Nougat or Oreo but i want to go original what i need to do my question is from which method i want to install like from ruu.exe or ruu.zip or i need to flash stock recovery first or re-lock the boot-loader or do S-ON from S-OFF state please give all the links which i needs i am very thank full in advance plz.
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
i have HTC 10
***UNLOCKED***
S-OFF
htc_pmeuhl
CID--HTC__621
MID--2PS620000
RADIO--1.0.U01................
OS--2.41.709.73
and twrp recovery INSTALLED and have a Viper Rom but problem is phone hang on some function and heat up and shutdown like when i make shortcut an app from app drawer to home screen phone is hang with no response and heat and shutdown and also when i download from chrome or other apps so i decided to go to the original software no matter is Marshmallow or Nougat or Oreo but i want to go original what i need to do my question is from which method i want to install like from ruu.exe or ruu.zip or i need to flash stock recovery first or re-lock the boot-loader or do S-ON from S-OFF state please give all the links which i needs i am very thank full in advance plz.

sadaqatrajput said:
i have HTC 10
***UNLOCKED***
S-OFF
htc_pmeuhl
CID--HTC__621
MID--2PS620000
RADIO--1.0.U01................
OS--2.41.709.73
and twrp recovery INSTALLED and have a Viper Rom but problem is phone hang on some function and heat up and shutdown like when i make shortcut an app from app drawer to home screen phone is hang with no response and heat and shutdown and also when i download from chrome or other apps so i decided to go to the original software no matter is Marshmallow or Nougat or Oreo but i want to go original what i need to do my question is from which method i want to install like from ruu.exe or ruu.zip or i need to flash stock recovery first or re-lock the boot-loader or do S-ON from S-OFF state please give all the links which i needs i am very thank full in advance plz.
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
i have HTC 10
***UNLOCKED***
S-OFF
htc_pmeuhl
CID--HTC__621
MID--2PS620000
RADIO--1.0.U01................
OS--2.41.709.73
and twrp recovery INSTALLED and have a Viper Rom but problem is phone hang on some function and heat up and shutdown like when i make shortcut an app from app drawer to home screen phone is hang with no response and heat and shutdown and also when i download from chrome or other apps so i decided to go to the original software no matter is Marshmallow or Nougat or Oreo but i want to go original what i need to do my question is from which method i want to install like from ruu.exe or ruu.zip or i need to flash stock recovery first or re-lock the boot-loader or do S-ON from S-OFF state please give all the links which i needs i am very thank full in advance plz.
Click to expand...
Click to collapse
Flash this using SD card method.
Do NOT relock bootloader or return to s-on.
https://androidfilehost.com/?fid=745425885120725537
Sent from my Pixel 3 XL using Tapatalk