Sadly, I installed the Kitkat ota, through a misclick. I am on the Verizon LgG2. So the problem isn't that I'm stuck on the logo after the ota, it is that after successfully rooting, flashing twrp recovery and creating a backup with which I can get out of this loop easily, I cannot get a rom to work. Every time, and of four roms I have tried I am stuck in a bootloop. I am not new to doing this sort of thing and have done it perfectly without troubles before the ota, but now I can get no roms to boot correctly, and I am thus stuck on the logo. I have tried AutoRec, but to no avail, maybe because I had applied twrp before using AutoRec. Nevertheless, is anyone else having this issue or has anyone corrected the problem when they had it? I'd love to get a rom going!!
Related
Hello,
I Have a German LG G2 D802 from Vodafone.
It is Rooted and any rooted app works fine,
the first thing i realized is that i got no questions from SU for Root Access from any app but they are defenetly have them.
Then i tryed to flash a boot animation from TWRP, because i have a Vodafone boot animation.
Its flashing something but nothing changes, still the VF animation.
Today i tryed flashing the Multiwindow, but its the same.
What is wrong with my G2?
Update:
Flashed CWM With Flashify, now i think i have 2 recoverys.
After that i tryed istalling twrp With Loki via ADB, still nothing work.
now i have CWM and if i flash a file it says that i have to lokify the boot???
what the hell should i do?
Please help me
I have a question, I am using LG G2 D802, rooted, using CWM v6.0.4.4. My sister also uses LG G2 D802, she updated her G2 in Kitkat. So I want to get the update also, I opened the Update Center and tried to update, but I can't see the update for kitkat. Only "V10f-DEC-23-2013" appeared on my update list, so I update my G2, and restarted the phone, and stuck on CWM. Resolved this problem by following instructions on the threads here (Thanks to you guys!), but my question is, how can I update to kitkat when I can't get passed updating to V10f-DEC-23-2013 that stucks my phone to CWM boot loop (Tried downloading many times but stucks me up at CWM bootloop)? Anyone out there experienced this kind of problem? Can you guys please suggest me what to do?
you should update on clean stock rom without root and the custom recovery.
golinale said:
you should update on clean stock rom without root and the custom recovery.
Click to expand...
Click to collapse
What steps should I do?
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?
Hi guys I just wannted to share my expierence with my Galaxy Tab 3. From 4.1.2 to 4.4.2 I encoutered many problems and created solutions to fix them. And here are some.
The first thing that I had a problem with was when I unrooted and left busybox installed. When I did a factory data reset, the device became so laggy and almost unusable. I I could not root my device for some reason. To fix this, just simply reflash the stock room using odin. After I fixed this, I upgraded to Kit-kat and looked for a custom recovery to install. I went for clockwormod and found my self getting stuck in a cwm bootloop. To fix this, download the latest version of TWRP and install via odin. I strongly recomend to use TWRP as it does not go into a recovery bootloop unlike CWM. Now for Xposed I noticed that the boot up is way slower then before. A simple install of the module boot manager can help.
That's it. I hope I can help some new users with problems on the galaxt tab 3. If you have any other problems, just let me know and I'll do my best to help.
Sent from my SM-T210 using XDA Free mobile app
I flashed TWRP and got a recovery boot loop.
hen I flashed Clockwork, which didn't loop.
So, use most recent one which resets the switch for booting into recovery! Doesn't matter for this problem which one, as long as it is the lastest loader.
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?