Database Users

[Q] How to re-root after CM 10.2 flash

I have a Sprint L720 GS4 that was originally rooted and running CM 10.1 off of the official nightlies. I flashed the new CM 10.2 build for jfltespr posted here : http://forum.xda-developers.com/showthread.php?t=2383143
Aside from a few apps acting weird because of the new way Android 4.3 handles notifications, everything runs pretty smooth. Biggest issue is that I lost root after upgrading. (Focal is bada**, in case anyone was wondering lol. I love having Photosphere on a non-nexus device)
The research I have done trying to solve this says all I should need to do is flash Chainfire's newest SuperSU app (v1.43 at the time of this post) and bingo, you will have root access again because version 1.43 gets around whatever issue Android 4.3 has with root. I have flashed this via CWM recovery and get the error "There is no custom binary installed and SuperSU can't install it, this is a problem. If you just upgraded to 4.3 you must manually re-root." when opening the SuperSU app after the phone reboots, and no root apps like Root Explorer or Adaway work anymore.
I have wiped data, cache, davlik, fixed permissions, re-flashed the CM 10.2 ROM and the 4.3 Gapps, then the re-flashed SuperSU app, fixed permissions again, and still nothing, tried several variations of the above process for several hours. As per procedure from Chainfire's G+ posts on how to do this, I did select 'No' when asked if I wanted to disable stock recovery flash as CWM is rebooting the phone. What am I missing?
BTW, I have no access to computer/laptop ATM, so if there is a way to do this without having to use ODIN or some other rooting tool, that would be great.

Verilin said:
I have a Sprint L720 GS4 that was originally rooted and running CM 10.1 off of the official nightlies. I flashed the new CM 10.2 build for jfltespr posted here : http://forum.xda-developers.com/showthread.php?t=2383143
Aside from a few apps acting weird because of the new way Android 4.3 handles notifications, everything runs pretty smooth. Biggest issue is that I lost root after upgrading. (Focal is bada**, in case anyone was wondering lol. I love having Photosphere on a non-nexus device)
The research I have done trying to solve this says all I should need to do is flash Chainfire's newest SuperSU app (v1.43 at the time of this post) and bingo, you will have root access again because version 1.43 gets around whatever issue Android 4.3 has with root. I have flashed this via CWM recovery and get the error "There is no custom binary installed and SuperSU can't install it, this is a problem. If you just upgraded to 4.3 you must manually re-root." when opening the SuperSU app after the phone reboots, and no root apps like Root Explorer or Adaway work anymore.
I have wiped data, cache, davlik, fixed permissions, re-flashed the CM 10.2 ROM and the 4.3 Gapps, then the re-flashed SuperSU app, fixed permissions again, and still nothing, tried several variations of the above process for several hours. As per procedure from Chainfire's G+ posts on how to do this, I did select 'No' when asked if I wanted to disable stock recovery flash as CWM is rebooting the phone. What am I missing?
BTW, I have no access to computer/laptop ATM, so if there is a way to do this without having to use ODIN or some other rooting tool, that would be great.
Click to expand...
Click to collapse
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium

nicotheandroidguy said:
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
So did that, went to superuser in the settings app, made sure apps had access, made sure prompt was on, everything else looked OK, rebooted. Still getting the 'No custom binary installed' thing with SuperSu and have no root access. Any other ideas?

Verilin said:
So did that, went to superuser in the settings app, made sure apps had access, made sure prompt was on, everything else looked OK, rebooted. Still getting the 'No custom binary installed' thing with SuperSu and have no root access. Any other ideas?
Click to expand...
Click to collapse
Reflash the rom and Gapps you won't loose any apps make sure you don't have any trace of super su then do what I said in the last post.
Sent from my SPH-L720 using xda premium

Couldn't get the supersu app to uninstall so I did a data wipe to get rid of it, re flashed ROM and gapps, went into superuser settings and set them as above. Still no root access via root checker, other root apps also don't work. Any other ideas?

Same issue on Pac-rom 4.3.

