yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 General] jk8260:
Success, different TWRP experience than expected

Noob things worth noting about my experience...

- First thank you for these instructions and the links they were all very helpful. :good:

- At first my device was not recognized by 'ADB devices' command I think because my S4 drivers were conflicting (windows would ding and act like it was connected but no tablet showed up in Explorer). So from Windows device manager I uninstalled the drivers (only possible while plugged in to the tablet or it would disappear) then reinstalled and did then get the yellow triangle in device manager and then pointed the update of drivers to the Google USB Debug Driver from post #1. I also toggled between MTP (Media Device) and PTP (Camera) under the USB computer connection setting in the Notification area. Then ADB wold finally list my device with 'ADB devices' command.

- After the unlock the bootloader screen said 'unlocked' but I was no longer connected via ADB, so after waiting awhile to be sure that it was finished I then manually rebooted with the power button. At that point I got the android guy with the universe in his stomach for awhile (formating and resetting I am guessing) then rebooted once more when all done just to be sure before

- Similar to #31 after unlocking my V510 and manually rebooting I then booted into TWRP but had not copied the SuperSu to my SD card (dooh). So when I selected Reboot from the TWRP menu it then prompted me something close to 'You do not have root yet, would you like to install SuperSU' which I agreed to and the tab rebooted. Once rebooted back into the stock ROM I checked the notifications area and there was a message that said something like 'Click here to install SuperSu' and finish rooting which I did. After that when I tried starting SuperSu it told me that I needed to upgrade it from either the PlayStore or by downloading and the using TWRP. I choose the PlayStore method and simply clicked the 'Update' button on the SuperSu page in the PlayStore.

All good and rooted now.

Just wanted to add my observations that were slightly different than expected so to help any other noobs out there, all in all it was very easy and fun. Just rooted my S4 recently and this was much easier, partly why I got the GPE version of the LG 8.3...

thanks again
[G Pad 8.3 General] 1barlog17:
I cannot find the platform tools folder ,could you explain where I might find that?
[G Pad 8.3 General] sleekmason:
Are you using Linux? It will be in the SDK folder, in opt if you moved it there. See #12 of my post about using Linux above.
[G Pad 8.3 General] 1barlog17:
Never mind I figured it out. Thanks
[G Pad 8.3 General] bstaruk:
Everything worked perfectly for me, except one thing: make sure you put the recovery img file in the same directory as your ADB executable. So if you followed this guide, that'd be in "C:\Android-adb\".

If you try to install the recovery img from another folder (like I did) it'll say it was installed successfully, but when you try to boot into recovery you'll get the broken android symbol.

Cheers!
[G Pad 8.3 General] Mixinitup4Christ:
*edit* You can also direct ADB to look in a specfic folder like:

fasboot flash recovery C:\*YOURFOLDER*\recovery.img
[G Pad 8.3 General] bstaruk:
I've got extensive experience with terminal in Linux, just not much with Windows command line.

In Linux, if you run "rm sample.txt", it will look for "sample.txt" within your active directory. I wouldn't have guessed Windows handled that differently, but apparently it does.

In any case, I just wanted to make a note of this in case anyone else was running into the same problem as I was.
[G Pad 8.3 General] Mixinitup4Christ:
Sorry, tired today, didn't mean to be snippy. DOS command line only operates within the system paths or your current directory, when you run ADB from command prompt the actual executable runs out of it's installation folder which has been added to the system paths. So even though your prompt might be in the same directory with the recovery.img the ADB executable isn't. So as you figured out you need to either put the recovery.img in the ADB folder or give ADB a direct location of the file.

Sorry again for being snippy!
[G Pad 8.3 General] drzoo2:
Yes....and delete it.

rm = remove

rm -R = remove recursively .....

Did you mean grep?
[G Pad 8.3 General] Sean09:
Has anyone gotten Kingo Root to work on the v510? I know it worked on the v500. I only see one comment about it not working, but given the other issues I am not certain it is definitive.
[G Pad 8.3 General] Aredubu:
Don't think it works on the GPE. Follow the Nexus 5 rooting technique.
[G Pad 8.3 General] Mixinitup4Christ:
If you try it out let us know and I will add that info to the post!
[G Pad 8.3 General] Sean09:
I ended up just unlocking the bootloader and temporarily loading the custom recovery to flash root, that way I can still get OTA updates.
[G Pad 8.3 General] :
Bootloader unlock

