Develop Bugs

My DHD stuck on htc logo

hi I tried to install IceColdSandwich-1.2.0 Rom on my DHD but after i did it my device stuck on htc logo and never boot the problem is i am new in this stuff and i can't get my device back to life i 'v downloaded the ice cream sandwich using
clock work mode and my Hboot screen shows:
****UNLOCKED*****
ACE PVT S-on RL
Hboot -2.00.0029
MICROP-0438
Radio-26.14.04.28_M
eMMc-boot
Dec 22 2011,14:28:19
and i don't know what Ruu to install
please help and thx

Your phone isn't rooted. How did you manage to flash recovery onto it in first place?
Search for advanced ace hack kit on xda. Read a LOT about how to use it and once ready, let the kit do its thing. After that you'll be S OFF and able to flash any custom ROM.
Sent from my HTC Desire HD with Beats Audio using XDA App

He unlocked it using the official HTC dev tool. It allows you to flash a custom recovery.
This is an obligatory to the op. Please research before you go and do stuff to your phone. I just don't get how someone will take a risk on there phones.
The reason it didn't boot is because you have to flash the boot image seperately. One simply can't just flash a rom, in cwr and call it a day if you did it using HTC tool.
What you need to do is. Boot back.into hboot select fastboot.
Take the boot image from your rom and place in your folder where fastboot and adb are located.
Then run the command
Fastboot flash boot boot.Img
Fastboot reboot

Its not working
marsdta said:
He unlocked it using the official HTC dev tool. It allows you to flash a custom recovery.
This is an obligatory to the op. Please research before you go and do stuff to your phone. I just don't get how someone will take a risk on there phones.
The reason it didn't boot is because you have to flash the boot image seperately. One simply can't just flash a rom, in cwr and call it a day if you did it using HTC tool.
What you need to do is. Boot back.into hboot select fastboot.
Take the boot image from your rom and place in your folder where fastboot and adb are located.
Then run the command
Fastboot flash boot boot.Img
Fastboot reboot
Click to expand...
Click to collapse
yeah you are right I used htc dev to unlock my DHD but I tried to took boot.img from the Ice cream sandwich Rom and it did not workout with me please if you know any way help me
and thx for your reply

AAHK
This is the AAHK (Advanced Ace Hack Kit) thread.
It is ONE click Root, S-Off & SIM unlock kit.
Read carefully, go step-by-step and than you'll be ready to go.
This is how I unlocked and unleashed my beast

ordevski said:
This is the AAHK (Advanced Ace Hack Kit) thread.
It is ONE click Root, S-Off & SIM unlock kit.
Read carefully, go step-by-step and than you'll be ready to go.
This is how I unlocked and unleashed my beast
Click to expand...
Click to collapse
thanks but i only can access to Hboot menu and i can enter the clock work mode but the AAHK doesn't workout with me

