Develop Bugs

[Q] Can't update HBOOT no matter what?

Right. Let me try being as precise as possible. It's time to bid goodbye to my WFS so I need to get everything back in stock. As far as I remember the phone was locked to Vodafone and I've been using a goldcard throughout it's Xda life. The current HBOOT version is 1.08.0099, been HTCdev unlocked and as mentioned, I've been trying to get everything back in stock.
Although I run on a goldcard, I can never get a PG76IMG file to run via HBOOT (The main reason I'd like to try upgrading it in the first place?). It says wrong image error every time (Tried it on different files so can't be a file issue)(Also remade another goldcard and still remains the same).
An RUU exe file always ended up on an ERROR 190: Unknown error regardless of whether it was a Vodafone RUU or not. My only choice to flash a stock ROM was via fastboot and I did successfully flash the boot, recovery and system images on that method. HBOOT and Radio flash via fastboot ended up in a signature verification failure.
So I'd like to know if there's any way I could possibly update my HBOOT or even run an RUU exe or PG76IMG without an error?
PS. I also noticed that after flashing stock recovery, the recovery always ends up in a red triangle on the screen? I'd have to press Vol.up+ Vol.down+ Power to get it at the Android system recovery. Is this normal? Also says 'E:Can't open /cache/recovery/command' in yellow at the bottom of the same screen.

Hboot update
I recently updated by WFS hboot. First I had to unroot then relock the bootloader before applying the update as described in #4 of http://forum.xda-developers.com/showthread.php?p=22742315#post22742315
or http://forum.xda-developers.com/showpost.php?p=21231962&postcount=2
Then I had to unlock it via HTCdev and root it again.
Hope that helps

Thanks for that! Seem to have fixed it using the bootloader controller tool.
My question about the stock recovery going into the red triangle screen still remains though? As far as I remember, it did enter the Android system recovery directly after selecting recovery in bootloader mode?
EDIT: Just added pictures in order of what happens after selecting recovery. The 3rd screen comes in after I press Vol.Up+ Down+ Power at the 2nd screen. Can someone please confirm if that's how it's supposed to be in stock? (The last time I saw my phone stock was ages back! Sorry!)

Bump. Can someone please confirm if that's what stock recovery 'normally' looks like?

Yep, I believe that is stock mate.

intel007 said:
Yep, I believe that is stock mate.
Click to expand...
Click to collapse
Cheers mate. The red triangle bit made me wonder if I broke it!

???
can someone please explain me in simple language the fuss about the hboot thing?

[Q] Did some searches, spent more than four hours looking..

Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone

Valkalkas said:
Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Click to expand...
Click to collapse
haha... Love :victory:
Now back to issue.
If you're in the bootloader you don't need USB Debugging enabled, you can still use the fastboot command regardless of USB debugging mode. Check
Code:
fastboot devices
not
Code:
adb devices
.
Make sure all the drivers are still fine on the PC, reinstall if you must.
On a side note, try not to use all-in-one toolkits as you really don't get to learn from using something like that. If you did it manually you'd already have a pretty good understanding on which command gets used in which instance i.e bootloader vs in-system.

I actually didn't use a all-in-one this time around but as soon as I unlocked boot loader and rooted I had issues installing the custom rom. I've used both phil z and twrp but it still gets stuck when I install the sky dragon, or viper for that matter to test and make sure it wasn't just a bad download. Earlier when I did fast boot devices it did show something but now it's just a blank space. I'm in bed now I would double check again to make sure but like I said it's been a few hours and now it's 4:38 am and I'm tired. I'll double check in the morning but I appreciate your response and I'll double check. Drivers should be good from last time but I will double check and make sure. Again thanks for responding!

Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.

Valkalkas said:
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Click to expand...
Click to collapse
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device

ckpv5 said:
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
Click to expand...
Click to collapse
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.

Valkalkas said:
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Click to expand...
Click to collapse
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423

ckpv5 said:
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Alright, thank you for your help. I relocked and I tried the second link you posted, but the ruu messes up after I accept the EULA and just keeps popping up boxes. Downloading the RUU from the first link now and gonna try that. I just run the RUU in fastboot usb right?
Again thanks, I had no idea to check for hboot versions when rooting/flashing in the time I've rooted some devices so guess I'm learning something the hard way.
Edit: Same thing with the first link. I feel like I'm in the wrong place trying to run the RUU in fastboot usb?

