Database Users

[Q] Help PLEASE!!

Okay first of all, let me start by saying this is my first post and I AM a noob, so be patient.
Okay, my problem is that I can't root my Sprint Samsung Intercept. I've tried SuperOneClick, Z4Root, Universal Androot, and some other one. NOTHING has worked. The SuperOneClick somewhat worked, it installed SuperUser but when I downloaded apps that require a root, they said my device isn't rooted.
I'm with Sprint and running 2.2.1.
Pease help because this is driving me crazy!!

i dont know how this stuff works either but my brother has that phone. it could be your usb isn't reading. or rather, your computer isn't recognizing the device. google samsung intercept usb and you'll see a lot of issues. this may not be your problem but its better to tell you just in case. so far for his cell phone, because he wants to tether it to his computer, so far nothing works. not downloading the right drivers. loading without debugging. mounting the sd card. thats one big solution that hasn't worked. i have high hopes for this other fix, to load samsung pc studio. New_PC_Studio_1.4.0.IL2_4.exe is the file. you can google and find it.
this site has some info. if it works and i remember to, ill repost and let you know.
en.kioskea (take out space, insert a dot)net/forum/affich-240949-samsung-sgh-f480-usb-driver-problem
hope this helps. if not then good luck. and heck if anyone else knows why exactly it does this and a real fix other than the whole disable usb debugger issue. then let me know. i even thought about trying to load the sdk for android to see if that would create some sort of connection with the phone and computer. thanks and take care

hope this helps
sdx-developers is the best place for intercept developement
http://forum.sdx-developers.com/int...ructions-on-rooting-spring-samsung-intercept/
follow the first step to get SWUpgrade setup (the rest is instructions for eclaire [pretty sure])
http://forum.sdx-developers.com/int...-2-2-(easy-root-via-swupgrade)-(battery-mod)/
flash this kernal with SWUpgrade and youll be rooted.
http://forum.sdx-developers.com/int...important-features-working!)-(updated-11311)/
i assume youll be wanting a recovery as well i recommend cm01 get the tar and flash it just like the kernal
intercept doesnt have many custom roms but there is tons of mods you can apply to the stock rom

I tried SWUpgrade and I bricked my last phone but it didn't matter because it was already defective.
Sent from my SPH-M910 using XDA App

did you patch SWUpgrade? delete everything in the binary folder except the file you were trying to flash?
ive never had a problem with it. it even saved me from quite a few softbricks in the short time ive had my intercept.

I did everything the videos and forums said to do. When I did that I got a different kernal but I couldn't get any service, my phone would restart every 2-5 minutes, and it would randomly vibrate. Until I got another one. I finally got SuperOneClick to get passed the "waiting for device" stage and I supposedy rooted my phone, when I tried to install apps that required root access they said my device is not rooted.
Sent from my SPH-M910 using XDA App

Root intercept on froyo????

My friend has the samsung intercept and I was going to help him root it. I have tried Z4root and gingerbreak but they didn't work.
Does anyone have a site on how to root? Or instructions?
I am a very experienced android user and I am very comfortable with ADB if it is needed.

Anybody know?

Let's try again. Does anyone here know?

S.D.X. Everything you need to know for the intercept

Yes I found that method as well. We tried that about twenty times along with another 1 click at xda, z4, and gingerbreak. Is there an Adb method? Also, would rageagainstthecage work?

Jmoney47 said:
Yes I found that method as well. We tried that about twenty times along with another 1 click at xda, z4, and gingerbreak. Is there an Adb method? Also, would rageagainstthecage work?
Click to expand...
Click to collapse
S.D.X. is a website S.D.X. developers They have several guides to rooting.I rooted mine with a programed called sw updater with my pc but now ther are easier ways.

Ok thank you I will check it out

You're going to need to run one (or several) of the root exploits (until they 'take') and then edit some files manually via adb to make it permanent. See the SDX Developers website as previously noted.

It won't let me post a link but Google this...
how-to-install-custom-kernelrom-on-your-intercept-using-cm01-recovery
I did it with SWUpgrade Tool, but...
1) Even though I could connect and swap files between my phone and my computer over USB, SWUpgrade for some reason would not recognize my USB connection on Windows XP SP 3. This page along with the Samsung driver link on the same page saved my ass...
Google this - Troubleshoot driver error June Fabrics android
2) With the SWUpgrade you have to be really quick and unplug the USB and take out the battery when he says to, or you will not get the custom recovery installed. It took me about 4 tries before I was able to get the custom recovery in my phone.
I previously did the rageagainstthecage method, and while it worked, at one point I stupidly took out the battery when it froze before I had put in a custom recovery and done a backup and I very nearly bricked my phone. It would not bootup after that no matter what. Fortunately I was able to boot into the Virgin Mobile recovery and start from scratch wiping and resetting my phone, but I had to re-download all my apps from the Market all over again which fortunately the Market kept a record of.
I used the first link for the kernel and I am very happy. Just take it slow, be careful, and follow the instructions exactly.

