I searched for my particular issue and haven't found a solution that works yet so here goes. any help with this issue would be greatly appreciated.
I've painted myself into corners before tinkering with this phone and always found a way out but this time I'm stumped.
HOW I BROKE MY PHONE:
1) had latest CM 11 nightly installed but wanted to try the OTA.
2) In TWRP I restored a back up of my stock rooted software.
3) Unfroze bloat in titanium back up.
4) Checked on phone for OTA, received notification, and began download
5) On completion of download I initiated the update.
6) It booted to recovery (TWRP) and every time I rebooted, or started the phone from powered down it always goes into TWRP.
7) I attempted a factory reset and restoration of my stock back up- same result. It booted straight into recovery.
8) I factory reset and installed cm11 fresh from the SD card- same result
9) Here's my real screw up: since neither installing a fresh ROM or restoring my stock recovery weren't working I went for the nuclear option, I decided to format everything and use the LG Flash tool to get this puppy back up and running.
10) Only to discover I can't get into Download mode and while the G2 is "seen" by my PC it's listed under "other devices."
Dear kind and wise individual who's read my tale of woe. What might my next step be? I've considered attempting to sideload a ROM with TWRP in sideload mode, but I'm afraid I'd just have the same result as when I tried reinstalling CM11 from the SD card.
this
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Many thanks! I'll give this a try.
Related
So I am fairly new to rooting and didn't know that it's not a great idea to do an OTA update while you're rooted. So I did just that and when prompted to restart the phone, it did and loaded directly in to TWRP. I tried to just reboot from there and it kept going back to TWRP. So I tried to recovery from a backup, same thing, right back to TWRP. Also, I can't get into download mode. What do I do?
floydmcscroops said:
So I am fairly new to rooting and didn't know that it's not a great idea to do an OTA update while you're rooted. So I did just that and when prompted to restart the phone, it did and loaded directly in to TWRP. I tried to just reboot from there and it kept going back to TWRP. So I tried to recovery from a backup, same thing, right back to TWRP. Also, I can't get into download mode. What do I do?
Click to expand...
Click to collapse
This should help. http://forum.xda-developers.com/showthread.php?t=2451696
You need to first download the kdz and lg flash utility with drivers.
Install drivers
The factory reset deleting system, cache, internal sd.
Then shutdown your g2.
Start to downloaded mode connecting your g2
Flash kdz & voila... Done
I too bricked my phone before. My flashing stuck at 49%. Recovered using above method, all is well now
This works 1000%. I bet on it. Just remember to wipe the phone completely before flashing. You will return to stock with unrooted status in download mode. U will have your warranty back too
Sent from my LG-D802 using XDA Premium 4 mobile app
Hi all,
After holding off on the kitkat bandwagon for a while, I decided once the OTA was available that I should just do it.
Background - this is a D802 european model with root on stock 4.2.2 firmware. I also have TWRP 2.6.3.3 installed.
Prior to proceeding with the update, I made a backup of the phone and rebooted the phone a couple of times to make sure everything was okay.
After that, I then clicked install on the OTA and the phone rebooted. After rebooting it has been constantly going to TWRP. I have tried wipe dalvik, wipe cache, restore backup, restore factory settings, reboot to system but nothing works.
Also, trying to get into download mode just boots into TWRP. When I try to do a adb sideload, the device just shows up on the PC as LG-D802 and no drivers are found for the device so I am not able to install a new firmware or can't try to go back to stock either.
Please help!
Regards,
sobers_2002
*sigh*
http://forum.xda-developers.com/showthread.php?t=2451696
Hi folks,
After reading all of the horror stories about attempting to update a rooted/custom-recovery LG G2 to the latest vs98024a KitKat update, I still decided to give it a go. Mostly due to the pestering of the update dialog that kept coming up. Having a fully backed-up phone made me a little less uneasy about it. My phone is both rooted and has CWM recovery.
First, rather than attempting OTA, I used the windows-based software updater application that comes on the phone. My last OTA attempt failed, so I didn't even bother this time. The program ended up launching C:\LGMobileUpgrade\LGMOBILEAX\BYRLauncher.exe, and after downloading and installing the ROM, the phone took the update just fine. Even despite saying "ROOTED" after the phone rebooted to flash the new ROM. At this point, I have a phone that is updated to KitKat, and it's retained all of my preferences. Cool. But the phone is no longer rooted.
Oddly, the OTA dialog still came up, despite being for the same ROM version that I'm running. I allow it, and it fails. And no longer prompts me. Fine.
Back to the root thing. ioroot25 should get me root again on the phone. I follow the steps, it says that it's rebooting into recovery and then says When recovery loads, select: *apply update from adb* with power button.... Only it doesn't seem to reboot into recovery, and it doesn't give me any options. It just sits at an animated Android icon for a bit. The phone reboots and it goes through the initial setup. It did a factory reset! It's still KitKat, but everything including the SD card is cleared. Perhaps this all happened because I had CWM installed before upgrading? Slight annoyance, as I've got backups.
I do ioroot25 once again, and this time it does reboot into recovery where I can select apply update from adb. At this point I have a rooted KitKat G2. I do a reverse rsync to restore the contents of the SD card, and then restore apps via Google's backup and/or TitaniumBackup, as well as restore SMS/MMS messages via TitaniumBackup. The main annoyance now is to re-arrange icons how I had them before.
What's not clear at this point is how I get CWM back onto the phone. I had originally used FreeGee, but it reports that my phone isn't supported. ROM Manager says that CWM (from FreeGee) is installed, but rebooting into recovery still results in the Android system recovery <3e> menu system that was present when doing the successful ioroot. This is a stock android recovery, right? I don't recall seeing it before, but I guess it may be different between android phones and versions. I also tried installing CWM via ROM Manager, and the installed version number updates to what it supposedly installs, but rebooting into recovery still shows the same menu system.
Is CWM not (yet?) supported on my KK LG G2? If it is, how can I get it loaded?
Thanks.
forrestgump2000 said:
Is CWM not (yet?) supported on my KK LG G2? If it is, how can I get it loaded?
Click to expand...
Click to collapse
FTR, I ended up using AutoRec to install TWRP. It was trivial to do and worked fine.
EDIT: Well it's not solved, but in the process of trying to fix it I soft-bricked it so I forced myself to have to tot back to 4.2.2 using this thread: http://forum.xda-developers.com/showthread.php?t=2687768 . Now I'm simply trying to get it to OTA back to D80020y (on Cricket... using a prepaid AT&T sim to try and force an OTA... no luck).
I'm sure I'll end up facepalming as I've gotta be missing something simple.
I was running stock D80020y, rooted with a few exposed tweaks - nothing major. I flashed TWRP using Autorec, did a full "nandroid", then proceeded to install Blisspop 3.3 by doing the following steps:
A full wipe
Flashing LP_30d loki'd bootstack (my hunch is this is the problem)
Flashing the rom + gapps
I had lots of issues with it not recognizing my sim card and acting as if I had no service, despite the APN settings looking accurate. So I got back into recovery (had to install/run autorec again as I couldn't get into it from the rom), restored my EFS just in case, then did a full wipe and restored the nandroid - all of it.
The first time it booted up, it went through the update of every app and just hung on "starting apps". I let it go for a good 10 minutes before rebooting and it just hung at the logo prior to full boot. I got back into recovery and restored again, but no luck - it just hangs every time.
Is the bootstack my problem? I REALLY don't want to have to flash back to stock via kdz or tot as I'm on cricket and won't be able to OTA back to D80020y. Any input is appreciated!
Sprint LS980 in an odd state after trying to flash CyanogenMod 12.1
Ok... so I got two of these Sprint LG G2's. I was able to successfully flash the first one with a minimum amount of problems considering I was just learning how to do it.
This second one is a problem though. Here's what I did:
I tried to root but it could not due to the version of the Sprint firmware on the phone. I did the TOT stock flash to get it back to stock. That worked fine.
Then I was able to root it via ioroot. Once rooted, I installed FreeGee and tried to install TWRP, that didn't seem to work, so I installed CWM Recovery. I did option two on this thread to try to get the loki stuff installed using openrecovery-twrp-2.6.3.4-ls980. That "installed" and I was able to boot into it. I installed cm-12.1-20151125-NIGHTLY-ls980 (same one I used on the other phone). That would not install via CWM and gave an error about not being able to lokify (or something like that).
So I said, OK, I must have done something wrong, so I tried to redo stock flash again. That acts like everything works fine LGFlash does it's thing (using LS980ZVA_01.TOT), but the phone boots up and does not seem to finish the install process. The LG logo comes up and not the Sprint screen that I would expect. I can do this over and over again and the results are the same whether I let it sit for an hour or 10 minutes after flashing. So now, the phone boots, but I can't do anything with the touch screen, and will then go into a reboot loop (getting into the OS but rebooting shortly after). I CAN get into CWM where I can wipe data/factory reset and wipe cache partition. After I do that, the phone will boot and will let me interact with it, but after a short time (a few minutes I think), it will reboot again and be in the same state it was before I went into CWM. I tried to do a factory reset in settings. It would say that two reboots would occur, but then nothing happens.
I'm at a bit of a loss as to where to go from here. I don't think that it's an unrecoverable brick, but heck if I know how to fix it.
In between reboots, ADB does see the device in ADB Devices, but shows that it's offline, so I can push an APK to it.
Here are the options that I get in recovery mode:
Reboot System Now
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Any assistance is greatly appreciated!
Ok.. well.. I downloaded and flashed ZVE and it seems to have greatly stabilized the phone. However, it seems that I have lost the ability to do download mode and recovery mode. I can still get into the device through ADB, but ioroot no longer is able to root the device, so I can't install any recovery. There is a system update available to install, but didn't want to do that unless I'm good an stuck in this mode.
I also don't seem to be able to enable the cellular service. I don't know if the update it wants to install would fix that or not.
Edit: I can still do ADB reboot recovery and get into recovery mode with these options:
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Edit2: I was able to root with Stump. FreeGee won't run on ZVE, so not sure what to do from here. The phone does not work at all. None of the phone info is listed in About Phone. No IMEI or anything.
Edit3: I have been able to get TWRP installed and can boot into it. I have also verified that I can get into download mode now. I'm very concerned about my EFS info though. I did back it up, but not to the PC, so effectively I have no EFS backup and no way to recover the IMEI information. Not cool...