my phone works, it can connect to my computer, it used to vibrate and make noise when i received a call, it just stopped accepting input and the screen stays blank - it used to power on but all black screen.
i thought it was a flash problem so i upgraded to the latest energy rom, now naturally devoid of its connection to my phone number it no longer vibrates when it gets a ring, just sits there dead. the screen has not come to, ive attempted to hard reset it a few times, nothing works. it is still capable of connecting to my computer and being recognized for what it is, an HTC Fuze.
Its out of warranty so any help would be greatly appreciated.
Related
Hello Guys,
I started to have problems with my wing and end up in three-color bootloader screen. I can tell you that I am not playing around with my phone. I do not even install any software not to risk its basic phone functionality since I am using this phone as a business phone. So, no crazy rom flash or etc has been done prior to this problem.
My phone started to have problems with answering calls last week. When it was ringing, it was keep ringing and I was not able to take the call even though I was pressing every possible buttons on the phone. It was locking.
I noticed that phone was locking the buttons too. So, I selected "do not lock buttons when the device is off". But, this does not have any effect. Phone was keep locking my buttons.
Last night, I noticed that my phone was unresponsive once again as usual, I soft reset the device, and it booted to the three color screen (I think you guys call this bootloader screen?) where it says "IPL 4.26.0002" and "SPL 4.26.0000". Tried to soft reset probably another 10 more times. same thing...
I took out the battery, went to sleep. Put back the battery in the morning, it booted to the OS and phone is running. But none of the hard buttons were working. It also hangs up the incoming call after first ring. I soft reset the device once again and it went back to the three-color screen.
I went to the Tmobile website, and found that there is an upgrade ROM. I downloaded and ran that program. It said that it installed it to the device successfully, and then the device rebooted itself. Guess what, back to the three-color screen.
I have been reading your forum since morning, and read a lot about brick phones etc. I tried couple of the techniques for recovering brick phones, but nothing helped. Hopefully, someone here can tell me what is going on, even though if the answer is to throw the device to the trash.
Additional Observations
It looks like nobody is interested
I have other observations.
- When "do not lock buttons" is checked, phone starts acting even more weirder. it generates keystrokes by itself. Camera starts taking photos.
- If the battery of the phone is out at least an hour (I don't know why), phones boots fine. If you soft reset at the moment, it will always goes back to the three color bootloader.
Can this be a virus?
The other day, I hit the power button on my touch pro, and the screen didn't come on. I did a soft reset, and it started working again. Now today, the same thing is happening, but a soft reset isn't helping.
The screen's back light comes on, the LEDs on the buttons come on, and the phone seems to be working fine. I hear all the sounds, including the HTC sound while it is booting, and the new message sound, but the screen stays black. It still recognizes touches, it just doesn't show an image. I want to do a hard reset, and will if I can get it to come one one more time, but its been about a month since I backed up my contact list. Lesson learnt there. I'm afraid it might be a hardware problem since I don't see anything while its booting either.
Anyone know if this is a known hardware issue with the touch pro? The phone is less then 3 months old, and I've been real careful with it. I haven't dropped it from more then 2 feet, and even that was onto carpet. Its the Verizon version if that makes a difference, and I'm running one of the NFSFAN roms. Its not the newest one, but rather the one posted on October 19th. I doubt its the rom, though, as I've been using it for around 2 months with no issues.
EDIT: Ok, I went into the bootloader to see if it was hardware of software. I figured if it was hardware, the screen would be black, and if it was software, it would be the rainbow. Sure enough, the screen stayed black. Hit the reset button, and the screen actually came on! Go figure. Went to do a backup, and the screen literally crapped out on me while I was watching it. Definitely a hardware problem.
similar with Touch HD... kinda
I've been having a similar problem with my Touch HD. The problem is very intermittent though and is sometimes hard to reproduce. The screen and phone will be working fine then once in a while when I push the power button to lock the phone, I'll unlock it and the screen stays black. I know that the phone is still on and even unlocked because pushing the buttons at the bottom makes the phone vibrate. The only consistency in reproducing the problem happens after I do something major on the phone such as making a phone call, browsing the internet, sometimes charging the phone. Other than that, I can sit here and push the power button all day and it'll come on and off with no problems. When the screen does go black I've taken the battery out repeatedly as well as repeatedly rebooted the phone until it comes back on. I've tried doing hard and soft resets to no avail. I've tried deactivating "turn off backlight if device is not used for" and "turn off device if not used for" without any resolve. After this I've even left the screen on (disabled backlight off) to see if it flickers or shows any sign of being faulty and it seems to be fine. I'm currently on Dutty's HD WM 6.5 Leo R5 WWE rom, but this has happened with two other roms (NRG, LIA). Other info include:
OS: 5.2.23016
Manila: 2.519192828.0
Radio: 1.14.25.24
Protocol: 52.64.25.34H
I guess the only consistent software has been my radio. Please help! Any advice would be awesome. I've tried google search and xda search without much help. Thanks
Hello there,
I have recently received an HTC HD2 from a friend of a friend of mine. It didn't work and was stuck at a black screen.
After receiving the HD2 I saw that the HD2 was in a boot loop of some sort. Every time I would turn it on it would vibrate once, and then turn off. Then it would vibrate once again and it turned off again. The backlighting of the screen would turn on, and then after a certain period of time (maybe like 5 seconds) they turn off again.
Somehow (by luck, maybe) I managed to boot the phone into windows mobile 6.5. I still got a black screen, but I could hear the sound that the phone makes after it boots windows. I then attached the phone to the computer and downloaded the latest HTC HD2 Windows 6.5 ROM and flashed it to the phone as standard procedure. Now, every time I turn the phone on I hear the sounds of windows booting up and I can connect with it using windows mobile device center. I also hear sounds when I push the buttons on the phone.
TL;DR-> Black screen, phone reacts to input.
Question: will replacing the screen fix the phone? Or is it some other component failing. Booting windows proves the phone isn't bricked, right?
Thanks in advance.
Might Help
ikheetkoen said:
Hello there,
I have recently received an HTC HD2 from a friend of a friend of mine. It didn't work and was stuck at a black screen.
After receiving the HD2 I saw that the HD2 was in a boot loop of some sort. Every time I would turn it on it would vibrate once, and then turn off. Then it would vibrate once again and it turned off again. The backlighting of the screen would turn on, and then after a certain period of time (maybe like 5 seconds) they turn off again.
Somehow (by luck, maybe) I managed to boot the phone into windows mobile 6.5. I still got a black screen, but I could hear the sound that the phone makes after it boots windows. I then attached the phone to the computer and downloaded the latest HTC HD2 Windows 6.5 ROM and flashed it to the phone as standard procedure. Now, every time I turn the phone on I hear the sounds of windows booting up and I can connect with it using windows mobile device center. I also hear sounds when I push the buttons on the phone.
TL;DR-> Black screen, phone reacts to input.
Question: will replacing the screen fix the phone? Or is it some other component failing. Booting windows proves the phone isn't bricked, right?
Thanks in advance.
Click to expand...
Click to collapse
Hi, you can always try to boot into three colored screen, by turning the phone on while holding the DownVol key at the same time. If this doesn't work you would need to buy a new screen to see if that fixes the problem.
Heres a link to amazon where you can buy a new LCD, you can also search how to change the screen on Youtube
http://www.amazon.com/HTC-HD2-DIGITIZER-COMPLETE-ASSEMBLY/sim/B003QSDSM0/2
Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.
I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead
Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.
I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.
reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?
Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.
Hi guys,
I am experiencing the wierdest thing on my brother's Xperia Z3.
2 days ago, the phone randomly stopped showing images on the screen, but the backlight would still switch on and off as normal when pressing the power button. If the phone is restarted in this state by using key combos, the Sony logo won't even show up. This problem started intermittently, but now it does this for a much longer period. The issue would usually occur after the phone being locked, or if it were being used, the screen would show horrible distortion on the bottom half and become non-responsive until the screen switched off and any attempt to switch it on would be make the phone behave as described earlier.
I used to be able to make the image work by plugging in the USB cable, but this method seems to have stopped working, or at the very least has a really low success rate. I have tried all the soft reset methods: Power+VolUp, yellow button in the sim tray, none of those work for me.
I have just stopped short of reflashing the phone with Flash Tools.
Has anyone had this problem before? It is really confusing me as to whether this is a software or hardware issue.
Any suggestions?
I reflashed the phone using Flash Tools and the phone is still behaving the same way; just the backlight is turning on. Besides that, the phone seems to be making the correct noises and responding to the USB cable. Anyone have any ideas? Could it be the screen itself? I'm worried that it may be the motherboard.
Ok, I found something that works. If I hit the device with my hand on the back or the screen a few times, it seems to bring the phone back. My suspicion is either a loose screen connector or something on the motherboard. I'm not really comfortable with opening the phone up, so this is going to be my go-to solution. Hope this is able to help someone.