When i enter recovery mode ADB will not list my phone, it lists it just fine however when my phone is on.. anyone have a idea?
I know it sounds stupid but make sure you have debugging mode on. Also when you mount your device (while its turned on) select the sync mode on your phone. I had to do that and then just play with it while loop is running pull the battery while usb is still plugged in and then power back on while holding volume down. I had to do that over and over and it eventually caught it.
I have debugging mode on, and while it is turned on and mounted as a disk drive ADB will recognize it. Ill try switching it to sync instead of disk drive.
Yeah it should recognize while in disk drive mode but it did not for me one time until I switched to sync. Could have just been a weird fluke but maybe not.
So you switched it to sync instead and while it was trying to sync you pull the battery out and hold the volumn down and the power button then put the battery back in? it will not catch it when i do this!
Not exactly. I switched it to sync and then let it do its thing for a minute. Then I powered off started running loop and powered back into recovery. Your computer shoukd make a little beep sound and the loop might hang up a bit when recovery loads. I then took the battery cover off and pulled the battery (loop still running and usb still plugged into phone) then hold vol down and put the battery back in. It will load into the boot loader from there you select recovery. I had to do that about a dozen times and finally it just caught on and showed my device in the loop as recovery.
Ill try this and post what happens thank you !
So far no luck, my computer will confirm that the phone is connected (by playing the sound confirmation) however it does not seem to be catching within windows or ADB
A thought occurred to me about this ... A couple people have said that it started working for them when they had a new/freshly installed microSD card in their phone. The card that comes pre-installed in the phone has doubletwist on it, including an autorun file. I noticed that until I removed these things from the memory card, Windows was identifying the card as "Media sync powered by doubletwist" or some crap like that. I took all that junk off and it started identifying it as just "Removable Disk." Now, I took off all this before I tried the rooting process, so I don't know if it would've caused any problems. Could it be that this has something to do with it? It doesn't seem likely to me, but I thought I'd mention it.
At any rate, try a new or freshly formatted SD card, see if that helps.
Restarting over and over again finally made it work. now have a fully rooted slide.
Just curious did you restart you phone or your computer over and over again?
Related
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
tlglegacy said:
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
Click to expand...
Click to collapse
Something worth trying:
1.You could take out the battery for one minute or longer.
2.Now put the ROM's .nbh on your SD card [Make sure it is named "RHODIMG.nbh" (no quotes)].
3.Put the SD card and battery in and press/hold Power button and the Volume Down button at the same time.
4.That'll put you in Bootloader Mode, and it should ask you if you want to update your phone's image (something like that).
5.Follow the prompts and it should start flashing (you'll see the bar).
6.Soft reset after the flash says it's complete.
I once went through that and this is what I did. I was able to unbrick my phone.
However, (back in September/October) there was another instance of the same thing happening to someone, but he never got it fixed; he did get the stock ROM and SPL back on it, but had to return it to HTC because it still kept cycling into Bootloader.
Good luck!
My case
The battery was drained yesterday (is not the first time) and ever since then, it won't get pass the window screen in the beginning. It would immediately shuts off after the window screen appears.
I am able to get into tricolor screen
When connecting to the computer, it would restarts instead of shutting off.
Tried:
Reinstalled Hardspl, radio and window rom - didn't help
Any pointers?
beely said:
My case
The battery was drained yesterday (is not the first time) and ever since then, it won't get pass the window screen in the beginning. It would immediately shuts off after the window screen appears.
I am able to get into tricolor screen
When connecting to the computer, it would restarts instead of shutting off.
Tried:
Reinstalled Hardspl, radio and window rom - didn't help
Any pointers?
Click to expand...
Click to collapse
Recharge the battery using any External Charger (called universal charger)
Then, put battery back into your kaiser. Keep Camera Button pressed and insert USB Cable (remember you must have sim card and SD card removed). Then Disable USB in activesync and flash with default HTC rom
I was able to install the stock rom.
The phone only load up on one occasion with the following things are met:
sd card removed
connected to computer or charger
and hold onto reset button for 3 seconds
It won't load in any other way.
THe next thing I did was to install an android kernel.
I was able to get into linux with the above items are met.
In the linux screen, I try install the SD card in while it was "waiting for a SD card" <- not sure if I should be even doing this, the phone will immediately shut off.
Could this mean my SD card became faulty? Window is still able to read it via a card reader.
Any help would be appreciated.
As I understand from this thread;
http://forum.xda-developers.com/showthread.php?t=2118259&page=8
you can't get out of APX mode. Well, I did. Maybe my phone wasn't in proper APX mode, or maybe I'm confused as to what APX mode is, anyway I thought I'd share in case it can help anyone.......
Here is my original problem;
http://forum.xda-developers.com/showthread.php?p=51066504
As it says, I replaced the battery and the power flex cable (which I broke during disassembly). When connected to Windows it made the connect sound, and 'USB Device not recognised'. I pressed and held the power button and heard the sound again, nothing else changed. Went into Device Manager, it said APX device.
I searched and read through the above linked thread. Felt gutted.
I decided to run the battery charging script again (originally tried it before opening up the phone). It was running for about 5 min (with no progress) when I thought I'd try pressing and holding the power button again. While I was reading a thread, I kept pressing and holding the power button, and releasing when I heard the windows connect sound, then pressing and holding again. After about 5 times doing this, the phone just booted up normally! Everything was fine, all ok, all my stuff (texts, call logs, apps, media etc..) was all there
After charging it to 100%, I went into recovery (TWRP) to check it was all working ok. I was asked for a password, searched the forums briefly for it, will sort this after I post this thread. It couldn't see the sdcard, or mount, but this is related to the password problem I think.
Now, when I went to reboot, system, it said no OS installed. I rebooted anyway, and when it booted up it was like a fresh rom install. All my apps, texts etc... were gone, but my media was all still there.
Soooo, I'm pretty chuffed my phone is back! Does anyone know why my phone was reset just by going into recovery?
And i have read that you are back in apx. It's a shame we have to repeat it over and over. APX is a hardware failure which can't be 100% fixed. As you see now it kicks back in, the phone will never be reliable again.
Sorry mate.....wish it would be different for you ......
Cheers.
Today hasn't been one of the better ones this week. Putting aside my pride for a moment, here's what happened. In my frustration, I threw my phone into a cardboard box. Aiming for the side of the box...it ricocheted of the floor then the side. Yeah, not the best available option to vent!
So...screen spiderwebed and the screen will no longer turn on. Phone vibrates when the power button is used, yet screen is blank.
I'd like to ask for help for the following:
Retrieve several important files that weren't back yesterday: Pictures & program files not synced for privacy reasons, plus TWRP backup from a couple of days ago to internal memory b/c SD full.
Screen damage or more involved? To determine if I spend time fixing or buying a replacement phone.
Phone is the Canadian Koodo T989D running CM11 8/04 with TWRP 2.7.1
Phone Symptoms:
After removing and replacing battery
Pushing power button - Normal 'turning on' short vibrate, screen doesn't turn on (no light/pixels light up)
Recovery Mode - Normal Vibrate, release pwr button and again screen blank with exception of top Left corner showing multiple pixels, unrecognizable
Download Mode - Plugging in the USB cord causes the phone to vibrate every 2 or three seconds and the cycle repeats. vibrate...vibrate...vibrate...continuous
Any thoughts on troubleshooting to determine if retrieving files on the phone is still an option?
Would appreciate ya'll sharing your common knowledge that uncommon while I'm this frustrated. After switching to an AWS service provider (WIND) 2 weeks ago my backup phone isn't compatible - Galaxy Ace GT-S5830D. Thought it was until I tried, then realized it isn't. I'm kind of flustered that I acted so impulsively and doubly because I thought I had a backup phone, ughh!
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
MASTERBLASTER69 said:
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
Click to expand...
Click to collapse
Thanks for the educated guess and ADB suggestion to recover files.
Yes the computer shows 3 drives when attached in Recovery Mode. And darn it I can't remember if debugging on or off. The computer doesn't recognize the phone by default while in recovery mode. If this is the case, would ADB likely allow access to the phone? Not a tool familar with yet.
Unlikely that the battery is damaged if the phone turns on. Still stays cool while on or charging. Which is good news.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
the computer shows 3 drives when attached in Recovery Mode.
Click to expand...
Click to collapse
I don't understand why you see 3 drives... I'm sure Windows will ask you to insert removable storage if you try to access the drives, right? If that is the case, and you have no screen/touchscreen, only ADB will allow you full access to everything in the phone.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
Click to expand...
Click to collapse
Yes. Here's the tricky part though, in order to make adb work, your computer needs the right drivers for your phone.
I think you should try to follow the HOWTOS (How to Install Android ADB Interface Drivers) on installing the drivers for ADB.
If all goes well, you can check if it worked by typing 'adb devices' from the windows commandline. Then it would be possible to use adb to get your files back.
If the phone boots into the system...if, since you can't see it....you should be able to open the sd folder on your pc and simply copy/move what you want to the pc.
Just checking if you've tried this.
I think I have hard bricked my HTC One X, I had recently installed the new layout with twrp2811.BIG.img so I could install crDroid rom everything went well I formatted the partitions so it would change to the new layout and followed the threads instructions. I managed to install crDroid and that worked phone and then I loaded it back into recovery so I could transfer back all of my sdcard contents that started to go well and then windows kept popping up with device not responding or disconnected would you like to stop copying or skip file at this stage did not know how much of my files had been moved so I clicked skip file seemed to be ok and then windows crashed and then resarted the windows explorer so the copying was stopped, I went to restart recovery just re establish MTP connection and then recovery froze after i had swiped to reboot waited for a few and it was still frozen so I held power to force it shutdown. now my phone will not power on, led wont turn on to indicate charging ive plugged it into the wall no luck tried computer no luck, but windows detected that I had inserted device but popped up with unknown device and a ballon saying the device had malfuctioned or stopped working. I have ubuntu on my laptop so I booted it into that and ubuntu does not detect it. so I don't know what to do now. Is it completely dead? or is there a way to revive it? Ive tried leaving it plugged in for a few hours still no luck though.
please help!
powerwill said:
I think I have hard bricked my HTC One X, I had recently installed the new layout with twrp2811.BIG.img so I could install crDroid rom everything went well I formatted the partitions so it would change to the new layout and followed the threads instructions. I managed to install crDroid and that worked phone and then I loaded it back into recovery so I could transfer back all of my sdcard contents that started to go well and then windows kept popping up with device not responding or disconnected would you like to stop copying or skip file at this stage did not know how much of my files had been moved so I clicked skip file seemed to be ok and then windows crashed and then resarted the windows explorer so the copying was stopped, I went to restart recovery just re establish MTP connection and then recovery froze after i had swiped to reboot waited for a few and it was still frozen so I held power to force it shutdown. now my phone will not power on, led wont turn on to indicate charging ive plugged it into the wall no luck tried computer no luck, but windows detected that I had inserted device but popped up with unknown device and a ballon saying the device had malfuctioned or stopped working. I have ubuntu on my laptop so I booted it into that and ubuntu does not detect it. so I don't know what to do now. Is it completely dead? or is there a way to revive it? Ive tried leaving it plugged in for a few hours still no luck though.
please help!
Click to expand...
Click to collapse
Hey any luck, or new updates?
Yeah ive fixed it now i had to hold volume down + power for around 5mins and then it came back to life.
Nice