Develop Bugs

[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?

HTC One M9 RUU gets stuck a 50% on "Sending"

Hello,
I have been having a lot of trouble lately and all of my problems can be fixed by doing an RUU. The issue is my m9 will not take a full RUU it gets stuck at 50% and I get an error 155 in the HTC exe. The phone itself freezes on the screen with red security text a phone with a spinning circular arrow and a green progress bar. After the freeze I can reboot the phone by volup and pwr. I can access bootloader, and download mode. Doing an RUU by the zip file on the sd card in download mode results in "Failed: -2, 8: fail to flash via downloadzip
How I got here.
relocked bootloader without selecting allow oem unlock in dev settings
attempted an RUU and it froze no ROM installed
attempted to unlock bootloader to get error message because of allow unlock not selected in dev settings
attempted to flash using sd card and download mode to get error above
I am s-on and relocked
I am so stuck right now and I need some help

lpcar04 said:
Hello,
I have been having a lot of trouble lately and all of my problems can be fixed by doing an RUU. The issue is my m9 will not take a full RUU it gets stuck at 50% and I get an error 155 in the HTC exe. The phone itself freezes on the screen with red security text a phone with a spinning circular arrow and a green progress bar. After the freeze I can reboot the phone by volup and pwr. I can access bootloader, and download mode. Doing an RUU by the zip file on the sd card in download mode results in "Failed: -2, 8: fail to flash via downloadzip
How I got here.
relocked bootloader without selecting allow oem unlock in dev settings
attempted an RUU and it froze no ROM installed
attempted to unlock bootloader to get error message because of allow unlock not selected in dev settings
attempted to flash using sd card and download mode to get error above
I am s-on and relocked
I am so stuck right now and I need some help
Click to expand...
Click to collapse
ok. so error 155 could be a connectivity issue. Check device manager or try a different USB port.
Also, do you have HTC Sync Manager installed on the PC? It's required for an RUU to run. Otherwise you get 155.

jollywhitefoot said:
ok. so error 155 could be a connectivity issue. Check device manager or try a different USB port.
Also, do you have HTC Sync Manager installed on the PC? It's required for an RUU to run. Otherwise you get 155.
Click to expand...
Click to collapse
I do have sync manager does it need to be running?

lpcar04 said:
I do have sync manager does it need to be running?
Click to expand...
Click to collapse
No. just needs to be installed.
What firmware are you currently on and what is the version of the RUU you're using? People have had issue running an ruu version that is older than their current firmware version.

if this helps i have tried to update firmware using fastboot and I get this messgae
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (58525 KB)...
OKAY [ 4.028s]
writing 'zip'...
(bootloader) HOSD CL#556164
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 7.881s

jollywhitefoot said:
No. just needs to be installed.
What firmware are you currently on and what is the version of the RUU you're using? People have had issue running an ruu version that is older than their current firmware version.
Click to expand...
Click to collapse
I am on 2.6.651.11 trying to flash that same version because the first time I flashed that It never finished flashing the ROM portion

lpcar04 said:
if this helps i have tried to update firmware using fastboot and I get this messgae
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (58525 KB)...
OKAY [ 4.028s]
writing 'zip'...
(bootloader) HOSD CL#556164
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 7.881s
Click to expand...
Click to collapse
lpcar04 said:
I am on 2.6.651.11 trying to flash that same version because the first time I flashed that It never finished flashing the ROM portion
Click to expand...
Click to collapse
You can't flash firmware when you're s-on.
For the RUU, maybe open device manager while it's running to make sure the device is recognized throughout the process. I suppose it's possibly a bad download, but I'm not sure the exe would run at all of that was the case.

jollywhitefoot said:
You can't flash firmware when you're s-on.
For the RUU, maybe open device manager while it's running to make sure the device is recognized throughout the process. I suppose it's possibly a bad download, but I'm not sure the exe would run at all of that was the case.
Click to expand...
Click to collapse
ok thanks will try now

lpcar04 said:
ok thanks will try now
Click to expand...
Click to collapse
Ok I just tried it phone stays detected in Device manager the entire time but right before it fails it says "updating signature" in the exe then closes and gives me 155 and phone freezes

Im in the exact same boat. what to do ? how do i revive the phone ?

arm5263 said:
Im in the exact same boat. what to do ? how do i revive the phone ?
Click to expand...
Click to collapse
Meaning you are s-on, relocked, can't boot into the OS, and did not tick "allow oem unlock"?
If that's the case, your only options are to run the ruu for your firmware version or, if that doesn't work or none exists, return it to htc for repair.
Sent from my HTC One M9 using Tapatalk

yes unfortunately I am S-on, bootloader reloacked (to take the official update). It all started when my official HTC RUU crashed mid way!!! it still crashes..I can get to fastboot, recovery download mode etc but just cant RUU any more as it will crash around 62% saying errror 115 ..get the correct RUU for your device ... it stops at fail to update signature or something... Repeated this this multiple times..same result... I was trying to update to 5.1 from 5.01 software. The download mode does say that I have 2.X.502.18 OS but I believe it did not finish installing all...
I have head there is another way of putting the RUU.zip file and renaming it to some specific name and putting it in your sd card and applying update or may be it will automatically install in download mode?
Can someone help me get that zip file for ATT 5.1 version or outline the process ? my last hope!

arm5263 said:
yes unfortunately I am S-on, bootloader reloacked (to take the official update). It all started when my official HTC RUU crashed mid way!!! it still crashes..I can get to fastboot, recovery download mode etc but just cant RUU any more as it will crash around 62% saying errror 115 ..get the correct RUU for your device ... it stops at fail to update signature or something... Repeated this this multiple times..same result... I was trying to update to 5.1 from 5.01 software. The download mode does say that I have 2.X.502.18 OS but I believe it did not finish installing all...
I have head there is another way of putting the RUU.zip file and renaming it to some specific name and putting it in your sd card and applying update or may be it will automatically install in download mode?
Can someone help me get that zip file for ATT 5.1 version or outline the process ? my last hope!
Click to expand...
Click to collapse
Can't you just unlock with htcdev, get TWRP and flash a rom to check "allow oem unlocking"?
I don't really understand what that option does as I was unlocked at version 5.0.2 though, sorry for my ignorance.

arm5263 said:
yes unfortunately I am S-on, bootloader reloacked (to take the official update). It all started when my official HTC RUU crashed mid way!!! it still crashes..I can get to fastboot, recovery download mode etc but just cant RUU any more as it will crash around 62% saying errror 115 ..get the correct RUU for your device ... it stops at fail to update signature or something... Repeated this this multiple times..same result... I was trying to update to 5.1 from 5.01 software. The download mode does say that I have 2.X.502.18 OS but I believe it did not finish installing all...
I have head there is another way of putting the RUU.zip file and renaming it to some specific name and putting it in your sd card and applying update or may be it will automatically install in download mode?
Can someone help me get that zip file for ATT 5.1 version or outline the process ? my last hope!
Click to expand...
Click to collapse
There's a thread on the ATT M9 forms for converting to a dev edition that has the SD install method listed.
Sent from my HTC One M9 using Tapatalk

Ajxx16 said:
There's a thread on the ATT M9 forms for converting to a dev edition that has the SD install method listed.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
@arm5263
You can find it here >> http://forum.xda-developers.com/showthread.php?t=3086948
Sent from my HTC One M9 using Tapatalk

the problem is since the RUU failed in the middle of updating to 5.1 and I already have relocked the bootloader before applying RUU (you have to lock the bootloader or RUU will fail) and now with partially installed 5.1 on my phone, there was a new security feature that was added that youa have to check allow oem unlock on developer settings.
So now I am stcuk, cant got to developer setting as I cant boot to OS, RUU keeps failing on me, can not unlock bootloader as its not even letting me get the token...fails saying "
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
any way to allow oem unlock in fastboot instead of through developer settings?
any other clue?

arm5263 said:
the problem is since the RUU failed in the middle of updating to 5.1 and I already have relocked the bootloader before applying RUU (you have to lock the bootloader or RUU will fail) and now with partially installed 5.1 on my phone, there was a new security feature that was added that youa have to check allow oem unlock on developer settings.
So now I am stcuk, cant got to developer setting as I cant boot to OS, RUU keeps failing on me, can not unlock bootloader as its not even letting me get the token...fails saying "
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
any way to allow oem unlock in fastboot instead of through developer settings?
any other clue?
Click to expand...
Click to collapse
Did you try the SD-card method ?
Code:
rename the RUU.zip to 0PJAIMG.ZIP,
place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work),
reboot into DOWNLOAD_MODE, agree and it should flash.

