Hi guys it's been a while since I've rooted any devices but decided to root my LG G PAD 8.3 (V500), since it is so outdated. I'm gonna go over exactly what I did on how I got here to better understand. Sorry in advance for the long winded post.
-Anyway, I had to downgrade to 4.2.2 by using the LG Flash Tool 2014.
-Then, I rooted my device by running root.bat Also, I had SuperSU when I rooted.
-After rooting, I installed TWRP via the play store, downloaded the most recent twrp.img and flashed it via the app. It took me forever to get to recovery by pressing power+volume down and then pressing power+volume down+volume up. But after what felt like 20+ tries, I got to TWRP recovery.
-I wiped my phone and flashed the most recent Lineage ROM. Unfortunately, after flashing the ROM, I could not flash GApps because it rebooted to the ROM after flashing. TWRP let me know that I had to update TWRP and since I did not have the play store and I was once again having trouble getting into recovery, I downloaded the most recent TWRP apk.
-When trying to open the apk, it gave me a "can't open file" message which I didn't understand why. After rebooting, for some reason, it then let me run the TWRP apk and installed the TWRP app. This is when I found out that I was no longer rooted because TWRP notified me. I double checked with root checker and indeed I was no longer rooted. I have no idea when or how that happened.
-Again, I couldn't get into TWRP recovery until I plugged in my phone to my PC and for whatever reason, it helped me get into recovery. I wiped the phone and proceeded to flash Lineage and GApps.
-I read that by flashing SuperSu I may regain root, so downloaded an updated SuperSu, went into recovery and flashed SuperSu. When rebooting, the LG screen came up with a message at the top left corner reading "secure booting error! Boot certification verify". At that point, I was in a bootloop and had to go into recovery, wipe and flash again minus supersu. So I am now on Lineage with GApps and no root.
How do I regain root? And anyone know how I was able to lose it? Back in the day when I was into flashing, I never had these problems and never lost root out of nowhere like this.
Also, if I wanted to get back to stock LG 4.2.2, how would I go about that? I know that currently, I can't use the LG Flash Tool 2014 because my current ROM does not have a USB Software option in order for the tool to recognize the tablet.
Any help would be greatly appreciated, thank you.
Related
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
kaif15 said:
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
Click to expand...
Click to collapse
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Misterjunky said:
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Click to expand...
Click to collapse
The app is constantly crashing!
It would start for a second then close. I tried the TWRP manager as well with the same result.
I've lost root access when I Odined back to stock, won't I need root access to install new recoveries?
Sounds like you flashed the stock 4.4 firmware and now need recovery to root. Flash this TWRP file using Odin http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.1-hltetmo-4.4.img.tar
Once you flash it, you need to boot into recovery to install supersu to root.
Switch off the Galaxy Note 3 (remove the battery and reinsert if needed)
Next, press and hold simultaneously Volume Up, Home and Power.Release the buttons when the screen flickers and wait for the TWRP menu.
Select Reboot, then System and install Supersu for root.
Once booted, open Supersu to update it and grant permission.
Hope this helps. Good luck.
N00b needing some help. It seems I have corrupted the recovery on my rooted G3 VS985. Used TWRP Manager to flash TWRP. Followed the app's instructions, installed BusyBox, applied the KitKat/Lollipop patch, went ahead and flashed. Booting into recovery just gives me a black screen and blinking blue and red LEDs. Since I'm not an expert, I'm a little paranoid to continue.
If I use bump to flash TWRP, will that wipe the corrupted file and flash a working version of TWRP (assuming I don't eff it up)? I've also seen root methods for the G3 that install TWRP as well. If I unroot and reroot with one of those methods with a bum recovery, will I brick my device? Sorry for the n00b questions, and I appreciate the help!
Look at here forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
I have d851, looking for another alternate solution for the corrupted recovery. please help.
Same issue
Same question here also. Updated twrp from twrp manager playstore app now when i enter recovery i get black screen and boot security error. Other than that i can go to download mode easily and can boot my device to android cloudy g3 without a hitch the only problem is that i can no longer use recovery
ok so I have a vs985 that was rooted with twrp and was running stock 4.4.2 10b. Ive been on it for a while and wanted to update. went though my usually backup routine, then updated base band to 23c installed cyanogenmod 12.1 then went to install gapps but when it started it rebooted back in to twrp so I tried again with no luck same thing, so I figured I'd boot the phone and go out and grab a new download reboot into recovery and install gapps, but after rebooting wasn't able to boot back into twrp. for some reason the button combination wouldn't work nor an apps I downloaded from the browser as I didn't have play store. either way I was able to get into something that allowed for a safe mode and reboot but that was all. so I said ok I use recovery tool to flash 10b root then install twrp then same as before update modem, cyanogenmod then gapps, but after going back to 10b I was not able to get root using stump root as I had before. every time I tried loading the app and I got an error saying something about phasing and everything I tried I was able to get it to load. so I thought maybe I could run some updates and try and root from other methods and so far no luck. so I'm currently on 5.0.1 and still cant root this methods like lg one click root so others. any ideas why this is happening? I don't mind going back to 4.4.2 10b to get root but I've had no luck with the multiply stump root or others I've tried.
thanks
Andrew
So i was trying to flash hacker kernel
It bootlooped.
So i reflashed renegade and tried reflashing.
it rebooted
now everytime i try and flash anything it reboots
super su is missing.
I installed super su from play store
when i go to flash binaries it reboots.
I updated TWRP
still same thing.
If i flash anything it just boots back to recovery.
Any thoughts?
Flashed back to stock and rerooted.
Did the trick.
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
koop1955 said:
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
Click to expand...
Click to collapse
No I had previously been rooted fine and dandy. for some reason TWRP started just rebooting on any flash.
so is it not going into bootloop mode anymore? because i've been having this problem for the last 6 months. i thought i'd try again and still doing the same, it'll get to the setup at the beginning and then reboot back to twrp????
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.