Howdy folks -- I'm having issues with my G2 that I hope people here can help me with. I've already had some advice in the Noobs thread, so thanks for that.
My phone is a LG G2 D800 (AT&T) and is unlocked, being used on the Rogers network. The previous owner of the phone had installed CloudyFlex, which is what I was using until recently.
Here's the story in a nutshell:
On my first attempt to upgrade my ROM from CloudyFlex, I booted into recovery (TWRP installed by the previous owner) and then flashed the newest TWRP for my phone. I then realized I didn't have all the files needed to do the upgrade, so after the TWRP image was successfully flashed, I went to "Reboot System". Doing so gave me a non-responsive phone (LG logo then nothing but a slowly flashing LED).
I managed to get the phone into Download Mode and followed the instructions for LG Flash Tool in the first post here exactly: http://forum.xda-developers.com/showthread.php?t=2432476 which gave me a "stock" functional phone again, but one now running Jellybean (4.2.2, software version D80010o). I'd like to be on Kitkat or (preferably) Lollipop.
I am able to root the phone easily using the LG One Click Root tool. No problem there.
So that's the story. I now have a AT&T D800, unlocked and running on Rogers with Jellybean 4.2.2 (D80010o). I would like to bring my phone into 2016 by updating it to at least KitKat, preferably Lollipop (if I can). The problem is that I can't get a working recovery. Here's what I've tried:
Flashify: following its instructions exactly seems at first like it's working (I get some kind of "success" message) but when it then goes to reboot the phone, it reboots to a black screen (phone is non-responsive -- have to hold down the power button to shut it off, then turn it back on, at which point it boots normally into Android)
TWRP Manager: I've tried it as well, and get the same outcome as Flashify (apparent success followed by a black screen etc.). Once the phone is on and back into Android, TWRP Manager seems to think that TWRP is not installed.
AutoRec: I installed the version from the thread here: http://forum.xda-developers.com/showthread.php?t=2715496 ran it, and again it appeared to be successful. When it rebooted, it did go into recovery, TWRP 2.7.0.0 or something like that. Then I went to "reboot system" but got the same problem as before -- phone non-responsive, slow flashing LED, had to go back into Download Mode and flash the Jellybean TOT file, etc.
Can anyone help me figure out what is going on? I just want to get my phone to a nice stable Lollipop state with decent performance and battery life. Failing that, KitKat. Not sure what to do next.
Crisis averted: I managed to get CloudyG2 2.2 running on my phone and all seems well. Here's what I did:
I installed stock KitKat on my phone using the procedure outlined at http://forum.xda-developers.com/showthread.php?t=2663369
I then rooted the phone with ioroot (following its instructions)
I then used AutoRec to install recovery. For some reason I'm only ever able to boot to recovery directly from AutoRec -- when I try to get into recovery using the usual techniques, the phone locks up. I literally have to reinstall recovery every time and then say "yes" when AutoRec asks me if I want to reboot into recovery. Not sure why this is. The TWRP version I see is 2.7.0.0
I then flashed the KK bootloader and then CloudyG2. So far so good.
I'm a bit too shellshocked to try to install a Lollipop ROM on this phone right now. Maybe some day. In the meantime, many thanks to those who helped me out on other threads.
Why didn't you just tot to the latest rom?
stan54 said:
Why didn't you just tot to the latest rom?
Click to expand...
Click to collapse
Based on comments at http://forum.xda-developers.com/showthread.php?t=2432476 I was under the impression that the farthest I could get would be Jellybean. Then found the other thread with the KitKat TOT. That enabled me to use Autorec (though recovery still works wonky on my phone) so I now have CloudyG2.
Related
I installed superSu using this info: http://forum.xda-developers.com/showpost.php?p=48256853&postcount=664
Then I installed Rom Manager, flashed CWM 6.0.4.4, but when I choose reboot into recovery the phone reboots then nothing happens. I guess it goes off. I can restart it using the power button, but no recovery loads. What can i do to boot into cwm?
bump
Well, just in case anyone stumbles across this in the future, here's a little update.
My issue was that I guess Att had updated me to the latest stock FW (ended in o) So, what I did was follow this guide: http://forum.xda-developers.com/showthread.php?t=2432476
Then once I was back to the earlier firmware I rooted the device using this: http://forum.xda-developers.com/showthread.php?t=2448887
and finally installed CWM recovery using this method: http://forum.xda-developers.com/showthread.php?t=2497577
hope this helps someone.
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
AlexRamallo said:
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
Click to expand...
Click to collapse
This might help;
http://forum.xda-developers.com/showthread.php?t=2451696
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?
SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960
So I'll tell you the steps I've tried since I've read the guides etc. What I've done this far: So in the official wiki guide you're supposed to flash a custom recovery of course first like TWRP and then flash a Cyanogenmod ROM.
You're supposed to use FreeGee for this in the App store but this does NOT WORK so one of our awesome developers on here made a tool on here AutoRec APK that DOES work. I used that tool on here with a rooted phone to install TWRP. TWRP does work and I can boot into it, but when I flash the latest nightly for my phone in TWRP it says it flashes successfully but then after rebooting the phone you end up in an infinite boot loop.
Essentially the phone goes to the LG logo and keeps rebooting over and over and over again. I fixed this by just flashing BACK TO STOCK in download mode but I've tried twice to flash a Cyanogenmod ROM and both times I end up flashing back to stock because it won't work. What's the deal with this? I can't stand this Verizon crap and their ridiculous encrypted boot loader. Never again will I buy a Verizon phone/main service mind you. Next time I'm just going to get a Nexus or whatever. It looks like Verizon doesn't want you doing anything with the bootloader for YOUR OWN PHONE.
What should I do?
I got my spare G2 today and have run into a bit of a problem with rooting it. The root process seems to have gone fine. It says I am rooted and I can use Root Explorer to remove bloat and such, but something seems to have gone wrong with the recovery. If I try to boot into recovery, I get an error message that says something about Secure booting error. It has some other info, but the screen goes black so quickly that I can't make out what it is saying. If I hold the power button down, I can reboot the phone as normal so it's not bricked, but without a recovery I can't do any custom Roms. I've tried various methods to flash a new recovery and they all said they were successful, but I still can't get into recovery mode.
Does anyone know what I did wrong or how to get around this? The phone came with firmware 4.4.2 26a if that means anything to your advice.
Thanks a million for any help.
Looks like your recovery gone. Flash stock Lollipop Kdz then root and install TWRP with Autorec from Google Play.
Thank you. Just did the TOT method to flash back to stock 26a so thankfully all is back to normal. Now i'm afraid to try it again because I don't know what went wrong. The ioroot version I have is an older version for 24a or backwards. That's the one I used for my original G2. So I tried using a different method (one click) for this phone and it was a mistake. Could I use the flash tool to kdz back to 24a and then root using the method I know or do I have to stick to 26a for hardware reasons?