thatts the only thing I have not tried. I will do so tonight and report back.
BTW any place I can grab the ATT 5.1 RUU.zip ? It has to be 2.X.502.18 OS as thats what I see in download screen. With locked bootloder I believe I can only update or re-install the same version.
I extracted rom.zip out of the HTC RUU.EXE file (grabbing it from the temp folder). Do i Just rename it from rom.zip to 0PJAIMG.zip ? I tried to open rom.zip in the arhive app abut it failed to open it ? is that expected?

arm5263 said:
thatts the only thing I have not tried. I will do so tonight and report back.
BTW any place I can grab the ATT 5.1 RUU.zip ? It has to be 2.X.502.18 OS as thats what I see in download screen. With locked bootloder I believe I can only update or re-install the same version.
I extracted rom.zip out of the HTC RUU.EXE file (grabbing it from the temp folder). Do i Just rename it from rom.zip to 0PJAIMG.zip ? I tried to open rom.zip in the arhive app abut it failed to open it ? is that expected?
Click to expand...
Click to collapse
yes rename that rom.zip
no you can't open them their encrypted, and if i recall that RUU was corrupt directly from AT&T
have they updated it ?
http://forum.xda-developers.com/att...ruu-how-to-t3086948/post62629949#post62629949

Sd card method failed too...gives some error say unable to flash from sd card ERROR -2.
Seems like I'll have to return it to ATT or should I send it to HTC ? it is S-on but bootloader is re-locked. I hope ATT wont mind taking it back. I believe its under one year warranty period. I mean was just trying to install 5.1 manually after it failed to take OTA.
Never relock your bootloader on HTC especially on 5.1 and spend $25 to get S-OFF lesson learned!

S-OFF is gone, CyanogenMod is installed -> How to S-OFF? SunShine ain't working!

Hi there,
I need to upgrade the bootloader in order to upgrade my Cyanogenmod.
But the problem is, that I lost S-OFF, I don't know when it happened...
Sunshine doesn't, work, it requires stock ROM.
The other thing is, that I can't flash stock ROM for the same reason!
How do I fix this issue? ._.
Thank you!

BloodySword said:
Hi there,
I need to upgrade the bootloader in order to upgrade my Cyanogenmod.
But the problem is, that I lost S-OFF, I don't know when it happened...
Sunshine doesn't, work, it requires stock ROM.
The other thing is, that I can't flash stock ROM for the same reason!
How do I fix this issue? ._.
Thank you!
Click to expand...
Click to collapse
You don't need S-OFF to flash a stock ROM. Flash the latest FW, run the RUU. You only need to relock the BL before running the RUU. If you have used Sunshine in the past (purchased it for your device) it should recognize that and you should be able to use it again on the same device without purchasing it again.
1) LOCK BL (not s-on, just relock) Steps are in the FW thread.
2) Flash FW zip (again, steps in FW thread)
2) Run RUU (steps in the RUU thread)
3) Reboot into ROM, install Sunshine, use it.
4) install whatever you want.

Thanks for trying to help me but I can't even flash the latest HTC firmware because my bootloader is too old (3.18, expected is 3.19)...
I didn't use SunShine back then, I used the HTC Developer Unlock...
Looks really bad for this device. It was replaced with an OPO3 anyway but I would like to give it to a poor friend for free. Without the doze bug!
Good Night from Germany

