I rooted with kingroot, it worked and then tried to replace it with supersu using supersume. Everything worked fine. Supersu updated and asked for reboot. So I rebooted the phone and it got stuck at verizon screen. Factory resetted it from recovery menu, still stuck at verizon screen.
LG G2 VS980
No custom recovery
No custom rom
Download mode working
I remember turning USB debugging on but it could be off I'm not sure.
Please help
Fixed it by flashing kitkat kdz file with lg flash tool. (This is my other account, idk why I made the OP one)
Related
Hi all,
I have put myself/phone in an interesting situation, which I am hoping the community can help me with.
I recently bought an LG G2, dold with stock 4.4.2. I proceeded to root it, and tried installing custom recovery.
I first installed ROM manager, which didnt work.
I then tried flashing twrp through adb using loki, which gave me a 'this is not a loki file' error.
I eventually realized that they had closed the Loki loophole in stock 4.4.2.
At this point, trying to enter recovery wouls give me a 'secure booting failed' error, making me have to reboot the phone again.
I then unrooted my phone, and factory reset it. I realized Clockworkmod recovery (which ROM manager installed) persisted despite the data wipe, so I unchecked that option in ROM manager and wiped it again.
My thinking was that I vould now downgrade to 4.2.2, install custom recovery there, then flash 4.4.2 whitout losing root or recovery.
Problem: I can't do any of this, because I can't reroot my phone with ioroot25. It fails as when it reboots inti recovery it gives me the 'secure booting failed' error.
Thanks for any help. I simply want to root my phone and if possible, have a functional recovery in order for me to flash some mods. At least being able to have it rooted again would be sweet.
Hehh...
Last thing you can do is try to flash with LG Flash Tools Method or LG Support Tool
Flash stock recovery either via fastboot / or dd(on linux). Then you can proceed further.
Or ^ kdz via download mode.
I have a similar problem. I restored the stock recovery via adb using a dd command. Then I unrooted in order to accept the latest OTA. The OTA fails with a "suspected root" error. Download mode still has "ROOTED" in red letters. At this point I gave up on the OTA and wanted to get back to where I was.
IOROOT25 doesn't work because when the phone reboots to recovery mode, I get the broken android with the red triangle but nothing else on the screen at all. There are no options, nothing. Eventually it reboots. I've done a factory reset to no avail. Recovery seems corrupted.
I need instructions for flashing the stock recovery with no root.
I managed to get my recovery rewritten using the LG Mobile Support Tool on a different computer. Then I was able to root again using ioroot25. I'm not sure why I couldn't run on my own laptop, but it's fixed now.
Could use some help/advice.
I restored the kdz using the lg flashtool to jellybean. I didn't update directly kitkat. Instead, I used towelroot to root, then I used autorec to install twrp 2.7.0.0 (or whatever it was). I then flashed twrp 2.8.5.1 and I flashed CM12. CM12 doesn't boot at all.--stuck at LG logo. If I try to use download mode to reflash kdz, it doesn't detect the phone. I can access phone in TWRP via ADB. and it detects it. Is there a way to restore the download mode to detect the phone.? I think this mess happened b/c I didn't update to kitkat and the partitions didn't get updated, but I'm not sure.
Any advice to either get download mode working again from within TWRP, or get CM12 working would be appreciated.
Thank You
zipeee2 said:
Could use some help/advice.
I restored the kdz using the lg flashtool to jellybean. I didn't update directly kitkat. Instead, I used towelroot to root, then I used autorec to install twrp 2.7.0.0 (or whatever it was). I then flashed twrp 2.8.5.1 and I flashed CM12. CM12 doesn't boot at all.--stuck at LG logo. If I try to use download mode to reflash kdz, it doesn't detect the phone. I can access phone in TWRP via ADB. and it detects it. Is there a way to restore the download mode to detect the phone.? I think this mess happened b/c I didn't update to kitkat and the partitions didn't get updated, but I'm not sure.
Any advice to either get download mode working again from within TWRP, or get CM12 working would be appreciated.
Thank You
Click to expand...
Click to collapse
You need to install the kk bootstack for your device and wipe data.
Sent from my LG-VS980 using XDA Free mobile app
EDIT: This can be marked as resolved -- I used ADB to succesfully send a reboot recovery command to the phone and it worked!
Hope I don't run into any more issues down the road.
-----------
Hi guys
In short, my LG D802 International model has lost it's ability to enter DL mode, and the recovery is also missing.
It is now running Stock Lollipop (Custom version) which I installed according to instructions with no problem
However once it was installed I then realized TWRP is no longer accessible. My next step was to then go to the Play Store and download Autorec Lollipop for LG G2 D802
https://play.google.com/store/apps/details?id=b007.autorec2&hl=en
Once that was installed I tried to install the recovery, but the app was unresponsive. The author of the app then mentioned ->If you experience unresponsive button (the button flash doesn´t work) look up this post
http://forum.xda-developers.com/showpost.php?p=65698392&postcount=797
I went ahead to uninstall SuperSU using it's full cleanup and remove function. BIIIG mistake!
That's where the problems compounded, because now SuperSU is not even working and won't let me install the SU Binaries, and the app is telling me to search forums for help
Basically: No TWRP -- No Download Mode -- No Root -- Cannot install SuperSU either!
I'm now stuck with a very unstable phone that hangs and crashes every 10 minutes. I have tried to factory reset but to no avail -- I still cannot use SuperSU.
Thanks in advance
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
nemesis101x said:
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
Click to expand...
Click to collapse
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Exodusche said:
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Click to expand...
Click to collapse
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Gamool said:
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Click to expand...
Click to collapse
Ok sorry you said 6.0 in comment that's why I asked about bootloader. Also thought was just the root giving you a hard time not the dreaded bootloop that some 6Ps get.
So i've tried rooting and installing root+TWRP over a script on my lg g2 d802 which sent the phone into a boot loop. Then i downloaded a Stock ROM (i didn't find mine so i just chose one from my country) and flashed it on the phone. I then rooted it with some script i found on youtube IOroot, which worked and and proceeded to install TWRP over AutoRec, which worked aswell BUT i was not able to get back into the system because of the phone boot looping again. I was able to go back to TWRP but not into the system itself. So i just reflashed the phone again.
Does anyone know what my mistake is here? I am pretty new to this. Could it be that because i have a different Stock ROM it doesn't work? Tbh, I don't know if i will destroy it by installing a american Stock ROM on a german phone. I've read a lot of tutorials but many are down and most of them lead to AutoRec or this Auto Script from here.
EDIT: Ok, nevermind. I installed some Stock Lollipop ROM and with that everything was pretty easy. Installed LineageOs 15.1, works great.