Rooting using ADB Tool Manual Method
Please see my post in the following thread:
http://forum.xda-developers.com/showthread.php?p=13849534#post13849534

Ok guys thanks for the advice however I have been having one problem:
I cannot seem to get the drivers installed successfully on my computer. It is windows vista x86. I have tried the easytether drivers and the samsung drivers but for some reason they don't work. Any ideas?

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

Lollipop update for gpe live

I have the update installed on my tablet right now. I pulled the update from cache and am working on uploading the file now.
and here it is
https://drive.google.com/file/d/0B_zOoAATV12ZNmVpb1BISndoWkU/view?usp=sharing
Restore to completely stock 4.4.4 here.
http://forum.xda-developers.com/showthread.php?t=2910570
V510 4.4.4 .tot
Also, there seems to one thing left out of the instructions. Don't plug your phone into the USB until after sitting up the file paths in lgflashtool and hitting the arrow to begin the flash. After the message reads ready, then plug in the phone.
Although you initially have to connect the USB to set up the driver before getting to the above step. Its a tricky process and took me a little while to get to work.

Also just had the system update notice on my gpe, downloading now. Hope it is a good update on the gpad
Sent from my LG-V510 using Tapatalk

What if I am rooted
Would it be a problem to get back root? I actually need to be rooted for some stuff I do at work. I ask because I do not see a big developer presence for this tablet.

vtmike said:
I have the update installed on my tablet right now. I pulled the update from cache and am working on uploading the file now.
and here it is
https://drive.google.com/file/d/0B_zOoAATV12ZNmVpb1BISndoWkU/view?usp=sharing
Click to expand...
Click to collapse
I got the OTA but I had forgotten that I still had TWRP installed even though I'm on the stock 4.4.4 rom and not rooted anymore. TWRP interfered with the install and now it says my system is already up to date! Grrr.
Would it work if I just flashed your file via TWRP?

kuboa said:
I got the OTA but I had forgotten that I still had TWRP installed even though I'm on the stock 4.4.4 rom and not rooted anymore. TWRP interfered with the install and now it says my system is already up to date! Grrr.
Would it work if I just flashed your file via TWRP?
Click to expand...
Click to collapse
I had a similar situation. It does not work with twrp. I followed this thread to get completely back to stock 4.4.4 and then adb pushed the update file.
http://forum.xda-developers.com/showthread.php?t=2910570
V510 4.4.4 .tot
Also, there seems to one thing left out of the instructions. Don't plug your phone into the USB until after sitting up the file paths in lgflashtool and hitting the arrow to begin the flash. After the message reads ready, then plug in the phone.
Although you initially have to connect the USB to set up the driver before getting to the above step. Its a tricky process and took me a little while to get to work.

vtmike said:
I had a similar situation. It does not work with twrp. I followed this thread to get completely back to stock 4.4.4 and then adb pushed the update file.
http://forum.xda-developers.com/showthread.php?t=2910570
V510 4.4.4 .tot
Click to expand...
Click to collapse
Thanks for the quick reply! I suspected that much and I've been trying to find a "back to stock recovery" tutorial for the last hour but failing, so I really appreciate the link. Cheers.

kuboa said:
Thanks for the quick reply! I suspected that much and I've been trying to find a "back to stock recovery" tutorial for the last hour but failing, so I really appreciate the link. Cheers.
Click to expand...
Click to collapse
No problem. It was a bit frustrating to get everything to work and not very straight forward process. Would be much easier to just push the stock recovery in fast boot, but I couldn't find a file anywhere. It may be possible to extract it from the tot file from that thread but I couldn't figure it out.

vtmike said:
No problem. It was a bit frustrating to get everything to work and not very straight forward process. Would be much easier to just push the stock recovery in fast boot, but I couldn't find a file anywhere. It may be possible to extract it from the tot file from that thread but I couldn't figure it out.
Click to expand...
Click to collapse
Same here, no stock recovery anywhere. When I first bought the tablet I thought it was gonna have developer support like crazy, but no, it hasn't gained much traction unfortunately.
I'm doing the LG FlashTool thingy, but I don't see any movement in the tool. The tablet is in Download Mode and the tool looks like this: http://gyazo.com/47c9009fc9f90bffa582890d0a8e1587 No feedback whatsoever... is it working? Should I just be patient, do you think?