dopy25 said:
You don't need S-OFF to flash a stock ROM. Flash the latest FW, run the RUU. You only need to relock the BL before running the RUU. If you have used Sunshine in the past (purchased it for your device) it should recognize that and you should be able to use it again on the same device without purchasing it again.
1) LOCK BL (not s-on, just relock) Steps are in the FW thread.
2) Flash FW zip (again, steps in FW thread)
2) Run RUU (steps in the RUU thread)
3) Reboot into ROM, install Sunshine, use it.
4) install whatever you want.
Click to expand...
Click to collapse
Wait! Does flashing the HTC firmware also flashes the bootloader?
If yes, that could be a way out of this problem!
I will try it later.
Thanks!
Edit:
NOTHING WORKS!!
I flashed SuperSU 2000 times and I get no S-OFF!
WHY?? I just want to upgrade the freaking HBOOT so that I can flash the new CWM13!!!
Why do they even require a new bootloader version. The 3.18 was fine until now. Why did they abandon it????
I am realy mad!
Edit2:
fastboot oem lock failed, too! Unknown error... So, nothing works on this device!

I was in the same boat as you, and finally managed to get the boot loader updated and CM13 installed. All while S-ON.
I can't post links yet, but look up thread ID 2701376 on XDA. It has everything you need.
You only need to get to where you can get the OTA updates. So, you'll need a nandroid, and the stock recovery. I didn't even need to re-lock the boot loader. Good luck.

reckless76 said:
I was in the same boat as you, and finally managed to get the boot loader updated and CM13 installed. All while S-ON.
I can't post links yet, but look up thread ID 2701376 on XDA. It has everything you need.
You only need to get to where you can get the OTA updates. So, you'll need a nandroid, and the stock recovery. I didn't even need to re-lock the boot loader. Good luck.
Click to expand...
Click to collapse
Hey. Ugh, I will give it a try this weekend. Wish me luck. Thanks!
This device is meant as a gift to a friend who cannot afford any usable phone...
But I don't wanna give it away with the doze bug. I hope it is fixed in the latest CM13 builts.

BloodySword said:
Thanks for trying to help me but I can't even flash the latest HTC firmware because my bootloader is too old (3.18, expected is 3.19)...
I didn't use SunShine back then, I used the HTC Developer Unlock...
Looks really bad for this device. It was replaced with an OPO3 anyway but I would like to give it to a poor friend for free. Without the doze bug!
Click to expand...
Click to collapse
There's nothing wrong with the device, its likely perfectly fine to be updated, if done properly. The main issue is pilot error; as it appears you have a poor understanding of the processes and terms.
There is no limitation that prohibits updating firmware, if your hboot is older (3.18). Its more likely you are simply trying to flash the wrong firmware (not correct CID, MID).
HTCDev.com bootloader unlock is not the same thing as s-off. If you didn't use Sunshine to s-off (or Firewater when it worked, but that was before Dec 2014), then you never had s-off. But as described, you don't need s-off to flash custom ROMs (all you need in an unlocked bootloader) and you don't need s-off to flash the proper signed firmware.
Need more info on the device to properly advise. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what firmware are you trying to flash (exact file name)?
---------- Post added at 10:53 AM ---------- Previous post was at 10:01 AM ----------
BloodySword said:
Wait! Does flashing the HTC firmware also flashes the bootloader?
If yes, that could be a way out of this problem!
Click to expand...
Click to collapse
Yes, firmware contains hboot, along with a number of other partitions you need to update (since they are outdated) like radio, media, WiFi, Bluetooth etc.
That is the whole point of the suggestion of flashing the firmware.
BloodySword said:
NOTHING WORKS!!
I flashed SuperSU 2000 times and I get no S-OFF!
Click to expand...
Click to collapse
Not sure what you are saying here. SuperSU in itself just give you root, not s-off.
Or do you mean, that rooting the current ROM doesn't allow Sunshine to s-off the device? If so, its not what you typed, and that makes it confusing. Also, if you are still talking about CM, its already rooted, and you don't need to root it with SuperSU (and doing so often creates more problems).
Also, Sense ROMs (preferabley stock, or stockish - only certain custom ROM Sense ROMs will work) are best for Sunshine compatibility (and rooted).
BloodySword said:
WHY?? I just want to upgrade the freaking HBOOT so that I can flash the new CWM13!!!
Why do they even require a new bootloader version. The 3.18 was fine until now. Why did they abandon it????
Click to expand...
Click to collapse
Why? Because outdated hboots are known to cause issues on newer ROMs. In addition, older firmware (not just hboot) may cause issues on newer ROMs as well. So its highly advised to keep all firmware updated, not just hboot.

redpoint73 said:
There's nothing wrong with the device, its likely perfectly fine to be updated, if done properly. The main issue is pilot error; as it appears you have a poor understanding of the processes and terms.
Click to expand...
Click to collapse
I must admit, I thought SuperSU and root makes me able to also unlock the special areas on the eMMC like HBOOT, RADIO etc.
There is no limitation that prohibits updating firmware, if your hboot is older (3.18). Its more likely you are simply trying to flash the wrong firmware (not correct CID, MID).
HTCDev.com bootloader unlock is not the same thing as s-off.
Click to expand...
Click to collapse
Aha! That explains it!
If you didn't use Sunshine to s-off (or Firewater when it worked, but that was before Dec 2014), then you never had s-off. But as described, you don't need s-off to flash custom ROMs (all you need in an unlocked bootloader) and you don't need s-off to flash the proper signed firmware.
Click to expand...
Click to collapse
Is there a way to S-OFF it with the current state of the device? Variables further below. I would rather like to have S-OFF, so I can flash HBOOT, RADIO, etc manually anytime I need it.
Need more info on the device to properly advise. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what firmware are you trying to flash (exact file name)?
Click to expand...
Click to collapse
This is what I want to flash in the end:
http://download.cyanogenmod.org/get/jenkins/174461/cm-13.0-20160815-NIGHTLY-m8.zip
The HTC firmware is deleted from my HDD.
Yes, firmware contains hboot, along with a number of other partitions you need to update (since they are outdated) like radio, media, WiFi, Bluetooth etc.
That is the whole point of the suggestion of flashing the firmware.
Not sure what you are saying here. SuperSU in itself just give you root, not s-off.
Or do you mean, that rooting the current ROM doesn't allow Sunshine to s-off the device? If so, its not what you typed, and that makes it confusing. Also, if you are still talking about CM, its already rooted, and you don't need to root it with SuperSU (and doing so often creates more problems).
Click to expand...
Click to collapse
Sure? CM itself in its fresh installed form was NOT rootet for me, because Xposed didn't work... It didn't even install before I rooted the ROM.
Also, Sense ROMs (preferabley stock, or stockish - only certain custom ROM Sense ROMs will work) are best for Sunshine compatibility (and rooted).
Why? Because outdated hboots are known to cause issues on newer ROMs. In addition, older firmware (not just hboot) may cause issues on newer ROMs as well. So its highly advised to keep all firmware updated, not just hboot.
Click to expand...
Click to collapse
Ah okay.
So here are the vars:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <CENSORED>
(bootloader) imei: <CENSORED>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: <CENSORED>
(bootloader) cidnum: HTC__102
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So, what firmware can I flash via TWRP? Or MUST it be done via adb push?

