Root unlock problem - HTC Desire 500

My HTC Desire 500 had a broken battery (it was swollen up) and the phone wouldn't stay on for more than a few minutes without having it plugged in, but it worked as long as it was plugged in. Now that I changed the battery it stays on without having to plug it in but it won't get past the logo screen when I turn it on. I kept restarting it, I did a factory reset, I let it sit like that for an hour and it still wouldn't get past the logo screen. Sometimes (1/10 chance) when I boot it from HBOOT in RECOVERY it gets past the logo screen but the WI-FI doesn't work and errors keep popping up. I also tried it with the old battery to see if it would work like it did before but it doesn't, it gets stuck at the logo screen.
For the past few days I've been trying to root it and reflash the ROM but I am unable root it because when I get to the part where I have to type the command fastboot oem get_identifier_token it doesn't return anything it just says "Waiting for device". I've looked this up on google and it seems to be a driver problem, I've installed and unistalled all the possible drivers over and over, tried it on both my laptop and my desktop (both Windows 10) but the desktop/laptop still doesn't recognize the phone when it is in fastboot usb mode (It did recognize it when I managed to boot into the Android OS though, as I could get photos from it). Any advice would be greatly appreciated.

Related

[Q] Strange Reboot Loop, searched forum Not Addressed

Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD

[Q] Bricked? Stuck on either white AT&T screen or grey, frozen battery screen, no USB

[Q] Bricked? Stuck on either white AT&T screen or grey, frozen battery screen, no USB
While trying to install Cognition v2.2b3 via Clockworkmod (from stock at&t 2.1 froyo) something happened mid-install and my phone ended up rebooting, and I have not been able to turn it on since.
-When attempting to power on normally, phone shows white AT&T screen and hangs there
-When attaching USB, phone shows battery screen but battery is all grey and rotating progress icon is frozen. Does not appear to be charging.
-Computer does not recognize phone in any state. Latest USB drivers are installed and I have had no issues connecting via USB previously.
-Cannot get into download or recovery mode using any volume/power button combination or through adb. Also tried attaching USB with ODIN running while attempting button combinations, inserting/removing battery etc, still nothing.
Has anyone else experienced this? Anything else I should try?
Louros said:
While trying to install Cognition v2.2b3 via Clockworkmod (from stock at&t 2.1 froyo) something happened mid-install and my phone ended up rebooting, and I have not been able to turn it on since.
-When attempting to power on normally, phone shows white AT&T screen and hangs there
-When attaching USB, phone shows battery screen but battery is all grey and rotating progress icon is frozen. Does not appear to be charging.
-Computer does not recognize phone in any state. Latest USB drivers are installed and I have had no issues connecting via USB previously.
-Cannot get into download or recovery mode using any volume/power button combination or through adb. Also tried attaching USB with ODIN running while attempting button combinations, inserting/removing battery etc, still nothing.
Has anyone else experienced this? Anything else I should try?
Click to expand...
Click to collapse
Go into Download mode, hold both volume buttons down and plug your phone into USB. If it doesn't work than pull the battery and try again.
If that doesn't work keep trying until it does. I'm serious, it took me like 40 tries last night to flash stock with the 1 click and then finally get cognition running (that only took one flash)
Odin is a piece of crap, it works maybe every 10th time for me. I've never used the rom manager to install roms, always use clockwork recovery. Less to go wrong if your in recovery mode I suppose.
But literally just keep trying until it works o.0
Hi. I've experienced exactly the same this night. Try this: forum.xda-developers.com/showthread.php?t=775911 it helped instantaneously.
BTW, you really need to wait at least 10 secs after removing battery.
I have the exact same problem.
My battery screen shows up with nothing but a flash loading icon and a grey battery. When I simply turn my phone on its stuck in ATT boot screen. I tried the instructions many times trying to get into download mode but right when i put it in the battery while holding down up/down/power it simply just shows the "frozen battery charging" screen again.
HELPP

[Q] Was stuck at TAMPERED screen, restored factory settings and now appears bricked

