Related
Hi guys,
Since a few days my touchscreen is not working properly anymore. It automatically presses certain points on the screen, without me even touching the phone. This means I can't even type a whatsapp message propertly without my phone randomly typing gibberisch.Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again. I also think the issues happen on the lowest 1cm of the screen (where your quickbar is with the icons of dialing etc). That part is unresponsive most of the times.
I tried several solutions (other rom, other kernel etc.) that didn't work. Since this morning, I upgraded my hboot to 1.39 (release keys 3.20.401.3) and the problem still persists. Even in my recovery (Philz recovery 5.0.5) the touchscreen automatically presses certain points on the screen.
Any of you guys have any idea on how to fix this? I am clueless right now .
Phone details:
International HTC One X
Hboot 1.39
Software: 3.20.401.3
CID: HTC__E11
Baseband: 5.1204.162A.29
If it ain't a software problem, it's gonna to the hardware that's at fault here!
I would suggest to get your phone back to full stock and then send it to HTC under warranty...!
vin4yak said:
If it ain't a software problem, it's gonna to the hardware that's at fault here!
I would suggest to get your phone back to full stock and then send it to HTC under warranty...!
Click to expand...
Click to collapse
Will they accept it? Since I totally rooted it . And which RUU should I use to go back to stock?
Is it a hardware related issue then? Ive read many posts of people complaining about the touchscreen.. That would be a coincidence, wouldnt it?
EDIT: Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again.. Maybe that might change your view a bit
EvertorN said:
Will they accept it? Since I totally rooted it . And which RUU should I use to go back to stock?
Is it a hardware related issue then? Ive read many posts of people complaining about the touchscreen.. That would be a coincidence, wouldnt it?
EDIT: Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again.. Maybe that might change your view a bit
Click to expand...
Click to collapse
Post the result of fastboot getvar version-main
We will find a suitable RUU or nandroid backup for your device...
All I can say is: If you have the latest JB Hboot, all roms should work fine. and you've also tried flashing multi roms... Can't be that all roms have the same problem... So it's gotta be hardware related...
Now you can try one last time... Fully wipe (data/cache/dalvic/format system) the device in recovery... flash the boot.img via fastboot and then flash the rom via recovery and see if it fixes it...
if everything else fails... Return to stock (rom+ recovery), lock your bootloader and send it for warranty!
EvertorN said:
Will they accept it? Since I totally rooted it . And which RUU should I use to go back to stock?
Is it a hardware related issue then? Ive read many posts of people complaining about the touchscreen.. That would be a coincidence, wouldnt it?
EDIT: Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again.. Maybe that might change your view a bit
Click to expand...
Click to collapse
Not coincidence but a design issue. I'm currently having trouble with the touch buttons. The symptoms are similar to yours in that it's an intermittent problem. I'm sure it's a hardware fault, I was just hoping it was a loose cable or something inside that I could fix myself. But having fiddled with all the cables already and not had any improvement I've pretty much conceded that this isn't going to be the case.
Sent from my HTC One X using xda app-developers app
vin4yak said:
Post the result of fastboot getvar version-main
We will find a suitable RUU or nandroid backup for your device...
All I can say is: If you have the latest JB Hboot, all roms should work fine. and you've also tried flashing multi roms... Can't be that all roms have the same problem... So it's gotta be hardware related...
Now you can try one last time... Fully wipe (data/cache/dalvic/format system) the device in recovery... flash the boot.img via fastboot and then flash the rom via recovery and see if it fixes it...
if everything else fails... Return to stock (rom+ recovery), lock your bootloader and send it for warranty!
Click to expand...
Click to collapse
Just ran the fastboot command, it returned version-main: 3.20.401.3.
Pff, I think I'm kinda done with HTC and their crappy designs . This is the second HTC phone I'm having issues with. Guess my next phone will be a Samsung.. I guess I can live with TouchWiz over Sense, though I think Sense is a lot better..
EvertorN said:
Just ran the fastboot command, it returned version-main: 3.20.401.3.
Pff, I think I'm kinda done with HTC and their crappy designs . This is the second HTC phone I'm having issues with. Guess my next phone will be a Samsung.. I guess I can live with TouchWiz over Sense, though I think Sense is a lot better..
Click to expand...
Click to collapse
Well you just unlucky m8! I'm sure once you've used HTC phones, you wouldn't find sammy's plastic finish phones attractive
ahh so your on the latest base is it? (3.20.401.3)... No RUU for your device, you will need to restore a nandroid backup.. However, no nandroid backup is available for that base but 3.20.401.1 backup would surely work afaik! So if you tell your device's cid, fastboot oem readcid I would give the correct backup for your region as well...
vin4yak said:
Well you just unlucky m8! I'm sure once you've used HTC phones, you wouldn't find sammy's plastic finish phones attractive
ahh so your on the latest base is it? (3.20.401.3)... No RUU for your device, you will need to restore a nandroid backup.. However, no nandroid backup is available for that base but 3.20.401.1 backup would surely work afaik! So if you tell your device's cid, fastboot oem readcid I would give the correct backup for your region as well...
Click to expand...
Click to collapse
Yep I tried every possible update to fix the issues , so Im on the latest base.
My CID is HTC__E11, as stated in OP
So once I restored that nandroid and relocked my phone, it will be ready to be send to HTC?
EvertorN said:
Yep I tried every possible update to fix the issues , so Im on the latest base.
My CID is HTC__E11, as stated in OP
So once I restored that nandroid and relocked my phone, it will be ready to be send to HTC?
Click to expand...
Click to collapse
Sorry didn't read it! here's the backup : https://mega.co.nz/#!tsYj0DSK!T65wiGBygge4w-AOwEjxvUcZ2ytvdxhj2EKXgOT7Oao
Yes... flash boot.img.. wipe everything in recovery and then restore the backup... After that flash this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img and then finally lock the bootloader!
It will be full stock (rom + recovery) with locked bootloader... Yes, you can send it to HTC after doing these things but there's always the chance of warranty getting void because of the **Relocked** bootloader... But worth a try! Besides, there's nothing you can do...
vin4yak said:
Sorry didn't read it! here's the backup : https://mega.co.nz/#!tsYj0DSK!T65wiGBygge4w-AOwEjxvUcZ2ytvdxhj2EKXgOT7Oao
Yes... flash boot.img.. wipe everything in recovery and then restore the backup... After that flash this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img and then finally lock the bootloader!
It will be full stock (rom + recovery) with locked bootloader... Yes, you can send it to HTC after doing these things but there's always the chance of warranty getting void because of the **Relocked** bootloader... But worth a try! Besides, there's nothing you can do...
Click to expand...
Click to collapse
Thanks a lot mate.. Seems my phone has less frequent issues atm. So I'll try if I can manage with it. If not, I'll go back to stock, see if the problem still persists and then send it back to HTC..
Hmmm ohkk ! Do keep us posted! :good:
Alright it has been a few days since I created this post.. Phone seems to have stabilized a bit. Yesterday I experienced the weird behavior 1 time and today I didn't experience it at all. However, I think I might have found some kind of pattern in the strange behavior. Whenever I have had my phone with me in my pocket for a while, the problems seem to start. Also when my phone is in my car holder, so basically any vertical position. When my phone is on my desk all day, I don't have any problems at all...
So yea.. Most likely a hardware related issue..
I was also fond of HTC and their phones, but with the One X, they kind of ruined my positive view.. I totally love Sense, but the build quality of the One X is far, far below my expectations. For my next phone, I am seriously considering changing to Samsung, depending on the issues with the HTC One (since my contract ends next year, I will probably get a next generation phone)..
What's is your opinion on HTC nowadays?
Hi
I don't think it's the hardware problem, because TOO MANY people have this problem. So do I. I already did post this issue before http://forum.xda-developers.com/showthread.php?p=41820803 (see the video what my phone does) but all I got was "return it to HTC"
After I did dig a little I found some posts where people say I should downgrade the touch panel firmware - http://forum.xda-developers.com/showthread.php?t=2159863
I can't do S-OFF I always get stuck at error 99 no matter what I do.. maybe you should try downgrading the touch panel and see if that fixes the problem.. do please let me know.. thanks..
another guy I messaged wrote to me I should try ViperXL ROM, he also could not get his phone to S-OFF:
"ViperXL rom is based on telus HTC one x, (HOX evita), which works fine on all US and Canadian hox phones. It has all the firmware and everything else required including sense, so it will work on your phone. I was in the worst situation as there was no OS on my phone and I could not find the original OTA, but this rom worked like a charm. Give it a shot."
so I think I'm gonna try the ViperXL..and see..
EvertorN said:
Alright it has been a few days since I created this post.. Phone seems to have stabilized a bit. Yesterday I experienced the weird behavior 1 time and today I didn't experience it at all. However, I think I might have found some kind of pattern in the strange behavior. Whenever I have had my phone with me in my pocket for a while, the problems seem to start. Also when my phone is in my car holder, so basically any vertical position. When my phone is on my desk all day, I don't have any problems at all...
So yea.. Most likely a hardware related issue..
I was also fond of HTC and their phones, but with the One X, they kind of ruined my positive view.. I totally love Sense, but the build quality of the One X is far, far below my expectations. For my next phone, I am seriously considering changing to Samsung, depending on the issues with the HTC One (since my contract ends next year, I will probably get a next generation phone)..
What's is your opinion on HTC nowadays?
Click to expand...
Click to collapse
An Evita rom won't work on a tegra device. Nor downgrading the touchpanel without s-off
so no luck again.. thanks
xichtiq said:
so no luck again.. thanks
Click to expand...
Click to collapse
I can't watch your video.. it's private .. I still think this is a hardware related problem, as it happened to me in recovery as well. The reason many people experience this issue, is because of the crappy design by HTC I guess.
vin4yak said:
Sorry didn't read it! here's the backup : https://mega.co.nz/#!tsYj0DSK!T65wiGBygge4w-AOwEjxvUcZ2ytvdxhj2EKXgOT7Oao
Yes... flash boot.img.. wipe everything in recovery and then restore the backup... After that flash this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img and then finally lock the bootloader!
It will be full stock (rom + recovery) with locked bootloader... Yes, you can send it to HTC after doing these things but there's always the chance of warranty getting void because of the **Relocked** bootloader... But worth a try! Besides, there's nothing you can do...
Click to expand...
Click to collapse
I did this earlier tonight and it looks like the touchscreen issues are gone! . I'll report back in a day or so to notify whether the issues are permanently solved, but looking good so far!.
What could possibly the cause of this issue? Touchscreen driver in the kernel? If we find a solution, maybe rom developers can add it to their roms, so people with similar issues and I can start using custom roms again
EDIT: Problems started again today . Seems like I have to send it to HTC...
After having a lot of problems with crashing apps (possibly due to corrupt storage hardware) I did one last attempt to fix it before trying to claim warranty. I installed RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe. It failed, but somehow magically locked my bootloader again. It is now locked, not relocked. I'm stuck with a phone that will only boot to bootloader, and it won't unlock again even though I do get the unlock screen where you have to choose yes or no. It will always stay locked, so I guess this is a brick? Anything I can do but claim warranty?
Without an unlocked bootloader you can't do anything except performing a factory reset from the bootloader.
Was the ruu even ment for you ? Does it match the outcome of
Fastboot getvar version-main
Mr Hofs said:
Without an unlocked bootloader you can't do anything except performing a factory reset from the bootloader.
Was the ruu even ment for you ? Does it match the outcome of
Fastboot getvar version-main
Click to expand...
Click to collapse
Yes it is, I've used the same RUU a week prior. Factory reset does nothing now, so I can only claim warranty at this point? I guess I will have to buy a new phone, since Dynafix (repair center) always claims "water damage" no matter what. I will still give it a try though.
Yep when the bootloader is locked and you can't get it unlocked , the ruu is your only chance.
Otherwise its warranty.....so its a company who makes money with stating all phones have water damage ?! :thumbdown:
Mr Hofs said:
Yep when the bootloader is locked and you can't get it unlocked , the ruu is your only chance.
Otherwise its warranty.....so its a company who makes money with stating all phones have water damage ?! :thumbdown:
Click to expand...
Click to collapse
Basically yes. Not 100%, but a lot. They have been called out on a tv show, but they aren't showing much progression. Anyway, I was on hboot 1.31 and the RUU updated it to 1.39. I think that's why it doesn't work anymore now.
Well if the ruu did run succesfully it should boot fine. Must be a hardware failure/brick somehow
Mr Hofs said:
Well if the ruu did run succesfully it should boot fine. Must be a hardware failure/brick somehow
Click to expand...
Click to collapse
I mean the RUU updated my hboot about a week ago. This time it didn't run successfully. It is also very strange that my bootloader is locked again, instead of relocked.
Yep, what some people reported in the past is that they did all this on a completely different pc.....try it. No harm can be done anymore
Mr Hofs said:
Yep, what some people reported in the past is that they did all this on a completely different pc.....try it. No harm can be done anymore
Click to expand...
Click to collapse
Unfortunately I still get bootloader version error. Thanks for your help.
Then its off for repair
Even i had a similar problem with regular crashing apps. and by regular i mean EVERY SINGLE app i opened FCd. Then the com.google.something fcd and phone would restart. Even get stuck in APX mode occasioanlly, and it all happened after i upgraded my HBOOT 1.39. Anyhow i managed to wipe my phone, install stock ROM, and relock my bootloader. Never got the "LOCKED" thing though, only "RELOCKED". Thats what i was worried that i might not get warranty. But fortunately/unfortanately, the HOX went into APX mode again, never to get out, so i gave it for repair, and turns out the service center could NOT get the phone to turn on and found the motherboard was screwed. I found another couple of users on the HOX forums whose phones got bricked and APXed after HBOOT upgrade.
ANYHOW, Service Center gave me a refurbished phone (after a month -_- ) So all good for now. My advice is Service Center.
livin.legend said:
Even i had a similar problem with regular crashing apps. and by regular i mean EVERY SINGLE app i opened FCd. Then the com.google.something fcd and phone would restart. Even get stuck in APX mode occasioanlly, and it all happened after i upgraded my HBOOT 1.39. Anyhow i managed to wipe my phone, install stock ROM, and relock my bootloader. Never got the "LOCKED" thing though, only "RELOCKED". Thats what i was worried that i might not get warranty. But fortunately/unfortanately, the HOX went into APX mode again, never to get out, so i gave it for repair, and turns out the service center could NOT get the phone to turn on and found the motherboard was screwed. I found another couple of users on the HOX forums whose phones got bricked and APXed after HBOOT upgrade.
ANYHOW, Service Center gave me a refurbished phone (after a month -_- ) So all good for now. My advice is Service Center.
Click to expand...
Click to collapse
Thanks for your comment. I'm awaiting a reply from the service center for pick up, but they are slow.
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Wildfire64 said:
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Click to expand...
Click to collapse
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Wildfire64 said:
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Click to expand...
Click to collapse
Hmmmm. If it was s-on then HTC safeguards would have prevented a hard brick. Is it possible the hardware has been damaged?
Sent from my HTC Desire S using Tapatalk
Try hard reset through youtube
Sent from my GT-S5570 using xda app-developers app
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Stone. Cold said:
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Click to expand...
Click to collapse
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Stone. Cold said:
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Click to expand...
Click to collapse
That's no problem pal it's good to keep these terms clear, so many people have misinterpreted them in the past. That being said thank you for reminding me of the black screen hboot issue. It's been ages since I've heard of that happening. Its good to keep notes
But back on topic, OP do you or your friend have a working fastboot path? If so try to boot into hboot with volume down and power, wait 30 seconds then push power. Then on the PC issue the command
Fastboot devices
If nothing happens its toast :/
Sent from my HTC Desire S using Tapatalk
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
You need to ask in the m7 sections. This is the m8 area. What rom was it running? . I have a couple things to try if it's a Verizon one.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
maybe best to see if you can unlock it via HTC Dev(as u are in fastboot mode)
Then install custom recovery, full wipe and flash a new rom via adb sideload, that will give you the system back and it should boot.
m7misery said:
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF.
.
Click to expand...
Click to collapse
This is false. RUU is designed to run on stock devices and will run just fine with S-on or S-off as long as you are running the correct RUU for your version (and also the RUU number needs to be equal or greater than what is on the phone, you can't "downgrade" while S-on).
But as mentioned previously, this forum section is for the M8 as clearly noted in the forum title. You need to get advice in the M7 forum, as advice given here (applicable to the M8) can be incorrect or even harmful to your device.
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.