Develop Bugs

htc one x iscompletely messed up. Please Help!!!

Hello i have the tc one x and i have alot of problems. when i first bought the phone i rooted it and i was happy. i downloaded root apps and i was set. then i wanted to start flashing roms. so i downloaded a custom rom on my computer, followed all the instructions carefully and it did not work. i had installed clockworkmod and the whole 9 yards.When i would try to boot into recovery mode i would get a security warning and i was not allowed to. i tried many tutorials to install it on to my phone using my computer and command prompt and things like that but that did not work. So i came to the conclusion that i did not unlock my bootloader. so i went through the whole process on htcdev.com and my key was invalid. i had gotten the error 160 and mid not allowed. now i wanted to completely restore and unroot so i deleted superuser and the su files and did the whole thing with fastboot files and command prompt using a video to help me through it. When i was done my phone still said tampred on the bootloader and i got the same security warning error when i tried to restore the phone. so i cannot restore my phone to stock. now my phone cannot recieve att updates and when i try to manually update it is says htcdm has stopped and then after the button does nothing. and many apps stop unexspectedly and i am very upset about this. i have tried unrooting and unlocking bootloader at least 10 times now and nothing works!! PLEASE HELP!!! i really dont want do have to sell my phone and save up for a new one. thank you.

ewokiscool said:
Hello i have the tc one x and i have alot of problems. when i first bought the phone i rooted it and i was happy. i downloaded root apps and i was set. then i wanted to start flashing roms. so i downloaded a custom rom on my computer, followed all the instructions carefully and it did not work. i had installed clockworkmod and the whole 9 yards.When i would try to boot into recovery mode i would get a security warning and i was not allowed to. i tried many tutorials to install it on to my phone using my computer and command prompt and things like that but that did not work. So i came to the conclusion that i did not unlock my bootloader. so i went through the whole process on htcdev.com and my key was invalid. i had gotten the error 160 and mid not allowed. now i wanted to completely restore and unroot so i deleted superuser and the su files and did the whole thing with fastboot files and command prompt using a video to help me through it. When i was done my phone still said tampred on the bootloader and i got the same security warning error when i tried to restore the phone. so i cannot restore my phone to stock. now my phone cannot recieve att updates and when i try to manually update it is says htcdm has stopped and then after the button does nothing. and many apps stop unexspectedly and i am very upset about this. i have tried unrooting and unlocking bootloader at least 10 times now and nothing works!! PLEASE HELP!!! i really dont want do have to sell my phone and save up for a new one. thank you.
Click to expand...
Click to collapse
Yup.

First, your not clear with what you actually did.
IS your Phone the AT&T version? If YES, then this is the wrong forum.
Also all you need to do to get a custom ROM running is this.. (in the respective order ) -
1- Unlock using HTC. Your error is probably because you did not clearly read on how to copy the UID part. even one extra character here or there can generate an invalid key.
Follow the instructions to the letter.
2- Flash ClockWorkMod Recovery using fastboot.
3- Before flashing the ROM, from CWM, make a backup of the stock ROM, by going to Backup and Restore - Backup.
4- Wipe Date/Factory reset option in the recovery. Then Goto Mounts section and format /system.
5- Now flash your ROM from the sdcard.
6- PROFIT?
If you are not confident enough to follow each and every instruction to the letter, then flashing custom ROM's is not for you.
From your post i can clearly see that you find the whole process a little too cumbersome. I can be wrong. But please at least be clear what you exactly did. Which ROM did you try to flash? And how did you go back to stock? Which RUU did you use? Was it the correct one?

If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.

how do you run an ruu
Rusty! said:
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
Click to expand...
Click to collapse
how do you run an ruu?

Boot into bootloader then go into fastboot and run the ruu that's all but sure thing before doing this u have to flash the stock recovery and kernel and lock bootloader
Y U WANNA KNOW FROM WHERE SENT??

Just download one and run it, dead easy.

But he has to return the recovery and kernel and lock bootloader first
Y U WANNA KNOW FROM WHERE SENT??

His post is so disjointed it's impossible to figure out the state of his bootloader (hence mentioning it), but you don't need to replace kernel and recovery, that's the point of the RUU.

Rusty! said:
His post is so disjointed it's impossible to figure out the state of his bootloader (hence mentioning it), but you don't need to replace kernel and recovery, that's the point of the RUU.
Click to expand...
Click to collapse
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning

ewokiscool said:
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
Click to expand...
Click to collapse
Then you haven't unlocked it properly.
Sent from my fauxed HOX running ParanoidAndroid JB