BloodySword said:
Is there a way to S-OFF it with the current state of the device?
Click to expand...
Click to collapse
You need to be on stock ROM (or close to stock, some Sense custom ROMs work, with root, in order to use Sunshine.
BloodySword said:
Sure? CM itself in its fresh installed form was NOT rootet for me, because Xposed didn't work... It didn't even install before I rooted the ROM.
Click to expand...
Click to collapse
Yes, I'm absolutely sure that CM comes pre-rooted. Its a common mistake to think its not rooted, as you need to "enable" root in Settings. Do so by going into Settings>Developer's Options, and toggle root "on". If no Developer's Options in Settings, go to About>Software information, and tap Build Number 7 times, and you will see a message that "you are now a developer" (seriously, not joking, it says that!) and the Dev Options will appear in Settings.
You made some error posting getvar output (my comments in red):
BloodySword said:
(bootloader) serialno: DELETE THIS
(bootloader) modelid: <CENSORED> Don't censor this
Click to expand...
Click to collapse
There was no need to censor modelid (MID) as its not personal info, and thousands of phones have the same MID. Yours is probably 0P6B10000 (or it may display with one less zero, can't remember).
Serial number on the other hand, is unique to your device, and should be removed (as I previously instructed).
BloodySword said:
So, what firmware can I flash via TWRP? Or MUST it be done via adb push?
Click to expand...
Click to collapse
No, it can't be flashed in recovery. And not with adb push. Its flashed with fastboot.
You can flash the stock firmware (full wipe) 6.12.401.4 from here (includes instructions to flash with fastboot): http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Alternately, you may choose to RUU back to full stock (in order to run sunshine s-off). File and instructions here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6&nocache=1&z=2525208588331338
Then unlock the bootloader again, flash TWRP 3.0.2, and flash SuperSU 2.76 to root. Then you can run sunshine app ($25 US) to s-off the device.
In either case (flash stock firmware or install RUU) backup any personal data from the phone that you want to keep. Either route will wipe your data.

Ugh.. I ran over three times and I didn't see serialno? Give me a break. I need more sleep...
I then thought modelid is the same...
The MID you guessed is correct.
I censored the serialno in the post above.
So Variant A is when I just want to upgrade to the latest CM, just flash the firmware with fastboot, then immediately after CM again?
Variant B would also be alright, too. The device can be wiped, I have already migrated to stock OnePlus3 with O2OS3.

BloodySword said:
I then thought modelid is the same...
The MID you guessed is correct.
Click to expand...
Click to collapse
Not as much a guess, as a result of some prior knowledge about the CIDs and MIDs (or call it detective work, if you will).
The MID identifies if its the Euro version, which in this case I can also determine from the CID.
But its good of you to confirm, as sometimes the MID can be modified by a previous owner or vendor. Or CIDs can also be the same for other versions (such as dual SIM - although in that case the product name would be different from "m8_ul" - so another clue there).
Not the same as serial number, which is unique to your individual M8.
BloodySword said:
So Variant A is when I just want to upgrade to the latest CM, just flash the firmware with fastboot, then immediately after CM again?
Variant B would also be alright, too.
Click to expand...
Click to collapse
Basically, yes.
Method A (relock bootloader, flash signed firmware) would be best if you want to then install CM, but stay s-on.
Method B (relock bootloader, RUU) would probably be best if you want full stock Marshmallow Sense (for instance to s-off).
BloodySword said:
I have already migrated to stock OnePlus3 with O2OS3.
Click to expand...
Click to collapse
How you liking that phone? I'm actually pretty curious about it as an upgrade, also.
Obviously, any current "flagship" phone is going to be a significant CPU/GPU upgrade, as well as a lot more RAM in the case of the OnePlus3. And the displays and camera modules in general have come a long way in 2 years. But how is the speaker sound quality compared to the M8? That is really my main concern with the OnePlus3, since sound is important to me. And that is one area where HTC is still striving to be provide a superior experience with the HTC 10 (although of course its much more expensive).
I know the OnePlus 3 just has a single bottom facing speaker, and its not going to match stereo front-facing Boomsound on the M8. But is the sound at least decent and passable; or a big downgrade?
I usually don't like to go off topic like this. But given the age of our beloved M8, I'd say its pretty fair game, as many of us are probably looking to upgrade soon (or have already).

redpoint73 said:
Not as much a guess, as a result of some prior knowledge about the CIDs and MIDs (or call it detective work, if you will).
The MID identifies if its the Euro version, which in this case I can also determine from the CID.
But its good of you to confirm, as sometimes the MID can be modified by a previous owner or vendor. Or CIDs can also be the same for other versions (such as dual SIM - although in that case the product name would be different from "m8_ul" - so another clue there).
Not the same as serial number, which is unique to your individual M8.
Click to expand...
Click to collapse
So just logic in the end.
Method A (relock bootloader, flash signed firmware) would be best if you want to then install CM, but stay s-on.
Method B (relock bootloader, RUU) would probably be best if you want full stock Marshmallow Sense (for instance to s-off).
Click to expand...
Click to collapse
Relock bootloader. I'm feeling sick... This is what also failed last time.
Code:
fastboot oem relock
threw an unknown error or file missing. :crying:
Then the device was basically bricked, it only booted into fastboot with a security warning. If it occurs again, I will post a log. Will happen Saturday or Sunday as I am back to work after hospital amusement... Not related to this phone.
Offtopic
>> One Plus 3
How you liking that phone? I'm actually pretty curious about it as an upgrade, also.
Obviously, any current "flagship" phone is going to be a significant CPU/GPU upgrade, as well as a lot more RAM in the case of the OnePlus3. And the displays and camera modules in general have come a long way in 2 years. But how is the speaker sound quality compared to the M8? That is really my main concern with the OnePlus3, since sound is important to me. And that is one area where HTC is still striving to be provide a superior experience with the HTC 10 (although of course its much more expensive).
I know the OnePlus 3 just has a single bottom facing speaker, and its not going to match stereo front-facing Boomsound on the M8. But is the sound at least decent and passable; or a big downgrade?
I usually don't like to go off topic like this. But given the age of our beloved M8, I'd say its pretty fair game, as many of us are probably looking to upgrade soon (or have already).
Click to expand...
Click to collapse
The speaker itself is very loud and can deliver loud sound without distortion, but little at full volume. Much better as the ones in m8. However, the low frequencies are not as defined as with HTC's BoomSound(TM) technology.
In fact, the speaker is so loud and efficient at the mid-range and highs, that notification and ringtone volume level 1 is too loud for work. The only workarounds are low volume sound files for notification or vibration-only mode, which is bit annoying.
Besides that, the display is very bright and very readable in the sun. However, it also suffers from pen-tile fly screen issues. In everyday life it is no big deal but it's noticable. For VR applications I imagine this is very bad. I hope they go for S-IPS and 100% AdobeRGB in the OnePlus 4 next time... Not a fan of Scamscum Displays.
I first had the dark grey one, but it has dust between the glass and the AMOLED!! I then ordered the new available soft gold version and did a return RMA. I am currently waiting for the results and refund.
The processor is very fast and the 6GB ram are really a step forward.
However, Oxygen OS still suffers from the "doze" bug, some push notifications are postponed or only fetched when waking the device up. The last update should fix it, but it just got better instead of fully resolved... I hope they will fix this soon.
Oxygen OS doesn't have many ringtones built-in, I miss the Google stock ones. But I grabbed them from CyanogenMod out of my m8 and put them on the internal UFS. :victory:
OTA updates are fast and reliable, too.
/Offtopic

BloodySword said:
Relock bootloader. I'm feeling sick... This is what also failed last time.
Code:
fastboot oem relock
threw an unknown error or file missing. :crying:
Click to expand...
Click to collapse
Wrong command. It should be: fastboot oem lock
Also, thanks for the "off topic" comments!

Code:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Invalid argument))
finished. total time: 1.178s
Failed. Sticks in fastboot until I unlock again using HTC-DEV. :crying:

BloodySword said:
Failed. Sticks in fastboot until I unlock again using HTC-DEV. :crying:
Click to expand...
Click to collapse
Does it still say UNLOCKED on the bootloader screen, or RELOCKED?

This is what it displays:
http://i.imgur.com/GNEVHyt.jpg
Oh and you're welcome!

BloodySword said:
This is what it displays:
http://i.imgur.com/GNEVHyt.jpg
Click to expand...
Click to collapse
That is exactly what is supposed to happen. The phone won't boot after being relocked, that is normal and intended.
Flash the RUU, or the firmware I linked previously, using fastboot (whichever method you prefer).
After RUU or firmware, you should see the OS number changed to 6.12.401.4, and hboot should be 3.19.

Failed.
MD5 sum was correct after download.
Code:
C:\adb>fastboot flash zip fw.zip
target reported max download size of 1830477824 bytes
sending 'zip' (82794 KB)...
OKAY [ 3.470s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.643s
Edit:
Tried:
stock 6.12.401.4 International
Also tried:
M8_6.12.1540.4_DevEd_FullStock

BloodySword said:
Failed.
MD5 sum was correct after download.
Code:
C:\adb>fastboot flash zip fw.zip
target reported max download size of 1830477824 bytes
sending 'zip' (82794 KB)...
OKAY [ 3.470s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.643s
Edit:
Tried:
stock 6.12.401.4 International
Also tried:
M8_6.12.1540.4_DevEd_FullStock
Click to expand...
Click to collapse
That's a big size firmware .... you can't flash unsigned firmware on S-On device.
Get the htc signed 6.12.401.4 firmware in post #5 on my backup thread linked in my signature.

http://imgur.com/a/BvaYN
Console locked up.
I don't have the balls to CTRL+C it...

Bricked boot loop HTC M9 - Help me XDA developers you're my only hope!

I have an HTC One M9. It used to have Venum's Viper OS installed. Then about a week ago it began to update all the google apps, consequently they would then regularily but randomly close. It was annoying but I was living with it until I had the time to google what the cause/solution may be.
However the other day I was forced to reboot my phone and discovered that it would not boot. I got the initial white HTC screen with the red build notice at the bottom as usual then it would start the boot animation but would then freeze and reboot. Essentially it was stuck in a reboot loop.
I tried booting into TWRP and clearing the Cache - No change
I tried a full factory reset - No change
I tried flashing the viper rom again - It appeared to go well but when it came to the reboot I was back at sqaure one.
Ok getting desperate now I tried flashing the system.img and boot.img from TWRP - The behavior remained.
Then I made what I believe to be a real mistake and flashed what I think was a stock recovery.img
This left me in a real mess.
I can boot into the bootloader. It is unlocked and S-ON.
If I select reboot to download mode it fails with a nice red message.
I can select recovery mode but it will slip back into the reboot loop.
To actually get into recovery I have to select reboot to bootloader and once it's rebooted and back on the bootloader screen I can the select recovery mode.
Once in recovery mode I have some very limited options.
Apply update from ADB - I've been unable to get this to work
Wipe data/factory reset - This works but doesn't fix anything
Wipe cache partition - This works but doesn't fix anything
Reboot to bootloader - This works
Power Down - Also works
View recovery logs - Yep loads of technical gumf I don't really understand
Apply from phone storage / Apply from SD card
At the bottom of the recovery mode screen in yellow I have a number of error messages. Something like
E;missing bitmap oem_unlock_bg
(code -1)
E;missing bitmap oem_unlock_bg_yes
(code -1)
E;missing bitmap oem_unlock_bg_no
(code -1)
handle_cota_install: install cwpkg to /cota/cwpkg.zip
handle_cota_install: install cwprop to /cota/cw.prop
E:Fail to open file /sys/devices/platform/android_usb/host mode
Write host_mode error
handle_cota_install: no CW files. Skip cw installation.
I have ADB/Fastboot however...
Fastboot oem lock fails as does fastboot flashing lock
Attempts to fastboot flash the TWRP recovery back fail due to the S-ON state.
Fastboot getvar all shows the following but no CID or MID info
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA5B5YJ01037
all:
finished. total time: 0.133s
htc_fastboot finished. total time: 0.351s
I've tried connecting the device to laptop and running RUU update utility from HTC but it either cannot connect or it reports a battery state of less than 30% (when I know it's fully charged).
I read somewhere that you can flash an RUU by putting it on the SD card and rebooting into the bootloader but I've not had any luck with this yet. It maybe that I'm not using the right RUU without being able to gather the CID or version numbers it's just guesswork.
I'm currently researching if it would be possible to get the recovery partition mounted to my Kali Linux laptop and use DD to flash the TWRP image back on but so far I've found nothing suggesting that this would be possible.
Apologies for such a long post but I wanted to paint as detailed a picture of my current hell as I could. I suspect this maybe a case of NAND death. If so does anyone know if replacing the mainboard will resolve the issues?
I'm running out of options here but I'm determined. I just need help with my next move. Any suggestions are welcome.

You dont have "allow oem unlock" enabled in settings/developer. If you got that fastboot result from download mode then the phone is dead.
S-on is restricting you from flashing system.img.
You need to flash back to stock following flippy's thread in the general section stickies. As flippy will tell you, you've saved yourself a lot of pain by staying s-on but it could also be your undoing.
Good luck!.
Beamed in by telepathy.

@shivadow
According to the OP the bootloader is already unlocked. And as already written in the S-OFF thread here in the Q&A section you don't need S-OFF for restoring a system image. Aside from that, the shown fastboot getvar result is the normal result that you get if you use that command while the phone is booted to the bootloader instead of the download mode. (The OP states that booting to the download mode isn't possible.)
All in all the whole situation has nothing to do with being S-ON or S-OFF since it's simply a hardware failure ("the dead nand issue"). Even with S-OFF you couldn't save this phone. And no, this issue has nothing to do with the custom rom that got used on the phone since it can happen on a stock, never modified phone, as well. There just seem to be some units that suffer from bad hardware.
@mikegrimwade
Your assumption is correct, as far as I can tell. Your issue seems to be a dead nand. Changing the mainboard is probably the only solution for the problem since I haven't seen anyone being successful with repairing such a dead phone just by flashing some files. All repaired phones that I've heard from got sent to HTC and they all came back to their owners with a replaced mainboard.
A little sidenote: The SD card method requires a working download mode not a working bootloader that's why you couldn't use that method. (That requirement actually applies to all RUU flashing methods.)
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
@shivadow
According to the OP the bootloader is already unlocked. And as already written in the S-OFF thread here in the Q&A section you don't need S-OFF for restoring a system image. Aside from that, the shown fastboot getvar result is the normal result that you get if you use that command while the phone is booted to the bootloader instead of the download mode. (The OP states that booting to the download mode isn't possible.)
All in all the whole situation has nothing to do with being S-ON or S-OFF since it's simply a hardware failure ("the dead nand issue"). Even with S-OFF you couldn't save this phone. And no, this issue has nothing to do with the custom rom that got used on the phone since it can happen on a stock, never modified phone, as well. There just seem to be some units that suffer from bad hardware.
@mikegrimwade
Your assumption is correct, as far as I can tell. Your issue seems to be a dead nand. Changing the mainboard is probably the only solution for the problem since I haven't seen anyone being successful with repairing such a dead phone just by flashing some files. All repaired phones that I've heard from got sent to HTC and they all came back to their owners with a replaced mainboard.
A little sidenote: The SD card method requires a working download mode not a working bootloader that's why you couldn't use that method. (That requirement actually applies to all RUU flashing methods.)
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks Flippy498 it is as I feared. I'm not afraid to open the device to replace the mainboard but I'd hoped to avoid it. Can anyone advise where I can get replacement mainboard for the M9? Also will it matter which board I get as I understand there are different boards US, Europe etc?