I have followed the instructions step by step but when I type fastboot oem unlock it stay saying <waiting for device> The drivers are installed and its in the right mode. any ideas?
[G Pad 8.3 General] Sean09:
Read your tablet screen. Did you authorize it?
[G Pad 8.3 General] :
I did. It doesn't shows any message
[G Pad 8.3 General] schalmers:
Then I think your drivers are not setup correctly, go back to the 1st post and check the section related to installing the drivers and also confirm all is ok in the Device manager section if you are using Windows.
[G Pad 8.3 General] Mixinitup4Christ:
Do you see your device in the list when you type

fastboot devices
[G Pad 8.3 General] :
It doesn't show when I type fastboot devices but it does when I do adb devices. I have a windows 7 home premium x64
[G Pad 8.3 General] evinkay:
Frustrated.

Trying to install the drivers has been an absolute nightmare for me. Tried with a Win 7 Laptop that shouldn't have any possibly conflicting drivers, put the tablet in USB debugging mode, find it in device manager as "other device after disabling MTP and PTP.

"

Low and behold, I get this message stating that it doesn't work.

View attachment 2563729

Tried it again on another Windows 7 machine and same problem. I have rebooted everything repeatedly as someone suggested earlier, turned USB debugging on and off over and over along with toggling MTP and PTP but no luck.

I'm already frustrated with this and I haven't even begun! A helping hand would be much appreciated.

-Kevin
[G Pad 8.3 General] Mixinitup4Christ:
Sounds like you aren't in the bootloader. You must be in the bootloader to issue fastboot commands. Your device will not be seen in adb devices if you are in the bootloader.
[G Pad 8.3 General] Mixinitup4Christ:
Sometimes windows won't automatically see what drivers your device needs. Two things:

First, make sure that you have installed the google drivers as well ad the LG drivers.

Second, if you have to Google drivers installed then you right click on LG-V510 in device manager and choose update drivers. Then in stead of automatic installation choose let me pick the best drivers. Once you get to the list of device catgories you can choose adb category and then the adb composite bridge driver. I think I wrote the exact instructions out in another thread, but I just moved and don't have my computer up to find them. Try searching posts by me in this forum.
[G Pad 8.3 General] evinkay:
Thanks for the reply. So I should somehow have the Google drivers installed before I try updating the drivers to my device? Installed how so? I get the feeling that this is where my problem is as I have chosen manual installation when trying to install the drivers. I'll look for that other thread you mentioned.
[G Pad 8.3 General] Mixinitup4Christ:
I link two drivers setup files in the OP, LG United Mobile and Google. You need to have both installed to use your device with ADB.

That said, sometimes, even when you have both drivers installed, your computer won't recognize that your LG-V510 in USB debugging mode needs the use the Google ADB drivers. So you may need to go and manually select the Google ADB Composite device as the driver for the LG-V510 device you see in device manager the first time you plug it in with USB debugging enabled.
[G Pad 8.3 General] evinkay:
Okay I understand that much and I'm doing exactly what your saying but I'm still running into the same issue, that is, even when manually selecting the drivers, Windows will not install them as the drivers of choice for the LG-V510.

The LG drivers are installed through a wizard/exe program and that part is done. Now for the Google drivers is there anything I must do before selecting them in device manager? Maybe something that will allow them to actually be installed?
[G Pad 8.3 General] Mixinitup4Christ:
No, if you ran the google driver setup program from the op you should have the ADB drivers available to manually pick.... OH don't forget to uncheck the box that says "only show drivers compatible with my device" when updating the device drivers.
[G Pad 8.3 General] Mixinitup4Christ:
Here's the post try this out! It was different than I remebered!

http://xdaforums.com/showpost.php?p=49034647&postcount=11
[G Pad 8.3 General] evinkay:
Google driver setup program? Hmm I don't have any "program", just a zip file that I unzipped with seemingly un-executable files inside. I assume it does not matter whether or not MTP or PTP is checked or unchecked on my tablet as well.