ewokiscool said:
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
Click to expand...
Click to collapse
OK that means you're good to go with the RUU if you want to return to stock and have everything working again.

Dude becareful if its saying security warning then your battery is very low,becareful because if the phone drains completely while using ruu the phone would get hard bricked also u can't select ruu you just have to go into fastboot
Y U WANNA KNOW FROM WHERE SENT??

Ok. Stop.
Where did you get your phone? Is it quad or dual core? What is the model number written on the case?
Before you do more damage, let's figure out what device you have, which forum you need to ask questions in, and what procedures you need to follow.

Defo sounds like an XL to me
Sent from my HTC One X using xda premium

Given AT&T updates were mentioned in the OP, that's a given

EddyOS said:
Defo sounds like an XL to me
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Agreed. Not seen tampered on the intl x. Would also explain everything else not working.
M.
Sent from my HTC One X using xda premium

BenPope said:
Ok. Stop.
Where did you get your phone? Is it quad or dual core? What is the model number written on the case?
Before you do more damage, let's figure out what device you have, which forum you need to ask questions in, and what procedures you need to follow.
Click to expand...
Click to collapse
i have the usa version dual core
i bought it from radio shack
on the box it has a proof of purchase and says Model: Htc One X
imei: 359691041968911
sku:65383

Rusty! said:
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
Click to expand...
Click to collapse
ok i downloaded the RUU now what do i do to run it on my phone?

ewokiscool said:
i have the usa version dual core
i bought it from radio shack
on the box it has a proof of purchase and says Model: Htc One X
imei: 359691041968911
sku:65383
Click to expand...
Click to collapse
Right, well, I'm not sure what you've done to it, but this is the wrong sub forum.
If it is an AT&T phone, htcdev won't work.
Best bet is to visit the ONE XL forum. And post what you problems you have, and then what you tried to do before arriving where you are now.
Word of advice, your first post in this thread was awful. It's too long, too confusing and unreadable. Try to cut out as much as you can. I don't care how many yards, that you got instructions from a video, and that the video was hosted on YouTube. Just list what you did to the phone. Use spaces (including vertical spaces), punctuation and bullet points to good effect. End of the day, you want as wide an audience as possible.
Good luck.

[Q] Problems with installing blackout ics ROM Desire HD

So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.

TH3_M0Nk said:
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
Click to expand...
Click to collapse
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....

glevitan said:
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
Click to expand...
Click to collapse
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.

TH3_M0Nk said:
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
Click to expand...
Click to collapse
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?

glevitan said:
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
Click to expand...
Click to collapse
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks

TH3_M0Nk said:
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
Click to expand...
Click to collapse
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:

glevitan said:
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
Click to expand...
Click to collapse
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.

TH3_M0Nk said:
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
Click to expand...
Click to collapse
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?

glevitan said:
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
Click to expand...
Click to collapse
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks

TH3_M0Nk said:
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
Click to expand...
Click to collapse
Ok, just let me know when you are online and be arrange it.

glevitan said:
Ok, just let me know when you are online and be arrange it.
Click to expand...
Click to collapse
Yes I am online now. Let me know how to proceed.

TH3_M0Nk said:
Yes I am online now. Let me know how to proceed.
Click to expand...
Click to collapse
download the teamviewer: http://www.teamviewer.com
Get the ID and PASS and send them over a Private Message, NOT HERE

confused.com

Hi folks,
quick intro ans explanation, I've started a new job, been given a Desire (Bravo) to use until the phone contracts come up in a few months. I need to use this for business, so I dont want anything to extreme, I have upgraded with the official GB firmware (it was on 2.2.1? first, then OTA update to 2.2.??, then i found the official GB and flashed that.
I'm coming from the Galaxy 3 forum (GT-i5801) been flashing that for a few years, so i understand the basics, root/custom rom/recovery etc., even rooted the wifes Galaxy Mini for her to give a boost with ram manager/set cpu and off course app2sd/link2sd. These are the same reasons i want to root the Desire, lack of storage, be able to run ram managers and clean off the bloatware, but still be stable on stock rom. The Galaxy 3 can be clean flashed with ODIN, or through CWM with GB/ICS/JB roms, the Mini was even just with an update zip.
I have been researching the past few nights, watching tuts, various forums and sites, and i must admit i'm still lost, I was about to try and flash, when i read somewhere that some methods may not work with official GB...
I cant even find the HBOOT USB setting..... I dont fancy having to go to work and say I bricked the phone ( i know, always a chance, take no responsibility etc. etc.)
Dont want to spam the board to much, even if someone can pm me with the best way forward, I've even read some stuff that seemed contradictory, i only want to get root/su to move all my apps etc with TB, and clean up a bit (bloatware).
device info;
Bravo PVT1 ship S-ON
HBOOT 1.02.0001
Radio- 5.17.05.23
Thanks in advance, and repeated use of the thanks button will be used :silly:

click desire all things root guide in my sig, and read the s-off with revolutionary link. everything u need is there
Sent from my HTC Desire

jmcclue said:
click desire all things root guide in my sig, and read the s-off with revolutionary link. everything u need is there
Sent from my HTC Desire
Click to expand...
Click to collapse
off to check, cheers!

#edit-sorry, was being a muppet....
edit 2- now S-OFF

aaargh, cant get the phone into HBOOT anymore, press and hold back, vol. up or down just gives normal reboot.....

Skivit said:
aaargh, cant get the phone into HBOOT anymore, press and hold back, vol. up or down just gives normal reboot.....
Click to expand...
Click to collapse
lol pull the battery out n put back in then volume down + power
Sent from my HTC Desire

pulled battery, got it....
trying the adb commands, fastboot not recognized....help?

placed CWM file in My Documents folder, not getting recognized.

gonna have to hit the sack, anybody point me in the right direction? I'll check during the day, "fastboot is not recognized as internal or external commmand etc. etc. (roughly translated, system is in NL)
merci!

You need to run fastboot command from the fastboot directory.. so if it's for example in "C:\SDK\platform-tools"
Then first you need to do following: (in CMD window)
cd C:\SDK\platform-tools
Then you can use fastboot commands.
Also word of advise: use 4ext recovery, it's better in every possible way.
You dont even need to use fastboot, once you're S-OFF you can flash recovery using this method: http://forum.xda-developers.com/showthread.php?t=1751258&highlight=4ext
If you want to use fastboot just unpack PB99IMG.zip and flash recovery.img

k3lcior said:
You need to run fastboot command from the fastboot directory.. so if it's for example in "C:\SDK\platform-tools"
Then first you need to do following: (in CMD window)
cd C:\SDK\platform-tools
Then you can use fastboot commands.
Also word of advise: use 4ext recovery, it's better in every possible way.
You dont even need to use fastboot, once you're S-OFF you can flash recovery using this method: http://forum.xda-developers.com/showthread.php?t=1751258&highlight=4ext
If you want to use fastboot just unpack PB99IMG.zip and flash recovery.img
Click to expand...
Click to collapse
i must update that thread to latest recovery, thanks for reminding me.
Sent from my HTC Desire

k3lcior said:
You need to run fastboot command from the fastboot directory.. so if it's for example in "C:\SDK\platform-tools"
Then first you need to do following: (in CMD window)
cd C:\SDK\platform-tools
Then you can use fastboot commands.
Also word of advise: use 4ext recovery, it's better in every possible way.
You dont even need to use fastboot, once you're S-OFF you can flash recovery using this method: http://forum.xda-developers.com/showthread.php?t=1751258&highlight=4ext
If you want to use fastboot just unpack PB99IMG.zip and flash recovery.img
Click to expand...
Click to collapse
thanks, gotta go work now, will try again tonight, chose CWM because i used it on the galaxy, devil you know kind of thing , let you know how i fare later.....

Skivit said:
thanks, gotta go work now, will try again tonight, chose CWM because i used it on the galaxy, devil you know kind of thing , let you know how i fare later.....
Click to expand...
Click to collapse
We used it on Desires back in time too, but now it's just outdated and missing some important functionality.

@k3lcior;
@jmclue-
once again , many thanks for your patience, succesfully S-OFF, rooted with su access!:victory:
the 4eXT Recovery is really nice to use, smooth as!
Installing the PB99IMG.zip was a piece of cake, maybe a good idea to update that tut, with this as another "solution".
Restored everything with TB using Link2sd, just need to erase bloatware, check all apps, and see what difference Rammanager etc will make.
What should I do, ask the mod to delete this thread, or let it sit for the time being?
Hope everyone had a good laugh at my struggles, see you all on the forums! :laugh:

nah dont bother reporting it to be closed coz mite be helpfull to someone else. glad u got it all sorted
Sent from my HTC Desire

everything seems to have settled down, still getting a low memory warning even with Link2sd (only used it once before, most of the custom roms i used had app2sd), TB cant see 2nd partition, but for the rest, Rammanager and Setcpu have made the phone pretty snappy.......

OK only took a day before I flashed jb....
Sent from my HTC Desire using xda premium

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?

HTC M8 stuck in bootloop

Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.

So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup

ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.

Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.

You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.

Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).

redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.

Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).

redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.

Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.

redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?

Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.