Hey,
The issue is that the screen is blank and goes on a boot loop because the volume down button on the volume rocker is continuously pressed.
Because of which the phone doesnt allow android revoluntion to boot at all..
Always goes to the HBOOT menu from which if i click the power button it goes into bootloader mode but windows shows
QUALCOMM CDMA driver instead of the correct drivers.....
it doesnt show the correct driver.
Then i tried adb after removing the battery again.
i typed
adb devices
(once it found the devices)
adb shell
recovery.
now the screen comes alive and shows my 4ext recovery console.
The biggest problem here is the volume button not allowing me to boot into a ROM.
Is their a way to disable that or is it something else that i have done that i am not even able to revert to stock rom in
BOOTLOADER mode??
I thought it was a SLCD because i saw this post
http://androidforums.com/desire-all-things-root/215886-solved-desire-slcd-black-screen-bricked.html
But i realised that the above was for Desire and NOT of DHD.
I cannot even see the HBOOT menu. I somehow managed to get to the recovery becos of the shell command by adb.
What am i to do??
Can someone please help?
Moderator can close this Tread
I fixed it....everythings in working condition now...
I just took a twesers and removed the volume rocker from its housing by pulling the cable under the manufacturing sticker.
And then suspected that putting it back in its place would make it go back to the same state again but i hasnt for now...
It wasnt showing the HBOOT menu as the volume down button was constantly pressed instead of being released.
I wish i would have just done it sooner but anyways phewww.....
Related
Phone seemed fine until earlier when the volume just decided to go right down and it started vibrating. I restarted it and now I'm stuck at recovery as the volume rocker seems to be stuck from the inside. The rocker switch seems to work ok but it's as if the volume is stuck in the down position so that whenever I get into the recovery menu, the cursor just goes loopy as if the vol down is being held.
Has anyone heard of such a thing before and recovered from it or is it a warranty repair job?
Also, any tips on how to RUU the handset in this state?
Any help greatly appreciated.
you can run a RUU while in fastboot mode.
since vol down is constantly pressed i dunno if you will be able to get into it.
try switching phone off, then switching it on pressing BACK + POWER buttons
hopefully this will boot into fastboot rather than bootloader.
if succesful, just plug your phone with a usb cable to PC and run the RUU.exe
A friend has asked me to look at his Wildfire, he said it was updating the Market and then blank screened. Since then it will not turn on, vibrates, then nothing.
I suspected screen (replaced a few wildfire ones now) but no sign of life from touch buttons, volume key, etc - so suspect it is bricked.
Tried to flash it with RUU but the phone will not go into the boot menu via volume down & power on. I've tried numerous times and it went into boot menu once, but you could not select anything, no keys working.
Hooked up to laptop and laptop could see it, but when you try to run the RUU you get Error 170, probably becaused it's not actualy in USB Boot mode.
Has anyone seen this? Any other tricks to get it into boot menu? Anything I can run from laptop or SD card to force it into a recovery or boot menu?
This is a stock ROM phone, not modified at all.
Any help much appreciated*
I have a way but I cant remember it lol
If I can remember when I get home, i'll re-post.
OK, cool
Made slight progress today, even though I had the boot menu come up once yesterday, but no response from keys, I did notice that even though I was trying to access boot menu, it was actually acting like it was in the menu, just blank screen, i.e. if I held power button afterwards I got no vibration, but if I did pull battery and hold power, I did, as if it was booting up.
I wonder if in actual fact the screen is dead, but also there is a software hang up, as if display was dead, you would still be able to swipe the screen, get touch keys to light up when pressed, etc.
Anyway, so I went into boot mode, blank screen, pressed power anyway which would be FASTBOOT - right?
Hooked up to PC, ran an RUU and it connected OK, went through process but failed on ID, because the phone has a T-Mobile ROM and I was trying to flash with non-branded one.
So I either need to find a T-MOB UK RUU, I found one but it wouldn't run, or I need to create a goldcard (can I do that with a semi bricked device?) and go down that route.
Either way, I'm pretty sure the LCD is dead, so for the sake of £7.50 I'll replace that first, even if it has got further issues, having a working LCD will help!!
yeah get the screen fixed first.
you will only have to fix the screen later and the hassle of trying to fix a phone with broken screen, to have to have it fixed later anyway isnt really the most logical way of doing things
My G2 won't boot normaly and is acting very straingly. I did a search of other similar problems people have had, but nothing matches what is happening to mine. It started when I noticed my power button and volume up button stoped working. I assumed it was a glitch and thought a reboot might help. Since the power button wasn't functioning, I pulled the battery to reboot it. That's when it stoped working. When I turn it on normaly with the power button, the screen stays off, it vibrates three times, and the led blinks orange untill I put the battery. If I attempt to boot into recovery with the button combination, it does the same. If I attempt to boot into HBoot, it vibrates five times and the led lights up solid green. Here's where things get realy strange. When I plug the phone into the charger while the phone is off, after about five seconds the phone comes on into the recovery bootloader even though when I boot while holding the buttons it dosn't work. I have the ClockworkMod touch recovery installed. From within the recovery I have full access to everything including ADB with root access. When I select the reboot option from recovery, it does the same thing with the vibrating and the blinking led. I tried the key test in the recovery and I discovered that my volume up button only works intermitently and my power button seems to be working fine. I haven't attempted to flash a new rom yet because I'm assuming it must be something else since I can't even access HBoot, and I'm scared if I touch anything I'll loose access to recovery and ADB as well.
Any advice? Could a damaged volume up button contact cause all this to happen? Should I try flashing it from recovery even though I can't access HBoot?
Thread moved to Q & A section, post in the relevant section next time.
in adb try
adb reboot-bootloader
demkantor said:
in adb try
adb reboot-bootloader
Click to expand...
Click to collapse
Just tried it. Screen goes black, vibrates three times, and led blinks orange untill I pull the battey. It was a good Idea though, I didn't think to try that myself.
you know what, are these very quick vibrates? you mentioned there is a problem with your volume rocker (sticky keys?) your phone may be trying to get into the jtag/download mode.
not sure how to use this mode on the vision but tell me if this is the same response you get.
take out battery, hold both volume buttons, plug phone into computer.
it should vibrate three times rapidly and computer should look for driver :
Qualcomm CDMA Technolgies MSM driver
not sure where to get the proper driver for the vision but ive used this mode to root other android phones and i know there is a "unbricking project" for various phones that use this mode.
nothing for the vision that i know of though.
but being you have adb access maybe test a few things first like see if anything is accessible from your emmc
type:
Code:
adb shell
dmesg | grep mmc0
and see what happens
edit:
i can replicate you situation by holding volume up while powering on
you have a stuck volume up key, almost 100% just open up phone and clean it out and you should be just fine!
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.
I tried to flash a kernel s-on from recovery and now my screen won't turn on. I can hear notifications and even took a call but I can't see anything on the screen. I have a nand backup but I am having trouble accessing bootloader or recovery. I was using Dirty Underground rom I believe so I'm not sure if USB debugging was enabled. I currently only have access to a Mac computer. When I hold down the power button the notification light keeps blinking and the phone stays on, when I hold down power + volume down nothing happens, and when I hold down power + volume up it just reboots briefly showing the splash screen with red text and bringing me back to my black/dark gray screen. If anyone could help me get my phone back to working order I would be extremely grateful. Thanks for reading my post
welshwarriorsf said:
I tried to flash a kernel s-on from recovery and now my screen won't turn on. I can hear notifications and even took a call but I can't see anything on the screen. I have a nand backup but I am having trouble accessing bootloader or recovery. I was using Dirty Underground rom I believe so I'm not sure if USB debugging was enabled. I currently only have access to a Mac computer. When I hold down the power button the notification light keeps blinking and the phone stays on, when I hold down power + volume down nothing happens, and when I hold down power + volume up it just reboots briefly showing the splash screen with red text and bringing me back to my black/dark gray screen. If anyone could help me get my phone back to working order I would be extremely grateful. Thanks for reading my post
Click to expand...
Click to collapse
Hold Volume UP + Power button for 10seconds, device will boot then, then immediately press Volume DOWN + Power Button to enter Fastoot.
Connect phone to PC, open command prompt and change directory to adb folder. Type in fastboot erase cache then fastboot reboot to see if it helps. If it doesn't, repeat process to enter bootloader then go into recovery and reflash.
What Kernel did you try to flash? ElementalX?
If you have adb access then just plug in your phone and type "adb reboot recovery". Then restore your backup or push a working kernel to your phone to flash.
Sent from my killer M8.