Hey,
I've messed up my phone many times before but I usually find my way and end up fixing it. This time, I have no idea.
I got a new refurbished LG G2 in the mail after my old one had completely broken down and Rogers honored their warranty and sent me a replacement. This replacement took a while and I became an iPhone guy for a bit (about a month). Usually there aren't much options for the D803 but this time I seen the new 5.0 Lolipop Resurrection Remix for D803 and having been away from andriod for so long I wanted the latest and greatest features so I blinded installed it (after rooting using towelroot and installing recovery through AutoRec). I used TWRP to flash the ROM and then GAPPS right after. When the phone restarted it would pass the LG boot logo but got hung on the Resurrection Remix boot logo for quite some time. I let the phone sit for a few minutes and it finally went to the setup page of the ROM. I input everything and being worried that this would happen again when I restart my phone, I used Flashify to flash a 4.4.4 ROM because I thought it was the 5.0 ROM that was causing the problems. The phone still hangs sometimes. So I thought I would go back to stock using LG Flashtool and a D803 Kdz. (which I've done numerous times before). I then realized that whenever I connect my phone to my computer, it doesn't recognize it at all. (makes no noise, but it charges). The phone doesn't prompt me to select which method I want to use for my usb connection either (usually it asks if I wanna use it just to charge, MTP, tether, etc).
I realized I probably did a couple of things wrong here and I was wondering if anyone knows where I would start to get my G2 back to working order. (I hate using the iPhone)
Any help
Same probem here, i read in other post that it's a problem on boot image, i don't know i kdz tool can be the cause but after that i got back stock firmware doesn't work.
here my post http://forum.xda-developers.com/lg-g2/help/usb-otg-t3012311
Related
Hello all,
This is yet another bootloop story, although I haven't found anything quite like it yet, hence the idea to post it here for reference and in case some of you have interesting ideas to explore...
This is gonna be a bit long, but TL;DR: After my phone got "spontaneously" stuck into a bootloop, I find that only the stock 4.2.2 rom works, and no other.
So, tuesday I get back home with an empty battery and a Nexus 4 (running latest OTA) that has switched itself of after a day of somehow intense usage. No worries, I plug the AC adapter, let it charge for a bit and switch it back on. Booting seems a bit long, but I have to take care of a few home chores so I let it do its thing before coming back to it a few hours later. Only to find it still displaying the animated nexus logo. After a few switch off/switch on cycles, I understand its pretty stuck and I need to be more radical about it. So I enter the bootloader menu, and OEM unlock the phone (I had never needed to do that) hoping the full wipe associated with that will clear things up.
Well, it didn't. So I guess I'll need to flash a stock rom, and so I do. Since 4.4 is available on Google's stock roms page I try that, the animated logo changes but the end result is the same. So I try again with the latest JB (4.3) and still the same result. I get more than a bit frustrated but it's late and I need some sleep.
The next day, I call Google's warranty desk in France. They tell me that since the phone fell a few month ago, they cannot take it under the warranty program, and so I have to ask LG. Knowing there's no reasoning that will get me past the clerk that answered the phone I hang up after saying I'll get back to them via snail mail. Which I'll probably do soon, because I'm very disappointed with the way that warranty desk works.
Once at work, everytime I have a few spare minutes, I try to reflash with a new tool just in case it does more than automate what I did manually (nexus root toolkit being the one I tried most). It doesn't change a thing and my phone is still a nice animated paperweight.
I don't know why I ended up trying that, but I finally tried flashing the original 4.2.2 rom, and lo and behold, my phone finally got to the SIM code screen ! Everything worked nice after that, so once back at home, I go for the offered OTA upgrade to 4.3. Well, guess what, back to paperweight. Before reflashing 4.2.2, I took the time to flash CWM and activate adb by modifying /system/build.prop in the 4.3 image. This showed a recurrent problem with "system_server" segfaulting at launch (and it might have been caused by hal_sensors_get_list not returning anything, I have no clue). Trying the same on 4.4 yielded the same result.
Back to 4.2.2 and everything works fine, but I get nagged by the OTA notification, and more than that I'm wondering if there's any hope I might understand and fix the problem with my phone.
So, ladies and gentlemen, any clue that would help me is very welcome !
I plan to try a CM rom this week-end to see if it has the same problems as the stock one, but I have little confidence it doesn't. My guess is I have a hardware problem that's non-critical except it triggers a bug in 4.3+...
Thanks for reading !
--
Alain Perry
Same case, mi phone is totally stock and stuck on logo
KRT16S: no luck
I only had the time to try KRT16S this week-end, and this latest update doesn't change a thing. Same symptoms. So I guess I'm stuck on JB 4.2 for the coming week...
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Bump
dantheman9703 said:
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Click to expand...
Click to collapse
try to flash kdz via flash tools
gembo said:
try to flash kdz via flash tools
Click to expand...
Click to collapse
I've done this. But I found one from a new source and I'll try it again. Would I need to flash the radio again? Thank Thank you for the help.
This is almost embarrassing to post, but I need some help...
I have the T-Mobile G2, btw, which was rooted and with TWRP 2.6.3.3
So I was installing an AOSP ROM, and like a dumbass, instead of installing gapps like I meant to do, I accidentally flashed Smikey's KitKat ROM on top of Cyanfox. I realized it too late to stop it, and once the flash finished, I did a wipe of everything but internal storage and tried to restore a backup of CloudyStock. When I rebooted it goes to the LG screen with a secure boot error, and then a black screen where you can still see the backlight if you tilt the phone.
I tried using the LG Mobile Support tool to go back to stock, (It will go into download mode), but I can't get it to push any of the three stock images to the phone.
Holding down and power to do a hardware reset doesn't work either.
Help!!!
I picked up a cheap Tmobile prepaid to use until I get this figured out, but I want my G2 back! Does anyone have any advice at all, or did I brick my phone beyond repair?
I forgot to mention, I'm not sure if it's the phone or the drivers aren't properly installed on my computer, but LG Mobile support tool is reading my phone as a V500...
http://forum.xda-developers.com/showthread.php?t=2010624
Anyone know if this method for unbricking the Optimus G will work?
Main:
Ok, so I was waiting until i got a new phone so i can root my g2, well never happened as my g2 decided to randomly freeze up and restart and get stuck in boot loops either on the LG logo, or freeze on the T-mobile splashscreen and restart infinately. So now i got a new phone and i want to root the old one, But first up I need to figure out what is causing the random boot loops, freezing, and shut offs. It's a T-Mobile variant
ALSO: IT WAS NEVER ROOTED, So it's not a root related issue.
NOTES:
plugging it in help increase chances of escaping loop
It doesn't require a plug in to fix but it helps.
Reboot/Glitching occur when phone is in use and out of use.
Phone works normally otherwise but suffers these glitches
Phone has be factory reset twice
Phone has no external damage
Possible Internal:
Broken L. speaker due to rain
Maybe water damage from steam (phone was on counter as i showered a few times)
possible battery issue
Maybe a bit of drop damage as i did drop it a bit, but it was in a tech21 impactology case, and it remains not cracked
I have a similar issue. The phone will loop the LG logo, but only sometimes--at other times it will poop android's boot animation until it decides it wants to boot normally.
It happens in every ROM(ota or cuatom) even after flashing the stock .tot file about 4 times, so it's clearly a hardware defect for me & probably you too. I read the logs & saw rtc blah blah time will be lost on reboot & other errors. During normal use it randomly freezes prior to rebooting itself, though it reboots even while idle for long periods.
Unfortunately I don't have a solution for your problem besides restoring the stock image.
http://forum.xda-developers.com/showthread.php?t=2432476
After that you can trade the phone in, sell it, or send it to LG.
Powered By "Yeeart!"
So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops
pvt900 said:
So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops
Click to expand...
Click to collapse
It fixed my problem temporarily, but not too long afterwards all the issues came crawling back. For this reason I suggested ditching the phone completely unless you really want LG to examine it.
Powered By "Yeeart!"
Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff
pvt900 said:
Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff
Click to expand...
Click to collapse
I've heard of the random reboot issue. Fixes have been created and detailed. Please give me the following info, and I can help you resolve the problem:
Current Baseband Version
Current Bootstack / Modem
Root status in recovery
Current ROM and Carrier
Current Recovery
I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?
jkeats20 said:
I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?
Click to expand...
Click to collapse
What I had in mind is a multi-step solution that didn't involve opening the device - we can try it, and if it doesn't work then I guess you should try it. I've never actually heard of the pin-shorting, can you post links to the threads?
Anyways, this is roughly what we can try (I can give you all the files you need if you give the info from my first post):
1. Get to fastboot
2. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things
3. Reboot to download mode
4. Reinstall the kitkat TOT
5. Install custom recovery and wipe all partitions
6. Kitkat TOT again
7. Factory reset (yes, even though this is a fresh install)
8. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things AGAIN
I've tried these steps before on a friend's VS980 and they seemed to fix the problem. I know that this seems overly complex, but it has been documented in other threads. Provide the info, I'll get the files, and let's get started.
I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
jkeats20 said:
I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.
dmezh said:
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.
Click to expand...
Click to collapse
Did you have a chance to try this out? It sounds like a good way to get the phone into fastboot but am reluctant to try without knowing if it's going to work. Thanks for your suggestions so far - and no rush on getting back I have a working backup phone at the moment.
Hi guys!
I just registered now but I am not new to this site at all.
Well, I have been using an LG G2 D802 (currently D80230B 5.0.2) for about one and a half years now, and I thought about proceeding further than rooting. I installed TWRP and flashed a volume boost mod with it succesfully.
The problem occured when I tried to flash a custom kernel in the hope of smoother system, features and customizability. I will write down in steps what I did:
1. I downloaded the kernel and put it on the storage of the phone.
2. I booted into TWRP and flashed the zip
3. I Wiped dalvik (or art? idk) / dalvik cache
4. Tried to reboot, I have only seen the lg logo appearing from time to time, but it's stuttering and sometimes the logo has green pixels around the screen. I can get it into download mode, but I had no result with flash tool, the software either stopped responding when I started the update without reading the phone, or it said after a minute of waiting to read the phone that port not found (USB or something).
Any ideas I can unbrick my G2 with, I really don't want to have it gone, I can't afford a new phone yet.
P.S: I have sent it to the service once in the past, so I guess my warranty is void by now.
EDIT: I got it working, the problem was that I didn't set the folder containing the kdz file at 'Work Directory'.