Hey everyone,
So my friend’s HTC One was having some troubles, he said out of no where it got stuck in the ‘TAMPERED’ screen and he didn’t know what to do. Now he definitely didn’t try to root it or anything like that, it is completely stock. So yesterday he gave me the phone so I could take a look at it. The battery was dead when I got it so I plugged it in and got the red notification light to say it’s charging. A little while later I attempted to turn it on, surely enough I was shown the ‘tampered, locked, security warning etc.’ screen. So I wasn’t really sure what to do from there, I tried to see if I could get into the recovery mode but it just seemed to power down. I booted back up and went to the restore factory settings option, it showed me a progress bar for a bit but powered down again. Now it appears to be bricked… When I plug it in I don’t get the red notification light anymore and I’ve tried holding vol down + power again and again to no avail. I also tried the bright light trick.
If anyone has any ideas on what I could try next I would really appreciate any help at all.
Thanks guys.
the tampered screen wont appear out of nowhere, he must have tried a custom recovery, kernel or something.
IINexusII said:
the tampered screen wont appear out of nowhere, he must have tried a custom recovery, kernel or something.
Click to expand...
Click to collapse
From a bit of googling around I saw some people that let their phones' batteries die completely flat and were faced with the tampered screen when they turned it on again so I guess this is what happened to my friend. I'm sure he didn't try anything custom.
Here are two examples:
http://support.t-mobile.com/thread/60279
http://forum.xda-developers.com/showthread.php?t=2433477
What happens when its plugged the PC. Does it show up at all or does it show QHSUSB_DLOAD. If it does show that, then it is bricked and only a motherboard replacement will bring it back to life. If not then charge the phone for 24 hours. dont mess with it, then holding POWER + VOLDOWN (phone under a bright light,) after about 5 seconds, buttons should start blinking, and after 20 to 30 seconds, phone should reboot or you may at least get into bootloader.
you may need to try 2 or 3 times, to get it to work.
bored_stupid said:
What happens when its plugged the PC. Does it show up at all or does it show QHSUSB_DLOAD. If it does show that, then it is bricked and only a motherboard replacement will bring it back to life. If not then charge the phone for 24 hours. dont mess with it, then holding POWER + VOLDOWN (phone under a bright light,) after about 5 seconds, buttons should start blinking, and after 20 to 30 seconds, phone should reboot or you may at least get into bootloader.
you may need to try 2 or 3 times, to get it to work.
Click to expand...
Click to collapse
How can I check for QHSUSB_DLOAD? Install the HTC Sync and HTC drives then adb devices or something?
RoBz18 said:
How can I check for QHSUSB_DLOAD? Install the HTC Sync and HTC drives then adb devices or something?
Click to expand...
Click to collapse
You must have HTC drivers installed anyway. Download and run HTC sync and let it complete. then just uninstall HTC Sync. The drivers will remain.
You must also have adb and fastboot setup on your PC. I take it you are set up for those
bored_stupid said:
You must have HTC drivers installed anyway. Download and run HTC sync and let it complete. then just uninstall HTC Sync. The drivers will remain.
You must also have adb and fastboot setup on your PC. I take it you are set up for those
Click to expand...
Click to collapse
Ok so i got the drivers, adb and fastboot installed. I plugged in the phone and in device manager it is showing QHSUSB_DLOAD under other devices. So for sure now this thing needs a motherboard replacement? Have you ever heard of a phone getting bricked from the restore to factory settings option? Seems a bit strange to me.
I just called my friend to double check with him that he didn't try anything custom...he had no idea what I was talking about so it's definitely all stock here. Why on earth would a factory restore cause a brick? Would I be right in saying that HTC should replace this for free...?
There is no factory restore option. Only factory reset.
Keep out plugged in over night and then tomorrow keep trying to power on with a bright light. It should turn up
sent from my mobile device

HTC One Continuous Reboot / com.htcdialer error