Look at the bottom of the backside of your phone. There should be a small engraving which states the Model ID of your phone (0PJA***). Compare that one with the MIDs that are mentioned in the first post of the ReadMe thread and you'll know which hardware variant you own. Just be aware that the engraving lacks two zeros if you compare it with the MID that you get from fastboot getvar. You should at least avoid trying to use a CDMA mainboard with a GSM phone or vice versa. I'm not sure whether you can use a US GSM mainboard with a European device or vice versa (c.f. the next paragraph).
Fortunately for me/unfortunately for you, I didn't have to replace any parts of my M9 or my older One S, yet. Therefore, I can't recommend any sellers because I don't have any experiences with them.
Sent from my HTC One M9 using XDA Labs

Need RUU for HTC 10

My phone is bricked,i know its old and people probably forgot about it but my issue is this.
I unlocked bootloader since i got it about 1 year ago and i was happy with rooted phone few custom app here and there,so i got bored with my phone (like all of us do :angel: ) so i decided to flash custom rom on it.
I flashed lineage os with TWRP and decided to revert to stock,so grab RUU and im set right? nope i was getting some errors here and there and read somewhere that i need to relock bootloader using command fastboot oem lock so i copied that command to my clipboard and my phone was in download mode with custom rom and custom recovery ready to be relocked,you probably know where this is going :silly:
So i decided wait a minute im certain that i need to revert to stock recovery and so on,i went online used keyboard shortcut Ctrl+C on adb reboot bootloader to reboot and enter recovery to backup and of course my damn C on keyboard didnt register so i pasted command fastboot oem lock on custom recovery and custom rom.
So phone is bricked it wont boot into rom or recovery but it is able to enter download mode and receive some command and i was like "DONT PANIC ALL IS WELL" and oh boy i was wrong.
I still have original unlock_code.bin and so i went to flash it to unlock phone and it tells me that i need to enable oem unlocking in settings and i cant get into rom phone just reboots after 2 seconds after powering on.
I was still like all is well yada yada and went to fing RUU and OMFG HTC 10 has bad support so my phone turns out to be:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: FA6B8BNxxxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) version-main: 3.18.166.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: VODAP110
Tried every single thing under the sun on google and nothing works,ruu exe is impossible to find,zip to flash boot and recovery give me security error.
Aparently there is site called firmware something something but i need to pay to get the file and all in all it seems to me like big scam so no avail but i was able to get file name and there it is:
2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_release_520816_combined_signed_2_4.zip(file RUU)
But searching on google and everything else im unable to find it to try to flash it as RUU in download mode.
So if any expert out there can give me some advice on what to do i would greatly appreciate it.
Is there some way to force boot on relocked phone with custom rom on it just to enable "Enable OEM Unlock"
Phone is in great condition no scratches at all new battery put in it half year ago holds 2 days easy,records 50 seconds 4k with 3% battery left without turning off,all in all best HTC phone ive ever had it would be shame to throw it away or sell for parts.
Sorry for any typos im in a hurry dont have a phone and im working so i hope to see some answers soon.
Thanks in advance...