Anyone have any more thoughs on this? I know there's a huge movement that thinks Root isn't really needed anymore, but I do it for Adaway and being able to move files I download from internal to SD Card (which file explorers won't do without root for some reason), not to mention having CM on my phone. Lol, I almost can't wrap my head around the fact that I have a custom ROM and a custom recovery but no Root access.

Verilin said:
Anyone have any more thoughs on this? I know there's a huge movement that thinks Root isn't really needed anymore, but I do it for Adaway and being able to move files I download from internal to SD Card (which file explorers won't do without root for some reason), not to mention having CM on my phone. Lol, I almost can't wrap my head around the fact that I have a custom ROM and a custom recovery but no Root access.
Click to expand...
Click to collapse
ES File Explorer will accomplish this file moving without root.
Are you using Odin?
No computer... Answers that.
Do you have goo manager?
If no DOWNLOAD IT.
You may have to flash the recovery file (again. You have to do it two different ways to achieve root) through goo manager.
Goo> Menu> Install Custom Recovery it will ask you if you have custom installed. Select yes and it will freeze up for about 10 seconds and USUALLY reboot into recovery and voila, full and proper root achieved.
Source: I dealt with this for almost 2 days and accidentally figured it out. None of my super apps would work. SuperSU, SuperSU Elite, Superuser, nada.
Sent from my SPH-L720 using Tapatalk 2

Thanks for the suggestion. Downloaded GooManager. The path you specified doesn't exist. It is GooManager>Menu>settings>install OpenRecovreyScript. I tried that path anyway in case you had just accidentially misphrased it. It downloaded a TWRP file, and then did nothing else, didn't reboot. I tried rebooting to recovery directly through the main menu in GooManager, but it gives an error because I don't have root access. I have to manually reboot to recovery. Thankfully (I prefer CWM to TWRP) it didn't install TWRP. I still have CWM and nothing else has changed, still no root access.
Using a file manager when trying to move something from the downloads folder on my internal memory to the SD Card, it says operation failed every time, and in GooManager, I cannot access my SD Card files, only internal memory. I tried to re-flash the ROM via GooManager in case that would get results, but the /extsdcard is not listed and I cannot access the root folder to get to it.
I will try just about any suggestion that anyone throws up here because I am at the end of my rope with this, but doing anything via the settings or through an app is likely not going to work because you have to have root access for these things to function to start with in most cases. I had a similar issue when I first rooted my S4. I carelessly accepted the OTA update on initial activation without thinking about it, then when I went to root it I found out that update added a SETUID RESTRICTION to the kernal, essentially changing how Superuser apps interact with the kernal. I had to track down the original kernal and flash that to remove the SETUID RESTRICTION so SuperUser would work. I have a feeling the solution to this will be along those lines, but in hours of researching the only thing I can find to do is 'Flash SuperSU, it will re-root your phone'.
Is there anyone else that has had this issue with the unofficial nightlies of CM 10.2 linked in the OP where the Chainfire SuperSU workaround for re-rooting doesn't work?

I'm not entirely sure what I did, but my Super SU is working properly now.
Last thing I did was flash a version of Super SU I knew worked pre-4.3 (https://dl.dropboxusercontent.com/s...UHFu_xV9MFXYEd9A8ZltJ8l6RjX2l2QtUcGFlWWA&dl=1). I opened it and it gave me the regular error, so I gave up and decided I'd wait a few days. However, I just checked this thread to see if any other solutions were available, and someone mentioned GooManager, so I opened it and it asked for SU permission, and it was granted. I then opened Super SU and noticed it works properly now.
Sorry if this doesn't help.

PwnCloud said:
I'm not entirely sure what I did, but my Super SU is working properly now.
Last thing I did was flash a version of Super SU I knew worked pre-4.3 (https://dl.dropboxusercontent.com/s...UHFu_xV9MFXYEd9A8ZltJ8l6RjX2l2QtUcGFlWWA&dl=1). I opened it and it gave me the regular error, so I gave up and decided I'd wait a few days. However, I just checked this thread to see if any other solutions were available, and someone mentioned GooManager, so I opened it and it asked for SU permission, and it was granted. I then opened Super SU and noticed it works properly now.
Sorry if this doesn't help.
Click to expand...
Click to collapse
I tried an earlier version of SuperSU, sadly no dice.

nicotheandroidguy said:
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
So I continued to play with this, and I FINALLY got it to work. The thing is that you actually have to turn it on in two places, in superuser and developer options as well. I had tried that before, but it hadn't worked I think because I also had the SuperSU app on there. so steps I took when I got it to work:
1) Wiped data/cache/davlik (again, uggh, must have been my 7th data wipe in 3 days)
2) Reflashed ROM and Gapps
3) Wiped cache and davlik a second time
4) Fixed permissions
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
I verified root access after that with root checker. While in developer options, I also turned on USB Debugging, I doubt that had an effect, just noting for thoroughness.

