Ok, here's what happened. Battery died completely, phone wouldn't charge when plugged in. Used an external charger to charge battery, installed fully charged battery, turned on phone. Display shows "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I wasn't using Kies and have never used it. So, I install it, plug the phone into my laptop and no connection. I figure, no big deal, I'll restore via Odin and be back in business. Only problem is, the phone is not recognized by Odin and I can't flash the restore. Pretty sure it's toast, unless somebody has any other ideas.
Edit: Disregard. I finally got it to work. Had to remove the battery and sd card, let it sit for a while(about an hour), then put the battery back in without the sd card. Odin finally recognized my phone and I was able to run the restore. Now to set everything up 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!
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?
What would be the most likely reason an Evo wouldn't charge?
Here's my situation:
I've been flashing nightlies for a while. Figured that might be the problem so I restored to an older version. Won't charge. Won't even turn on the orange LED when the phone is off. If I pull up the bootloader at this point, the battery is too low for me to do anything. I've tried charging it from numerous outlets, my computer in multiple USB ports, and my PS3. I don't know what's going on. When I woke up this morning the battery was at 93% and the phone wasn't charging, but I figured the extension cord just got jarred in the middle of the night or something. Any ways any suggestions?
Update: Took it to a Sprint store and asked a guy to try putting in a different battery. He said it booted up and that it was charging, so it appears that might be the problem. Does anyone know how to force my phone to charge THIS battery, or at least what might have caused this?
Update: Turns out this is what's called a 'bricked usb', however, I can't figure out how to fix it. I've done some things with files on a terminal emulator, as well as trying to do stuff in fastboot (I don't think my computer can recognize the phone in fastboot). My phone doesn't recognize ANY usb activity- right now the way I'm charging it involves hotwiring USB leads to the battery. It won't charge when it's off, and I don't think it's recognized in fastboot (when I type 'fastboot oem boot' it says waiting for device and doesn't do anything.
Check cable and charger. It could be the port tho
I"m having the same issue
how did you fix it?
if the sprint guy put a different battery in it and it started charging just fine, then the battery is your problem. YOUR battery may have either fried, or has drained so low that it's unable to take a charge. Sprint techs can "boost" your battery so it will start charging again, or ebay has batteries for extremely cheap. like a few dollars.
I'm having this problem too. Tried new ebday batteries, and the battery life still SUCKS! What's going on!?
Right now I'm trying to get some sort of charged battery life, unroot, and take it in.
how can i unroot the phone if i dont have access trhu the usb?
please help me i need to gt a new phone and i dont want to loose my warranty
cabezapreta said:
how can i unroot the phone if i dont have access trhu the usb?
please help me i need to gt a new phone and i dont want to loose my warranty
Click to expand...
Click to collapse
Take the memory card out of the phone, mount to a pc, via card adapter, download the unrevoked s-on tool, flash it in recovery.
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip
Rename the file to PC36IMG, while memory is in the pc, drag it over. Place the file on the root of your sdcard, boot into the bootloader, then apply the update. You'll be s-on, stock unrooted.
i was able to flash PC36IMG, but when i try to flash the s-on tool all i get is a phone with a triangle when i select recovery
what am i doing wrong?
Phone turns off during use and will not complete boot unless plugged to charger even when the battery is almost full.
This error started last night after I did factory reset because of observed phone lag. I did mistakenly "wiped internal storage" but got the alert of "no OS during reboot", so I restored from my backup from SD.
the phone started properly but went off during initial setup and will go back off each time I tried turning it back on. I thought it was battery so I plugged it to power.
it did boot but will go back off once I have few touches on the screen.
I had to leave it plugged to setup my accounts else it will go off.
I'm using its Wi-Fi to send this message via my PC because any 2 - 3 touches will switch the phone off.
once it does that, it won’t even boot to bootloader before it goes off again unless plugged to power.
what I do to solve this please??
Problem has been solved.
It was actually the battery. I got a replacement and the device is okay now.
Thanks.
I have a Note 7100 that suddenly decided to shut down and when I turn it back on, the phone is stuck in the "Samsung Note NT7100" logo screen. When I plug the charger in, the phone won't charge. When I turn the phone on while it's plugged in, it just shows the battery screen with the circle in the middle not moving.
And so, the phone is brought to me where I tried to do a factory reset/data wipe using volume up, home button, and power button. Upon trying to reset, I get multiple lines indicating E:\ fail to mount, E:\ fail to load, etc.
I then try to use Odin to flash another ROM but my computer is not detecting the phone. And yes, I have Samsung driver installed. The only thing I get is Windows saying it has found a new hardware named Samsung_Android and searches for updates but never finds one.
So the phone won't boot, won't charge, can't be detected by my computer. Is there a way to fix this? What caused the phone to shut off and the E:\ fail errors is unknown at this point.
eMMC chip got corrupted, change it at the nearest service center.
It's not completely dead I guess.
Yesterday, I went into odin download mode on the phone and plug the cable in from my computer. Opened odin and it detected the phone.
I tried to flash some firmware but it failed.
In odin download mode, at the top left corner of the screen, it's still giving me information of the phone.
Does this mean the phone is recoverable or is eMMC replaceable still the only solution?
It is not completely dead, it's just that storage memory is dead, unfortunately.