So I went to flash my MDA today, did the usuals, checked the battery indicator (was showing 100%, which I thought was odd). Sure enough, it was odd, as the battery must have been low, since it powered off mid flash.
Now unfortunately it's stuck in the bootloader, and I can't charge the damn thing. Problem is, even if I pop the battery to power it off and kill the bootloader, as soon as I put the battery back in and connect the power cable, it automatically fires the bootloader up, even if I don't touch the power.
Anyone know a workaround for this?
Try to hold the power button in bootloader, sometimes it can be powered off, then charging is possible.
After fully charged, flash it again.
Unfortunately that was no go, I could get it to turn off, but it would immediately fire the bootloader back up.
I was able to rig an external power supply as well as test the battery -- both of which proved to me that it's not really a power problem, though it looks like one. I'm not really sure what's going on.
Basically what happens is during a flash, the unit will randomly power off, looking like a power failure -- but then boot back up into the Bootloader. The problem is that the Bootloader, when connected to USB, also constantly reboots itself, making it impossible to do an RUU. Not really sure what to do with it at this point. Only thing I can think is the bootloader somehow got corrupted?
shadowimg said:
Unfortunately that was no go, I could get it to turn off, but it would immediately fire the bootloader back up.
I was able to rig an external power supply as well as test the battery -- both of which proved to me that it's not really a power problem, though it looks like one. I'm not really sure what's going on.
Basically what happens is during a flash, the unit will randomly power off, looking like a power failure -- but then boot back up into the Bootloader. The problem is that the Bootloader, when connected to USB, also constantly reboots itself, making it impossible to do an RUU. Not really sure what to do with it at this point. Only thing I can think is the bootloader somehow got corrupted?
Click to expand...
Click to collapse
I would flash the official ROM first. Make sure the batt is charged. Flash your carriers official ROM, then go from there.
That's the problem, the battery is fully charged (and even when I do a probe based 3.7v dc power source), but the bootloader goes into a reboot loop. It reboots before the ROM can actually load.
Related
My Tilt was low on battery so I went to plug it into my computer. Turns out my brother took my USB cable, so I went to my room and found a USB power plug for an old iHome.(Only after plugging it in did I realize it wasn't standard USB voltage, it was 9v) Well I plugged it in, and my phone immediately turned off, and now it constantly reboots to the Smart Mobility boot screen, vibrates, and restarts again. I left it with the battery/microSD card/ SIM card out for 24 hours, but still nothing. I've tried Hard Resetting, and re-flashing through the microSD card, but nothing seems to work. Any ideas?
erik29gamer said:
My Tilt was low on battery so I went to plug it into my computer. Turns out my brother took my USB cable, so I went to my room and found a USB power plug for an old iHome.(Only after plugging it in did I realize it wasn't standard USB voltage, it was 9v) Well I plugged it in, and my phone immediately turned off, and now it constantly reboots to the Smart Mobility boot screen, vibrates, and restarts again. I left it with the battery/microSD card/ SIM card out for 24 hours, but still nothing. I've tried Hard Resetting, and re-flashing through the microSD card, but nothing seems to work. Any ideas?
Click to expand...
Click to collapse
Have try another battery?, probably your battery was the one that really got smashed with those 9v.
I don't think its the battery, because it still holds a charge, and can boot into the boot loader and hard reset screen fine. Is it possible that the battery just can't provide enough power for the full OS? Is there anyway to boot off of USB alone? I don't have another battery (currently) so I can't really test that.
erik29gamer said:
I don't think its the battery, because it still holds a charge, and can boot into the boot loader and hard reset screen fine. Is it possible that the battery just can't provide enough power for the full OS? Is there anyway to boot off of USB alone? I don't have another battery (currently) so I can't really test that.
Click to expand...
Click to collapse
Try to reflash, since you can get in bootloader and see if that solves the problem.
erik29gamer said:
I don't think its the battery, because it still holds a charge, and can boot into the boot loader and hard reset screen fine. Is it possible that the battery just can't provide enough power for the full OS? Is there anyway to boot off of USB alone? I don't have another battery (currently) so I can't really test that.
Click to expand...
Click to collapse
Same thing happened to me, it had enough power to get and remain in bootloader but not enough to boot OS. Put in a new battery and has run perfect ever since. 3 mon.
denco7 said:
Same thing happened to me, it had enough power to get and remain in bootloader but not enough to boot OS. Put in a new battery and has run perfect ever since. 3 mon.
Click to expand...
Click to collapse
Agree with mate
Sorry for reviving my own post, but i finally got a replacement battery and it still just vibrates, smart mobility screen, then repeats. I just tried flashing it with the stock att rom and the only difference is att screen instead of smart mobility. Any other suggestions?
EDIT: Also tried flashing android but does the same thing, vibrates, flashes boot screen, repeats
My phone (which is currently running Incubus26Jc's Android 2.2 FroYo RLS10 NAND) rebooted at around 12:30 AM. I noticed that it reboots, randomly, about twice a day. Not sure of the cause, haven't looked in to it, but normally it comes back to the desktop, like a fresh boot of the phone. So I thought nothing of it.
Last night, however, during the reboot, SOMETHING happened, and it seemed to have gotten stuck in an infinite loop. It would show the boot animation for a while, then lose power... then it would notice the power cable was plugged in, and try to automatically boot up.
If you notice, plugging the power cable in forces the phone to boot all the way into the Android OS. There seems to be no "charge while off" feature, at least for me.
Anyway, this endless loop caused the phone to reboot over and over and over, until the point where the battery was so far drained, that this "hand off" between the boot screen and the actual OS (somewhere during the boot animation) where the phone had to run on battery for a split second, was long enough to cause the phone to power off completely.
I couldn't flash back to Windows (I thought) because the phone didn't have enough of a charge to stay in bootloader mode while flashing the phone. Which was mostly true.
FYI (how I fixed my problem): should something similar happen to you, put the phone in true BOOTLOADER mode (hold the camera button when you press the power button, see the colored bars across the screen), even though the indicator doesn't light up, the phone DOES charge when in this mode and plugged in to a wall charger (and probably while plugged in to USB).
As far as I know, you are required to maintain a certain level of charge to run the RUU because the USB cable cannot charge the phone WHILE FLASHING, but while waiting in bootloader mode, the battery will charge. I was able to let the phone sit at the bootloader for about an hour then started up my phone and had over 70% charge according to Android. Working again!
thank for the 411. i had a similar issue with rls10. went to 10.5 and rls11 and flashed a new kernel, no further issue since
The newest update bricked the device and i'm looking to get some files off the phone before using the sbf to restore. Is there a way to have ADB access if you are not able to successfully boot into the OS?
Hey, as an avid flasher (gosh i believe i did it over 15 times just this month =O), I noticed that even if you reflash everything on your phone, only your apps are erased as well as some data. If you're looking to back up stuff in the internal SD card, you should be fine as flashing won't touch that. As for if you're looking to grab some user data, I don't believe there's a way to do that, but I could totally be wrong. Sorry if that didn't help =\
if you reboot holding arrow down, it seems like I saw a USB enumeration option if you keep pressing down volume through the option. That may be a way to get the stuff off, depends what you want to do though.
I can also confirm SBF'n back to factory will retain SD info. I did it this morning to update to latest OTA.
Accidentally rooted and bricked ... but now the battery won't charge ... so RDS says battery is too low to flash ... any suggestions?
My only thought is to go to the ATT store and ask if they can swap batteries, but I don't see why they would.
If you plug it into the wall it should charge with the phone turned off. If the battery is completely dead- it will appear nothing is happening. Just leave it plugged in for a while, drink a beer, do something around the house, then come back. It should show a charging light at this point or have tried to turn itself on.
I will also 2nd that SBF flash will keep the files on /sdcard/ level intact.
Thanks for the quick reply...I feel silly asking, but how do you turn it off? As soon as I plug it in it turns on and gives the message "Failed to boot 2 / Starting RSD mode / Battery too low to flash." I press power, nothing happens. I hold down power, nothing happens. I hold Vol Down and press power, nothing happens. I charge overnight 12+ hours with the screen on, it gets warm, but otherwise nothing happens. I charge with the USB to the computer, the screen stays off, and it seems to get a little bit of charge (enough so that it doesn't shut off as soon as it's unplugged), but hours of trying to charge this way nets the same error message. She's bricked. I guess you can't flash without a battery in place?
Edit: Or just buy this spare battery desktop charger
My next best suggestion for you is to find a way to get 3.7 volts of power to those battery pins. Either with a regulated power supply or another lithium cell battery. I'm not sure whether or not the detection circuit will allow the phone to boot or not or if that is charge-related only, but it would be an alternative to keeping a bricked phone. If you choose to try to run this without a battery keep in mind wall wart type power is unstable (read: voltage changes) at different current draws.
Went to the store near closing time (10 min) and they gave me a fresh battery instead of going through warranty, said that could take days with no phone. Fortunately he didn't test the battery and, upon putting a new one in, he only looked at it long enough to see the dual core logo and not the Failed to Boot message.
Flashing worked perfectly after I had a fresh battery, thankfully. No longer bricked, no longer using 6-yo crackberry!
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
I tried following this guide, though without success. The phone still has that white LED lit when it's connected to the PC.
After a reply on this thread I also made, it might be possible that the battery is charged, but the phone refuses to boot at all. Is there any way to unbrick the phone in this state?
Do you think your device is really BRICKED?
If so, you can try to flash your original sbf file into your phone. Guide here: http://forum.xda-developers.com/showthread.php?t=696845
If you are using a Linux, google for "sbf_flash".
I agree with my front floor..ermm, u dont need to worry about its 'dead'. just flash original sbf can rescure your phone.
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
algopem said:
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
Click to expand...
Click to collapse
"My phone is in limbo state... "
That's a pretty cool statement.
From technical view, it might have happened that something caused a kind of deadloop when reading scratchpad SRAM inside OMAP processor.
This SRAM, as well as the internal RTC is powered by a small battery soldered on the mainboard, while the phone is shut down and the battery is taken out.
What you did was, to wait untill this battery became uncharged.
All SRAM and RTC setting as well then gets erased.
Afterwards the CPU will start up with empty scratch SRAM, might be called a "real" cold boot
Normally the phone should not behave like this. Even if SRAM is not valid the phone should boot up...
...but anyway as you observed it like this, it might happen.
@andoruB:
Apart from that, the Milestone is hard to brick in general.
Might happen though, if you do evil things while flashing new firmware.
Especially while flashing bootloaders...
If you got some more information about the things you did, would be helpful!
Good luck anyway!
scholbert
andoruB said:
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
Click to expand...
Click to collapse
how did u root it? can u give a more detailed description? and hows ur phone? sometimes, the milestone would just shut off and wont come up if the battery is gone. Try charging it for maybe 2-3 hours, untouched, and see what happens.
Have this exact problem. Was doing a nandroid recover when the phone got stuck. Pulled the battery out. Placed it back in, pressed the power button. Nothing.
Led lights up only when connected to the computer's USB. Battery was charged before Nandroid recover. Used nandroid a lot of times but for some reason, my stone stopped playing nice.
I just removed the battery. Hoping this works. Can someone please post if you got this same issue resolved? I like this phone no matter how slow it goes sometimes. Thanks!
I completely forgot about this thread, sorry guys!
I don't remember exactly what happened, it's been so long... but I do remember I left the phone "inactive" (it's not like i had much of a choice! XD ) for 1 or 2 months, with the battery out. After I got hold of a wall charger, I plugged in the battery, after I plugged in the charger, and what do you know? It worked! It started charging (was 60% charged, fully charged, I unplugged it, but after putting it to charge again just to make sure it was fully loaded before I would flash a new ROM, it was charged up to about 80%, weirdly, so I guess it was a weird battery problem)
I do remember I didn't do anything to it, so I'm not sure what to tell you guys to do, except leave out the battery for a month or so ^^;
Stuck on "please lock bootloader" screen when plugging in after depleting the battery
No button inputs work. The only solution seems to be waiting until the battery fully runs out and plugging it in again, after which it sometimes boots up. At least I got it to the first time, it failed just now. Maybe I need to hold some button combination while doing so?
How do I fix this properly? And what's a sure way to get it to boot from this? I'm already wasting half and hour on a minute's charge, God forbid I ever forget about it plugged in for longer. Would have to throw it in the drawer for a couple days and probably end up with some permanent burn-in too.
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
What seems to have done the trick is holding power&volume+ (probably just power is enough), so it loops through the 'empty battery' splash screen at least once. I think that's how I did it the first time too.
drwharris said:
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
Click to expand...
Click to collapse
It never seemed to make any difference whether I pressed the power button or not, in fact it always booted up automatically after some time, this scenario excluded.
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
VonZigmas said:
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
Click to expand...
Click to collapse
i had a similar problem after a failed attempt to boot into recovery.
for me the following did do the trick and booted my phone back into system:
- deplete battery completely
- plug in charger and keep power button pressed until phone is charged enough to attempt boot
- keep the power button pressed until nokia logo appears
THMSP said:
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
Click to expand...
Click to collapse
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
VonZigmas said:
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
Click to expand...
Click to collapse
Well, multiple definitly isn't one I haven't stopped the time yet, but expect waiting and pressing them for around 2 to 3 minutes, maybe even 5. It might sound stupid, but it will work.
About fixing it, I don't know. It might be a bug in the reference bootloader that Qualcomm provides for Snapdragon 835 chipsets, and I doubt that FIH / HMD have the resources to debug and fix that.
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
OneDream said:
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
Click to expand...
Click to collapse
No, I guess it isn't. I've tried to plug it in while it's off and turn off as it's charging and in either case it resulted in the phone hanging up on that screen. I can confirm though that holding all three buttons for a while does turn it off and allow me to boot normally which is cool.
But is that possible with a locked bootloader anyway? Or does it always power on? I can't tell if I ever needed it to charge like that.
I see this "warning" message only on android pie builds, it doesn't seem on oreo builds. I think problem seems that kernel dependent (oreo is on 4.4.78 and pie is on 4.4.153). There is one way to get rid of that message, as @THMSP said, holding all 3 buttons pressed during 2-3 minutes and let it to be shuted down. Then, let the device to boot normally and plug in. Finally you shouldn't connect to charger when it's turned off on any pie build.