Related
I tried to go back to unroot and stock HTC rom, Flashed wrong ROM, downloaded BOTH, now, phone vibrates one time (like its supposed to), but the screen does not work. Charge light does not work as far as I can tell so far.
Is there any way to get this back working or is it pretty much gone?
Edit: Charge light comes on..
Can you get into recovery through Hboot? Power it on while holding down the volume down button and see if Hboot loads.
Sent from my ADR6300 using XDA App
frostincredible said:
Can you get into recovery through Hboot? Power it on while holding down the volume down button and see if Hboot loads.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope, I downloaded two recovery images. One for SLCD sreen and one for the other screen. I looked, and apparently flashed the wrong one. I get just a black screen.
So, you can't get to recovery, not even Hboot? If Hboot is black, I don't know if there is much you can do...
frostincredible said:
So, you can't get to recovery, not even Hboot? If Hboot is black, I don't know if there is much you can do...
Click to expand...
Click to collapse
If I cant get HBoot to open..or anything for that matter, will verizon be able too? I took it to the store, told the guy very simply "the screen wont show up and nothing happens besides the single vibrate (as usual) on start-up). They hooked it to something...had the phone for about 20 minutes. Then came back and told me they ordered another one...
Edit: Once the recovery image flashed, Hboot came back up initially. S-ON was displayed. S-ON was the one thing I am glad happened.! lol
LOL, I hear you, I had a similar issue with my PSP a few years back. was getting random memory errors, and crash to reboot. I had enough sense to flash it back to stock fw, before bringing it back in. it crashed around 78% thru the stock fw flash. So that was kinda a godsend, since the only data they will be able to get off of it if they try, is stock.
Well your issue was the image you flashed. You went to unroot and flash a stock 2.1 ROM. Although this sounds correct, there is a problem. The stock 2.1 ROM was made for the release DInc's, and those, my friend, come AMOLED. So by flashing that stock 2.1 ROM, it does not contain the correct hardware drivers to support the newer batch of DInc, the SLCD.
What you could have done was:
Download the correct ROM that supports the SLCD from here (which can be found on http://dougpiston.com
Place that file in the root of your sdcard.
Now since your phone's display doesnt work, like you said it vibrates once, like normal, your phone still functions properly.
Boot your phone into HBOOT and allow it a few minutes, like normal to find this PB31IMG.zip file. It then will prompt you to press UP to confirm the update or press DOWN to not update. (you will not see this, but if you have flashed a radio then you know this process)
when you press up, it will then start updating to the stock ROM. however, you wont see any of this. just a black screen.
allow that to run, usually for 10 minutes. to be safe wait 15-18 minutes and then press UP. When the update is complete you are asked to reboot. UP for yes DOWN for no. again you will not see this. Then when it reboots....you will be happy and see the HTC Incredible white screen
It got me too, same thing you did. Just dug around and figured it out.
JWhetstone02 said:
Well your issue was the image you flashed. You went to unroot and flash a stock 2.1 ROM. Although this sounds correct, there is a problem. The stock 2.1 ROM was made for the release DInc's, and those, my friend, come AMOLED. So by flashing that stock 2.1 ROM, it does not contain the correct hardware drivers to support the newer batch of DInc, the SLCD.
What you could have done was:
Download the correct ROM that supports the SLCD from here (which can be found on http://dougpiston.com
Place that file in the root of your sdcard.
Now since your phone's display doesnt work, like you said it vibrates once, like normal, your phone still functions properly.
Boot your phone into HBOOT and allow it a few minutes, like normal to find this PB31IMG.zip file. It then will prompt you to press UP to confirm the update or press DOWN to not update. (you will not see this, but if you have flashed a radio then you know this process)
when you press up, it will then start updating to the stock ROM. however, you wont see any of this. just a black screen.
allow that to run, usually for 10 minutes. to be safe wait 15-18 minutes and then press UP. When the update is complete you are asked to reboot. UP for yes DOWN for no. again you will not see this. Then when it reboots....you will be happy and see the HTC Incredible white screen
It got me too, same thing you did. Just dug around and figured it out.
Click to expand...
Click to collapse
Thanks for posting this. I would push thanks but I'm on my phone. All to often people run into this exact situation and don't realize there phone is still working normal. They just don't know it because of the black screen. For future reference those are great instructions.
DINC|CM7|PROUD AMERICAN!
Alternative solution:
http://forum.xda-developers.com/showthread.php?p=14144155#post14144155
OK.. I've had several dinc's and finally got a charge. A buddy gave me a dinc and here's what I got. I can get into hboot fine. Phone was wiped when I got it. I have lights when charging and all seems well. I boot and just after HTC splash everything is black. He told me he did the latest ruu (pb31img method) . I've tried using the PC ruu and the .zip method to no avail.
Its hboot 0.92
Radio 2.15.10.07.07
And is s-on :s ( I know)
Can't get into any recovery...factory reset.. or anything. Also when using the pb31img method of restore it will sometimes just "go black" as soon as I try to update. Any help would be greatly appreciated.
I would try flashing the stock 7.28 radio (If you can) and see if that helps.
I've tried flashing just the radio as well as the older gingerbread ruu and radio being older than gb. It will even complete the ruu update (1 out of 10 times). But will not reboot. But if doing the ruu from PC it will still connect/disconnect USB. All the while screen is pitch black. But here is the interesting thing. Its actually booted all the way to sense unlock screen just for a second... then poof.
Now that I think about it my brother had this similar issue with his Inc. It first started doing random reboots constantly. I tried everything I could think off. At the end it would just reboot over and over and once in a while after letting it sit for a day or 2 it would load as far as the unlock screen and then reboot. Turned out to be a hardware issue. This may be the case for your Inc...I hope not though!
Ya me too.. but the more and more I delve into it its starting to look like a hardware issue.. but like I said.. it's just a hobby/mod phone (although its still better than my charge..lol) but ill continue to tinker. Thanks for the info.. ill post if it does wind up working.
Having an issue with my HOX today. It was in my pocket all day at work, pulled it out to make a phone call and afterwards when I went to hang up, the screen would not turn back on. It is still responsive to touch input and I can still unlock while the screen is black, but it still does not turn on. I can however hard restart it and the screen comes back on and I can still enter fastboot/recovery. But if I let the phone stand-by the issue repeats itself. I was on BinDroid v2 without any kernel when this happened, I got the phone into recovery and flashed both Energy and franco.Kernel and this issue is still happening. Is my best option to try and flash the original RUU and a stock rom?
I've had this issue since flashing the bricked kernel. I think the best option would be to go back to stock.
Sent from my HTC One X using XDA
i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.
Can't you restart the phone by holding the power button in?
If not then that's a strange one.
Sent from my HTC One X using XDA
IPS1989 said:
i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.
Click to expand...
Click to collapse
This is what I'm doing as well. I tried using a nandroid to go back to stock and that still doesn't work. It's almost impossible to get the phone into the bootloader but it's do able. One thing I'm noticing though, is that if the screen does manage to turn on when I boot it up, it wants to send an error report to HTC about it. Also, once the screen goes off and won't come back on, it's very laggy to other inputs. Example, pressing the power like you want to wake it and then pressing to volume keys has a very noticeable delay.
Thankfully, HTC is already doing a warranty call on it for the yellow spots on my screen (now like dark orange spots now)
Update: HTC said that the screen issue I'm having is unlikely able to be fixed by a software repair and that I have to send it in for a repair. 7-10 business days.... great.
Also with an untouched phone
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it ;-)
lisophorm said:
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it
Click to expand...
Click to collapse
Hi.. I'm also facing the same issue ... however this didn't start till few days ago. I have had this phone for six months now and was on stock most of the times.
But since this week , I started getting issues where once the screen goes black , it doesn't come back on. Although , I can reboot the phone with long press power button and also go back to bootloader/recovery without any issues.
Can u confirm its the hardware issue ? If yes, did the techinicians told you anything about what is causing this and it can be corrected easily ? I want to try my hands on it before going to customer care as I have void my warranty and will have to pay for repairs.
Cheers !
its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2
shadow fiend said:
its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
First time I started facing the issue, I was on stock 4.0.4 rom with stock kernels unrooted and locked bootloader.
So not sure if the issue was related to kernel. Anyways I'l try to get stock kernel and use it.
Cheers
OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio
dev997 said:
OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio
Click to expand...
Click to collapse
have you solve this issue?
okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.
mr.dj26 said:
okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.
Click to expand...
Click to collapse
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?
PAGOT said:
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?
Click to expand...
Click to collapse
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?
mr.dj26 said:
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?
Click to expand...
Click to collapse
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?
Turn off fast-boot. And then do a reboot. Elimination my friend.
PAGOT said:
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?
Click to expand...
Click to collapse
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help
oliseo said:
Turn off fast-boot. And then do a reboot. Elimination my friend.
Click to expand...
Click to collapse
so you think this is the reason of the problem?
thanks
mr.dj26 said:
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help
Click to expand...
Click to collapse
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..
mr.dj26 said:
so you think this is the reason of the problem?
thanks
Click to expand...
Click to collapse
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.
HebeGuess said:
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..
Click to expand...
Click to collapse
lol
thanks for your help
oliseo said:
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.
Click to expand...
Click to collapse
i really appreciate ur help guys
i just had the problem again, fast boot was off.. just did a factory reset
theres no crashs when transferring file or turning wifi on or off.
this is really weird.
do you think flashing RUU may help or its the ame as factory reset?
thanks..
Worth trying.
BenPope said:
Worth trying.
Click to expand...
Click to collapse
I have never flashed an ruu before.
can you tell me how that work and from where I can get it? my cid is J_15
and im useing mac, will it work?
thanks m8
There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.
BenPope said:
There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.
Click to expand...
Click to collapse
theres no guide on how this works..
my cid is J_15, which file should i download ?:S
i really hope this would do it, htc support at my place isn't that good and i really dont want to send it back and wait for ages
,,
i rebooted the phone now more than 10 times with now problems,
the phone now has no apps or anything brand new.
could it be a cause of apps or something?
Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.
BenPope said:
Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.
Click to expand...
Click to collapse
okay here it is 1.26.401.2
now when i want to download it it requires premium account WT* ?!
.
dose flashing the RUU require adb or only htc driver?
I'm in the same position. Woke up yesterday, booted phone, black screen after "HTC One" screen. Oddly I could change the volume and the volume changer would display on a black screen. Restarted, same thing. Factory reset, no problems. All the while fast-boot is off.
Same thing happened this morning, cold boot, "HTC One" screen then black screen. Factory reset and immediately rebooted - same thing again! is this a hardware issue or a corrupt software issue?
Will go and join the incredibly long and slow moving at the HTC service centre after work.
---------- Post added at 12:34 PM ---------- Previous post was at 11:50 AM ----------
I've spoken with HTC customer services and they recommend taking the phone in to get it flashed - basically they think that there is a problem with the software. They claim it is a quick job.
They offered to come out to my office and collect my phone and return it tomorrow - I'm impressed with that level of service... pending they can fix it with a simple flash of the firmware!
Hi all,
I have been reading through this forum and some other links trying to solve my problem, but I haven't managed to find the answer. There seems to be a lot of very similar issues though, which makes it all the more frustrating.
A friend and I got my HTC Desire to S-OFF and flashed a custom ROM onto it over two years ago, and it was working perfectly well. After a while I noticed that the phone got very hot with extended use, and often reset itself, which I believe is a fairly common thing. Then suddenly one time, it reset and got stuck in a bootloop. The HTC splash screen just came up for about 30 seconds, then a black screen, then the HTC splash again, repeatedly. I can get into HBOOT, but when I select RECOVERY, the HTC splash screen comes up and stays up. Also, seemingly randomly, whenever the HTC splash screen comes up, sometimes it decides to vibrate seven times, other times only once. I forgot about the phone after I upgraded, but now I'd like to get the phone up to working order to play around with.
As I said, this all seems familiar from other posts, but none of them solve my problem. I've tried reflashing various HBOOT and recovery images in fastboot as is often suggested, none of which change the situation. I've also tried flashing the recovery in HBOOT using the .zip version, which still changes nothing. I'm wondering if a hardware problem could explain the issues I'm having, following the repeaded overheatings, but I'd expect an error to pop up when flashing the recovery image.
I feel like the problem is either a serious hardware failure, or I'm overlooking something critical in the flashing process. I apologise if there is an exact post already open that solves this. Any hints that could help would be great.
Oops
Sorry, I meant to post this in the Q&A section, not here.
Guffmeister said:
Hi all,
I have been reading through this forum and some other links trying to solve my problem, but I haven't managed to find the answer. There seems to be a lot of very similar issues though, which makes it all the more frustrating.
A friend and I got my HTC Desire to S-OFF and flashed a custom ROM onto it over two years ago, and it was working perfectly well. After a while I noticed that the phone got very hot with extended use, and often reset itself, which I believe is a fairly common thing. Then suddenly one time, it reset and got stuck in a bootloop. The HTC splash screen just came up for about 30 seconds, then a black screen, then the HTC splash again, repeatedly. I can get into HBOOT, but when I select RECOVERY, the HTC splash screen comes up and stays up. Also, seemingly randomly, whenever the HTC splash screen comes up, sometimes it decides to vibrate seven times, other times only once. I forgot about the phone after I upgraded, but now I'd like to get the phone up to working order to play around with.
As I said, this all seems familiar from other posts, but none of them solve my problem. I've tried reflashing various HBOOT and recovery images in fastboot as is often suggested, none of which change the situation. I've also tried flashing the recovery in HBOOT using the .zip version, which still changes nothing. I'm wondering if a hardware problem could explain the issues I'm having, following the repeaded overheatings, but I'd expect an error to pop up when flashing the recovery image.
I feel like the problem is either a serious hardware failure, or I'm overlooking something critical in the flashing process. I apologise if there is an exact post already open that solves this. Any hints that could help would be great.
Click to expand...
Click to collapse
Might be an overheating issue. Try putting your phone in the freezer for about 10 minutes, with the battery taken out , then try to boot.
Hi, thanks for your response. I saw you posted a similar comment in the Q&A section.
I'll give it a go. I'll also try flash the RUU as you suggested in that same post if that doesn't work. How exactly does putting the HTC in the freezer help? I can understand if it was still hot from being on a lot, but it's been sat on a shelf for well over a year switched off.
Guffmeister said:
Hi, thanks for your response. I saw you posted a similar comment in the Q&A section.
I'll give it a go. I'll also try flash the RUU as you suggested in that same post if that doesn't work. How exactly does putting the HTC in the freezer help? I can understand if it was still hot from being on a lot, but it's been sat on a shelf for well over a year switched off.
Click to expand...
Click to collapse
Well, it takes a lot less time for it to heat from 24°C than from -10°C.