schalmers said:
Also just had the system update notice on my gpe, downloading now. Hope it is a good update on the gpad
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
Check to see under device manager if the driver is set to com41, and the other thing I mentioned previously, get to the point that photo is at without the tablet plugged in, then when it says ready plug it in.
kuboa said:
Same here, no stock recovery anywhere. When I first bought the tablet I thought it was gonna have developer support like crazy, but no, it hasn't gained much traction unfortunately.
I'm doing the LG FlashTool thingy, but I don't see any movement in the tool. The tablet is in Download Mode and the tool looks like this: http://gyazo.com/47c9009fc9f90bffa582890d0a8e1587 No feedback whatsoever... is it working? Should I just be patient, do you think?
Click to expand...
Click to collapse

I have an error during update. And now the update notification is gone after restarted the tablet
Sent from my LG-V510 using XDA Free mobile app

Would be great if someone could get this working for the V500.

chding said:
I have an error during update. And now the update notification is gone after restarted the tablet
Sent from my LG-V510 using XDA Free mobile app
Click to expand...
Click to collapse
You have to make sure you have completely stock 4.4.4 and recovery for it to work.

vtmike said:
You have to make sure you have completely stock 4.4.4 and recovery for it to work.
Click to expand...
Click to collapse
Any idea where can I get the factory image?

My update finally works!
My Gpe Gpad only has root and Xposed. I uninstalled Xposed and removed root but OTA was still failing with a generic 'ERROR' message. No details. However, when I sideloaded the update, I got the message "system/etc/permissions/platform.xml has unexpected contents". I figured out which app modifies this file. It's called Kitkat SDFix. This Play Store app modifies this file to enable read/write access for external sdcards. The developer makes a backup of the original platform.xml file (in the same location - system/etc/permissions/). So all you need to do is rename the modified platform.xml into anything else and rename the original backup back to platform.xml. You'll need a root explorer to achieve that.
After that the OTA works fine for me. Hope this helps someone else. Not that I had no custom recoveries or kernels so this process is for people who only had root and Xposed.

vtmike said:
I had a similar situation. It does not work with twrp. I followed this thread to get completely back to stock 4.4.4 and then adb pushed the update file.
http://forum.xda-developers.com/showthread.php?t=2910570
V510 4.4.4 .tot
Also, there seems to one thing left out of the instructions. Don't plug your phone into the USB until after sitting up the file paths in lgflashtool and hitting the arrow to begin the flash. After the message reads ready, then plug in the phone.
Although you initially have to connect the USB to set up the driver before getting to the above step. Its a tricky process and took me a little while to get to work.
Click to expand...
Click to collapse
From this thread mentioned earlier.
chding said:
Any idea where can I get the factory image?
Click to expand...
Click to collapse

vtmike said:
You have to make sure you have completely stock 4.4.4 and recovery for it to work.
Click to expand...
Click to collapse
vtmike said:
From this thread mentioned earlier.
Click to expand...
Click to collapse
Thanks mate. I was using this restoration instead.
http://forum.xda-developers.com/lg-...510-gpe-4-4-4-ktu84p-l002-stock-twrp-t2797883
and follow http://forum.xda-developers.com/showthread.php?t=2575783 to boot twrp

kuboa said:
Same here, no stock recovery anywhere. When I first bought the tablet I thought it was gonna have developer support like crazy, but no, it hasn't gained much traction unfortunately.
I'm doing the LG FlashTool thingy, but I don't see any movement in the tool. The tablet is in Download Mode and the tool looks like this: http://gyazo.com/47c9009fc9f90bffa582890d0a8e1587 No feedback whatsoever... is it working? Should I just be patient, do you think?
Click to expand...
Click to collapse
Same here. Uninstalled LG drivers, cleaned up drivers in device manager (Win 8.1), still stuck. I'm clicking the yellow arrow, then plugging in.

Colchiro said:
Same here. Uninstalled LG drivers, cleaned up drivers in device manager (Win 8.1), still stuck. I'm clicking the yellow arrow, then plugging in.
Click to expand...
Click to collapse
When you plug in the tablet it shows up as LG-something-something in Windows Device Manager. It was showing up as COM4 though, after changing that to COM41 I didn't have problems anymore. Did you do that first? The option is buried under a menu a couple of clicks down but it's there.

vtmike said:
Check to see under device manager if the driver is set to com41, and the other thing I mentioned previously, get to the point that photo is at without the tablet plugged in, then when it says ready plug it in.
Click to expand...
Click to collapse
Thanks for the tips. I was able to restore to stock with your link and apply the 5.0 update. The port was off on mine, so that tripped me up a bit at first.

Trying to go back to stock but having problems with the LG Flash Tool giving me the Download user image is only available in the online environment!! error message. Any ideas?
Edit: Never mind. Got it working.

Lg G Tab 10.1 Vk700 Root Method Confirmed!

