Here's what happened to my (not rooted) G3
The phone has been weird for a couple of days, rebooting randomly once in a while, but working fine whenever plugged onto a power source. Google told me it could be a battery related issue, so I bought a new battery online (and I didn't get it yet).
This morning the phone entered a boot loop, even when plugged in to any power source. Google this time told me I could put the phone in "download mode", then restore upgrade errors via LG PC Suite. I try to do that, and the phone actually goes into download mode, but I'm not able to restore upgrade errors with that ugly piece of software because it keeps "losing" my phone usb connection. I unplug and plug it back in several times, the phone seems to make progress on the firmware upgrade screen but I see a red ASSERT error on my phone at around 15% of recovery.
Now whenever I turn on my phone and try to put it on download mode keeping the volume up button pressed, the screen will just go straight into firmware update, warning me not to unplug the usb connection, even if the phone isn't plugged. I'm able to start a restore but again the usb issue comes up and the phone is totally frozen and stuck to that firmware update screen. If I want to turn it off I need to remove the battery.
I'm doing this because I would love to recover some data from my phone, otherwise I would have done a hard reset or a flash of some kind
Please someone help me before i throw this piece of junk out of the window
Nobody able to help me in any way?
bump =(
Contact LG in this case. Might be faulty NAND memory. If it is then it will probably be impossible to get those files back...but they will replace it and fix the phone. (if it is under warranty that is...)
BTW if you take out the battery during flashing...you may hard brick the phone...then you're technically more fked
Related
I'll be as brief as I can! Been using a app from the Market called Friendcaster on my rooted Defy running a pays ROM(I cannot remember which one, but it was a early Froyo, been using it for months). Noticed phone running hot after Friendcaster updated, and got a memory warning, turned out Friendcaster was constantly syncing and filled phones memory. Went to delete app, saw a fix, so installed that. Restarted phone, soon started syncing constantly then, and when ever I went into contacts phone locked up. Deleted app, rebooted, and phone went into a boot loop. Went to recovery, cleared phone storage. Phone refused to boot. Tried flashing SKTJRD-3.4.2.74.sbf flash it got to 100%, but never went to complete, even after leaving a few hours.
Phone now won't respond, won't go into recovery, only gets white LED when you connect USB, RSD lite does not see phone. Not sure if the McGuyver hack will help, the battery gets hot if you put phone on charge, and tried a fully charged battery from a visitors phone and still with no response, I understand you only need to do this if battery is flat and you cannot charge phone.
I've had a good search around on here, and on Google but can't find anything that seems to help, frustrated, I might be a new n00b, but this is the first time I haven't been able to solve a problem with a bit of Googling ARGH! Plus my phone doesn't work.
Hope you guys can help, if not what's the chance of Moto/Voda UK swapping out/repairing phone if I send it in?
If you have a new full battery, Can you put Defy into Bootloader mode?
If it cant, it should be realy brick
You should try this thread...
http://forum.xda-developers.com/showthread.php?t=1206708
Try to :
Uninstall RDS and the drivers;
Reboot PC;
Reinstall newer dirvers and rds (the 4.9 version);
Reboot PC;
Connect Defy with USB, wait 1 minute, if not recognized try to press power button and wait 1 min. If not recognized yet, try click on Config-->DeviceID and try both options.
If not recognized yet... try another pc, try another full battery... if this doesn't work there's nothing left to do.
The McGyver trick is dangerous! Don't charge your battery with this method more than 15 minutes!
Trying to fix my daughters SGIII Sprint phone.
This morning it started going into a bootloop.
What I've tried:
1) Attempted CWM recovery by pressing (VOLUP+HOME+POWER). The screen flashing "SAMSUNG" with in small blue font in upper left "Reocery Starting..." And then the phone shuts off right away.
2) Attempted ODIN recovery by pressing (VOLDOWN+HOME+POWER). Once in download screen in ODIN I try and flash KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 but after a few seconds the phone just shuts off.
All in all I think if I can just get the phone to stop shutting down while in download mode I can at least flash something and this thing back up.
rattfink said:
Trying to fix my daughters SGIII Sprint phone.
This morning it started going into a bootloop.
What I've tried:
1) Attempted CWM recovery by pressing (VOLUP+HOME+POWER). The screen flashing "SAMSUNG" with in small blue font in upper left "Reocery Starting..." And then the phone shuts off right away.
2) Attempted ODIN recovery by pressing (VOLDOWN+HOME+POWER). Once in download screen in ODIN I try and flash KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 but after a few seconds the phone just shuts off.
All in all I think if I can just get the phone to stop shutting down while in download mode I can at least flash something and this thing back up.
Click to expand...
Click to collapse
Okay, so I had this problem and at the end of the day I had to turn it in to Samsung for warranty purposes because the phone would automatically turn off when on and then restart the boot process and turn off again. However, I found a temporary fix, if you pull out the battery wait for a while (like an hour) and put it back in, the phone should stay on longer so you can flash through Odin. The phone will no longer turn on normally because once you start the flash with Odin the boot.img has been flashed but it's a broken flash due to the fact that the phone turned off in the process.
Here are simple steps:
Take out the battery and leave it out for an hour or so (longer won't hurt)
Get the USB plug and make sure it's in the computer and Odin is started with the correct tar file already selected so that you can flash it quicker
Put the battery back in and start the phone in download mode
Connect the phone and just let it sit for a couple second to make sure it stays on
If it does stay on for more than 15-20 seconds then you can begin the flashing process
If it turns off while in download mode you can take out the battery and put it back in (you don't need to wait)
It's really all just a matter of patience because eventually, the phone should turn on for long enough
Once flashed, the phone should work for a while
So after following that process, I got the phone to work for about 2 months but the issue reoccurred. I was eventually able to flash the stock rom but the problem persisted. So I called in to Samsung to turn it in for the warranty. So far, they have "Replaced a component" in my phone. I SHOULD have it back by Monday. :fingers-crossed:
Thanks, for the response. Battery is out now so I'll try later this evening after it sits for awhile.
I hope it works for you. Just as an update, Samsung has fixed the problem and my phone has shipped as of today! So I guess it's an error on their part.
No luck yet.. Going to leave battery out overnight and try again in morning.
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem
Hey everyone,
This is an LG G3 D855, initially running on stock ROM, which shows me a completely unknown state of bricking. From what I gather, its a kernel crash.
1) Normal power button boot results in bootloop, where it restarts after a few seconds of showing the LG logo/splash screen.
2) When restarted in recovery mode, the phone is able to boot into it, shows the factory reset screen and when I confirm the reset, reboots the phone into bootloop.
3) When I hold the volume down key and connect the USB cable to boot into download mode, it temporarily shows the download mode logo and then reboots into bootloop.
4) When connected to a charger, it shows the inital battery charging screen and then reboots into bootloop.
5) When I remove the battery and connect it to a windows PC, the device is not recognized by LG PC Suite or the device manager, even after installing the drivers for the phone.
Please suggest me possible ways to think about debugging this issue. I'll be uploading the videos for each of the point shortly.
Thank you.
androiduser93 said:
Hey everyone,
This is an LG G3 D855, initially running on stock ROM, which shows me a completely unknown state of bricking. From what I gather, its a kernel crash.
1) Normal power button boot results in bootloop, where it restarts after a few seconds of showing the LG logo/splash screen.
2) When restarted in recovery mode, the phone is able to boot into it, shows the factory reset screen and when I confirm the reset, reboots the phone into bootloop.
3) When I hold the volume down key and connect the USB cable to boot into download mode, it temporarily shows the download mode logo and then reboots into bootloop.
4) When connected to a charger, it shows the inital battery charging screen and then reboots into bootloop.
5) When I remove the battery and connect it to a windows PC, the device is not recognized by LG PC Suite or the device manager, even after installing the drivers for the phone.
Please suggest me possible ways to think about debugging this issue. I'll be uploading the videos for each of the point shortly.
Thank you.
Click to expand...
Click to collapse
Try a new battery. G3 batteries die without warning sometimes and will put you into a bootloop once they fail.
If you truly were bricked you wouldn't get, albeit briefly, download mode or the factory reset screen and the phone would show up as a qualcomm or some other device on your pc.
As far as #5 goes, you need a functioning battery to get into download mode on the G3; some other devices - samsung I think - will allow you to load software without a battery but for us that is not the case.
Hopefully a new battery sorts you out.
Good luck :good:
*Anker makes a decent replacement if you can't find an original LG battery.
startswithPendswithOOH said:
Try a new battery. G3 batteries die without warning sometimes and will put you into a bootloop once they fail.
If you truly were bricked you wouldn't get, albeit briefly, download mode or the factory reset screen and the phone would show up as a qualcomm or some other device on your pc.
As far as #5 goes, you need a functioning battery to get into download mode on the G3; some other devices - samsung I think - will allow you to load software without a battery but for us that is not the case.
Hopefully a new battery sorts you out.
Good luck :good:
*Anker makes a decent replacement if you can't find an original LG battery.
Click to expand...
Click to collapse
That might just do it. I think the battery might have drained out due to broken charging port or some other reason and then died out. For now, I have an external charger on the way. I'll be trying that, and if not, the next step I'll try is to replace the battery itself.
Will keep updating.
Update: It was a battery fault. I got a new one off Ebay to test it and it has been working fine until now. Will probably change it for an extended battery later.