Develop Bugs

[Q] Phone won't turn on! Vibrates and Green LED only

morning guys/gals,
last night i put my phone to charge, woke up this morning and turned on the screen and it said "no sim card detected, reboot device". Now when I rebooted the device all I get is 5 vibrates and the green led light stays on. Screen stays blank!!. I tried battery pull several times, tried vol-down + power but all I get is the vibration with the screen off and the led on.
When I hook my phone to the laptop I can't access it via fastboot/adb, it shows up as "Qualcomm CDMA Technologies MSM" with a yellow exclamation mark in the device manager. I tried forcing different drivers on it (e.g. adb composite, bootloader) but none let me access the device via cmd.
Now I got clockwork, running latest android revolution 2.0.8, device is radio-soff and eng-soff.
What am I to do now? Is there possibly a hardware fault? If I cant get to access to the device to restore it to stock, I'm going to struggle to get the device replaced, isnt it?
any help is very much appreciated!!!

What ROM were you running on it Prior to this happening?
was there any apps running in the background?
the Vol - + Power should get you into bootloader, if you cant get into bootloader I would be tempted to say fooked, and take it back to the shop as they wont be able to boot it either,, but thats the defeatist attitude...

lefty83 said:
morning guys/gals,
last night i put my phone to charge, woke up this morning and turned on the screen and it said "no sim card detected, reboot device". Now when I rebooted the device all I get is 5 vibrates and the green led light stays on. Screen stays blank!!. I tried battery pull several times, tried vol-down + power but all I get is the vibration with the screen off and the led on.
When I hook my phone to the laptop I can't access it via fastboot/adb, it shows up as "Qualcomm CDMA Technologies MSM" with a yellow exclamation mark in the device manager. I tried forcing different drivers on it (e.g. adb composite, bootloader) but none let me access the device via cmd.
Now I got clockwork, running latest android revolution 2.0.8, device is radio-soff and eng-soff.
What am I to do now? Is there possibly a hardware fault? If I cant get to access to the device to restore it to stock, I'm going to struggle to get the device replaced, isnt it?
any help is very much appreciated!!!
Click to expand...
Click to collapse
it sounds like a h/w fault, i had a simlar problem on my classic desire, turned out it was the 3rd party battery i bought that was at fault, yours sounds diffrent though hope you sort it out

darkenedhammer said:
What ROM were you running on it Prior to this happening?
was there any apps running in the background?
the Vol - + Power should get you into bootloader, if you cant get into bootloader I would be tempted to say fooked, and take it back to the shop as they wont be able to boot it either,, but thats the defeatist attitude...
Click to expand...
Click to collapse
ok very strange, I was playing i around with the phone, now if I pull the battery and connect it to the usb cable the light went red instead of green and it automatically booted in clockworkmod (thanks to the "bug"). vol down + power didnt get me there so once I was in clockwork I thought let me wipe battery stats (eventho I wiped them when rom was freshly installed). I thought the device is unplugged but the green light stays on (after full charge), maybe battery issue. Now after wiping battery stats I'm able to boot the device again.
Thats weird but hey atleast my device is back on track. Either faulty battery or some software bug, either way if anyone experiences a similar issues (phone wont boot, just vibrates 5 times and green led), just pull battery, connect phone to usb cable on your laptop or wallcharge and clockwork should boot up, wipe battery stats and u should be fine

You gotta love that ClockWorkMod recovery image

Hi
I had the same issue yesterday. After one hour of stress(I have DHD for 4 days), I finally find out solution which worked for me:
1.) pull out the battery from phone for at least 10 minutes.
2.) connect phone to the charger.
3.) pull battery to the phone and wait
4.) after orange light recovery should boot up.
5.) wipe battery stat.
6.) enjoy your phone again.
Hope this will help to somebody .

May I know why such incident occured?

thermoska said:
Hi
I had the same issue yesterday. After one hour of stress(I have DHD for 4 days), I finally find out solution which worked for me:
1.) pull out the battery from phone for at least 10 minutes.
2.) connect phone to the charger.
3.) pull battery to the phone and wait
4.) after orange light recovery should boot up.
5.) wipe battery stat.
6.) enjoy your phone again.
Hope this will help to somebody .
Click to expand...
Click to collapse
my phone doese not turn on, when i press the volume - with power button, green light blinks. would not go in to recovery mode. when only power button is pressed it vibrates three times and amber light flashes.
please help

ray00136 said:
my phone doese not turn on, when i press the volume - with power button, green light blinks. would not go in to recovery mode. when only power button is pressed it vibrates three times and amber light flashes.
please help
Click to expand...
Click to collapse
Having the same problem and wiping battery stats isn't working for me! See here for more info on my problem!