this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb

zxhian said:
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Ah yes, I realized I did that too, didn't think it had an effect though.

zxhian said:
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Worked for me

zxhian said:
this did it for me:
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Since I did no data wipe, this was all I had to do - switching from root access "apps" to "apps & adb" Thanks for the hint :good:

Fixing root for me was just going into recovery and fix permissions then reboot and boom I got root

I'm on PACman 4.3 and I don't manage to have a working SuperSU...
I flashed it twice from TWRP (SuperSU update v1.65).
I put apps & ADB in SuperUser menu + in Developer Options
I fixed permissions via TWRP
It doesn't still work... When I open TricksterMOD a pop up shows up "Trickster Mod needs a rooted device and root access"...

I had a few wks a while back where I was computer-less. I used a friend's pc and slapped Odin and a few unzipped rom tars, cf-auto root. ..etc on a sdcard.. I did this so that if I had an issue I could quickly fix my phone from anywhere on anyone's pc.. Just a suggestion for anyone who doesn't have access to a computer...?
Sent from my SPH-L720 using Tapatalk 4

[Q] Lost Root after OTA update. How to properly re-root without messing the system?

Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help

First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ

I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade

I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?

Easily got my root back using Wugfresh toolkit.

Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.

[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.

gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.

[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something

gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.

If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app

[Q] Downloaded 4.4.3 but not installed

I got the 4.4.3 update notification and downloaded it. When it rebooted for the install, it went into TWRP recovery. Not sure what to do with that, I rebooted. Now I am still on 4.4.2 and getting the "up to date" when I check for updates.
I am rooted running stock ROM. Does being unlocked and rooted with custom recovery prevent an OTA install of updates?

I vevs
Sent from my Nexus 7 using XDA Premium 4 mobile app

I'm also looking for help updating to 4.4.3. I uninstalled Xposed and tried to flash the update zip with TWRP but the install failed. Does the update need to be installed via adb sideload?
Sent from my Nexus 7 using Tapatalk

When my n7 was on 4.3.1 stock rooted with unlock bootloader i updated via ota and twrp can handle it. I dont know about 4.4.3. There is a thread discussing this matter but i dont remmember where, i think is in the general. I never used side load but im using nrt nexus root toolkit for udpating to 4.4.3 and it work fine.
vs980

Same problem!!
Exactly same has happened to me. I got the notification for update than i downloaded it, it was about 70 mb , then rebooted my device, goes to TWRP recovery than what ?? I just restarted my device and in settings its still on 4.4.2 what to do Now ????

Hey all
What does TWRP stand for please?
I also got the notification to update to 4.3.3 but after downloading, when the installation began I got an error screen with the android dude lying on his back. I switched my nexus off and on again and I'm still on 4.2.2.
Now I get the same message when I check for updates.
How can I get my tablet to update again please?
My nexus is a regular unrooted tablet with the stock ROM that was installed via the previous ota update.
Many thanks
Sent from my Nexus 7 using XDA Free mobile app

hmmmm, sounds odd. same thing happened to me.
maybe TWRP(Team Win Recovery Project) cant handle it, or we should have updated it first. Or maybe we should have used CWM or Stock Recovery.
but the strange thing is that the tablet cannot find the update again!!
i'll try to update NRT (Nexus Root Toolkit) and see if i can update using that.

Don't install it, until there's an answer in http://forum.xda-developers.com/showthread.php?t=2786758 - a couple of us did install it, and we've lost root, but more importantly, recovery has been wiped, and I've been unable to reflash CWM with fastboot.

My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.

GrillMouster said:
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
Click to expand...
Click to collapse
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...

hamid_valad said:
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
Click to expand...
Click to collapse
Flashing stock recovery.img and stock system.img does not wipe all my data. Everything was still there: all my media, files, apps, and app data.
I think you're right about the Stickmount app. I did have it on my son's tablet, and I had to flash system. Last night I updated my wife's tablet. She did not have Stickmount, so the OTA installed without me having to flash system. Just to be safe I did flash stock recovery first. I put TWRP back on and re-rooted after the OTA.

Shield Tablet OTA 2.2 Update

Hi Everyone,
a little while ago, I got notification of an OTA update. My Shield Tablet is rooted, but I tried and downloaded the OTA 2.2 anyway. It failed to install the about 130MB update and after reboot I still was on 2.1 and the 2.2 notification came up again.
If your Shield Tablet is rooted, get the FULL OTA 2.2 from this thread :
https://forums.geforce.com/default/...official-feedback-thread-released-2-17-15-/4/
( get LTE or WiFi version )
then copy this about 770MB file, as well as the SuperSU.zip file to your main storage
boot into your current custom recovery and select INSTALL ZIP.....
After you flashed the OTA, flash the SuperSU.zip and reboot.
Once rebooted, re-install BusyBox and run the NextApSDFIX and reboot again !
Voi la, all set !
( you don't loose your custom recovery or anything else if you do it this way ! )

I will give this a try, thanks mate ??

The links in that post are dead for me
Sent from my SHIELD Tablet using XDA Free mobile app

tcardozo said:
The links in that post are dead for me
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
When you click on the link, you are getting some extra text. Remove everything after ".zip" and they work fine.

I can't keep root on 2.2 I am using CWM 6.0.5.0 and I tried the new TWRP and no luck. Unlocked bootloader if it helps.
On CWM: I flashed the full 2.2, wiped cache and dalvik, then re-installed SuperSU from chainfire's zip. I can't get root to stick. If I flash TWRP, recovery gets lost and I have to flash CWM. I repeat the process and nothing. Any ideas?

sixstringedmatt said:
On CWM: I flashed the full 2.2, wiped cache and dalvik, then re-installed SuperSU from chainfire's zip. I can't get root to stick. If I flash TWRP, recovery gets lost and I have to flash CWM. I repeat the process and nothing. Any ideas?
Click to expand...
Click to collapse
Did you flash the SuperSU .zip in recovery? Did you use the latest SuperSU v.2.46?
Sent from my SHIELD Tablet using XDA Free mobile app

Sure did. Downloaded straight from Chainfire's website. Unfortunately, I think I will have to revert to stock and flash 2.2. I've tried every method I know and I can't get CWM to stick or root to enable.
EDIT: I just wiped everything and went fresh. Probably needed to happen anyway. Thanks for the support!

I think I've updated to the latest version (2.2.1 is it?) and I just unlocked the bootloader. Won't I be able to flash a custom recovery and root? :/ Sorry, I'm trying to figure out why the custom recovery won't flash so when I read this I kinda panicked!

Root & recovery for LG G Pad 8.3 v500 on Lollipop (5.x.x) in 5 minutes with no PC

Hey XDA!
I updated my LG G Pad 8.3 to the korean stock 5.0.2 a while back, and now I wanted the AOSP Marshmallow rom on it - but I had no root or recovery!
Turn out (after three hours of infinite searches and no progress) that the solution is really easy - and can be done on the tablet with no PC!
Just enable USB debugging, download the KingRoot app (http://www.kingroot.net/) and let it root the device for you - it loads pretty slow but works great.
Then follow this link to install TWRP (https://twrp.me/devices/lggpad83.html) by following their link to the Play Store. Install the TWRP app, select your device (v500) and the latest recovery image, then confirm the recovery location and let it install the recovery image for you. Mine gave an error but booted right into TWRP afterwards despite saying failed.
And that is it!

Hey dude, after almost a year, someone finnally discovered how to do it! .But I have one problem, I can install the 2.8.7.0 twrp version, but I can't boot into recovery. It just stays in the LG logo, with the (normal) error text on the top left. How did you make it?

Interesting... k

Perrotti said:
Hey dude, after almost a year, someone finnally discovered how to do it! .But I have one problem, I can install the 2.8.7.0 twrp version, but I can't boot into recovery. It just stays in the LG logo, with the (normal) error text on the top left. How did you make it?
Click to expand...
Click to collapse
Have you tryied installing something like quickboot?
I'm really interested in root not to change ROM but to remove bloatware, install a serious ad blocker and perform nandroid backups.

FandangoL said:
Have you tryied installing something like quickboot?
I'm really interested in root not to change ROM but to remove bloatware, install a serious ad blocker and perform nandroid backups.
Click to expand...
Click to collapse
I have the same issue.
root ok
twrp 2.8.7 ok
reboot to recovery stay on the boot logo with "boot certification verify problem" error.
Tried quick boot same issue ...

I tried KingRoot a few months ago and had similar problems. It was kind of like a partial root that worked of a fashion but not completely.
The only way I know of to go from Lollipop to a custom ROM is to download a KitKat kdz and flash it through the Mobile Tool and then root that. Quite a hassle - and one I'm just about to start now.
I've been off the V500 forum for a little while, so maybe there is a better solution out there.

I only rooted because I'm scared of bootloop since in this thread still no answer on how to boot to recovery.
Actually I installed and used successfully an ad blocker and titanium but SuperSU can't be installed because of the missing twrp.
I hope that the thread creator will answer on how to go to recovery.
Sent from my LG-D855 using XDA Free mobile app

kingroot is still dodgy?

Do you mean?
Sent from my LG-D855 using XDA Free mobile app

it still sends alot of data to china servers?

Ok now it's clear. I will check using a firewall on the Wifi router.
Do you know where to get more information on this?
Anyway I used information from this site:
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/#comment-8930
to remove kingroot and install SuperSU
Sent from my LG-D855 using XDA Free mobile app

@FandangoL
Thanks you for the tip, it works great.

Anyone had luck with this?
I get the Boot Error message when I try to boot with twrp.

I avoided to install twrp because another guy wrote that seems not working.
Root is enough for what I need
Sent from my LG-D855 using XDA Free mobile app

Thank you very much!!!!!!!!!!!!!!!!

Had to install - uninstall KingRoot 2-3 times before SuperSU would work. Lost root access the two first times I replaced KingRoot with SuperSU, but suddenly it worked
When installing recovery image with twrp I get a message that installation failed, but anyway twrp reports that recovery image is installed. (Same thing happened with KingRoot, but then recovery image was not installed)
When I try to boot in to recovery I get the annoying boot error message

Just flashed my G pad V500 20f with Hongkong v50030b. Applied root using this tutorial here. It works. Thank you.
Then, replaced Kinguser with Supersu from the link provided by @FandangoL. Success. Thank you. Pad works great now. As happy as a clam...
UPDATE : is it me ? or with Hongkong v500 30b, it doesn't allow stock recovery mode. Screen just stayed on android lying down exclamation mark. Tried all button combo hold power then tap vol up etc etc .. but none worked.
Read in Google+ Lg G Pad 8.3 forum :
Hi guys, I need your help. I just flashed the Hong Kong version of 5.0.2 to my gpad using LG Flash Tool 2014 and everything went well. Now I found out that there is a 5.1 update in the net for gpad and I even manage to download it. But the problem is that the update file is in zip format which means that I cannot use the Flash tool and it seems that LG disable recovery mode to allow sideloading of update zip files. I really don't want to install custom recovery so if anyone of you have any idea of what I can do to flash this update, please help.

Finally got TWRP to work
Next step is to install cm-13.0
Followed this post to get TWRP working. Had some problems regarding location of *.img files. But if you read the thread I have explained what I had to do.
http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846

xurena said:
.
Now I found out that there is a 5.1 update in the net for gpad and I even manage to download it. But the problem is that the update file is in zip format which means that I cannot use the Flash tool and it seems that LG disable recovery mode to allow sideloading of update zip files. I really don't want to install custom recovery so if anyone of you have any idea of what I can do to flash this update, please help.
Click to expand...
Click to collapse
Do you mean exist a stock update with 5.1 in zip format?
Sent from my LG-D855 using XDA Free mobile app