Just to reiterate where I am (for the sake of clarity), I have:

-MTP and PTP disabled

-USB debugging enabled

-LG Drivers installed through wizard

-Google USB Driver downloaded and extracted (just sitting there)

When I plug my tablet in, Device Manager recognizes it as "Other Device" that it is unable to find driver software for when I manually point it to my extracted Google USB Driver folder.

Yikes it's late.
[G Pad 8.3 General] Mixinitup4Christ:
Yup, that's it! Lemme know if it doesn't work and maybe we can hit IRC tomorrow. I'm off to bed, gotta be up in 7hrs.
[G Pad 8.3 General] Mixinitup4Christ:
Obviously was tired, didn't understand your post... :)

Ok, so when you point to the USB-Driver folder Windows doesn't see a compatible driver in the folder?

Try opening Device Manager>Right Click on V-510 Device>Update Driver>Let Me Pick from a List of Device Drivers on My Computer>Uncheck "Show Compatible Hardware">Choose "Have Disk">Browse to "usb-driver" folder>Choose "android_winusb.inf">and then select ADB Composite Bridge.

If that doesn't work then Open Device Manager>Right Click on V-510 Device>Click on "Details" Tab>Drop down "Property" menu>Select Hardware ID>CTRL-C>Paste in your reply here!!
[G Pad 8.3 General] evinkay:
So that seems to have worked but for some reason it is registering as "Android Composite ADB Interface" under "SAMSUNG Android Phone". Just wanted to make sure it's safe to proceed.
[G Pad 8.3 General] Mixinitup4Christ:
It should be okay, HOWEVER, I'm gonna go out on a limb here and say you had a Samsung phone at some point... If I remember correctly (big IF) Samsung unpacks their drivers in a folder called "usb-driver" also. I think maybe you are pointing at the folder from when you unpacked the Samsung drivers. Try unpacking the straight Google drivers into a folder like "USB-Driver2" and then redo the above procedure...

I'm gonna be in the G Pad room on Freenode IRC if you want to join me.
[G Pad 8.3 General] evinkay:
Yeah, Java is not playing nice with IRC so i don't think that will work for me right now...Hopefully everything works now
[G Pad 8.3 General] evinkay:
All is well, finally rooted. (that took too long)
[G Pad 8.3 General] Mixinitup4Christ:
Awesome!
[G Pad 8.3 General] techinv:
Just got my V510 today

Have rooted 3 phones and a Galaxy Tab, but I can't seem to get out of the gate with this, so far.

adb devices (both on Windows 7 and my Mac) shows 'LGxxxxxxxxxxx offline' which I assume means it not in the right mode.

All the other devices that I've rooted needed to be booted in firmware mode before any adb commands were run but the instructions

that I've read here don't mention that.

Can anyone assist me with what I'm missing?
[G Pad 8.3 General] sleekmason:
Have you confirmed the connection on your tablet? There should be a dialog box that opens on your tablet asking you to confirm that you allow the connection with your computer.
[G Pad 8.3 General] techinv:
Thanks for the reply. I'm not getting the dialog box on the tablet, which I guess indicates that USB communication is not working properly :(.

Like a previous poster, device manager on the Windows PC showed a Samsung Android Phone, although it did let me update the driver. I think I'll go in a delete that device, reconnect the tablet and try again.

I was able to run adb commands on my Mac laptop to my Nexus 5 without issue, but I guess those drivers may not be right for the G Pad.

Oh well, I guess it will work eventually but wasn't expecting this much of a challenge just to unlock and root the device.
[G Pad 8.3 General] techinv:
Installed now. The Samsung drivers were definitely interfering with communication to the G Pad. Once those were de-installed,

everything worked pretty smoothly.
[G Pad 8.3 General] ephayzee:
Sup guys, will this method work if the tablet has been updated to 4.4.2?
[G Pad 8.3 General] ej_424:
So am I missing something here....? ADB recognizes my device but when I issue the command to reboot into the bootloader it reboots but comes back to the main OS. So I can't issue the fastboot oem bootload unlock command.