Run a fitting RUU, relock your Bootloader and use AAHK afterwards.
(if you would have taken some time to get into this stuff, you wouldn't be messed up right now "Official HTC Unlock" is not that brilliant compared to AAHK ).
You say you don't know which RUU to use.
Where did you buy your phone? Was/Is it branded?
DN41

DN41 said:
Run a fitting RUU, relock your Bootloader and use AAHK afterwards.
(if you would have taken some time to get into this stuff, you wouldn't be messed up right now "Official HTC Unlock" is not that brilliant compared to AAHK ).
You say you don't know which RUU to use.
Where did you buy your phone? Was/Is it branded?
DN41
Click to expand...
Click to collapse
no my phone isn't branded and the version of my android was 2.3.5 , HTc sense 3.0 software number 3.13.415.2
and AAHK need downgrade to workout with me so I gave it a chance but every thing went wrong
thx for your help anyway

Try one of those, i think the latest should be fine.
[ROM]Ace Test & Stock ROMS [RE-UPLOADED]
DN41

ok i will thank you but do you know error "155" and how to solve it and if Ruu works with s-on or not and thx again

When do you get this 155-error?
If using a fitting RUU, it will always work afaik But I'm pretty sure.
DN41

DN41 said:
When do you get this 155-error?
If using a fitting RUU, it will always work afaik But I'm pretty sure.
DN41
Click to expand...
Click to collapse
I didn't really know what you meant by afaik
I tried alot of RUU but they all keeps popup with error 155 and i don't know how to fix it and i don't know how to fix this problem but i really need to work it out and thx for all of you

"As far as I know"
Did you try flashing it in fastboot mode?
Get your device into bootloader and choose fastboot. Try to run the RUU again.
DN41
Sent from my DHD @ ARHD 6.3.1

i did but its always error 155 comes up i don't know what to do but i really need my DHD back

Ok, another idea:
You have that stock RUU fitting your phone?
Open explorer here: C:\Users\"YOUR USERNAME"\Appdata\Local\Temp\
Then Run the RUU, it will extract the files to some folder in here, you will see it pop up when opening the RUU (or you run it and simply use search).
Inside there'll be a "rom.zip".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rename it to PD98IMG.zip, push it to your SD card (in root, not into a folder) and boot your phone into bootloader.
It should check the file and then you have to select "yes" to flash it. Should be fine after it.
DN41

thx I tried to do this before but it keeps tell wrong Image

So you're a hundred percent sure, that you've got a fitting image? Cant believe that it would block a fitting image that method.
Which version did you try? Most recent one?
And BTW: would be great it you would tell before what you already tried instead of letting me explain it and then say "oh i already did that"
DN41
EDIT: I guess it doesnt take the Rom because of the high hboot version (yours is somewhere around 2, "normal" ones around 0.84). Maybe it would be the best to contact HTC's Support regarding that you used their official unlock instead of AAHK.
Sent from my DHD @ ARHD 6.3.1

Just root it using the ace hack kit..might ne worthwhile?
Sent from my Desire HD using XDA Premium App

DN41 said:
So you're a hundred percent sure, that you've got a fitting image? Cant believe that it would block a fitting image that method.
Which version did you try? Most recent one?
And BTW: would be great it you would tell before what you already tried instead of letting me explain it and then say "oh i already did that"
DN41
EDIT: I guess it doesnt take the Rom because of the high hboot version (yours is somewhere around 2, "normal" ones around 0.84). Maybe it would be the best to contact HTC's Support regarding that you used their official unlock instead of AAHK.
Sent from my DHD @ ARHD 6.3.1
Click to expand...
Click to collapse
I am sorry i didn't tell but I really need my phone back so I am trying every idea comes to my mind and I tried a lot of versions but no one works
thx again for your help

Flashed custom ROM but SIM stopped working

Ok so I posted in another thread where I was trying to flash a custom but a few things went wrong but help has been slow there so I thought it may be better to post here.
I got MM through OTA updates, this was when my M9 was bootloader LOCKED, not custom recovery, everything stock. After I was on MM for a few days I used htcdev.com to unlock the bootloader, then I got TWRP 3.0.0 and then I got SuperSU 2.65 and installed it through TWRP. Before installing SuperSU I made a backup through TWRP of Boot, System and Data. I copied this backup to my computer as well. At this point this is the current information on the M9 (Look at 3 attached screenshots as well):
kernel: lk
product: htc_himaulatt
version: 1.0
version-main: 3.38.1500.2
boot-mode: download
version-baseband: 01.01_U11440801_96.01.51207G_F
version-bootloader: 1.0.0.0000
mid: 0PJA11000
cid: GLOBA001
So after creating the backup, I installed SuperSU 2.65, then booted up the phone, everythings fine. So I went back to TWRP and installed Android Revolution HD 20.0 (had it on an sd card) and used the wipe data option it gives before installing. So after a long time of optimizing apps the phone boots up and starts the setup. I got to entering google account information and it asked for 2 step verification which sends a code to my phone number, but I then noticed I had no signal and it said No Service so I couldn't sign in to Google and had to skip that. After the rest of the setup I popped out the SIM and put it back, still nothing (keep in mind the SIM is locked with a pin if that affects anything, but it never even asked for the pin).
Now I go to Accounts and try adding my google account but the phone gets stuck at checking info... and while i can use the rest of the phone there is no way for me to sign into any google account now because every attempt results in checking info loop. I tried to reboot the phone multiple times but that did nothing. Last thing to note is that when i went to Settings -> About, there was no IMEI number as well as other information about the phone was missing so something went wrong for sure.
After that I restored from the TWRP backup and its back to normal, SIM working, Google acc working, all that is good like it was before. So any suggestions on how to get ARHD 20 now? I noticed that since I'm on 3.38.1500.2 which is higher than the firmware that ARHD uses, maybe that is the problem since I'm essentially downgrading the firmware right? I read that you can't downgrade firmware unless you are S-off but my M9 is S-on. All help is appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Instead of twrp 3, use 2.9.0.1 and then flash supersu 2.65.
The problem lies with twrp. Supersu has its own issues so only 2.65!
ONLY TWRP 2.9.0.1 AND SUPERSU 2.65 FOR MM HTC M9! YOU WILL ENCOUNTER ISSUES OTHERWISE!
S-off is worth paying for too.
Sent from my HTC One M9 using Tapatalk

shivadow said:
Instead of twrp 3, use 2.9.0.1 and then flash supersu 2.65.
The problem lies with twrp. Supersu has its own issues so only 2.65!
ONLY TWRP 2.9.0.1 AND SUPERSU 2.65 FOR MM HTC M9! YOU WILL ENCOUNTER ISSUES OTHERWISE!
S-off is worth paying for too.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yea SuperSU 2.65 I understand but I heard 2.9.1.2 is quite stable? You don't agree?

Not tried it. I just flashed 2.9.0.1 and stuck with it because it boots. Beggars can't be choosers and a working phone is better than a broken one.
Sent from my HTC One M9 using Tapatalk

Just wanna update my situation as it is resolved and the solution: S-OFF
I was on 3.38 with twrp 3.0 and SuperSU 2.65 and flashing ARHD 20.0 (which is on 3.35) was messed up as my SIM card wasn't working and signing into Google account was not working.
I restored my nandroid backup, installed SuperSU 2.65 again and then bought S-OFF, which allowed me to change my cid to HTC__001 and mid to 0PJA10000. Next i flashed a nandroid that someone uploaded of 3.35.401.12 and once that was done I flashed ARHD 20.0 and boom its done. Basically from what I understand you can't flash ARHD 20.0 if the firmware you are on is lower (i failed to go from 3.38 to 3.35). Also my SKU was 1500 but ARHD is 401 so that might be a factor as well. So yea S-OFF is great

Future Note.
Always try to stick with the general update the ROM is based off of. The System partition in STOCK/CUSTOM roms have a firmware folder that have drivers and config files that are meant to be used with the firmware.zip originally in that update.
For example (not real sw numbers)
HTC releases an official update 3.40.1540.1
3.40.XXXX.X is generally the base while X.XX.1540.1 is any software mods made by carriers or specific region teams. Firmware Updates (Radio Baseband, TouchScreen Driver, etc) are released along side the actual Android/HTC software. These official ROMS have config files that are design around this new firmware. When developers here on XDA make custom roms they are in a weird XDA way a carrier (3.40.ARHD.1 etc). They modify the HTC rom and make it their own, but their roms are still based off that firmware update.
So if you start using a custom rom based off 3.40, but the last firmware your phone installed is 3.10. You will run into issues and they might be small (less battery life or cell signal) or pretty big. Your sim not working, or wifi, or any number of issues. Stick to ROMS based off the firmware you have on your phone. Or if youre S-OFF and want to take that ever present risk. Update your firmware to that newer version.

Can you go into a little more detail? I am S-off and unlocked. I upgraded to the latest Tmobile MM and then flashed ARHD and got the sim error/no signal. you changed your CID and MID? where did you get the MM nandroid from?

ig88b1 said:
Can you go into a little more detail? I am S-off and unlocked. I upgraded to the latest Tmobile MM and then flashed ARHD and got the sim error/no signal. you changed your CID and MID? where did you get the MM nandroid from?
Click to expand...
Click to collapse
Yea if you go to settings -> about -> software information it should say your firmware version. If your version is NOT 3.35 you'll get this problem, here are the nandroid files, you only need the 3.35 one but if I understand correctly restoring from this nandroid might make you lose all data. https://www.androidfilehost.com/?w=files&flid=48820
ALSO that nandroid is for 401 SKU which is HTC WWE, so if you're locked to tmobile i dont know how that'll affect you so dont just restore to that nandroid.
And yea i changed my CID and MID : (idk if you know but you need extra files on your pc to run the following commands from pc)
fastboot oem writecid HTC__001
fastboot oem writemid 0PJA10000
fastboot reboot
I did this right before the nandroid restore and everything turned out fine.

Awesome man thanks so much! that nandroid took care of it, couldn't find one.

ig88b1 said:
Awesome man thanks so much! that nandroid took care of it, couldn't find one.
Click to expand...
Click to collapse
Glad I could help

[SOLVED]Friend messed up his phone-gave it to me to fix-seems to be stuck in fastboot

Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.

eboy_gb said:
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.

Kyuubi10 said:
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Click to expand...
Click to collapse
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....

eboy_gb said:
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
If you can access TWRP the download a nandroid of stock, and follow the advice I already gave above.
Flash stock nandroid 4.25/4.20, from TWRP, then from fastboot flash stock recovery.
Reboot and wait for OTA updates.

All is well, got the running properly now - thanks everyone!

eboy_gb said:
All is well, got the running properly now - thanks everyone!
Click to expand...
Click to collapse
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems

Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.

xunholyx said:
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
Click to expand...
Click to collapse
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Sent from my htc_m8 using XDA Labs

Kyuubi10 said:
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Click to expand...
Click to collapse
Corrupting system won't affect the OS number on the bootloader screen. "OS" is a bit misleading, it actually indicates the firmware number, not the ROM version.
The bug is easily reproduced by flashing certain TWRP versions (not sure exactly which ones). Its very common. We see this pop up by folks almost on a daily basis (OS number blank) especially folks using older TWRP versions.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Kyuubi10 said:
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Click to expand...
Click to collapse
Additionally, its not clear whether your suggestion is what actually worked for him (and exactly what nandroid build, etc.). OP should post the solution that worked, 1) for benefit of "helpers" like you, to confirm your fix is what worked; and 2) for the benefit of others that may run into the same issue.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
The phone would not boot since the bootloader was relocked. This is what happens when you relock by definition, as relocking expects RUU to be run.
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
eboy_gb said:
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
RUU existing for the Desire Z (I had the same phone); and in fact for as long as HTC has been making Android devices.
RUU = ROM Update Utility
Its usually a Windows executable (although the zip format can be extracted to work with fastboot flash, or put right on an SD card) that will completely re-image the phone to stock firmware and software. You need to run the RUU that matches the phones carrier version (CID) and model (MID), and not all versions have RUU. Otherwise, the RUU will fail and not install anything.
RUU also requires a locked or relocked bootloader (although this requirement is bypassed with s-off).
RUU will also wipe any user data on the phone (including internal storage "media").

