Related
My Friend has a HTC Wildfire, he's on a tour with his friends
Problem starts now , He was talking with his friend and suddenly screen went blank. He's using VillianROM on it now when he switches on he can't see the screen at all, but phone it self works when someone calls he's still able to answers it. he cant flash new ROM Also. he can't see screen so
Any Help ? anyone had such kind of a problem with HTC ?
maheshpatel said:
He was talking with his friend and suddenly screen went blank. He's using VillianROM on it now when he switches on he can't see the screen at all, but phone it self works when someone calls he's still able to answers it.
Click to expand...
Click to collapse
This is certainly not related to VillianROM in any way.
I think it's a hardware problem - there's something wrong with display panel. If the backlight is dead you should barely see very dark image on the screen in bright lightning conditions.
Anyway, looks like there's nothing you nor your friend can do to fix it. You need to send it to service.
maheshpatel said:
he cant flash new ROM Also. he can't see screen so
Click to expand...
Click to collapse
If the phone has USB debugging enabled by accident (I guess it's hard to turn it on blindly) then you can access it using adb shell. If you have custom recovery image installed, such as Clocwork or Amon_RA, you can boot to it and fave full access to your phone through USB using adb (or fastboot) so you can flash new ROM images.
oyah said:
If you have custom recovery image installed, such as Clocwork or Amon_RA, you can boot to it and fave full access to your phone through USB using adb (or fastboot) so you can flash new ROM images.
Click to expand...
Click to collapse
Yes, what he said ^^.
I'll just add one more thing. To get to custom recovery easily, pull the battery out and put it back in again. Then perform what ever key combination to boot custom recovery.
Good luck to your friend!
You might also have more luck posting in the Wildfire sections where they me able to help. It does seem like a Hardware issue with the screen to me? Was it dropped or anything?
It seems like hardware. Probably connection between screen and PCB.
ya his phone dropped many times, ya it seems like hardware issue to me also..
hey. i went to take my evo off the charging dock and then went to wake up the screen and when i do the whole screen is in rainbow, snow pixel. like all i can see normal is the status bar. i can boot and reboot, boot into recovery ( but cant see anything except the very first line on the top of the screen) but the screen is just messed up. it looks like one of this old tv's that when they loose connection they get white and black snow except mine is colored snow.
any ideas?
thanks
Shotgun4 said:
hey. i went to take my evo off the charging dock and then went to wake up the screen and when i do the whole screen is in rainbow, snow pixel. like all i can see normal is the status bar. i can boot and reboot, boot into recovery ( but cant see anything except the very first line on the top of the screen) but the screen is just messed up. it looks like one of this old tv's that when they loose connection they get white and black snow except mine is colored snow.
any ideas?
thanks
Click to expand...
Click to collapse
I would imagine LCD failure, though I can't be quite sure. Could you include a picture of it?
Shotgun4 said:
hey. i went to take my evo off the charging dock and then went to wake up the screen and when i do the whole screen is in rainbow, snow pixel. like all i can see normal is the status bar. i can boot and reboot, boot into recovery ( but cant see anything except the very first line on the top of the screen) but the screen is just messed up. it looks like one of this old tv's that when they loose connection they get white and black snow except mine is colored snow.
any ideas?
thanks
Click to expand...
Click to collapse
The same problem with my GSM Evo 3d:/
What ROM, Radio, kernel are you using? LeeDroid V5.3 and LeeDroid V4.2.1-1.94GHz-KERNEL, radio - 10.59.9020.00_10.15.9020.06 in my case
http://img515.imageshack.us/img515/543/img20120225140835.jpg
I noticed that when I removed battery and tried to boot, in the beginning screen was black and then was LeeDroid's boot-sound and when phone is supposed to ask for my PIN code the rainbow-pixel screen appears.
Could anyone make step by step instruction how to reflash ROM? I cannot see anything so I need all information (like push vol down two times). I hope it might works
Akasa Fox said:
I would imagine LCD failure, though I can't be quite sure. Could you include a picture of it?
Click to expand...
Click to collapse
really... LCD Failure... how would i fix that... here are some pics. I am running this rom http://forum.xda-developers.com/showthread.php?t=1456793 on version 1.3.
so i will post pics, and do you think rogers would be able to fix this problem or would it cost a hell of alot of money?
I'm not convinced that it's LCD failure. LCD is working (in a strange way) and in my case touch is working as well. In my opinion it might be motherboard (or anything that controls LCD). I'm going to try changing radio, rom and kernel - maybe it will work. But I really need your help with the step by step guide I mentioned in my previous post.
ok, so what are you going to try and do, are you going to try and reflash a rom?
like i can try and give you instructions, but i need to know what you want to do.
EDIT: I have downloaded and tried to run the RUU for My rogers htc evo. it is installing the rom, stock radio, and what not. so when it is done i will update and post back if that worked or not.
UPDATE: Installing the new RUU did not work, the screen is still messed up im guessing its a hardware failure. im going to try to bring it into rogers and see if they will do anything to help me out.
Something new, now my screen is completely black (but i can hear that touchscreen and touch buttons are working).
@Shotgun4 - please let me know what you'll find out.
misiolin said:
@Shotgun4 - please let me know what you'll find out.
Click to expand...
Click to collapse
I Will do That.
Shotgun4 said:
I Will do That.
Click to expand...
Click to collapse
Thanks mate
My screen is once more pixelful
I don't want to start new topic so I'll ask here:
Could anyone please help me with going back to stock rom?
My LCD is still not functional so it'll be unusual guide.
1. I open cmd and run adb reboot bootloader command (with stock rom in PG86IMG.zip file)
2. Does phone starts in fastboot or bootloader? If fatboot I need to press power button right?
3. Now phone should check for PG86IMG.zip file, what should I press to accept flash?
4. Now few minutes for flash
5. And what button should I press to reboot?
Is there any easier way to flash stock rom without working LCD? with adb commands maybe? please help me guys
misiolin said:
I don't want to start new topic so I'll ask here:
Could anyone please help me with going back to stock rom?
My LCD is still not functional so it'll be unusual guide.
1. I open cmd and run adb reboot bootloader command (with stock rom in PG86IMG.zip file)
2. Does phone starts in fastboot or bootloader? If fatboot I need to press power button right?
3. Now phone should check for PG86IMG.zip file, what should I press to accept flash?
4. Now few minutes for flash
5. And what button should I press to reboot?
Is there any easier way to flash stock rom without working LCD? with adb commands maybe? please help me guys
Click to expand...
Click to collapse
Your in diagnostic mode. Hold down the power button for 45 seconds then press the camera button twice it should reset the phone.
Diagnostic Mode, never herd about it. I tried both with phone on and off, no luck :/. Anyone has idea what it might be? (I'll post picture once more http://img515.imageshack.us/img515/543/img20120225140835.jpg)
PS
I managed to reinstall my shipped ROM, but screen is still f*cked up ;(.
Guys I have a problem. Is there any way to switch on USB debugging without working screen? I need to s-on my phone and I cannot use adb without USB debugging. My touch screen and touch buttons are working though so maybe someone could make screenshots how to switch it on? I'm on stock ROM now.
Or maybe there is other method to use step 5 of this tutorial without USB Debugging?
And one more question, If my phone doesn't connect with computer in bootloader/fastboot, does it means that I have s-on?
As of late, my 3d turns on but nothing shows up on the screen. The capacitive lights turn on and it does the quick vibrate when you power it on. Other than that, it shows no life. It randomnly started doing this, does anyone have any ideas on how I can fix this? Any help is appreciated. Thanks.
b1gsby_02 said:
As of late, my 3d turns on but nothing shows up on the screen. The capacitive lights turn on and it does the quick vibrate when you power it on. Other than that, it shows no life. It randomnly started doing this, does anyone have any ideas on how I can fix this? Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Did this start happening after you tried flashing a specific rom?
valdesr11 said:
Did this start happening after you tried flashing a specific rom?
Click to expand...
Click to collapse
No, just did it after my battery died one day.
b1gsby_02 said:
No, just did it after my battery died one day.
Click to expand...
Click to collapse
Pull out your battery, put it back in, and try charging your phone for about 30 min without turning the phone on. Then try again. Report back.
Thanks.
valdesr11 said:
Pull out your battery, put it back in, and try charging your phone for about 30 min without turning the phone on. Then try again. Report back.
Thanks.
Click to expand...
Click to collapse
Will do thanks.
Additional info: When the phone is "on" my computer recognizes it, and I can tell it to boot into bootloader using adb. The phone is 100% stock, hboot 1.5 s-on. Also, after the phone is on, and I hit the power button, the capacitive lights turn on, and they shut off once I hit the power button again, as if the screen was being turned on, but it just doesn't display anything.
Also, is there anything I can do to possibly get the display back on. Something like put a stock ruu on my sd card, name it PG86IMG.zip, reboot into bootloader, apply the ruu and perhaps that would bring my display back on? Or is it more likely hardware related which I will have to take the phone apart?
Having the phone on the charger while off didn't change anything. Now I am flashing the latest stock ruu, while it's updating the phone's display SHOULD be on showing the status of the update, but it's not displaying anything. The update completed, the phone rebooted on its own, but again, the display never turned on. Not sure what to try now..?
b1gsby_02 said:
Having the phone on the charger while off didn't change anything. Now I am flashing the latest stock ruu, while it's updating the phone's display SHOULD be on showing the status of the update, but it's not displaying anything. The update completed, the phone rebooted on its own, but again, the display never turned on. Not sure what to try now..?
Click to expand...
Click to collapse
This happened to me when I flashed a incompatible kernel......now all you need to do is flash a Rom and also flash the boot.img from that ROMs zip using fastboot and you will be good to go.
mnomaanw said:
This happened to me when I flashed a incompatible kernel......now all you need to do is flash a Rom and also flash the boot.img from that ROMs zip using fastboot and you will be good to go.
Click to expand...
Click to collapse
Not sure how to do that when I can't even see anything on the phone.
b1gsby_02 said:
Not sure how to do that when I can't even see anything on the phone.
Click to expand...
Click to collapse
is your phone's bootloader unlocked with htcdev.com?
If you haven't unlocked your phone yet then I can't say for sure if flashing Rom and kernel will work or.not......
If you haven't unlocked , just use a RUU.exe and your phone should be working again unless its a hardware issue
mnomaanw said:
is your phone's bootloader unlocked with htcdev.com?
If you haven't unlocked your phone yet then I can't say for sure if flashing Rom and kernel will work or.not......
If you haven't unlocked , just use a RUU.exe and your phone should be working again unless its a hardware issue
Click to expand...
Click to collapse
Everything is locked, and I tried running the latest stock ruu and it completed everything, and my phone rebooted on its own after it was completed, and still the display won't come on.
b1gsby_02 said:
Everything is locked, and I tried running the latest stock ruu and it completed everything, and my phone rebooted on its own after it was completed, and still the display won't come on.
Click to expand...
Click to collapse
Might be a hardware issue I guess .....
mnomaanw said:
Might be a hardware issue I guess .....
Click to expand...
Click to collapse
Thank you for the quick replies.
If it is hardware related, what exactly would I need to fix/replace?
my evo ed screen show up anything help..
valdesr11 said:
Did this start happening after you tried flashing a specific rom?
Click to expand...
Click to collapse
i treid to flash a rom and my screen when black,i use(rom manager)..heeelllpp plzzz
I've been trying to find help for this problem and i just can't seem to find anything that actually works. I made an account for this website just so i could maybe get some help.
Well here's the story:
I tried to get CyanogenMod for my HTC One X+ device. I rooted my phone successfully but had a problem with installing CM. The installation got aborted everytime i tried to do so. The instructions said that i should flash boot.img so that's what i did. Well... then this problem happened The phone is stuck in the HTC logo when i try to power it up. I can access bootloader and clockworkmod recovery. I've tried almost EVERYTHING and it's still not working.
To be honest, i don't care about getting CyanogenMod to work anymore. I just want my phone working. Any suggestions what to do?
Just download a diffrent custom rom and install that then. Make sure to flash the boot.img for whatever rom you install...
As for your issue with cyanogen, are you installing the right version for your model of device? The HOX+ comes in two flavours. International, and the AT&T version (North America). The roms are not compatible, so AT&T roms wont work with internation devices and vice versa.
Sent from my HTC One X+ using Tapatalk
AndroHero said:
As for your issue with cyanogen, are you installing the right version for your model of device? The HOX+ comes in two flavours. International, and the AT&T version (North America). The roms are not compatible, so AT&T roms wont work with internation devices and vice versa.
Click to expand...
Click to collapse
Yes, i made sure that i have the right version.
AndroHero said:
Just download a diffrent custom rom and install that then. Make sure to flash the boot.img for whatever rom you install...
As for your issue with cyanogen, are you installing the right version for your model of device? The HOX+ comes in two flavours. International, and the AT&T version (North America). The roms are not compatible, so AT&T roms wont work with internation devices and vice versa.
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Wait, won't the AT&T Roms work on international but the "radio" wont be compatible? (A.K.A no signal/wifi..etc) ?
As for the main topic, I experienced this issue the first couple of times I flashed a custom rom but After that I just knew the process.
First you must make sure you factory wipe (Everything except "internal SD card" )
Then you flash the rom (Install zip file) using CWM
Then you wipe cache
Then you flash the boot.img using the PC's fastboot function.
However what do you mean by "the installation got aborted" ? Does it say "Failed" in red ? Or does it say "successful" or what?
If it says "Failed" in red , I have this issue with "zip md5 verification" when installing sense based rom on TWRP , so when I uncheck that box (I know that it should be enabled just to be sure the rom is correct..etc) and once its unchecked the rom installs fine. Maybe you have a similar issue?
Try redownloading the ROM again.
If it still fails as AndroHero said, try a different rom (maybe AOSP, AOSP + , AOKP ..etc.)
Best of luck mate Hope it works fine
Ghand0ur said:
Wait, won't the AT&T Roms work on international but the "radio" wont be compatible? (A.K.A no signal/wifi..etc) ?
As for the main topic, I experienced this issue the first couple of times I flashed a custom rom but After that I just knew the process.
First you must make sure you factory wipe (Everything except "internal SD card" )
Then you flash the rom (Install zip file) using CWM
Then you wipe cache
Then you flash the boot.img using the PC's fastboot function.
However what do you mean by "the installation got aborted" ? Does it say "Failed" in red ? Or does it say "successful" or what?
If it says "Failed" in red , I have this issue with "zip md5 verification" when installing sense based rom on TWRP , so when I uncheck that box (I know that it should be enabled just to be sure the rom is correct..etc) and once its unchecked the rom installs fine. Maybe you have a similar issue?
Try redownloading the ROM again.
If it still fails as AndroHero said, try a different rom (maybe AOSP, AOSP + , AOKP ..etc.)
Best of luck mate Hope it works fine
Click to expand...
Click to collapse
No that was the case with previous devices that had the same hardware using different radio frequencies. But as the AT&T version uses a dedicated Qualcomm radio chip, the two devices need diffrent kernels...
It's like when we used to have GSM/CDMA devices, there not compatible...
Sent from my HTC One X+ using Tapatalk
Ghand0ur said:
However what do you mean by "the installation got aborted" ? Does it say "Failed" in red ? Or does it say "successful" or what?
If it says "Failed" in red , I have this issue with "zip md5 verification" when installing sense based rom on TWRP , so when I uncheck that box (I know that it should be enabled just to be sure the rom is correct..etc) and once its unchecked the rom installs fine. Maybe you have a similar issue?
Click to expand...
Click to collapse
Well, it said something like this:
Finding update package...
Installing update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "enrc2b" | | getprop("ro.build.product") == "enrc2b"
E:Error in /sdcard/0/cm-10.1.3-enrc2b.zip
(status 7)
Installation Aborted.
Ok, i'm trying to do what AndroHero told and download a different custom ROM but how do i move the .zip file into my phone so that i can install it?
Jama96 said:
Ok, i'm trying to do what AndroHero told and download a different custom ROM but how do i move the .zip file into my phone so that i can install it?
Click to expand...
Click to collapse
Please read this topic (FAQ Thread) http://forum.xda-developers.com/showthread.php?t=2179337 Q15 explains thoroughly how you can add files to your SDCard in case you wiped your phone storage / have no ROM on the SDCard. Best of luck
Hi there i had the similar issue of bootloop on my At&t HTC One + , it has to do with boot.img that is the kernel. make sure u flash it after installing the rom. Try downloading other roms as well, Viper rom for international is also good. If you wipe everything from your phone , dont worry, goto recovery, TWRP and goto sideload option, and then through command prompt sideload your rom that you downloaded, install rom and then flash kernel boot.img. Enjoy.
I think i may have encountered another problem.
The bootloader says that the battery level is too low for flash even though i tried charging the battery last night. I'm not even sure if the battery is charging at all when i try to do so.
(Also, whenever the phone is turned off and is connected to a USB (either computer or for charging) it turns on automatically. When it's connected to a computer, it's impossible to turn off and when it's "charging" it turns on by itself every few hours.)
I need a higher battery level to flash stuff. What should i do?
Jama96 said:
I think i may have encountered another problem.
The bootloader says that the battery level is too low for flash even though i tried charging the battery last night. I'm not even sure if the battery is charging at all when i try to do so.
(Also, whenever the phone is turned off and is connected to a USB (either computer or for charging) it turns on automatically. When it's connected to a computer, it's impossible to turn off and when it's "charging" it turns on by itself every few hours.)
I need a higher battery level to flash stuff. What should i do?
Click to expand...
Click to collapse
First of all turn the phone completely off, meaning without booting to bootloader.
Put the phone into the charger over night, make sure its charging (you will find the red indicator lights up at the top of the phone)
If it boots up, hold down the power button until the screen turns totally black and make sure it doesn't "reboot" when you do that.
If you can't turn your phone totally off then you don't have any solution but to let it charge with the display is on. I know its bad for your phone but if you fail to turn it off, just let the screen on for a 4 hours (while you are awake) , should have the battery charged over 70% with the display on (Since the phone charges to 100% with screen off in 90 minutes).
But i think if you time it right you can just close it even while it charges.
Ghand0ur said:
First of all turn the phone completely off, meaning without booting to bootloader.
Put the phone into the charger over night, make sure its charging (you will find the red indicator lights up at the top of the phone)
If it boots up, hold down the power button until the screen turns totally black and make sure it doesn't "reboot" when you do that.
If you can't turn your phone totally off then you don't have any solution but to let it charge with the display is on. I know its bad for your phone but if you fail to turn it off, just let the screen on for a 4 hours (while you are awake) , should have the battery charged over 70% with the display on (Since the phone charges to 100% with screen off in 90 minutes).
But i think if you time it right you can just close it even while it charges.
Click to expand...
Click to collapse
It just keeps turning on if i use the power button to turn it off. I have to use the bootloader to turn it off.
Guess i'll have to charge it with screen on...
Jama96 said:
It just keeps turning on if i use the power button to turn it off. I have to use the bootloader to turn it off.
Guess i'll have to charge it with screen on...
Click to expand...
Click to collapse
Wait cant you do that? Open bootloader (hold down volume down while trying to boot up the phone) and go to "Fastboot" then "Power down" .. It should turn off
Ghand0ur said:
Wait cant you do that? Open bootloader (hold down volume down while trying to boot up the phone) and go to "Fastboot" then "Power down" .. It should turn off
Click to expand...
Click to collapse
Yes, i can turn it off from bootloader. I said i couldn't turn it off by using the power button.
Jama96 said:
Yes, i can turn it off from bootloader. I said i couldn't turn it off by using the power button.
Click to expand...
Click to collapse
Great so the charging problem is solved then ^^ Charge and try what we said in the first place and report back
Ghand0ur said:
Great so the charging problem is solved then ^^ Charge and try what we said in the first place and report back
Click to expand...
Click to collapse
Well it's charging but... EXTREMELY SLOWLY! (even when the phone is off)
Damn...
Well it's getting late. Hopefully tomorrow i'll get something done with my phone so i can finally get it to work.
Ghand0ur said:
Please read this topic (FAQ Thread) http://forum.xda-developers.com/showthread.php?t=2179337 Q15 explains thoroughly how you can add files to your SDCard in case you wiped your phone storage / have no ROM on the SDCard. Best of luck
Click to expand...
Click to collapse
YES! YEEEEEEEEEEEEEEEEEESH!
Guess what!?
That custom recovery me allowed me to install cyanogenmod!!!! I got it to work! YEEAAH!
Seems like the problem was in Clockworkmod recovery because it didn't allow me to install CM.
Thanks dude! And thanks everyone who tried helping me out.
Jama96 said:
YES! YEEEEEEEEEEEEEEEEEESH!
Guess what!?
That custom recovery me allowed me to install cyanogenmod!!!! I got it to work! YEEAAH!
Seems like the problem was in Clockworkmod recovery because it didn't allow me to install CM.
Thanks dude! And thanks everyone who tried helping me out.
Click to expand...
Click to collapse
Always glad to be of help
well jama96 you need to go in your display settings and set the back light turnoff timer, while on charge and while on battery i suppose that would solve ur problem.
Jama96 said:
YES! YEEEEEEEEEEEEEEEEEESH!
Guess what!?
That custom recovery me allowed me to install cyanogenmod!!!! I got it to work! YEEAAH!
Seems like the problem was in Clockworkmod recovery because it didn't allow me to install CM.
Thanks dude! And thanks everyone who tried helping me out.
Click to expand...
Click to collapse
Hi Ghand0ur,
I have an HOX+. I tried to install Cyanogenmod on it through CWM recovery. I ended up with the same problem as you (word to word). I first tried to install Cyanogen trough CWM but it gave me the same 'Error 7' message as posted by you, so then i installed boot.img file from PC using fastboot option. Since then my device it stuck in bootloop.
fastboot and CWM recovery still work (same as you) but the phone doesnt boot up.
Can u tell me how you finally managed to flash Cyanogen on your device?
Also, you mentioned that the problem was in CWM recovery. Which recovery did u use to flash Cyanogen (CWM or TWRP).
Did u install the boot.img first or the ROM.zip file first?
Hi guys.
Today at morning my phone stucked while i was talking with my friend. Then a strange problem appeared. If i lock screen or timeout itsell, my phone just doesnt wake even i hit all the buttons i just have black screen.
However i could connect it to computer, recieve notifications on notification light but screen just stays black.
First i did a factory reset, doesnt work, flashed a different rom it doesnt solve.
Now i could only use my phone until the screen locks itself also booting stage started to take hell longer with that problem maybe related i dont know.
I dont have a secondary phone to use dont know how to solve this problem. For temporal, i make screen timeout for ten minutes and everytime i had to unplug battery.
Thanks.
Stock rom or custom? Different kernels or mods added?
First go back to a fresh installation of stock rom to test if you have a hardware fault.
boomboomer said:
Stock rom or custom? Different kernels or mods added?
First go back to a fresh installation of stock rom to test if you have a hardware fault.
Click to expand...
Click to collapse
thank you for your anwser
was cm, now o stock.
i think ****ty thing is hardware related damn.
i flashed back o 4.0.4 after hitting menu button screen got light after 30 seconds... damn 4.1.2, 4.2.2 stock or cm only black.
If it does it on 4.1.2 stock, after full wipe then warranty repair required.
boomboomer said:
If it does it on 4.1.2 stock, after full wipe then warranty repair required.
Click to expand...
Click to collapse
will do. thanks.