Please assist as I just got my G Pad 8.3, this stuff isn't new to me though.

Thanks!

ej_424
[G Pad 8.3 General] gunnyman:
this is going to sound silly but sometimes I fat finger and mistype bootloader as bootlaoder. LOL
[G Pad 8.3 General] ej_424:
So I found out this thread is for the V510 (Google Play Edition) I have the stock LG V500. So I"m assuming this wont work and there is currently no way to unlock my bootloader so I can flash a customer kernel? I know I can still root and do the bypass to load customer recoveries etc, but really want to get my bootloader unlocked. Please advise!

Thanks
[G Pad 8.3 General] j2409:
Worked perfect with no issues.

This was my first time ever running adb shell and it went smoothly. Thanks for the instructions.
[G Pad 8.3 General] gunnyman:
There's no unlocking a V500 boot loader. That's why there's Loki.

Loki negates NEEDING to unlock the boot loader
[G Pad 8.3 General] rsevarg:
Unable to install Google USB drivers on my GPE... any ideas?

Hi, I am mystified by the trouble I am having installing the Google USB drivers on my GPE version of the GPad 8.3.

As MixinItup has said, the MTP driver installs automatically, but of course that does not let you run ADB or Fastboot.

- I have tried using SDK to download the drivers, and after doing so, I do see the Google drivers in the folders where they are supposed to be, but when I follow the normal procedure in the device manager, navigating over to c:\whatever\extras\google\usb_drivers (etc) I am told there are no drivers available to load (??) even though I can see the Google-drivers folders full of cat, dll and ini files, etc.

- By the way, on my tablet, USB de-bugging is checked.

- So, next I tried downloading the driver in its zip-file format from Developer.Android.com, but when I ran it, that I got the same result. The zip files gave me what appears to be an exact copy of the folders and files that SDK gave me. But. full of hope, I opened the Device Manager and navigated over there,. Again I was told there were no drivers there to load.