htc m8s stock in bootloader, no ruu mode, no twrp possible, os 1.21.111.1

hello to all friends of XDA.
im not new but i lost my old email. :silly:
i have a htc one m8s thats stuck in bootloader with os version 1.21.111.1 from T-mobile DE.
the problem is that i try to flash the unlock token, flashing the file, i select accept on the screen phone but when the phone restarts the booloader is still locked.
i try to flash a stock recovery (not the same as the os version, because i didnt find it) but it still doesnt work.
i try ti find the last ruu or stock rom version 1.21.111.1 or even the firmware but i didnt find it.
however when i try to boot to RUU mode it doesnt reboot in RUU mode.
i try every steep with the new htc_fastboot. but i dont use the md5 verification or any md5 file (because i dont know how)
i would like to have the phone working even with Lineage os or something like.
please if someone can help me please let me know the steeps.
best regards to all and thanks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

htc one m8 , i see on twrp says All variants , gsm i think also SO this means any htc m8 will take twrp right ?? any model or carrier ect ??
wanna buy this phone only if twrp good to go and root

Htc one m8s
Joeykatie said:
htc one m8 , i see on twrp says All variants , gsm i think also SO this means any htc m8 will take twrp right ?? any model or carrier ect ??
Htc one m8s is not the same as m8 you cant apply this version of twrp , just dl and flash it in the thread below, and then flash supersu and you will get root and twrp
https://forum.xda-developers.com/ht...ral/make-custom-recovery-htc-one-m8s-t3114245
Click to expand...
Click to collapse