Hello everyone -
The other day, I came home from work and noticed that my HTC One (M7) lost mobile data / connectivity for no reason. I thought it was just a fluke, so I restarted the phone.
From that point on, I noticed it wasn't a normal issue. I kept getting a com.htcdialer error / not responding and the phone would restart all the time. Now I'm stuck in a continuous reboot - sometimes w/ the error & sometimes without.
The weird part is that sometimes I'll get my mobile connectivity back and the phone will work. Sometimes it will work for a few hours, sometimes for a few seconds, other times not at all.
I've tried wiping the cache partition, factory resetting a few times, and even getting a new SIM Card. Nothing works. Is this a hardware issue? FYI this is a refurbed M7 that I got as a replacement from AT&T for my previously, defective One.
Unfortunately, I can't get the phone info. When I run getvar all I get <waiting for device> in the CMD prompt. Turned off fastboot, turned usb debug on, still doing it.
dgolpashin said:
Hello everyone -
The other day, I came home from work and noticed that my HTC One (M7) lost mobile data / connectivity for no reason. I thought it was just a fluke, so I restarted the phone.
From that point on, I noticed it wasn't a normal issue. I kept getting a com.htcdialer error / not responding and the phone would restart all the time. Now I'm stuck in a continuous reboot - sometimes w/ the error & sometimes without.
The weird part is that sometimes I'll get my mobile connectivity back and the phone will work. Sometimes it will work for a few hours, sometimes for a few seconds, other times not at all.
I've tried wiping the cache partition, factory resetting a few times, and even getting a new SIM Card. Nothing works. Is this a hardware issue? FYI this is a refurbed M7 that I got as a replacement from AT&T for my previously, defective One.
Unfortunately, I can't get the phone info. When I run getvar all I get <waiting for device> in the CMD prompt. Turned off fastboot, turned usb debug on, still doing it.
Click to expand...
Click to collapse
it could be a hardware issue ..
to post your fastboot getvar all you do it from the bootloader with fastboot USB showing on the screen
to get to the bootloader / power off / hold volume down + power / then go to fastboot with the usb attached to the PC
clsA said:
it could be a hardware issue ..
to post your fastboot getvar all you do it from the bootloader with fastboot USB showing on the screen
to get to the bootloader / power off / hold volume down + power / then go to fastboot with the usb attached to the PC
Click to expand...
Click to collapse
That's exactly what I did, and I just get <waiting for device>. Maybe I'll try it at home instead of at work.
If it's a hardware issue, could you guess as to what it would be? Perhaps the SIM reader? Mobo?

OS Boots to black screen? Anyway to recover data?

Hi all, forgive me if this has already been asked in some form.
My girlfriends Verizon Moto X lost battery one day while she was playing a game. After she charged and tried booting again, it just booted to a black screen. It still runs through the full boot animation. Weirdly enough, active display will still show her information (and can be interacted with until unlocked), and holding power will bring up a power menu for shutdown. The camera gesture also works to launch it, but you can't interact with anything at all. Safe mode provides the exact same issues.
She is running the latest 5.1 update and is fully stock. She also does not wish to root or flash a custom recovery.
I have tried to pull the data, which windows recognizes as a media device, but shows empty when clicked on. OSx immediately says that the storage can not be accessed over android file transfer. I plugged it in for ADB but ADB won't seem to find it when its turned on. It is recognized in fastboot though. I also wiped the cache via the stock recovery, but that didn't help.
I believe a factory reset will be the solution to the black screen, but she has a bunch of photos she would really like to save. Is there anyway for me to actually get them off of the phone? If she can get those, I can get it factory reset for her no problem.
Thanks for any advice!
The exact same thing has happened to my girlfriend's phone as well and I'm also looking for a solution to recover the data. Moto X (2014) Pure, 5.1
The device boots. The Motorola boot animation plays all the way through, the screen brightness dims slightly as normal, and then the Amber Alert from the previous night vibrates the phone several times and displays over a fully black background. There are no soft buttons and no status bar. The home screen appears not to have loaded (yet?)
Attempts to click "OK" to close the alert fail.
The phone is hot. It is working hard. Something stuck in a loop?
The power button will bring up the "Power Off" prompt with no issues. The animation plays smoothly and the phone can be powered off as normal. The phone is able to recognize touch input here.
Calling the phone while it's on will play a ringtone. It is receiving calls.
Plugging the phone into a computer will show up as an MTP device. However, there are no contents listed.
Sometimes, the phone will prompt that the "System" process is not responding and will ask to close it. This has no effect.
Booting into Safe Mode has no effect.
Clearing the application cache from recovery mode has no effect.
I have a CSE degree but absolutely no Android experience. Forensics on a NAND dump or something like that isn't out of the question, unless it's not possible. Hope you're able to get some help.
Edit: Some other threads with the same issue:
http://forum.xda-developers.com/mot...-screen-to-recover-data-t3168103#post62117413
http://forum.xda-developers.com/moto-x-2014/help/black-screen-boot-t3161110
https://www.reddit.com/r/MotoX/comments/3cf4gr/51_black_screen_after_turning_on/
https://www.reddit.com/r/MotoX/comments/3aqr95/moto_x_2nd_gen_black_screen_after_update/
https://www.reddit.com/r/MotoX/comments/383ej6/black_screen_on_startup/
I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
Update?
Hello,
I am having this issue as well.
Unfortunately I am unable to perform any form of factory reset, the bootloader also just brings me to the black screen and I am unable to use soft keys. The kicker for me is that I cannot connect to my PC with a working USB. I used to have that available and now no device is recognized.

Categories

Resources