Alright, tried running the RUU's again on the black screen with the silver HTC letters as suggested by someone else and the program still acts up after the EULA.

Alright, I was able to find a nandroid backup and restore it through there, so now I'm back in business. Thanks for the help!

HTCone M8 Not able to update firmware to 4.28.502.10

I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.

suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.

suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
You don't need to relock with s-off. Something else is going on. Post your getvar data (be sure to delete IMEI and serial number as these are personal info).

xunholyx said:
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.
Click to expand...
Click to collapse
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.

suzyq42 said:
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.
Click to expand...
Click to collapse
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.

suzyq42 said:
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.
Click to expand...
Click to collapse
As @redpoint73 said earlier, post your getvar. Hook up to your PC, get into ADB/fastboot and enter the command fastboot getvar all.
I was helping someone else with AT&T last night on the VenomROMs website, and mistakenly thought you were superCID when it was him. That won't be a problem though. It will abort with a CID mismatch.
The reason I suggested WWE firmware is that Marshmallow is coming out soon and WWE will get it way before AT&T updates.
If you want to stay on AT&T firmware, you could run the official RUU from HTC's US website.
Post your getvar, and we can go from there.

suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
OK here should be the final solution, when you are in fastboot/hboot screen you must enter "fastboot oem rebootRUU" then once you see the black screen with HTC logo then you may flash the firmware, you can not flash firmwares on PC while fastboot is actively running, but of course run the firmware flash command TWICE! first flash it will fail because HBOOT gets updated by it self, then on second flash the rest of the firmware files get updated.
If you have S-OFF then you never have to lock your bootloader again.

Help with installing AT&T Ruu

I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.

http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23

ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?

The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)

ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5

Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.

ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.

Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.

ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!

Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.

Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?

ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?

Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).

redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse

redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.

Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?

redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?

Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.

redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.

Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

[Q&A]Bricks, boot loops, and random shutdowns | Ask here | No new threads

This thread has been created for users who are experiencing a hard brick, soft brick, boot loop, or random shutdown on their HTC 10. Feel free to ask your question(s) here.
Going forward, new threads created regarding the topics listed above will be CLOSED by the moderating staff. Please remember to follow the XDA forum rules when posting.
Cheers,
Magnum_Enforcer
FSM

Well, I've pretty much managed to screw up my HTC 10. I'm on the latest 3.16.401.2 WWE, S-ON, with the bootloader relocked and stock recovery. I can access the download mode, the bootloader and the stock recovery, but I can't unlock the bootloader since I can't active the OEM unlock option. The phone doesn't boot, it's stuck in a bootloop at the white HTC logo.
Using the OTA available for WWE gives me the Status 7 fail error. Is there anything else I can do, besides from waiting for the Oreo WWE RUU?
Thanks in advance.

TheMadKing said:
Well, I've pretty much managed to screw up my HTC 10. I'm on the latest 3.16.401.2 WWE, S-ON, with the bootloader relocked and stock recovery. I can access the download mode, the bootloader and the stock recovery, but I can't unlock the bootloader since I can't active the OEM unlock option. The phone doesn't boot, it's stuck in a bootloop at the white HTC logo.
Using the OTA available for WWE gives me the Status 7 fail error. Is there anything else I can do, besides from waiting for the Oreo WWE RUU?
Thanks in advance.
Click to expand...
Click to collapse
I won't even ask how or why....
But yes you could S-off or wait for an RUU to magically appear.
Those are the two options.

santod040 said:
I won't even ask how or why....
But yes you could S-off or wait for an RUU to magically appear.
Those are the two options.
Click to expand...
Click to collapse
It's pretty complicated, but long story short, I was stupid.
I can't S-Off without being able to boot the phone, so well, I'll probably just wait for a RUU.

HTC 10 boot loop
Hello guys,
my wife yesterday tried to update OTA (our htc 10 are completely stock) to OREO from Nougat 2.41.401.41. Something went wrong and it's stuck in a boot loop. I can get in bootloader and tried to install the ota, which I downloaded, manually from SD card, but after verifying it says "error: partition has unexpected content". Is there a way to get the phone back working even with data loss? Thanks really for the help, the phone has never been modified, I am getting crazy reading the forums but I am a total noob ?