I think I can help
klevisi said:
hello to all friends of XDA.
im not new but i lost my old email. :silly:
i have a htc one m8s thats stuck in bootloader with os version 1.21.111.1 from T-mobile DE.
the problem is that i try to flash the unlock token, flashing the file, i select accept on the screen phone but when the phone restarts the booloader is still locked.
i try to flash a stock recovery (not the same as the os version, because i didnt find it) but it still doesnt work.
i try ti find the last ruu or stock rom version 1.21.111.1 or even the firmware but i didnt find it.
however when i try to boot to RUU mode it doesnt reboot in RUU mode.
i try every steep with the new htc_fastboot. but i dont use the md5 verification or any md5 file (because i dont know how)
i would like to have the phone working even with Lineage os or something like.
please if someone can help me please let me know the steeps.
best regards to all and thanks in advance
Click to expand...
Click to collapse
Did you get the phone in a locked, or unlocked state?
If locked, did you use Sunshine or a HTC unlock (the former option costs $$ and I would't recommend fabricated keys as they can break the device).
T-Mobile DE - a german version of the phone, or US version with German settings?
To reboot in RUU, you'll need to do so through ADB, while connected to a computer.
In order to run RUU, you actually have to re-lock the bootloader if it's unlocked. You also need to disable SuperCID, if it is enabled.
Do you have any more details? I was going to suggest a website that @graffixnyc used to keep updates on, but I don't see the list of files there anymore.
I bought mine three years ago and I feel bad that your outcome is like this.

furboom1240 said:
Did you get the phone in a locked, or unlocked state?
If locked, did you use Sunshine or a HTC unlock (the former option costs $$ and I would't recommend fabricated keys as they can break the device).
T-Mobile DE - a german version of the phone, or US version with German settings?
To reboot in RUU, you'll need to do so through ADB, while connected to a computer.
In order to run RUU, you actually have to re-lock the bootloader if it's unlocked. You also need to disable SuperCID, if it is enabled.
Do you have any more details? I was going to suggest a website that @graffixnyc used to keep updates on, but I don't see the list of files there anymore.
I bought mine three years ago and I feel bad that your outcome is like this.
Click to expand...
Click to collapse
The files are still there, they are just under Development Portfolio -> XDA Development Work -> Rom Development. http://graffixnyc.com/m8.php

HTC 10 Bricked? Bootloop. Don't know what else to do.

So, my GF's HTC10 was rooted and whatnot, mainly cause she wanted to get rid of certain bloatware HTC apps that kept spamming.
After a while she kept getting update notices from HTC which she couldn't install, and more recently her batterydrain went through the roof.
We decided to return the phone to stock.
Enter the problems.
For her phone (CID: HTC_034, S-ON) I couldn't find a RUU exe.
So I went and tried the TWRP backup restore.
It restored, and rebooted, and from there on out was stuck in a bootloop.
I then tried to install the only RUU stock zipfile I could find (1.90.401.5) by renaming it and placing it on the root of the SD-Card.
Enter Download mode -> Get promped to flash -> Get error: ru_main_ver_fail os-version in android-info missing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Picture: The error message when trying to flash Stock from Download Mode)
When in download mode it says: OS-2.41.401.41
So it seems there is a newer version of android on there, and I can't flash the Stock ROM because of the S-ON.
(Picture: All the info on the Download Mode Screen)
And for whatever weird reason I can't boot into Recoverymode (TWRP) either anymore.
Any help, tips, thoughts and prayers?
At this point I'm at a loss and don't know what to do anymore.
In 8 years of flashing custom and stock roms, rooting and unrooting I haven't bricked a single phone, and I'm kinda afraid I did now, not knowing how to fix it and if it's fixeable at all :x

darkfreak said:
So, my GF's HTC10 was rooted and whatnot, mainly cause she wanted to get rid of certain bloatware HTC apps that kept spamming.
After a while she kept getting update notices from HTC which she couldn't install, and more recently her batterydrain went through the roof.
We decided to return the phone to stock.
Enter the problems.
For her phone (CID: HTC_034, S-ON) I couldn't find a RUU exe.
So I went and tried the TWRP backup restore.
It restored, and rebooted, and from there on out was stuck in a bootloop.
I then tried to install the only RUU stock zipfile I could find (1.90.401.5) by renaming it and placing it on the root of the SD-Card.
Enter Download mode -> Get promped to flash -> Get error: ru_main_ver_fail os-version in android-info missing
(Picture: The error message when trying to flash Stock from Download Mode)
When in download mode it says: OS-2.41.401.41
So it seems there is a newer version of android on there, and I can't flash the Stock ROM because of the S-ON.
(Picture: All the info on the Download Mode Screen)
And for whatever weird reason I can't boot into Recoverymode (TWRP) either anymore.
Any help, tips, thoughts and prayers?
At this point I'm at a loss and don't know what to do anymore.
In 8 years of flashing custom and stock roms, rooting and unrooting I haven't bricked a single phone, and I'm kinda afraid I did now, not knowing how to fix it and if it's fixeable at all :x
Click to expand...
Click to collapse
You can't use that 1.90 RUU because it's a downgrade from your current version and you're S-on.
Try this one, it's the same version you currently have:
https://androidfilehost.com/?fid=817550096634797504
Rename it exactly to 2PS6IMG.zip, place in the root of your sd card and boot to download mode. It'll prompt you to flash it if done right

Tarima said:
You can't use that 1.90 RUU because it's a downgrade from your current version and you're S-on.
Try this one, it's the same version you currently have:
https://androidfilehost.com/?fid=817550096634797504
Rename it exactly to 2PS6IMG.zip, place in the root of your sd card and boot to download mode. It'll prompt you to flash it if done right
Click to expand...
Click to collapse
Thanks for the link (I wasn't able to find any official RUU except the 1.90 one, though I clearly didn't look well enough /shame).
However: Androidfilehost keeps giving me "No mirrors found" when I'm trying to download the RUU ?

Maybe these will work
https://forum.xda-developers.com/htc-10/how-to/htc-10-official-nougat-2-41-401-4-ruu-t3554624/page7

Mr Hofs said:
Maybe these will work
https://forum.xda-developers.com/htc-10/how-to/htc-10-official-nougat-2-41-401-4-ruu-t3554624/page7
Click to expand...
Click to collapse
Older version that what's currently on the phone, so won't work is my guess

darkfreak said:
Older version that what's currently on the phone, so won't work is my guess
Click to expand...
Click to collapse
I should try them. The last digits are only software updates and no firmware update.
So 2.41.401.4 or .3 will probably just work fine. Just try.....it won't hurt

Mr Hofs said:
I should try them. The last digits are only software updates and no firmware update.
So 2.41.401.4 or .3 will probably just work fine. Just try.....it won't hurt
Click to expand...
Click to collapse
Was gonna do that, but getting the same "No mirrors" message from Androidfilehost =/

darkfreak said:
Was gonna do that, but getting the same "No mirrors" message from Androidfilehost =/
Click to expand...
Click to collapse
That's strange because the one in the OP isn't even uploaded to Android file host.......

Mr Hofs said:
That's strange because the one in the OP isn't even uploaded to Android file host.......
Click to expand...
Click to collapse
The one in OP from your link is the RUU exe, that one appears to download fine.
Gonna check if it works, though I cant get ADB to work anymore, for whatever reason, so not sure if the exe works, then.

Mr Hofs said:
That's strange because the one in the OP isn't even uploaded to Android file host.......
Click to expand...
Click to collapse
Houston, we have lift off!
The RUU exe did the trick.
But not untill after I uninstalled HTC Sync and deleted the drivers, and re-installed HTC sync (with drivers).
Still many thanks to providing the link with the proper RUU exe!

darkfreak said:
So, my GF's HTC10 was rooted and whatnot, mainly cause she wanted to get rid of certain bloatware HTC apps that kept spamming.
After a while she kept getting update notices from HTC which she couldn't install, and more recently her batterydrain went through the roof.
We decided to return the phone to stock.
Enter the problems.
For her phone (CID: HTC_034, S-ON) I couldn't find a RUU exe.
So I went and tried the TWRP backup restore.
It restored, and rebooted, and from there on out was stuck in a bootloop.
I then tried to install the only RUU stock zipfile I could find (1.90.401.5) by renaming it and placing it on the root of the SD-Card.
Enter Download mode -> Get promped to flash -> Get error: ru_main_ver_fail os-version in android-info missing
(Picture: The error message when trying to flash Stock from Download Mode)
When in download mode it says: OS-2.41.401.41
So it seems there is a newer version of android on there, and I can't flash the Stock ROM because of the S-ON.
(Picture: All the info on the Download Mode Screen)
And for whatever weird reason I can't boot into Recoverymode (TWRP) either anymore.
Any help, tips, thoughts and prayers?
At this point I'm at a loss and don't know what to do anymore.
In 8 years of flashing custom and stock roms, rooting and unrooting I haven't bricked a single phone, and I'm kinda afraid I did now, not knowing how to fix it and if it's fixeable at all :x
Click to expand...
Click to collapse
So, whatever firmware version you are on, run an official RUU.exe from HTC. I seem to be the only one who has this problem with flashing RUUs, but everytime I try. The screen never shows up after the unpacking process. Well, turns out you need to download some runtimes. Get the latest version of .NET, and get ms vc++ 2015 redistrtubutable. I dont run windows, I have it but only for things like that. Or if I have to run odin on a device. Good luck. OH - After u run an offical RUU.exe and are able to boot up and everything.. Before u go changing ROMS and ****, get sunshine and s-off. Trust me, its worth the money.