This Has been confirmed to work on VzTab May not work when lolipop comes. So i found this on accident and tryed these two methods together to get the end desired result. Root Access! The first thing to adress is if your using windows 7 or 8 its a bitc# to get adb to recognize that your devices is connected. So if this becomes a problem i can find the link i used to address it. So you will download all the required files that go along with this 1st method contained here.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Along with the lg drivers youll need the tablet to install the verizon software upgrade assistant too.
Fallow all of the processes until you reach the download mode. I could not figure out how to manually push buttons to make it into download mode so use this next link and run all the procedures till its in download mode.
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Now you have the desired screen fallow the rest of the instructions from the first tut. Then press and hold power and volume buttons to reset. Since you cant take battery out or command it to reset. The Downloader will indicate 0% still so dont think it failed if it doesnt say 100%.

and too root the lollipop update download the files off rootjunkys site awesome work lol yes it was originally for the note 4 but shush it works
install kingroot (yes its in chinese dont worry we will be installing supersu very soon)
make sure adb is working and usb debugging is enabled which if you are on here i safely assume you are
extract the supersume zip (1 or 2 i couldnt see a diff)
and run the superme bat file (it will walk you through it )
itll soft reboot when done and you are solid and it will hold root
yes the bat will say disableing knox again it was for the note 4 but works fine ive done this
link to get files : http://rootjunkysdl.com/?device=Gala...=Kitkat Root

I don't have this tablet but replacing kinguser with supersu should be doable on this tablet as well (I did it on my forge tv)
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
all you do is install terminal emulator and copy files and run the command.

So now i cant upgrade to lolipop im guessing due to the fact it knows its modified now it will give error at 1% anyone have the factory image and how would i go about recoving it to stock image would i need cwm recovery to accomplish this? I really just want to upgrade so maybe the bluetooth stack has been fixed so i can use my wii mote to play games.

Alpha_wolf said:
and too root the lollipop update download the files off rootjunkys site awesome work lol yes it was originally for the note 4 but shush it works
install kingroot (yes its in chinese dont worry we will be installing supersu very soon)
make sure adb is working and usb debugging is enabled which if you are on here i safely assume you are
extract the supersume zip (1 or 2 i couldnt see a diff)
and run the superme bat file (it will walk you through it )
itll soft reboot when done and you are solid and it will hold root
yes the bat will say disableing knox again it was for the note 4 but works fine ive done this
link to get files :
Click to expand...
Click to collapse
Thanks for the timely post of this.
Don't know if it's something on my end but the link gives 'access denied', fortunately you had said it was for a note4 so I just looked for that and came up with the right files, just thought you might want to know.
One minor hiccup, and I'm not sure where to post it, so I'll post it here: SuperSu took 5 tries, finally got success, but now it keeps wanting to update the su binary again, it's definitely rooted, and the binary's already updated so...[shrugs]. The app said if there were any problems with it to post it to xda, soooo, here it is, sorry if this is the wrong place to put it.
Other than that tho, it worked great, thanks again!

laperro said:
Thanks for the timely post of this.
Don't know if it's something on my end but the link gives 'access denied', fortunately you had said it was for a note4 so I just looked for that and came up with the right files, just thought you might want to know.
One minor hiccup, and I'm not sure where to post it, so I'll post it here: SuperSu took 5 tries, finally got success, but now it keeps wanting to update the su binary again, it's definitely rooted, and the binary's already updated so...[shrugs]. The app said if there were any problems with it to post it to xda, soooo, here it is, sorry if this is the wrong place to put it.
Other than that tho, it worked great, thanks again!
Click to expand...
Click to collapse
idk i got that once and i updated it and it was fine so idk sorry tho

Alpha_wolf said:
and too root the lollipop update download the files off rootjunkys site awesome work lol yes it was originally for the note 4 but shush it works
install kingroot (yes its in chinese dont worry we will be installing supersu very soon)
make sure adb is working and usb debugging is enabled which if you are on here i safely assume you are
extract the supersume zip (1 or 2 i couldnt see a diff)
and run the superme bat file (it will walk you through it )
itll soft reboot when done and you are solid and it will hold root
yes the bat will say disableing knox again it was for the note 4 but works fine ive done this
link to get files : http://rootjunkysdl.com/?device=Gala...=Kitkat Root
Click to expand...
Click to collapse
Thank you thank you!!!
This worked...had to fight a few areas but it all worked...
Is it possible to get custom recovery like TWRP?

parcou said:
Thank you thank you!!!
This worked...had to fight a few areas but it all worked...
Is it possible to get custom recovery like TWRP?
Click to expand...
Click to collapse
not that i know of the device is still pretty new

I found this method incredibly easy: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
I just had to put it on PTP instead of MTP. And after the reboot, I had to manually boot it on download mode (following the software's directions).
It's working flawlessly.