- I have tried this on 1 Win8.1 machine and 2 different Win 7 machines. I get the same results no matter which way I try it (and because I have an AMD processor on one machine, and Intel on the other two, I tried using the appropriate driver (x386 or AMD ). But when that didn't work, I tried the other anyway. No result.

- I also tried the LGUnitedMobileDriver (#50)

So, hoping the LG universal driver might have loaded something up there without it being obvious (like Samsung Kies does), I flip over to the command line, and run the adb and fastboot commmands. I get back all the possible ways to use each utility. So I know ADB and Fastboot are working. And then I get the ultimate proof that the USB drivers are not working: Neither "adb devices" nor "fastboot version" produces any result.

I have spent nine days fiddling with this, reading anything I can find on XDA, but ... I am just stumped. Can any of you advise me?
[G Pad 8.3 General] jk8260:
I am sure you are but have to ask, are you logged in as an administrator to the pcs and have all firewall and antivirus software turned off ?

Sounds like access related issues.

:confused:
[G Pad 8.3 General] bamemanxxa3416:
I have the exact same issues, adb works with the Nook HD+ and Kindle Fire HDX just fine but not with my LG G Pad......l have done the list below.
[G Pad 8.3 General] sleekmason:
I have a couple of suggestions. The first one, is to erase from your computer everything you've done and start over from scratch following the guide exactly. Yes I know, you have already done this but I would do it again.

I frequently wind up doing these things several times and still find the mistakes, and this is after years of using the command line. The second thing I would do is bring your tablet into a phone repair shop and see if they can get ADB to work... or a friend. If so, at least you know it works on your device.
[G Pad 8.3 General] rsevarg:
Believe it or not, I have to answer no to all 3. I guess I have naively expected windows to just ask me whenever admin access was necessary. So I will give these a try shortly. Thanks very much for the suggestions...

---------- Post added at 07:20 AM ---------- Previous post was at 07:09 AM ----------

Yes, that all makes good sense. Re #1, I was sort of on the same track by using different computers, but #2 is making me wonder if I might have old drivers or something else that interferes on all the machines. So I will clean up and start over. and get a 2nd opinion on my adb. Thanks for your advice.
[G Pad 8.3 General] abadan:
wont it get v500??
[G Pad 8.3 General] Mixinitup4Christ:
Did you get it working? If so, let me know if you have any tips I can add to OP. Thanks!!
[G Pad 8.3 General] rsevarg:
Thank you for asking. I'm not finished yet, but I will report back shortly...
[G Pad 8.3 General] shipleythump:
Windows 8 ADB usb problem

I'm trying to get the ADB driver working. I plug in my tablet and it auto installs the MTP driver, as stated it would. Then I try to install the driver from op and it tells me something about making sure the driver works on x64 based systems.

Is this a shortcoming of windows 8? Or am I overlooking something here? I tried pointing to the directory (browse my computer > choosing directory) but that just tells me already have the right driver. So I go to Browse my computer > Let me pick from a list... > have disk > then picking the "android_winusb.inf" like I generally would on other devices, and then it pops up this error

The folder you specified doesn't contain a compatible software driver for
your device. If the folder contains a driver, make sure it is designed to work
for Windows for x64-based systems

Not really sure how to get this working. I just got the tablet a couple hours ago while at work, so I haven't had a chance to dig into it yet. Any guidance would be greatly appreciated.

Thanks

addition: Nevermind me. I'm looking at the fact that I have an LG G Pad, and overlooked the fact that I've got the VK810 4G from verizon, which incidentally isn't rooted yet.
[G Pad 8.3 General] rsevarg:
You were right! Too bad i got it in my head that I had windows conflicts, cuz i think i reinstalled windows for nothing :) But at least it did "erase everything" as you suggested. But now I am quite sure that I failed to _perfectly_ follow the instructions as you said I should be very careful to do. I am very embarrassed to say it, but it seems my problem was that when telling windows where to look for the driver, I navigated one directory lower than I was specifically instructed to do. The instructions on developer.android.com say "The Google USB Driver is located in <sdk>\extras\google\usb_driver\" So, why did I navigate one level below that exact level every time i tried to install the drivers? Let's not answer that. What matters is that your advice was spot on. Thanks again.

This has let me successfully unlock my bootloader, and I have now installed the chainfire zip file to root the device. Unfortunately I have hit another roadblock, but i think (having typed this much) that it might be more productive to ask that question that in a separate post
[G Pad 8.3 General] rsevarg:
Unlocked the bootloader with ADB/FB but now can't connect ADB anymore???

...I'm getting no answers from ADB or FB when I run some very basic commands

I have used ADB/FB to root and flash 2 other devices so, although I did (following previous advice from SleekMason) carefully go back over the above noted ADB/FB guide, I believe my understanding of these 2 apps is good. But, I am having yet another connectivity problem of some kind. .

My story: Once I finally installed the Google drivers, I was able to use ADB and FB quite successfully up to and until I unlocked the V510 bootloader. Both the screen of my V510 and the command line "response" from FB confirmed that the bootloader was indeed unlocked. I did a very careful reboot, as per the instructions, and (as expected) had to re-set-up my device with my Gmail ID, WiFi, etc. Then, immediately after that, when I wanted to continue to root the device, I was unable to connect with either ADB or FB.

Can anyone offer a suggestion?
[G Pad 8.3 General] sleekmason:
did you download and install super su?

and the more obvious are you plugged in?

or, are you at the part where you need to install the recovery?
[G Pad 8.3 General] rsevarg:
Ha, I discovered the problem was that after I unlocked the bootloader, and after the re-boot finished, you have to go back in and enable USB debugging again, and make sure the permissions were granted to the PC. Then adb and fastboot worked properly.

I should have thought of that sooner, since the unlocking performed a complete system wipe.

Thanks for the suggestions sleekmason!
[G Pad 8.3 General] rsevarg:
Rooted! (Yay!)

I was having the exact same problem (in Ubuntu 13.10). I thought I had created a path that would make it unnecessary to navigate all the way to where adb was. But doing what you said was all it took. One possible difference for me though was that I placed palman.img in the same directory as adb.exe beforehand.

Thanks for your help!