Develop Bugs

[Q] unroot hox for warranty

i'm one of the lucky guys with 3 failures at his phone at the same time:
1. yellow spot
2. wifi/bluetooth
3. flickering screen when grey
so i need to return my phone for a fix but it's rooted. At first followed more guides here. very usefull but i can't find my right RUU!
The phone was bought in the netherlands but it came with a Orange UK [branded] rom.
from the WIKI said:
Total recovery - flashing a RUU to completely restore your phone
If all else fails, this is your last resort.
This process will erase all your data, INCLUDING potentially your /sdcard partition (phone storage). But hey, beats having a dead phone, right?
First, ensure you have enough battery (more than 30%) to run an RUU.
Next, boot your phone into fastboot bootloader and open a command prompt window on your computer in the platform-tools folder.
Use the command:
fastboot getvar version-main
You now need to find the RUU that corresponds to this version. Start here. If you have problems visit #htc-one-x on freenode.
Now you must re-lock the bootloader using:
fastboot oem lock
It won't hurt to use the clear cache command as well
fastboot erase cache
Finally, run the RUU.exe that you have downloaded (must be used in Windows, and requires HTC drivers, which will have been installed whilst using HTCDev to unlock your phone).
This will write the /recovery, /boot, and /system to stock. You will need to start from scratch to unlock.
Click to expand...
Click to collapse
when i type getvar version-main i get: 1.28.061.9 but i can't find the rom anywhere on the internet.
can somebody help me to get a RUU that works on my phone? or a guide so i can run another RUU that will work.
[sorry for my english, not my native language]

Even if you run RUU, HTC will still be able to see that your bootloader has been unlocked.
Relocking your bootloader using fastboot oem lock will only relock it, not undone the original unlock.

shrubz said:
Even if you run RUU, HTC will still be able to see that your bootloader has been unlocked.
Relocking your bootloader using fastboot oem lock will only relock it, not undone the original unlock.
Click to expand...
Click to collapse
Yes, but this is a hardware issue, that has nothing to do with the ROMs and stuf.. I believe you can claim warranty. If not, fight with them, as this SHOULD be covered, as its not covered under warranty.
If you cant find the RUU, ask awesome devs like mike1986 for help, he might be able to help.