Ive also tried to mod ruu zip to my version but im getting security error,i have one zip with swisscon CH-DE ruu that has my version 3.18.166.2 but is unable to flash it because security error and why is there no oreo RUU available,ive read somewhere that htc pulled oreo ruu because of battery drain and since im S-ON i cant flash lower number RUU i need same or newer is that true?
Does enyone have some source where i can download firmware mentioned in previous post?
There is a site called EasyFirmware that apparently has that file and i need to pay some download package,big problem is im in third world sh++hole and proces to get card for online payments is not worth this phone which can be found for around 100$ in great condition.
It would be a shame to sell it for parts or throw it away its a very nice phone.
Thanks in advance and please experts on XDA tell me is it possible or not so i can search for another phone.
New poster to xda wanted to add something and i wrote it in reason for edit uuuups.
If anyone needs some details about phone fell free to ask i will gladly provide it if it can help in fixing this mess ive made.

Just searched online seems like EasyFirmware is a hoax anyway so no avail there even if i wanted to pay.

https://firmware.gem-flash.com/
This site is legit. Carrier Branded ruu files are usually hard to find.
---------- Post added at 06:10 PM ---------- Previous post was at 06:10 PM ----------
https://firmware.gem-flash.com/
This site is legit. Carrier Branded ruu files are usually hard to find.

Mr Hofs said:
https://firmware.gem-flash.com/
This site is legit. Carrier Branded ruu files are usually hard to find.
---------- Post added at 06:10 PM ---------- Previous post was at 06:10 PM ----------
https://firmware.gem-flash.com/
This site is legit. Carrier Branded ruu files are usually hard to find.
Click to expand...
Click to collapse
Thanks for the answer and there is a few firmware zip files there but i still need to pay even for one download,it gives me like free 3GB download but all files are featured and i cant download without some premium packages,its not those 3$ that i dont have its that i dont have credit card to pay for it.
There are multiple versions tho what do you think which one would i need
[a]2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_release_520816_combined_signed.zip[a]---(with combined signed on the end or)
[a]2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_release_519830_signed_Hboot.zip[a]---(this one or)
[a]2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_release_519830_signed.zip[a]---(this one or)
[a]2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_release_519830_partial.zip[a]---(this one?)
Im afraid it wont flash,my system is 3.18.166.2 and can RUU put on zip with same version be flashed,will it give me error like when i try to downgrade?
How there is no RUU.exe for this phone for recovery in case of something like this,i always loved HTC for that if you mess up there is always RUU run flash and back to original state bit even for non carrier phones like unlocked there is no oreo RUU only nougat ones and since my phone is S-ON i cant dowgrade to nougat.
Is there some way to edit some files to force flash different carrier file or at least something.
It really seems dumb to me that BL unlock needs system toggle to unlock bootloader,unlocking it factory resets phone anyways so data wont be exposed in any case.
Is there some command or hack to toggle that or edit some file to unlock BL since i have original Unlock_code.bin but im unable to flash it.
Any help is appreciated and thanks so much for the answer.
Cheers

2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_rel ease_519830_signed.zip
That's the one you need. There is no RUU.exe and you don't need that as a ruu.exe is usually harder to use as you need more windows pc settings in order too. The zip is 100 times easier, just by renaming it and booting to download mode it will flash automatically. No need for fastboot settings and such on your computer.
A firmware is also different than a RUU.
- RUU = Rom Update Utility (this contains the BL and system)
- Firmware = The bootloader only (basically the BIOS of the phone)
HTC usually doesn't "release" carrier branded ruu files and carriers themselves also don't because in general they don't support tampering with your device. When it's stock you have the option to factory reset it or use warranty. When you decide to mod your device it's out of free will so doing some homework in advance is a wise thing. And no you can't just mess around with other carrier's ruu files to use them on your device, the ruu files that are out are all encrypted. If it was that easy there would not be so many topics about going back to stock !
And another tip : NEVER RELOCK A BOOTLOADER UNLESS THE DEVICE IS 100% STOCK
(in capital so others might read it too !). It's false info that you need to relock it for anything ! RUU files flash just fine with a UNLOCKED BL !
1 more thing, you CAN downgrade without S-OFF but it is not easy when you are not completely familiar with fastboot and how to use it properly, and you keep the issue that you need your carrier branded firmwares and ruu files.
https://forum.xda-developers.com/htc-10/how-to/downgrade-problems-downgrading-htc-10-t3735658

Thanks so much on the answer its very interesting and helpful.
So you think that there is still some hope?
It was dumb of me to relock that but my damn clipboard had that command in it and as i explained i thought i copied command fastboot reboot-recovery and i pasted oem lock and hit enter like and idiot it was late 3am.
Also how is that custom rom does not have oem unlock option turned on by default,rom installed is lineage OS.
Im somewhat familiar with fastboot so if i do something in it plz tell me and i will check out this thread that you posted for sure.
I have RUU exe for nougat but not for oreo and zips i have a folder with like 20GB of RUU there tried everything but im not doing this all the time so advanced stuff like you just said downgrade without S-OFF im not familiar with.
Thanks so much and i will try to see what i can do and if i fail to do anything i will let you know.
If you have some advanced stuff and methods feel free to post if you have time ofc i will do my best,cant brick it harder anyway :silly:
Cheers

