My G3 (never been rooted, running stock Lollipop) softbricked three days ago for seemingly no reason (I was scrolling through Youtube videos and the screen just froze all of a sudden) and went into a bootloop. It's able to go into download and recovery mode, but not much else. USB debugging isn't turned on (and since the phone won't boot up normally, I presume there's not a way to turn it on now.) Is there any way, at this point, to recover the files on it?
Kinda.
My g3 did the exact same thing and it turned out to be a battery problem. First, let it sit on the charger and try to boot for a max of 10 minutes, if that dont work, see if a store that carries the g3 battery will let you buy one, recover the files, and return it. If putting a new battery in solve the problem atleast. But, that what i did, except i just ordered a new battery and its working fine now.
Related
Hi
I have a problem with my Galaxy S2 where it's in a constant reboot loop and the only way to stop it is by taking the battery out.
I'm sure that if I do a factory reset it'll go back to normal.
The problem is, I can't back anything up because as soon as the phone boots up it restarts.
Is there ANY other way to back up my photos and videos etc?
I have NOT rooted the phone
Cannot find any solutions online
I'm currently having this problem too. A couple of days ago it kept rebooting in a loop. I took the battery out and left it for a while, then let it charge. It seemed okay afterwards. Now today it keeps rebooting, and the past couple of days it has refused to charge the battery because apparently the battery was "too hot or too cold" (don't quote me on that) so I'm very confused. Just now though the battery was about half-charged and it still went into the reboot loop.
Something else you should know is that like the OP it has the stock OS on. It isn't rooted or modified. I don't want to factory reset it because I have spent so much time customising it (with apps) and it would be a pain in the ass if the problem still existed afterwards. One thing I must ask the OP is, did you recently get a 64GB MicroSDXC card for your S2? I ask this because I did a couple of weeks ago and it's been working fantastically and was said to work fine with the S2, but I'd like to explore any possible reason this reboot loop is happening.
Thanks.
Edit: To confirm I deleted the cache and this didn't help. I don't want to hard reset...
I've just done a factory reset - I hadn't realised that it only affects my apps and not my files.
The phone is ok now.
Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.
My tablet is unrooted, untouched, unmolested, etc. Running 5.0.1 from the ota update.
My tablet's battery died while I was using it a few hours ago. I put it on the charger and wait a bit before turning it on. It boots up normally but I'm immediately greeted with the "power off" message box as soon as android loads. I've done fastboot and did the recovery boot (whatever that means in this case) and nothing I have tried has helped.
I'm afraid of tampering with it to install custom roms, because if that doesn't work the warranty would be void.
Anyone experience this problem before?
Sounds unusual but my only recommendation is to leave it on the charger overnight to get it fully powered up.
If not, you might have to boot into the stock recovery and perform a factory reset. At that point if it still doesn't work, if your tablet is completely unrooted with a locked bootloader, just send it to Nvidia.
Yeah it sounds like it's gonna get rma'd. It was charging the whole time, in the 4 or so seconds it was on the lockscreen before turning off it would show the battery percentage at something like 60%+, so it was definitely charging.
After enough tries it just wouldn't even give me the nvidia start up splash screen. I managed to do a factory reset (which seemed to take a really long time). The factory reset let it get back to the lockscreen but it immediately turned off again.
Other things for people who might have this problem as well:
It started after I put in a 32gb micro SD card I bought for it. I think the SD card is fine because it works in my phone.
Also this tablet was only about 4 days old when it broke.
The tablet is completely stock. I'm lucky it broke so soon as I was about to root it.
http://forum.xda-developers.com/shield-tablet/help/tablet-shutdown-boot-t3035492
This is my story that happened with my LG G2
I recently purchased a LG G2 F320L, a refurbished one, from aliexpress(I think this was the biggest mistake of all)
I got the phone, I started using it, used it for 20 minutes and just installed antutu benchmark and ran the app and started the benchmark.
Firstly, I'd like to mention that the phone just got warm, just like other phones, during the test. While the multicore performance test was going on, the phone turned off, all of a sudden (Battery was as low as 9% when I started antutu benchmark). I thought that, it was because the battery was too low to run a benchmark app and turned on the phone back and waited, it just showed me the LG logo for 5 seconds, powered off, ended up with a bootloop. :crying:
I thought that the OS or the bootloader got corrupted and stuck and also thought that I could easily fix it by flashing boot.img or the original .kdz using LG flashtool.
I connected the phone to the PC, it was charging from 9% (That means, low battery isn't the reason for this problem). I waited until it charged till 25% and tried turning the phone on again, but, the same bootloop happened again. I downloaded the .kdz file for my exact model and prepared to flash it using LG flash tool. Unfortunately, the phone came out of download mode (Whilst the flashing was going on) and started with the bootloop again. I really got scared cause the flashing was interrupted indefinitely. I didn't know what to do and I just googled how to enter factory reset mode and I finally entered factory reset mode and chose to reset the phone completely. But, it has happened for a while and continued with the same kind of beat-up (But I was able to enter the factory reset mode later on, though) I was pretty much scared at this time and I gave the phone to one of my friends. I showed him the factory reset mode that was still working, but not useful, and I tried resetting 3 to 4 times but couldn't come out of the bootloop. But, suddenly I couldn't enter factory reset mode and the bootloop became pretty much faster that before (Just showed me the LG logo for 3 seconds and rebooted with the same bootloop). Now, no factory reset mode, download mode, and no charging either.
I got to know that it was a really serious hard brick that has ever happened to one's phone!
I handed over the phone to another one of my friends and he dismantled the phone and tried something, then connected to the computer and the computer detected the phone and QHUSB mode was saying 'Searching Windows update' with a loading symbol. He just stopped it there and told me to take it to a good service center (An expert, of course), and he also told me that I was supposed to ask him, to make the QHUSB mode work.
But, after he gave me the phone back, the bootloop was still happening, just like before, but, instead of LG logo, it was showing some bluish white lines on the 2/4 on the screen.
I haven't got time to go to a service center till date, as they might cost me more than I invested on my phone.
This is really serious problem and I need to enter the QHUSB mode and I need to flash the stock firmware cleanly. Please anyone give some time to read this thread and help me out in this situation. AGAIN, I have used the phone for like, just 20 minutes when it was in a working condition.
So, I request any experts to help me out, suggest me the solutions.
Sorry for my bad English, though.
Thanks in advance.
SumanthBv said:
This is my story that happened with my LG G2
I recently purchased a LG G2 F320L, a refurbished one, from aliexpress(I think this was the biggest mistake of all)
I got the phone, I started using it, used it for 20 minutes and just installed antutu benchmark and ran the app and started the benchmark.
Firstly, I'd like to mention that the phone just got warm, just like other phones, during the test. While the multicore performance test was going on, the phone turned off, all of a sudden (Battery was as low as 9% when I started antutu benchmark). I thought that, it was because the battery was too low to run a benchmark app and turned on the phone back and waited, it just showed me the LG logo for 5 seconds, powered off, ended up with a bootloop. :crying:
I thought that the OS or the bootloader got corrupted and stuck and also thought that I could easily fix it by flashing boot.img or the original .kdz using LG flashtool.
I connected the phone to the PC, it was charging from 9% (That means, low battery isn't the reason for this problem). I waited until it charged till 25% and tried turning the phone on again, but, the same bootloop happened again. I downloaded the .kdz file for my exact model and prepared to flash it using LG flash tool. Unfortunately, the phone came out of download mode (Whilst the flashing was going on) and started with the bootloop again. I really got scared cause the flashing was interrupted indefinitely. I didn't know what to do and I just googled how to enter factory reset mode and I finally entered factory reset mode and chose to reset the phone completely. But, it has happened for a while and continued with the same kind of beat-up (But I was able to enter the factory reset mode later on, though) I was pretty much scared at this time and I gave the phone to one of my friends. I showed him the factory reset mode that was still working, but not useful, and I tried resetting 3 to 4 times but couldn't come out of the bootloop. But, suddenly I couldn't enter factory reset mode and the bootloop became pretty much faster that before (Just showed me the LG logo for 3 seconds and rebooted with the same bootloop). Now, no factory reset mode, download mode, and no charging either.
I got to know that it was a really serious hard brick that has ever happened to one's phone!
I handed over the phone to another one of my friends and he dismantled the phone and tried something, then connected to the computer and the computer detected the phone and QHUSB mode was saying 'Searching Windows update' with a loading symbol. He just stopped it there and told me to take it to a good service center (An expert, of course), and he also told me that I was supposed to ask him, to make the QHUSB mode work.
But, after he gave me the phone back, the bootloop was still happening, just like before, but, instead of LG logo, it was showing some bluish white lines on the 2/4 on the screen.
I haven't got time to go to a service center till date, as they might cost me more than I invested on my phone.
This is really serious problem and I need to enter the QHUSB mode and I need to flash the stock firmware cleanly. Please anyone give some time to read this thread and help me out in this situation. AGAIN, I have used the phone for like, just 20 minutes when it was in a working condition.
So, I request any experts to help me out, suggest me the solutions.
Sorry for my bad English, though.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
Try looking here:
http://forum.xda-developers.com/showthread.php?t=2475045
and maybe posting your question in there
Good luck!
I have had nothing but problems with the two G3s I have had. One had a broken screen (not its fault) so was retired. One the screen started doing this weird backlight problem. So I swapped out the internals from one into the other. to make one good one. Both the same exact ATT LG G3 D850s.
Worked fine for a year. Then today the phone just turns itself off. So I tried to turn it back on, no response. Remove the battery, turn back on. Looks like it is going to boot, gets to the ATT screen, then loops back to boot again and again.
So I said screw it, everything on it gets backed up daily, so lets factory reset it. No go, it starts to do the factory reset then reboots over and over.
So I said fine, and started to follow this guide:
lgg3root com/lg-g3-root/how-to-unrootunbrick-lg-g3/
I downloaded the proper TOT and DLL files, but when it goes to do the update, it says Model Information CHECKFAIL
Any thoughts? I do not care if I have to put a custom ROM on or whatever, I just need it to work for a few more months.
Thanks!
Update today.
Not sure if this is a battery problem or hardware problem. I do not think it is a software issue. I suspected a battery issue, which is why I tried swapping them before. I have two genuine original LG G3 batteries. One used for a year and one for two years.
I decided to say screw it and see if maybe sitting overnight with the battery out did anything.
I have two batteries, both were at around 70% originally. I think through testing yesterday one had gotten up to 80%. I had tried swapping them at various times yesterday while troubleshooting. I put one in again. It came up and started optimizing apps like it was doing the reset. I said ok great! But then it crapped out after like 5 or 6 apps. So I put in the other battery, and it made it through the entire process and has been staying on without issue.
The thing is, it would stay on the DOWNLOAD MODE without issue before, so I am not sure it is a battery problem. But I am wondering if there is a problem now with both batteries where if it gets below say 70% it doesn't work.