i have seen i need a ruu, possibly zip since I can't boot and activate USB debug. Can someone please share a run.zip link at least equal to 2.41.401.41 (European)? Thank you very much

I have the same issue, HTC 10 in a boot loop after applying the OTA Oreo update. I'm able to get into bootloaders and such, but i need the data thats on the phone... Allready tried taking out the SIM and SD-card. Does anyone know if this can be fixed?

Same problem here!
After Reading what the rest of you lot mentioned here, i have the exact same problems! Installed the update from Nougat to Oreo, and the phone went into bootloader! I was stupid enough to delete most of it through TWRP, and even dumber to RELOCK it so that TWRP is out of the Picture. Download mode appears, but the recovery just brings me back to bootloader. Oh yes, and the OS is missing.
and fastboot / adb wont recognize the HTC Connected to the PC anymore.. Guess this is a total Brick? should i send it back since i have a warranty? Will they be able to fix this?

I too was stupid and relocked it while reverting to stock. At this point I had also flashed the stock recovery and recovered to what turned out to be a non-functional backup. (Stuck in boot-loop)
Thankfully Fastboot did however still work while in download mode, and I was able to unlock it again by flashing the same unlock_token.bin that I have kept since I unlocked it the first time, slapped in twrp again and I was good for another go.

M8 can you help out linking some procedure for a noob like me? Should I use a ruu? I am completely stock

I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.
This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.

Thanks a lot for your help, I'll give you a feedback asap.

varg300 said:
I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.
This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.
Click to expand...
Click to collapse
Everything worked smoothly! Thank you so much!

Hi,
I have HTC_10, Unlocked, S-ON, J_15, 1.90.401.5
Had custom ROM nougat, later flash with stock MM firmware (EU 401), after my phone base-band and IMEI gone and no sim card now.
any help please ???

husnainrasheed said:
Hi,
I have HTC_10, Unlocked, S-ON, J_15, 1.90.401.5
Had custom ROM nougat, later flash with stock MM firmware (EU 401), after my phone base-band and IMEI gone and no sim card now.
any help please ???
Click to expand...
Click to collapse
Flash the ruu that is posted 1 post above yours.

IMEI not showing
Mr Hofs said:
Flash the ruu that is posted 1 post above yours.
Click to expand...
Click to collapse
Thanks for reply, I flashed with this RUU, Oreo update showing now but still no IMEI and Baseband..
Any solution to fix this IMEI or base band issue ??

husnainrasheed said:
Thanks for reply, I flashed with this RUU, Oreo update showing now but still no IMEI and Baseband..
Any solution to fix this IMEI or base band issue ??
Click to expand...
Click to collapse
Take the OTA. Did you flash a Oreo ROM while on nougat firmware? If so updating to Oreo will fix the problem.

Thanks Alot
yldlj said:
Take the OTA. Did you flash a Oreo ROM while on nougat firmware? If so updating to Oreo will fix the problem.
Click to expand...
Click to collapse
:good::good:
I updated to Oreo and now I am back on track.
everything is back to normal, IMEI and baseband as well working SIM.
thanks alot man ..
:good:

I have an Indian HTC 10 (SD 820) full stock, no modifications. One day the phone froze and i restarted it and from that day it hasn't booted up. The htc logo shows up while it vibrates, then again the same screen. Stuck in a bootloop. When i get to bootloader and boot to recovery, the grey htc logo comes for 1 second and then it goes back to the original boot animation and it loops again until the phone dies. Whenever i plug my phone to the charger, it immediately gets stuck into the boot loop. Please help me !! Any fix please !

budgati said:
I have an Indian HTC 10 (SD 820) full stock, no modifications. One day the phone froze and i restarted it and from that day it hasn't booted up. The htc logo shows up while it vibrates, then again the same screen. Stuck in a bootloop. When i get to bootloader and boot to recovery, the grey htc logo comes for 1 second and then it goes back to the original boot animation and it loops again until the phone dies. Whenever i plug my phone to the charger, it immediately gets stuck into the boot loop. Please help me !! Any fix please !
Click to expand...
Click to collapse
Hold the power button and the volume down button to reboot to download mode. From there you can flash an RUU.zip to fix it.
What is needed to direct you to the proper RUU.zip to download and flash is for you to boot to download mode and post here what it says next to "OS"