Mr Hofs said:
2PS6IMG_PERFUME_UH[email protected]71204_84.09_F_rel ease_519830_signed.zip
That's the one you need. There is no RUU.exe and you don't need that as a ruu.exe is usually harder to use as you need more windows pc settings in order too. The zip is 100 times easier, just by renaming it and booting to download mode it will flash automatically. No need for fastboot settings and such on your computer.
A firmware is also different than a RUU.
- RUU = Rom Update Utility (this contains the BL and system)
- Firmware = The bootloader only (basically the BIOS of the phone)
HTC usually doesn't "release" carrier branded ruu files and carriers themselves also don't because in general they don't support tampering with your device. When it's stock you have the option to factory reset it or use warranty. When you decide to mod your device it's out of free will so doing some homework in advance is a wise thing. And no you can't just mess around with other carrier's ruu files to use them on your device, the ruu files that are out are all encrypted. If it was that easy there would not be so many topics about going back to stock !
And another tip : NEVER RELOCK A BOOTLOADER UNLESS THE DEVICE IS 100% STOCK
(in capital so others might read it too !). It's false info that you need to relock it for anything ! RUU files flash just fine with a UNLOCKED BL !
1 more thing, you CAN downgrade without S-OFF but it is not easy when you are not completely familiar with fastboot and how to use it properly, and you keep the issue that you need your carrier branded firmwares and ruu files.
https://forum.xda-developers.com/htc-10/how-to/downgrade-problems-downgrading-htc-10-t3735658
Click to expand...
Click to collapse
No progress at all.
Seems like now my only hope is for someone that has paid account for personal use on that site and can download file and somehow upload it for me to download on sites that are not paid.
If not for that i will order new board and change it my self since its like 30$ and i think its worth it for this phone.
Thanks for all the answers,if there is some suggestion feel free to post i will be happy to try it.
Cheers

I have found RUU.zip for this version its but cant flash it via fastboot it gives me error
target reported max download size of 1578400000 bytes
sending 'ruu' (264301 KB)...
OKAY [ 10.590s]
writing 'ruu'...
(bootloader) HOSD CL#1014340
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT ruu)
finished. total time: 11.600s
If i try it via SD card with name 2PS6IMG.zip it prompts me to flash and when i start the flash it gives me error like security fail.

I was typing fastboot flash ruu and got that error now i tried fastboot flash zip and i get this
target reported max download size of 1578400000 bytes
sending 'zip' (264301 KB)...
OKAY [ 10.825s]
writing 'zip'...
(bootloader) HOSD CL#1014340
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) get 36 images from zip(zip_type=3)
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: fail to flash zip: 8
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 16.106s
What does that mean?
Cheers

I can see error like partition name in android info.txt so i will attach it in this post.
Is there something to edit inside to force it to flash,if you think that i can brick it with some risky procedure i dont care i will try anything,look at me as a alfa tester for some crazy way of unlocking i will try anything.

It says it’s the wrong file, if you share the link of the file from where you found it and the name of the file i can check, now I just have to judge blindly if it’s the correct file or not but looking at all the errors it’s definitely the wrong one because when you have the correct signed RUU it will flash without a flaw with the Sd card method.

Mr Hofs said:
It says it’s the wrong file, if you share the link of the file from where you found it and the name of the file i can check, now I just have to judge blindly if it’s the correct file or not but looking at all the errors it’s definitely the wrong one because when you have the correct signed RUU it will flash without a flaw with the Sd card method.
Click to expand...
Click to collapse
Then it seems like i have a wrong RUU,in it says my model cid and everything but i think its some sort of modded and wont flash without S-OFF
So you think that firmware.gem is legit site?
I probably can find someone that has credit card and pay pal but plz if its fake dont let me chase down the rabbit hole if its fake.
Thanks and cheers

xxBeatsByDrDrexx said:
Then it seems like i have a wrong RUU,in it says my model cid and everything but i think its some sort of modded and wont flash without S-OFF
So you think that firmware.gem is legit site?
I probably can find someone that has credit card and pay pal but plz if its fake dont let me chase down the rabbit hole if its fake.
Thanks and cheers
Click to expand...
Click to collapse
Hence the question from where you got it from including the link so i could check !
I know for a fact the linked website is legit as i sent other users there too and never had any complaint about a non working RUU, and to be fair it’s probably the only option or toss it in the bin and get another phone

Mr Hofs said:
Hence the question from where you got it from including the link so i could check !
I know for a fact the linked website is legit as i sent other users there too and never had any complaint about a non working RUU, and to be fair it’s probably the only option or toss it in the bin and get another phone
Click to expand...
Click to collapse
Oke i will try to do credit card thing today and i will let you know.
As for this zip file i tried to flash i found it online but now on closer look it is 260MB or so and it says firmware only and probably is not signed.
So i need signed zip that you highlighted few posts ago.
I will try that in couple of hours and let you know.
Thanks man for everything i would have thrown it away if it wasnt for you.
Never used forum to post only to read.
xda experts like you saved my bacon many times.
Waiting for my colleague to come to work he has a card and i will download that signed file that you recommended.

I downloaded file signed like you said and i must wait to get home to try it but its 2.2GB and just in case i extracted andtoid info txt file and it goes like this
modelid: 2PS620000
cidnum: VODAP110
mainver: 3.18.166.2
aareport:1
btype:1
which matches my phone CID and MID so fingers crossed.
Will post results,and if it goes well i will let you know.
Cheers

It freaking worked.
My phone is back up and running and if someone needs this RUU file for CID VODAP110 and will gladly upload it just pm me.
Big thanks to Mr Hofs for helping me find solution and recommending site to download firmware from.
Thanks big time man you saved HTC 10 from going too garbage.
Cheers and i wish you good luck.

xxBeatsByDrDrexx said:
It freaking worked.
My phone is back up and running and if someone needs this RUU file for CID VODAP110 and will gladly upload it just pm me.
Big thanks to Mr Hofs for helping me find solution and recommending site to download firmware from.
Thanks big time man you saved HTC 10 from going too garbage.
Cheers and i wish you good luck.
Click to expand...
Click to collapse
That’s good news
Cheers