thermoska said:
Hi
I had the same issue yesterday. After one hour of stress(I have DHD for 4 days), I finally find out solution which worked for me:
1.) pull out the battery from phone for at least 10 minutes.
2.) connect phone to the charger.
3.) pull battery to the phone and wait
4.) after orange light recovery should boot up.
5.) wipe battery stat.
6.) enjoy your phone again.
Hope this will help to somebody .
Click to expand...
Click to collapse
Thanks for your reply! this worked for me, allmost.
I did however had to press the Power button ONCE to start the phone.
- Plugged in charger, pulled in battery, (orange light was turned), then after 25 sec I pressed the Power button - and Voila! My Phone started as normal.
I diden't need to do any "Wipe battery status", but after reading about it I did it anyway. It was'nt necessery though in my case.
THanks a lot you guys for your replys! I thought for sure my phone was dead.

try sptool to format your phone except the boot loader then try to flash the phone, if its not working then change the mother board !!!!!

Desire Z wont power on :(

Hey guys,
Running ILWT CM7. Flashed about two weeks ago. My phone has been working fine except for the past few days where it's been constantly freezing, requiring a battery-out and turn on, and rebooting on it's own.
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. After ~25minutes, I took the battery out and tried again.
Phone seems completely dead, won't respond to power on, volume down and power on, no lights come on when charger cable is plugged in. When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
Tried leaving battery out for 30minutes and trying again, but no luck.
Any suggestions?
Cheers!

Stuck in RUU mode?
Kaph said:
Hey guys,
...
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. ...
Phone seems completely dead ... When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
... Any suggestions?
Cheers!
Click to expand...
Click to collapse
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall

catherall said:
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall
Click to expand...
Click to collapse
Thanks for the help
When plugged in with the USB cable -> computer, I still get no response from the phone itself. Screen doesn't turn on, still seems dead. My laptop still says "Installing device driver software" to no avail, and phone is still dead. No lights, screen is off, nada. As though it was powered-off.
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.

Remarks
Kaph said:
Thanks for the help
My laptop still says "Installing device driver software" to no avail, and phone is still dead
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.
Click to expand...
Click to collapse
Windows seems to need a driver installation for using fastboot. Did you try to automaticall install device driver software? Have you installed HTC sync on your Windows computer?
When your device does not respond at all, and even refuses to connect in fastboot, then nobody can tell that you have been rooted.
Best regards,
Catherall

Sounds like your EMMC is fried, as of now I don't think there's a solution other than sending it back. Many say HTC accept and fix it even though it is s-off
Sent from my HTC Vision using XDA

did you get this worked out? i had a similar problem, ended up booting into fastboot by holding the trackpad and the power button, then just selected reboot and my phone powered on like nothing had happened, i was running the same rom.

Hey, did you alreasy tourned your phone to the fastboot mode?
Or does your device still have a black screen during boot?

I rooted this phone and when I was done trying S-OFF, phone would not respond to anything. It would only blink the orange notification light when I pressed Power and Vol+, or it would stay steady green with both Vol keys and Power. But the phone screen would never turn on. So after trying for hours to figure it out. I finally took the battery off, plugged the phone held pressed the power button and then put the battery in place the phone finally turned on and it worked. I turned the phone off again and it was doing the same issue. So I did the same step but this time with power and vol- to get in the bootloader and changed the hboot version to Desire Z. After that phone works perfectly, turns on and off with out any issues.
I did have to try the trick a couple of times idk why but it would work once in a while not everytime i tried it. Hope this helps anyone who also ends up with a similar issue.

[Q] Phone won't boot. Vibrates three times. Need advice.

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!

[Q] I can't access Bootloader or Recovery PLEASE Help!

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.

Self-Bricked Note 8 Pro, no access to it

Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome

afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?

wenyendev said:
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
Click to expand...
Click to collapse
They can’t boot….adb only works when booting or booted, and if it bootloops, they won’t have time to pull their data.

afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Bootloader locked or unlocked?

Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.

Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/

Unfortunately, USB debugging was not enabled. I stopped developing for Android quite a while back now, and I don't turn on USB debugging anymore.
@Arealhooman My bootloader is locked... I tried unlocking it with MTKClient, but no success since the phone reboots during the process.

wenyendev said:
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Click to expand...
Click to collapse
This helped a lot actually!
It seems that the power button got faulty and got constantly pressed, making the phone constantly hard-rebooting itself.
I have a piece of paper preventing the buttons from contacting the motherboard, and the phone stopped rebooting when charging!

Ingenious method. Glad you solved the issue.

I enabled USB debugging to be able to reboot into fastboot / bootloader without the buttons (since my piece or paper prevents all the button from working xD)

wenyendev said:
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Click to expand...
Click to collapse
Only custom. Stock doesn’t support it.

Bro first check if your power button is working fine, if it is being pressed by any hardware issue it can happen, and when you fastboot try flashing recovery within that time fastboot remains.