Related
Hey all, thanks for taking your time to read and possibly help me out with my problem. Yesterday I've tried rooting my droid in order to put cyanogen mod on it later. The reason I was interested in doing that was because I felt as droid was not working to it full potential and constantly crashing apps on me (browser, games, weather, etc). A friend of mine suggested cyanogen as he himself owns it. Being that I've did plenty of CFW on PS2, psp, xbox and mp3s/ipods, I thought there shouldn't be a hassle with this.
I followed the procedures listed on cyanogen's wiki page in order to complete the rooting process. But on the step where it asked to instal .sbf file trough RSD lite and wait till it says "pass" I've ran into trouble.
During the unpacking of that file to the phone using RSD lite the phone was undergoing several reboots, and after finally finishing the reboots on my PC screen in the RSD Lite window it showed 100% complete "please reboot the phone manually". I had no idea how to do that manually as the phone just kept going on and off by itself. (also for some reason it kept saying "error" force close/wait/send notice. But I thought it was probably just the process. After trying to reboot the phone a couple of times nothing worked. I didn't receive any "pass" signs on the droid screen.
I've got a little worried about the whole process and decided to shut the phone off and during that close the RSD Lite on my computer. Doing that made no further improvements for me. The phone just kept going on and off like crazy while in USB and not turning on at all while not plugged into either USB or AC. I've decided to go to recovery mode and just reset everything to stock as I was running out of time and had to get some sleep before work next day. After reseting the cache/data files I rebooted the phone but the same things kept happening to it. Now it was asking me to reconnect with gmail account and all that intro stuff. But the phone would always end up locking up and shutting off somewhere in the process of reconnecting the account.
Fast forward to today I've read that its possible to complete reset everything to stock version trough .sbf file once again. But now the problem consists of the phone not having enough batter life. (I'm not sure what the screen is called where the process of dumping .sbf trough RSD lite starts) but that screen keeps saying battery is too low to do anything with it. And mind me it has been charge for a very long time now in the AC adapter.
Now it also appears as the problem has worsened. The phone does not start up at all in either USB or without connection. It only starts up in AC adapter but then it shuts off in 2 minutes and back on and off , on and off. Recovery mode can't be accessed in any way, at least any way known to me. The black .sbf screen can only be accessed while the phone is not connected to anything but still keeps saying the battery is too low. And I've noticed the phone getting extremely hot during AC charge. (another small detail that sometimes when the phone does turn on and goes to home screen opening up the landscape view does not increase the length of the top (pull down) bar in horizontal view.
I've tried taking out both battery and sdcard and putting them back but no luck. I'm really lost as to what I can do next in order to fix this problem.
If you need any further information please let me know and thank you again for trying to help me!
I don't really see how you managed to get a fc with rsdlite.
Did you reboot your phone (turn off) then boot into usb recovery (power on while holding up, for the droid)?
Sent from my Droid using XDA App
I am by no means an expert and could be just wasting your time but in the absence of expert opinions something is better than nothing right? It sounds to me like maybe you have a bad battery that as luck would have it failed during the update/rewrite. Have you tried getting into recovery with the battery pulled running straight off the ac adapter? Hopefully you made a clockwork/nandroid backup before you started?
sent from a random hobo's droid on xda's app
I'm not an expert either, but having just successfully rooted my droid and installed cyanogen I feel the need to ask: did you hold up on the d-pad while RSD rebooted the phone the first time? If not then you needed to immediately restart the process.
I think you need to use a separate battery charger (meaning that charging battery without a phone) to charge the battery.
Sometimes, battery won't hold a charge when your phone is a brick.
BTW, it appears that you are having the same issue with mine.
(I can't post a URL because I am new here, but you can take a look at my article in this section, called "[S.O.S] A rare MILESTONE brick situation". )
I had the same problem (battery won't charge and phone won't start-up), I had to purchase a separate battery charger, and then flashed another SBF, to make the phone charging normal. (Although my phone is still a brick, but not a problem with battery. )
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!
Right off the bat, my Revo is non-responsive, no buttons will light, backlight, vibration, sound, and of course no splash screen since the screen isn't lighting. The only sense that it is partly there is after a time connected to USB/wall charger the battery warms as if it is charging. Yet, there is no indication during charge on the screen, it stays totally black as described above.
I have been poring over forum posts, CWR threads, and the like, but have come up short on a method of reviving this puppy. thecubed had posted something that seemed promising but doesn't work for me here. At all steps, the phone remains non-responsive and connecting it to the PC yields no mass storage connection. The only step I have abbreviated is letting it charge for an hour since the phone had charged about four hours since it shut down.
Two evenings ago, I flashed from Revolt ROM 1.0 to 1.1. It was successful but since I had just gone through battery calibration and running my battery down until the phone shut down the day before when I flashed it to 1.0, I was hoping (naive?) that I wouldn't have to do it this time (yes, naive!). So, I left the phone on all night, on the wall charger.
I was using it the next day and at one point, while using it in a low reception area, browsing the web, it rebooted on me. No biggie, had that happen in the past. After reboot however, the battery level seemed different so I wanted to get it topped off then calibrate. 1-2 hours later I noticed that the calibration app was showing the mV lower and capacity was at 70%. The battery felt unusually hot. I shut it down, removed the battery and cooled both battery and phone in a small fridge to accelerate the process (was near time to leave work).
Next boot was I recall having an extra FC, one beside the CarHome normal FC with Revolt ROM 1.1. This boot the battery showed maybe 20% capacity so I said "screw it" and deleted battery.bin with the battery calibration app (I recall the mV was low, in the 3600 range). I discharged it on the way home and left the display on to run the last couple percent down. It appeared to try and shutdown but ended abruptly. That was the last time I saw any life from my Revo.
The day after its first and only ever root, I did have an odd occurrence which I posted.
Boot Trouble - Rooted After Phone Downloaded OTA, Not Installed
That time, I had not installed a ROM yet but the phone got itself into a boot up funk. Removing the battery, connecting to wall charger, watching buttons flash ~5 times, disconnecting (which stopped the flashing lights), then battery in, power on... success! I was hoping that would happen this time around but I haven't been able to.
Full history, being my first root, I used S1C successfully, installed Titanium Backup (ran system and app backup), and RevoToolkit. The phone did download the OTA but I never let it install, instead selecting to delay it by 24hrs when it asked to install. Fearing that deadline and getting one more warning that it wanted to reboot and install the OTA, I went ahead and installed the Revolt ROM 1.0. All went fine, no drama. The next afternoon I thought going to 1.1 was going well too, until this brick hit me.
My hope of hopes is it's just a bad battery and the phone won't respond because the mV is too low. Reading thecubed's comment in his first link (above) how recoverable this phone is lends me hope.
It sounds like a bad battery. I would take it to a verizon store and see if you can try a different battery. If it still will not boot then they should warranty it out for you.
Sent from my VS910 4G using XDA Premium App
P.s. I never do anything for my battery. I charge until full then use until empty. Yesterday with moderate tI heavy use I made it from 6am until 8:30 pm
Sent from my VS910 4G using XDA Premium App
Thanks for the responses. I will be going to VZW shortly to figure this out. This phone is maybe two months old so hopefully the battery is the answer *fingers crossed*
Impressive battery life! At my office, I'm in a bit of a metal cubicle area and a bit low on signal strength. My phones will sometimes use up the battery trying to keep connected, it seems, so I am usually plugged in most of the time.
While I have your ear, thanks for the great work on Revolt ROM. I am very happy with it and look forward to its future development
Good news and bad.
The good news was they swapped in a new battery and the phone worked. Having the warranty, it didn't cost anything.
The bad news is that it looks like there may be another problem. On the way out of the store the battery was indicating 1% so I quickly got it on the charger in the car. Driving home, about 10 minutes later, I got a warning for battery temperature. Thinking the low battery may just be taking a charge and getting hot from that, I turned the car A/C on full, took the back cover off, and kept the phone in the cold air.
In about two minutes, just feet from home, I noticed the display was off. Faintly I could see the battery charge symbol that shows when the phone is powered down and charging, but the backlight was off and I couldn't see if there was any color or animation to it.
As soon as I shut the car off and the power quit, that faint display disappeared, full black, dead. Now it seems it is behaving exactly the same. I haven't fiddled with it much, holding out hope of hopes it can be started and maybe recovered.
Could calibrating the battery at the wrong time have caused something like this? Do batteries have a safety lockout if they overheat? To be fair, I was running an intensive app at the time, Waze GPS. Maybe the battery didn't keep up and the phone decided it was too low and shut off. I will post back after letting it sit, cool, hopefully charge, and see what comes of it.
My phone is behaving exactly the way you describe too. A couple of days with Revolt 1.1, and this is the only problem. I had my phone hooked to a lithium ion usb battery pack all day, and it showed "100%" while hooked up, but as soon as I disconnected the battery pack, the battery icon changed to red, then it refused to boot like the situation described in the Revolt 1.1 thread in Development. It also would not go into charge mode on the battery pack, but when I came home and hooked it to a genuine AC adapter and it went into power-off charge display. I'm going to give it a few hours on the charger before I attempt to boot it again, and I'll report back.
Still no luck. I haven't charged it too much yet for fear that it isn't charging properly. Seeing the new battery work for about 20 minutes yesterday lent me hope that if I figure out how to get a fresh battery in or just shell out for another new one, I can have a window of opportunity to change ROMs and see if that has anything to do with it.
This morning I got out my digital multimeter to measure the battery pos to neg and am getting nothing (unless you consider 0.01v something). I tested my old LG clamshell's bulging, old, and damaged 1000mAh battery and it reads 3.99v but couldn't keep my old phone up (lacks oomph now).
Comparing that battery to the Revo's, they have the same four contact pattern but different connection scheme which just stops contact when test fitting. After shaving down its casing on the bottom a little bit, it was just enough to make contact. Using four hands (yes, I am very talented ) to hold the phone, hold the test battery properly, and hold the power button, I was able to get the power-up vibration and the first LG splash screen. We lost it after that but that's likely due to the very weak test battery and/or losing contact while holding it in the Revo.
Since the spankin' brand-new battery is now reading zero, I'm left second guessing my decision of not shutting the phone down when I got the temperature warning. Maybe these batteries do have an internal protection to prevent runaway failure and it too is trash. I have no experience with this otherwise so this is just guesswork.
I'm contemplating rigging the new battery into my old LG phone to see if it can tell it "all clear" and charge it up. I'll post anything I find out here. Any other suggestions are highly welcome. Still, last ditch, I'm pretty certain I can set up another ROM to flash on the SD ahead of time, get another battery, and Clockwork to test another ROM if it's the phone or ROM. I may have had 20 minutes of uptime on the last battery.
I think I've gotten to the bottom of my problem. It's a syndrome of things that I have hopefully untangled.
First off, I had been messing with Power Manager, and wanted the phone to not sleep or timeout the display when plugged into both AC and USB. I figured that would help when I'm plugged into the computer, but it was probably a bad choice.
Yesterday I was out on a boat, which probably put me into a weak signal area, causing the phone to expend extra energy staying locked on a tower. In addition, I had plugged it into the external USB power pack, and thrown them in a bag together. This did two very bad things: 1) It allowed heat to build up from both the charging and 2) it invoked the "USB powered" Power Manager profile which kept the display active which created both additional heat AND crazy battery drain.
Here's what I think happened:
1. The battery overheated
2. The USB battery pack couldn't charge as fast as the display and radio could suck it out -- so five hours in that mode BOTH drained the internal battery AND tapped into about 30% of the external battery pack.
3. The USB battery pack will not provide enough initial juice to restart a flat-dead, overheated phone, or the firmware "knows" it is hooked to USB and refuses to start the phone -- for some bizarre reason.
So, I think my phone demonstrated normal behavior for a flat-dead, overheated phone, and hooking it up to AC brought it right back to life -- after about 5 hours of continuous charging. The battery also got very warm during charging -- more than I recall feeling ever in the past.
I'm hoping there is nothing that software power management could have done to physically damage the battery, but I assume Verizon would claim it could -- as part of the reason they forbid system modifications, and therefore withdraw their warranty if you modify.
At this point I think I have dodge a bullet, and my phone is fine -- other than a few of the quirks others are seeing in Revolt 1.1 (Phone occasionally FC, etc.)
Good to hear your phone is fine. Seems like mine is too as posted above but time will tell. I got the Revo battery set up and charging on my old phone. It seems to be connected well enough. The phone complained the first try that there was no battery but my second try has it displaying that it is charging. The battery isn't warm at all but maybe that's due to a different charging rate for the old phone's 1000mAh battery vs. the Revo's 1500mAh. Or, it really isn't connected perfectly. We shall see.
Success. The surrogate charge setup got the Revo battery up to 4.11v and indicated charge complete. The Revo completed a full boot on the battery and appeared normal.
Not normal was quick heating (still unsure of the cause). Going straight to Battery Calibrator, it indicated 68% and around 3.7v and falling. Not wanting to push my luck, I shut it down. Battery now read 3.9v. Not bad but it sure seems to be getting drained quickly which would explain all the heat. Going to set up later and see if I can get it back to stock and see if the behavior persists.
I don't know how to fix any of your issues but I would like to say thanks for giving such a detailed display of what you've been doing to fix this problem should anyone else run into this issue. Also, That picture in you one post: That is the most jerry rigged set-up to charge a phone I have ever seen in my life and I love it. Good luck getting your phone working I hope everything turns out for the best.
You're welcome. It was a bit of impromptu brainstorming with some fellow tinkerers that helped come up with a way to test charge the battery. Having it come back to life
I've come to a conclusion. Somehow, I think when the battery overheats, it must internally soft protect itself. Charging it on the old phone reset it and then it worked again on the Revo. Why the old phone works and not the Revo, unsure. That would at least explain why the battery tested at zero volts before the charging rig.
After many starts and stops on my Revo now, I have found that what was heating up first was the casing of the phone. I'm guessing heat conduction of heat from the processor as it wasn't the display which was set to minimum brightness (those are the main heat sources, right?). Looking into Settings > About > Battery Stats, it only showed Android System at 98%. It seems like the processor got locked into some some high power continuous use situation which survived reboots.
The battery gets hot later due to the high consumption and proximity to the hot casing (processor), especially with the back on. Withing 1-2 minutes from start, the sides of the phone would be quite warm and after 5 minutes becomes concerning. It seems that's why the battery was never able to get to 100%, but instead its percentage was always falling, phone over consuming greater than charge rate.
With the processor going full tilt, battery cover on, protective case on phone, sitting in a warm car without A/C, that got the battery too hot within 20 minutes. It was a similar situation with the prior battery when the problem cropped up.
I don't know what the cause of this predicament was in the first place however. The phone was plain stock, then rooted, later flashed Revolt 1.0, then Revolt 1.1. Between Titanium Backup, RevoToolkit for CWM, basically nothing unusual, I have no idea how it happened. Maybe I should have done Decrap first since I've read others doing such. Thinking back to my first post/thread, I had a boot issue and only had rooted, Titanium, and RevoToolkit, no ROMs yet.
And, don't get me wrong. I'm not placing blame anywhere, just documenting my "progress." There was a time I was on Revolt where it wasn't behaving this way. I am left without a solid conclusion as to the cause.
How to avoid the battery drain?
I had a similar situation, downgraded and then installed Revolt 1.3. Can't say what did it, but the battery got hot and drained so far it would even start charging.
I got the battery charged on the old phone, and the new one, with Revolt 1.3 is working. But I'm not sure how to make sure the overheating/draining problem doesn't occur again. After 10 minutes the phone is starting to get hot again, battery is down to 57%. With the phone on or off, it does not charge the battery, even with an AC wall charger. With the phone on, it indicates 57% charge, with the phone off, the battery icon just sits at red, no charging is happening. I erased the battery stats in ClockworkMod, but is there anything else to do? Any other ideas?
It sounds like Haxid had it happen and he got back to LG stock and unrooted, all good.
http://forum.xda-developers.com/showthread.php?t=1233668
Mine happened again this time totally dead battery. Trying to get some charge in it now to boot and remove cwm so I can take it to verizon.
Decrap 1.0 rom this time w/ CWM
I do not believe it is the rom. It has to be an app or hardware.
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Bait-Fish said:
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Click to expand...
Click to collapse
No my phone is actually super stable it just is sucking battery like its candy. Been off charger only 1 hour right now and its down to 83%. It has to be an app doing it but I have no idea which one. The phone shows 64% battery usage by android system.
When mine was hogging battery, same here. All I saw was Android process.
just to add my 2 cents here. I noticed my phone draining like crazy, I tried everything, then I changed the battery. boom. everything is now stable. I'm going to try to exchange that battery I think its my drain and reboot culprit.
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 ^^;
Thank you to the members on here, reddit, and other Android sites for the helpful insight. I did tons of research because I could just not stomach losing everything on my phone. I'm actually glad this happened because I will never be this careless again. I've been coming on this site to mod my phones since the PPC-6700 and have never heard of this issue. But SD cards fail and drops happen so that's no excuse.
I was able to get my defective phone to boot by freezing it for about 15 minutes in large freezer, and letting it run inside the freezer. I have heard of people being able to recover data by freezing the batteries and one person suggested to run your phone in the freezer. I tried it and it worked.
Before I tried the freezer method I was only able to get to the Android is Upgrading screen maybe 10 times out of over 100 boot loops. The farthest I ever got on that screen was 8 out of 101 apps. With the freezer method it fully booted on the first try.
First I froze the battery alone for maybe 20 minutes. Then I placed the battery in the phone and tried booting into recovery. It didn't work. So I removed the battery, put it back in and and let both of them sit together for about 15 minutes in the freezer. Then I returned and the phone fully booted on the first try. I tried booting into recovery from Nandroid Manager but that just reset the phone. Since it seemed stable and I wanted to keep the phone as cold as possible I just used My Backup Pro and Titanium Backup to back everything up.
I honestly gave up and I am sending my phone to LG today, so this was literally my last resort. Hope this helps someone.
Confirmed, sort of. After about 15mins my phone booted up, but froze again and restarted. Hoping with a few more minutes of freezing it stays put so i can transfer my TB to my SD card (I though it was already there :\)
Thank for useful information. It's happened to my phone too keep rebooting itself then after 100 reboot I got the home screen and use cable to copy all my stuff in laptop . I'm sending mine to tmo store
Sent from my Nexus 4 using Tapatalk
hollywood084 said:
Confirmed, sort of. After about 15mins my phone booted up, but froze again and restarted. Hoping with a few more minutes of freezing it stays put so i can transfer my TB to my SD card (I though it was already there :\)
Click to expand...
Click to collapse
I tried it again to get a nandroid backup and merely freezing the phone did not work. I had to let it run in the freezer, I got the best performance with the back off and the phone resting on a bag of frozen vegetables. The second time I had two reboots but that may be because I didn't get the phone quite as cold as the first time I did it.
Phone is sent off to tmobile and the replacement is working great.
Thanks for the tip, it helps! Confirmed working, left my phone 20 minutes in the fridge => boot but freeze during LG animation (not cold enough)
left the device in the freezer for a moment => success boot, but freeze minutes later once it gets warmer
So... there is a problem with some hardware pieces..
It still took dozens of tries to get everything working over a couple of days but using this method I was able to backup all my data and even wipe the phone! Just keep trying and keep it cold in the freezer. Also, charge your battery to 100% constantly rebooting drained the battery quickly. The CPU gets hot even when it looks like its running fine, keep it in the freezer while it does its commands.
I got the dreaded bootloop back in Dec. Tried the freezer method a few times to recover data, but I still get the bootloop. I got to the T-Mobile screen once, but every other try I got stuck at the LG logo.
Sent from my LG-E980 using XDA Free mobile app
For how long did you put your phone in the freezer?
bel57 said:
For how long did you put your phone in the freezer?
Click to expand...
Click to collapse
First few times like 15 to 20 mins. Then a little bit longer on the next few attempts. I thought it might work if the phone was a little colder, but still no luck.
Sent from my LG-E980 using XDA Free mobile app
It's not *a little*. First time it succesfully booted once put 30-45 mins in freezer, but not enough, since it started freezing after a few minutes of use.
I managed to retrieve my data after leaving it for at least 1-2 hours in freezer.
Going to shop to get back my device and try it..
trying the freezer method but not getting success. i guess it needs a big freezer.
Riiip
Thanks for posting - this method works! It took me a few tries to get it right - put the phone, no cover, in a ziploc, with battery inserted for over an hour in the freezer. Take it out of the bag, and let it boot inside the freezer (door closed), with back/battery resting on icepack or frozen bag of veggies. Once booted, connected the USB to laptop (with freezer door still closed as much as possible), and transferred all data! It seemed pretty stable and fast by that point. Upon taking it out, it went into bootloop again. No moisture damage.
I too tried this method, but no luck..
Tried letting the phone in the freezer for 10-20 minutes, no change
Let the phone in the freezer 40 minutes, nothing at all
Let it for 1 hours, same again
Let it for 2 hours and nothing seems to happen. It keeps bootlooping.
Maybe i'll try one last time putting both the phone AND the battery for maybe 4 hours, then power it on, see what happens...
why not make a KDZ with big cores disabled.. all the ones work but only for 815-815p. no 811 or 810
Well my replacement phone I got from lg has done this again. Yay me!
And my replacement phone broke again.. The freezer method worked again. But the replacement (my 2nd boot looping phone) usually won't even Boot Loop. When I plug it into a charger nothing happens. Insert a full battery and try to turn it on, nothing happens. I had to press on the back really hard to get any power to the phone. Then I was able to use the freezer method for a few days, my replacement has came and I cant get it to work again. I just wanted to double check that everything was backed up, I may be out of luck...
NVM, just realized this is the G4 forum, not the v10. Best of luck with bootloop issues.
celsius0010 said:
Thank you to the members on here, reddit, and other Android sites for the helpful insight. I did tons of research because I could just not stomach losing everything on my phone. I'm actually glad this happened because I will never be this careless again. I've been coming on this site to mod my phones since the PPC-6700 and have never heard of this issue. But SD cards fail and drops happen so that's no excuse.
I was able to get my defective phone to boot by freezing it for about 15 minutes in large freezer, and letting it run inside the freezer. I have heard of people being able to recover data by freezing the batteries and one person suggested to run your phone in the freezer. I tried it and it worked.
Before I tried the freezer method I was only able to get to the Android is Upgrading screen maybe 10 times out of over 100 boot loops. The farthest I ever got on that screen was 8 out of 101 apps. With the freezer method it fully booted on the first try.
First I froze the battery alone for maybe 20 minutes. Then I placed the battery in the phone and tried booting into recovery. It didn't work. So I removed the battery, put it back in and and let both of them sit together for about 15 minutes in the freezer. Then I returned and the phone fully booted on the first try. I tried booting into recovery from Nandroid Manager but that just reset the phone. Since it seemed stable and I wanted to keep the phone as cold as possible I just used My Backup Pro and Titanium Backup to back everything up.
I honestly gave up and I am sending my phone to LG today, so this was literally my last resort. Hope this helps someone.
Click to expand...
Click to collapse
celsius0010 said:
And my replacement phone broke again.. The freezer method worked again. But the replacement (my 2nd boot looping phone) usually won't even Boot Loop. When I plug it into a charger nothing happens. Insert a full battery and try to turn it on, nothing happens. I had to press on the back really hard to get any power to the phone. Then I was able to use the freezer method for a few days, my replacement has came and I cant get it to work again. I just wanted to double check that everything was backed up, I may be out of luck...
Click to expand...
Click to collapse
bel57 said:
Thanks for the tip, it helps! Confirmed working, left my phone 20 minutes in the fridge => boot but freeze during LG animation (not cold enough)
left the device in the freezer for a moment => success boot, but freeze minutes later once it gets warmer
So... there is a problem with some hardware pieces..
Click to expand...
Click to collapse
revo420 said:
It still took dozens of tries to get everything working over a couple of days but using this method I was able to backup all my data and even wipe the phone! Just keep trying and keep it cold in the freezer. Also, charge your battery to 100% constantly rebooting drained the battery quickly. The CPU gets hot even when it looks like its running fine, keep it in the freezer while it does its commands.
Click to expand...
Click to collapse
bel57 said:
It's not *a little*. First time it succesfully booted once put 30-45 mins in freezer, but not enough, since it started freezing after a few minutes of use.
I managed to retrieve my data after leaving it for at least 1-2 hours in freezer.
Click to expand...
Click to collapse
HELLO.
THANK YOU EVERYBODY FOR YOUR INPUT.
I am getting a replacement in 3 days but I still want to get all of my data. It's great that it worked for all of you.
Though, I have not tried it because I'm afraid that it will trigger the LDI (Liquid Damage Indicator, apparently there is a white paper indicator that turns pink/red when in contact with water or moisture. It can be located either above the SIM/SD card slot (circle-shaped), near the battery contact (square-shaped) and/or on the battery itself (circle-shaped) - near the contact, also).
Did your device got wet or moist after you did this method? Any of your indicators turned pink or red?
Is there an extra precautious way to NOT get it moist or wet?
A reply is VERY MUCH APPRECIATED.
Thank you in advance,
Liv