Lazy-eye said:
i'm one of the lucky guys with 3 failures at his phone at the same time:
1. yellow spot
2. wifi/bluetooth
3. flickering screen when grey
so i need to return my phone for a fix but it's rooted. At first followed more guides here. very usefull but i can't find my right RUU!
The phone was bought in the netherlands but it came with a Orange UK [branded] rom.
when i type getvar version-main i get: 1.28.061.9 but i can't find the rom anywhere on the internet.
can somebody help me to get a RUU that works on my phone? or a guide so i can run another RUU that will work.
[sorry for my english, not my native language]
Click to expand...
Click to collapse
HTC will honor any hardware issues providing you take the following steps prior to sending it back.
1: Relock your bootloader (fastboot oem lock)
2: Run the Orange UK RUU (http://www.filefactory.com/file/qwm...Radio_1.1204.103.14_release_256475_signed.exe)
3: When booking in the device for repair don't mention that you have unlocked. Let them figure it out for themselves and if they have an issue with it they will contact you.

ive tried the uk RUU but is was a different 1.26 version. after a few hours trying i got it worked by extracting the ruu and manually flash system.img and boot_signed.img from the quide of http://forum.xda-developers.com/showpost.php?p=25080910&postcount=1
tomorrow it will be send to HTC but i didnt mention the unlocked bootloader. my opinion is also that is is a hardware issue that was recognized by HTC.. hoping that the reapir company wont take a good look.

i send my phone for repair because right top corner was creaking when i pressed it. and i have custom rom on it. so i relocked bootloader, flashed original ruu and send it for repair. aftera freaking ONE MONTH of waiting i got my phone, they replace bazel(as I understood it was all back, phone corpus). on the warranty card they wrote, "bootloader unlocked, only mechanical issues can be repaired under warranty." So I think that all of us who have any problem with HARDWARE should send phone and get what they worth for such many $. Am I right? But this is not the end. After 4days(it's today) I saw that frame which is around the glass, from the right side is broken, and left side where is usb charging is creaking when i press it. So tomorrow my phone is going back for repair. And from 1.5 month I used it only 14days, i think this phone is not lucky. But i will fight till i get phone what i payed for.
ps. sorry for my english.

Well you don't exactly have software problems so relocking should not br an ossue as stated
Typed with XDA Premium on OneX

HELP PLEASE! (brick)

Hi, I have been the happy owner of an international HTC One X for just over a month now. I'm from Australia and my carrier is Vodafone.I have been using the Lee-Droid One Xtreme Rom without issue for almost the entire time I've owned the phone, however two days ago some huge issues appeared.
First the handset resest itself, this had happened before but this time it was stuck on the "HTC Quietly Brilliant" splash screen. I tried to wipe the cache from recovery but recovery wouldn't boot. I plugged the phone into my laptop and used "fastboot erase cache" which seemed to work but did not solve my problem, still hanging at the splash screen.
I then noticed that my bootloader had somehow locked itself again so I flashed my Unlock_code.bin again, the handset displayed the usual prompts which I followed but when my phone reset I was greeted with the now familiar hanging bootsplash plus a warning about the ROM being for internal HTC use only.
I also noticed this message in my terminal:
FAILED (status read failed (Cannot send after transport endpoint shutdown))
Can someone please help me here? I'm hesitant to send the phone away because I unocked the bootloader via htcdev.com so my warranty is invalid most likely.
Thanks for your time and sorry if this is a duplicate thread, I had done a few searches already and found nothing that spunded like my problem though.

Did your bootloader say locked or relocked
Sent from my HTC One X using Tapatalk 2

Did u flash de cwm last recovery? There are some problems with usb, try to use another One, install drivers, restart pc.
Htc One X Venom ViperX Rom & Show-p Kernel

@KrisPerry - the bootloader says either :
***LOCKED***
or
***LOCKED***
***SECURITY WARNING***
@drangonesdenano
last recovery I flashed CWM 5.8.4.0
have tried restarting pc, no change.
i use linux so there are no drivers to reinstall.
none of the cables i have fit, but this is the original htc cable, it seems to be in decent condition, i'll try and see if i can borrow one from a friend though.
sorry for taking a while to reply to you guys, i've been having login troubles with the xda site. thankyou for your help thusfar. any ideas?

Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel

dragonesdenano said:
Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel
Click to expand...
Click to collapse
hi, sorry for taking so long to reply, i have been having some major troubles with both my computer and then getting enough charge into the phone. i ended up writing this script:
Code:
#!/bin/sh
while true
do
./fastboot getvar battery-voltage
./fastboot reboot-bootloader
sleep 10
done
writing from a different pc with a fresh linux mint install i've tried unlocking the bootloader again but this time i'm getting this from the terminal:
Code:
./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
finished. total time: 9.179s
what do you think? i bought a second usb cable and have been switching between the two but it makes no difference... i can't flash recovery because the bootloader is locked and i seem to be stuck in a bootloop so i can't boot into CWM either.
i've been reading about people flashing RUU's, is that what i need to do?

Just a gentle bump on this thread, I've been without a phone for over a week now and it's getting pretty annoying (first world problems). Has anyone seen this before? What should I do? Any help would be greatly appreciated.
Cheers, Toby.

RUUs
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.

Free bump...
Sent from my HTC One X using xda premium

TobyJamesJoy said:
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.
Click to expand...
Click to collapse
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.

Update
whynot66 said:
Free bump...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks man!
So I've set out on a mission and made a Virtualbox Windows XP install, installed the sdk and HTC sync, configured the usb settings, and the virtual install seems to be able to detect my handset in fastboot.
Good times.
I was able to run all the fastboot commands I wanted, including "fastboot oem get_identifier_token" which wasn't previously working on the Linux side and now through some kind of voodoo works a charm under Linux too. After running this command I visited the htcdev site and requested a new Unlock_code.bin but that didn't work, still getting FAILED errors...
One thing I have noticed is that every time I run "fastboot oem get_identifier_token" I get a dramatically different token, wil this result in a different Unlock_code.bin? Maybe one of the will work eventually (doubtful).
On the other hand it seems that I've got everything ready to flash an RUU, I just need that RUU... So does anyone know where I can find it?

BenPope said:
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.
Click to expand...
Click to collapse
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.

TobyJamesJoy said:
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.
Click to expand...
Click to collapse
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.

BenPope said:
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.
Click to expand...
Click to collapse
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......

TobyJamesJoy said:
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......
Click to expand...
Click to collapse
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?

BenPope said:
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?
Click to expand...
Click to collapse
I've tried this numerous times, everything works right up to the final stage. My device is recognised by fastboot, I can get the identifier token, flash the Unlock_code.bin, it writes to the handset properly, the handset displays the black screen with "yes" and "no" options and the warnings about voiding your warranty, i choose "yes" and the phone reboots into fastboot while the terminal reads like so:
Code:
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
that's under Linux, in my Windows XP virtual box it reads the same except the final line is:
Code:
FAILED (status read failed (Unkown error))
I've tried this on two different PCs, one running arch linux, another on ubuntu 12.04, also on a fresh install of Linux Mint 13. I've tried every different usb port available and I've tried generating different Unlock_code.bin files - nothing seems to work.......
Brickland.

Idea
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?

TobyJamesJoy said:
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?
Click to expand...
Click to collapse
I think you only need this (and a fraction of it at that) if adb devices shows nothing.

TobyJamesJoy said:
I've tried this numerous times
Snip
Brickland.
Click to expand...
Click to collapse
I have no idea, I've never unlocked mine.
Sorry dude, but I'm sure it can be recovered, you just to find the right incantation.

BenPope said:
I think you only need this (and a fraction of it at that) if adb devices shows nothing.
Click to expand...
Click to collapse
hmm, i'm not sure i follow you but you have hit on one glaring omission of mine, i've never been able to get adb working.... maybe i should forage around for tips in that area.
are you saying that i only need the proper udev rules to get adb working and i should be able to do it with a fraction of the code? what do you mean by "if adb devices shows nothing"?

Bricked HOX

Yep, got it bricked. No, don't think it can be sorted out on my own.. unless someone knows how to revert neccessary partitions to rw, they seem to be all in read-only mode except cache. Have only bootloader/recovery available.
Since I'm guessing that if I send it to the repair, they will change the mainboard, as usual.. my questions are, what's the price/how much did you pay for it, and where are you from?

How did you end up in such situation? A RUU might do the trick. If you do not have an S-OFF HOX then it should be recoverable.

I can try flashing a RUU only if I can somehow do it without a relocked/locked bootloader. I don't have S-off HOX.
Trip had a faulty kernel 004 that came along with the his latest CM10.1 (do NOT worry, faulty kernel is no longer available for download, so you're as safe as you can be with your rooted phones) which caused a couple of ours devices, including his own, to brick. Some of them got into APX mode, some didn't, but the result is pretty much the same - I don't know which exactly but lets say that most if not all partitions are now read only.. so far only cache partition seems to be fine. Fastboot appears to have gone through with locking the bootloader successfuly, but that is not the case. Any attempts to copy over a ROM or any kind of file through mounting the phone as USB doesn't stick upon the next reboot, only those files that were available before are still there, and unable to delete.. and ofcourse, flashing anything isn't possible in read only.

Recovery?
Which recovery are you using?
I was using a version of CWM which had USB mount issues, updated and was able to push files from the laptop to the phone.
May be worth looking at?

BlueSingA said:
I can try flashing a RUU only if I can somehow do it without a relocked/locked bootloader. I don't have S-off HOX.
Trip had a faulty kernel 004 that came along with the his latest CM10.1 (do NOT worry, faulty kernel is no longer available for download, so you're as safe as you can be with your rooted phones) which caused a couple of ours devices, including his own, to brick. Some of them got into APX mode, some didn't, but the result is pretty much the same - I don't know which exactly but lets say that most if not all partitions are now read only.. so far only cache partition seems to be fine. Fastboot appears to have gone through with locking the bootloader successfuly, but that is not the case. Any attempts to copy over a ROM or any kind of file through mounting the phone as USB doesn't stick upon the next reboot, only those files that were available before are still there, and unable to delete.. and ofcourse, flashing anything isn't possible in read only.
Click to expand...
Click to collapse
Oh yeah, I saw that some ppl got bricked by his kernels/roms. You had really bad luck mate...
Trip said he bricked his bootloader on purpose to get his handset fixed for free, and guess what, he got a new mainboard free of charge. Ask him how he'd do it.
Sent from my One X

I gave a shot at bricking the bootloader intentionally but no success, I guess any kind of changes you try to apply to a read only simply doesn't stick, as intended.. can't even remount as read/write.. so back to the original question: 1.) What did you pay for your mainboard replaced? 2.) Where are you from?
The saddest thing is that HTCs centre in Serbia is in Belgrade, and I'm in a distant place, so I actually had to give my phone to the carrier first, and they will send it to HTC.. so any attempt at trying to manouver them by saying that I have been running the ROM/Kernel without any issues with an unlocked bootloader fails, as all they need to do is enter the hboot and the warranty becomes void.

for me with apx mode ... i sent my device to htc and after 2 days ( today ) they called me to pick my phone with new mainboard and all is free
so u are in the same problem so u should try steps we used to get into apx mode and then send it to htc to replace ur mainboard for free if u still in warranty
i think u read all comments in trip kernel thread so it's easy to get into apx mode with read only devices

Did you try reflashing your bootloader ? that deletes a lot of custom stuff in the process
if it works then you might be able to format /data and /system from your custom recovery
OH, and btw if you brick your bootloader(or APX), HTC can simply unbrick it and find all your nasty work(but it seems they didn't notice it yet)
here are instructions if interested
find your current boot.img(it gets deleted in the process)
find your current custom_recovery.img(it gets deleted in the process)
re-lock bootloader: Fastboot oem lock,
reboot to ruu: fastboot oem rebootRUU
flash firmware.zip fastboot flash zip Link/to/firmware.zip
then unlock like first time you did it, Fastboot flash unlocktoken Link/to/unlock_code.bin
restore boot.img: fastboot flash boot boot.img
restore recovery: fastboot flash recovery custom_recover.img

Vcek said:
Did you try reflashing your bootloader ? that deletes a lot of custom stuff in the process
if it works then you might be able to format /data and /system from your custom recovery
OH, and btw if you brick your bootloader(or APX), HTC can simply unbrick it and find all your nasty work(but it seems they didn't notice it yet)
here are instructions if interested
find your current boot.img(it gets deleted in the process)
find your current custom_recovery.img(it gets deleted in the process)
re-lock bootloader: Fastboot oem lock,
reboot to ruu: fastboot oem rebootRUU
flash firmware.zip fastboot flash zip Link/to/firmware.zip
then unlock like first time you did it, Fastboot flash unlocktoken Link/to/unlock_code.bin
restore boot.img: fastboot flash boot boot.img
restore recovery: fastboot flash recovery custom_recover.img
Click to expand...
Click to collapse
i don't think so .. as if they were able to unbrick it, they will do for sure and won't change mainboard for free
i don't think that they like to do repairs for free

Vcek said:
Did you try reflashing your bootloader ? that deletes a lot of custom stuff in the process
if it works then you might be able to format /data and /system from your custom recovery
OH, and btw if you brick your bootloader(or APX), HTC can simply unbrick it and find all your nasty work(but it seems they didn't notice it yet)
here are instructions if interested
find your current boot.img(it gets deleted in the process)
find your current custom_recovery.img(it gets deleted in the process)
re-lock bootloader: Fastboot oem lock,
reboot to ruu: fastboot oem rebootRUU
flash firmware.zip fastboot flash zip Link/to/firmware.zip
then unlock like first time you did it, Fastboot flash unlocktoken Link/to/unlock_code.bin
restore boot.img: fastboot flash boot boot.img
restore recovery: fastboot flash recovery custom_recover.img
Click to expand...
Click to collapse
I cannot reflash anything, I guess because even the partition where the bootloader is becomes read only. Fastboot oem lock doesn't relock or lock the device for me, and fastboot oem rebootRUU just does a normal reboot. There's literally no changes that I can apply. I guess it would be impossible for me to brick the bootloader as well because of this problem. HTC can get into APX mode easily, yes, but they cannot unbrick the bootloader.

It can be easily solved by flashing a new rom and recovery using android download tool (ADT)
my phone has bricked a hundredes of times an I only soved it using this method
HIT THANKS IF I HELPED

I don't think he can flash stuff with nearly all partitions r/o.
Sent from my One X

Please read. Partitions are read-only in my case. Unless ADT can flash partitions and repartition as intended for HOX, I would have use of it.

Dont go such deep just download any ADT flashable rom and flash it using ADT not ADB
HIT THANKS IF HELPED

Androyash said:
Dont go such deep just download any ADT flashable rom and flash it using ADT not ADB
HIT THANKS IF HELPED
Click to expand...
Click to collapse
lol. I'm fairly certain the only thing that stands any chance of helping us is signed HTC Diag files + Javacard or a route to S-off using APX mode.
Anyway, where to next: I can get a replacement HOX motherboard of unknown quantity from eBay for £150...If I do that, do I keep it, or flog it and get something else...? Or do I just sell the good LCD from my HOX to somebody who's broken theirs? (Can't flog the whole phone for parts, it's got all my data on it)
I don't really want an HTC any more after this experience.

Okay, I think I need to revise my plan of trying to have my HOX fixed without getting charged. :laugh:
Can they prove a non-stock kernel is faulty for rendering all partitions read-only if I'm not in the APX, or they're not really going to go into such details and look at the kernel's code and find where the problem is within it?

[Q] Possible Brick?

I have no clue what to do now, I've searched the forums for days now. I don't know what other options I have now. I had my phones bootloader unlocked and s-off. Even had clockworkmod installed (I believe it was version 6.0.4.5) I planned on putting it back to stock when I found out it wouldn't keep a signal and randomly rebooting. I don't know what happened or what I probably did to make it happen, but now I am stuck.
Where I stand now is looking at my phone in the bootloader. I can access fastboot from there but not the recovery. When I try to boot into recovery it seems to hang on a black screen, then after a little wait it shows me a picture of a phone with a red exclamation point inside a triangle. I guessing I would be safe to assume in saying that my recovery is shot. My bootloader says that it is locked with s-on and that it has been tampered (I attached a picture below). I've even tried using an RUU, however I don't know if I am doing it properly.
So I guess my question is this, Is there anything I can do from this point?
I've already accepted the fact I might as well have a brick. Just hoping there is a last resort.

try new recovery
Since you can get into fastboot, type fastboot devices and see if yours shows in list.
If not, check out HTC usb drivers and make sure they're right. Then get most current recovery
like PhilZ's or Clockwork or TWRP.
After connection is sure, type fastboot erase cache.
Then name your recovery recovery.img and flash it: fastboot flash recovery recovery.img.
Then type fastboot reboot-bootloader.
Try getting into your new recovery and go from there.

Forgot to attache the picture, my bad.
I will try that now.

No dice. What I get is this.
sending 'recovery' (9138 KB)...
FAILED (data transger failure (Unknown error))
finished. total time: 0.001s

...
Somehow, you got back to S-0n Locked, and it's not gonna let you do a custom recovery now.

If I'm not mistaken, since you're still only hboot 1.54, you can flash an RUU to get back to full stock. You can grab the RUU here, http://forum.xda-developers.com/showthread.php?t=2428276. Just make sure it's the VZW one. You can follow the directions here, http://forum.xda-developers.com/showthread.php?t=2251800. That thread is in the Sprint forum, but its the same process. You should be able to skip the first part where they re-lock the bootloader. Hope this helped.

I've tried that with different versions of it, many times. After I type the 'fastboot flash zip Rom.zip' all I get is
sending 'zip' (1178304 KB)...
Edit: Then it just hangs there indefinitely until I cancel it

d0m_ said:
I've tried that with different versions of it, many times. After I type the 'fastboot flash zip Rom.zip' all I get is
sending 'zip' (1178304 KB)...
Edit: Then it just hangs there indefinitely until I cancel it
Click to expand...
Click to collapse
If you're locked and s-on I don't believe you can flash an RUU. Could be wrong, but from what I remember, you can't.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
If you're locked and s-on I don't believe you can flash an RUU. Could be wrong, but from what I remember, you can't.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
If that is the case, then how would I flash an RUU?

eman7131 said:
You should be able to skip the first part where they re-lock the bootloader. Hope this helped.
Click to expand...
Click to collapse
So if we are S-Off, there is no need to relock the bootloader before flashing RUU?

d0m_ said:
If that is the case, then how would I flash an RUU?
Click to expand...
Click to collapse
You would have to wait until there is a newer RUU made available, I think. If you didnt get a failed flag when sending the RUU, I would let it sit there for a while. If you did then I don't know what to tell you.
"So if we are S-Off, there is no need to relock the bootloader before flashing RUU?"
The reason I said what I did was because he was already locked. And it depends on what you're looking to do.

You need to use a signed ruu since your s-on. You can get it in the second post of santods rom radio kernel thread in development.
Once stock and running, use weaksauce and firewater to get unlocked and s-off again, if so desired.
There is no need to relock the bootloader if you are s-off, to do an ruu.

I've tried that before, probably more than once. It seems that when I'm in either fastboot or the RUU option " black screen silver HTC" it seems to freeze.

Has to be a driver issue with your pc, or a hardware issue with the phone. My guess is the drivers.

so i think i finally figured it out. long story short i uninstalled the drivers and then reinstalled and then plugged my phone in and tried it again. now i see the black screen and silver HTC with the green bar underneath it. not sure how long that stays on but i'm to scared to touch it

That is just a splash screen for ruu mode. Once in that mode, you use other fastboot cmds to flash the ruu ( fastboot flash zip nameoffile.zip ). Once the ruu finishes in the cmd window on your pc, it will still be at that screen untill you type ( fastboot reboot ).

d0m_ said:
Forgot to attache the picture, my bad.
I will try that now.
Click to expand...
Click to collapse
i have the same problem
View attachment 3237063
any solution?

Morgandust said:
i have the same problem
View attachment 3237063
any solution?
Click to expand...
Click to collapse
what all have you tried? did you try to uninstall and reinstall the driver? that is what did if for me.

d0m_ said:
what all have you tried? did you try to uninstall and reinstall the driver? that is what did if for me.
Click to expand...
Click to collapse
you remember the name of the driver? QHUSB_DLOAD?

Morgandust said:
you remember the name of the driver? QHUSB_DLOAD?
Click to expand...
Click to collapse
not off hand, just a quick google search should be able to do it. i think it was their sync software. then after it is installed only uninstall the sync manager.

RESOLVED! [SOS!] Phone can't boot past bootloader

My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy

drago10029 said:
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
Click to expand...
Click to collapse
Are you on MM firmware or N?
Also S-OFF is the way to go.

andybones said:
Are you on MM firmware or N?
Also S-OFF is the way to go.
Click to expand...
Click to collapse
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
If you wish to s-off first, please follow >> THIS GUIDE << by @jcase & return when your device is back up and running.
First boot will take approximately 15 minutes due to Art optimization
Click to expand...
Click to collapse

UPDATE: things have gotten worse.... I was attempting to relock the bootloader since RUU was failing with error 155, someone in a diff HTC thread said locked bootloader was needed for RUU. now phone flashes HTC logo then powers off. buttons pressed not going to recovery right now anyone wanna chime in? please...

@defcomg you know anything about HTC phones? I am currently stuck in the sunken place lol

drago10029 said:
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1680928

andybones said:
https://forum.xda-developers.com/showthread.php?t=1680928
Click to expand...
Click to collapse
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also

drago10029 said:
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
Click to expand...
Click to collapse
Keep in mind the date on that post is from a few years back (2012). You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
From my small amount of time, I think you may be confused about what the difference is between an unlocked bootloader and S-OFF, which I'd need to even go back and read that article, but thought it touched a little on it
The 10 has changed quite a bit too from past phones. Before you'd need to be S-OFF and unlocked bootloader. Now S-OFF unlocked and S-OFF locked are basically the same, but that can be found in threads if you'd like to find more info on that.
Most the info is there, you just need to search. If you need help finding articles, I can try and help with that. I've been surprised with the great info I've found after awhile of coming up empty.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
It seemed you were in a simple bootloop, but I'm not 100%. I think your issue was flashing MM ROM on N firmware. Can't do that.
Also, Verizon doesn't allow us to unlock bootloader on Htc-dev. So if we want to root, we must S-OFF.

andybones said:
Keep in mind the date on that post is from a few years back. You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
Click to expand...
Click to collapse
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.

drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash

andybones said:
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
Click to expand...
Click to collapse
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?

drago10029 said:
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
Click to expand...
Click to collapse
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.

andybones said:
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
Click to expand...
Click to collapse
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.

drago10029 said:
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
Click to expand...
Click to collapse
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.

andybones said:
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
Click to expand...
Click to collapse
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)

drago10029 said:
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
Click to expand...
Click to collapse
Fastboot isn't recognized? As in it's not working?

drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?

andybones said:
Fastboot isn't recognized? As in it's not working?
Click to expand...
Click to collapse
xunholyx said:
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
Click to expand...
Click to collapse
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.

drago10029 said:
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
Click to expand...
Click to collapse
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3

xunholyx said:
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
Click to expand...
Click to collapse
oooh i see lol.. too many numbers.