Database Users

Can't Get Cyanogenmod On Verizon LG G2 V2980

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?

[Q] Custom recovery install bricks or overwrites

I can't get a custom recovery install to work. I've been at it for hours and I need to go to bed. For some reason, I can't install a custom recovery on my USA AT&T i337. I'm going to list what I've tried, it will be easier:
Installing TWRP through TWRP manager (TWRP manager crashes while flashing, soft brick)
Installing TWRP through Flashify (says it worked, then soft brick on reboot)
Installing CWM Touch through ROM Manager (says it worked, even shows version of currently installed recovery, soft brick on reboot)
Install/root with CASUAL (says it worked, soft brick on reboot)
I've never had this much trouble getting a custom ROM onto a new phone. Any idea what's going on? Seems like everything I read applies to everyone but me.

http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.

jmjoyas said:
http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
EDIT: found the list, ignore dumb obvious question.

v1nsai said:
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
Click to expand...
Click to collapse
Yes, you're limited to the roms you can flash. See this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app

Bit of a problem here.

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?

Help me get beyond Jellybean -- Weird recovery problems

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.

Root SM-T580 with Odin/TWRP and upgrade afterward

Hi,
My goal is just to root the device so that I can remove bloatware. I don't intend to run custom ROM. I'm currently running 7 QF1 build
Found https://forum.xda-developers.com/galaxy-tab-a/how-to/newbie-friendly-twrp-root-tab-tablets-t3552509 but want to confirm a few details before proceeding.
1. It seems the first the step is to flash TWRP with Odin. Is this correct? Is there a particular version of Odin or TWRP that I would need?
2. Once that's done, it's to install SuperSU using TWRP. Is that correct? Once that's done, what should I do if the SuperSU tells to upgrade later?
3. Once step 1 and 2 complete, the device would be rooted. At that point, what should I do with system upgrade? Can I still take it OTA? Or it has to be manual? If manual, how do I disable auto update?
Thanks

i know this is old but if you install twrp through ODIN you will no longer be able to get OTA. it will recognize that the recovery partition has been tampered with and refuse to update. only way around this is to update to current first before putting twrp and attempting root. As far as your other questions i cant help because im having trouble installing twrp myself, have to keep reverting to stock....

AesopRock127 said:
i know this is old but if you install twrp through ODIN you will no longer be able to get OTA. it will recognize that the recovery partition has been tampered with and refuse to update. only way around this is to update to current first before putting twrp and attempting root. As far as your other questions i cant help because im having trouble installing twrp myself, have to keep reverting to stock....
Click to expand...
Click to collapse
If you keep reverting to stock after flashing TWRP it is because you are allowing the tab to reboot to system after the flash. When it does that, it rewrites the stock recovery. You have to uncheck the auto reboot option prior to flashing. Then, after flashing, hold the Home, Vol down and Power buttons for about ten seconds. As soon as the screen goes black, switch your finger from Vol down to Vol up and the tab will boot to TWRP instead of system. You have to quick when switching from Vol down to up.
As to OTAs, that is pretty much a lost cause. What you have to realize is that once you have flashed TWRP, for all intents and purposes you are now running a "custom ROM" and won't get OTAs from Samsung. You might as well go ahead and install a ROM like RR and a minimal Gapps rather than manually erasing apps. That is pretty much their purpose. That and getting the latest Android versions without wait forever to get them from Samsung. They DO NOT need to be rooted and that is what most people that avoid custom ROMs are worried about.

lewmur said:
If you keep reverting to stock after flashing TWRP it is because you are allowing the tab to reboot to system after the flash. When it does that, it rewrites the stock recovery. You have to uncheck the auto reboot option prior to flashing. Then, after flashing, hold the Home, Vol down and Power buttons for about ten seconds. As soon as the screen goes black, switch your finger from Vol down to Vol up and the tab will boot to TWRP instead of system. You have to quick when switching from Vol down to up.
As to OTAs, that is pretty much a lost cause. What you have to realize is that once you have flashed TWRP, for all intents and purposes you are now running a "custom ROM" and won't get OTAs from Samsung. You might as well go ahead and install a ROM like RR and a minimal Gapps rather than manually erasing apps. That is pretty much their purpose. That and getting the latest Android versions without wait forever to get them from Samsung. They DO NOT need to be rooted and that is what most people that avoid custom ROMs are worried about.
Click to expand...
Click to collapse
Thanks for the info.... i was aware of all that and i was doing everything right i just didn't realize i couldn't use any old twrp posted for my device in my devices rom and recoveries section. Reading through the 50 some odd pages i found one that worked for oreo and voila everythings fine now