Anyone have luck rooting the Verizon G3? Purple Drake did not work for me, it says ERROR: UNSUPPORTED DEVICE, with my VZW LG G3, and Mac OS X Version 10.7. ADB is installed properly, and I also have the Android SDK Installed. Device IS found in terminal when I type: ADB DEVICES, but Purple Drake failed to root. So now I'm in Windows (in VMWare), with USB Devices set to: Always Connect To Windows, Android SDK installed, ADB Installed, device IS found in command line, and set to INTERNET/ETHERNET, and....
Nothing! Nothing works to root my phone. Now, obviously if others have been able to root the G3, it's a computer issue of mine. But I'm at a loss.
I used ioroot the day the phone came out and it worked like a charm.
Sent from my VS985 4G using XDA Free mobile app
mactechnm said:
Anyone have luck rooting the Verizon G3? Purple Drake did not work for me, it says ERROR: UNSUPPORTED DEVICE, with my VZW LG G3, and Mac OS X Version 10.7. ADB is installed properly, and I also have the Android SDK Installed. Device IS found in terminal when I type: ADB DEVICES, but Purple Drake failed to root. So now I'm in Windows (in VMWare), with USB Devices set to: Always Connect To Windows, Android SDK installed, ADB Installed, device IS found in command line, and set to INTERNET/ETHERNET, and....
Nothing! Nothing works to root my phone. Now, obviously if others have been able to root the G3, it's a computer issue of mine. But I'm at a loss.
Click to expand...
Click to collapse
Ioroot worked fine for me on a PC running Windows 8.
Look into Towel Root as well... It's just an apk you install then run on your phone
- Sent From My G3
the VS985 is not compatible with purpledrake
https://docs.google.com/spreadsheets/d/1hs0qlcGP80gl9wC0r9bs0AWMD-1D9iGgC9ulCG9roMs/edit
Lsantana954 said:
the VS985 is not compatible with purpledrake
https://docs.google.com/spreadsheets/d/1hs0qlcGP80gl9wC0r9bs0AWMD-1D9iGgC9ulCG9roMs/edit
Click to expand...
Click to collapse
Doesn't look like that has been updated with the new Purpledrake Lite (though I know that's not what the OP was asking about) as PDL claims to support "ALL" G3s...
joeliotta said:
I used ioroot the day the phone came out and it worked like a charm.
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
same here
Also, don't post the same thing in multiple forums.
joeliotta said:
I used ioroot the day the phone came out and it worked like a charm.
Click to expand...
Click to collapse
^^This. Windoze 7.
ioroot on a Mac.
Flawless.
Thanks for your prompt response. I tried TowelRoot and it gave me a similar message of not being compatible with my phone. I am running 10B firmware. Although multiple people have told me TowelRoot should be compatible. Weird. Maybe I should wipe my phone and NOT restore from Google, and try again? Maybe something weird came over from my rooted S4?
Sorry about that. (Posting on multiple forums). I was using my mac and my pc, and encountered errors. I didn't think the first post was accepted. I do know the posting rules
Use ioroot. It's the only method that works.
On a verizon phone, you need to make sure the phone is in "Internet - Ethernet" mode. Once you plug the phone in, open the notification bar and click on the USB Connection notification. Change it to Internet - Ethernet.
After starting the ioroot process, it will likely start and then wait for a minute or two before the fingerprint authorization screen pops up on your phone's screen. Just be patient, it will eventually pop up. When I ran it, I thought it wasn't working because the pause was so long. Just accept the pop up and the process will continue on.....
I literally just rooted my wife's Verizon G3 and those two things were what "got" me. I had to research to find out how to do it as it wasn't as simple or intuitive like the AT&T root method was. But once I knew the right mode to be in the process went pretty quick!
Towelroot does not work on Verizon lg g3. I know cuz I tried that first. Ioroot works great tho
Was there any resolution to this? I'm running into the same issue. I plugged my phone into my computer, started ioroot.bat as an administrator, pressed any key and watched the clock and waited a full 10 minutes but still no RSA Fingerprint window.
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
Open a command window on your PC, in the "bts" subfolder of ioroot -- this is the folder where the "adb" file is.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If you do not see that, unplug and replug the USB to your PC, try the adb devices command again.
Then I can "cd .." and run ioroot.bat.
Good luck!
I used the ioroot and it worked perfect once I finally got the rsa fingerprint to pop up. I just kept plugging the phone in and out and I also switched usb ports. I think what finally helped was restarting my computer and I said a prayer with my fingers crossed.
Related
Ok i have been looking EVERYWHERE and it seems like all the guides are outdated and may not work if i have android 2.2.1 on the phone already.
I have
PVT 32A
HBOOT-1.33.0013 (SAPP31000)
in the settings on the phone it says my baseband version is 62.50Sj.20.17U_2.22.28.25 which doesnt seem to match up with the different guides out there.
PLEASE somebody link me to a guide that still works nowadays with android 2.2.1!!!!
Thank you!!!!!
The old guide on the cyanogenmod site should work fine. An image is provided to downgrade to like Cupcake or something, then you can root it. I was able to follow the directions a few months back on my wife's old mytouch 3g with no issue.
Where are you running into a snag?
Sent from my HTC Sensation 4G using XDA App
Thanks for replying. Well to start, here it says.
wiki.cyanogenmod.com/wiki/HTC_Magic_(32A):_Rooting
About Screen
While booted go to Settings ยป About and look at the baseband version. You will see a long string with the last piece that looks like: 6.35.10.18 or 3.22.20.17 - that is the radio version
Except my baseband is something entirely different. I posted it in the original post.
Actually, if i just knew how to downgrade to cupcake for starters that would be great.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Help somebody???? Everything on the net doesnt match up with my phone for some reason. Like its all outdated.
Which mytouch 3g do you have?
T mobile my touch 3g. Its white and DOES have the regular headphone jack. And right now it has android 2.2.1 on it.
32A
HBOOT-1.33.0013 (SAPP31000)
baseband version says 62.50Sj.20.17U_2.22.28.25
Currently this phone is incredibly slow! I mean to the point of some people considering it unusable. I use it. But its a real pain. This is why i want to root. See if maybe an older version of android or a custom rom like cyanogen will speed it up.
If i simply put SAPPIMG.nbh on a freshly formatted fat32 sd card and fast boot or whatever it says unknown fail update fail.
injo503 said:
T mobile my touch 3g. Its white and DOES have the regular headphone jack. And right now it has android 2.2.1 on it.
32A
HBOOT-1.33.0013 (SAPP31000)
baseband version says 62.50Sj.20.17U_2.22.28.25
Currently this phone is incredibly slow! I mean to the point of some people considering it unusable. I use it. But its a real pain. This is why i want to root. See if maybe an older version of android or a custom rom like cyanogen will speed it up.
If i simply put SAPPIMG.nbh on a freshly formatted fat32 sd card and fast boot or whatever it says unknown fail update fail.
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=925182.
Yay!!! This appears as if it might work for me! Thanks so much!
Ok so im running into a snag even though im following this guid exactly. Im at the superoneclick part.
In the left pane of superoneclick it says
Killing ADB server Killserver 0.10s *server not running*
Starting ADB server Startserver 4.30s *daemon not running. starting it now on port 5...
In the right pane it says
*Daemon not running. starting it now on port 5037*
*daemon started successfully*
But its just sitting there forever. Nothing is happening. I have an hour glass for a mouse cursor. I have usb debugging on the phone turned on.
In my previous attempt to root my phone (following some other guide) i did use superoneclick and it said its been rooted but then wasnt. Or at least i couldnt do a su command (or whatever) from a terminal app on my phone. Could this previous attempt be messing with it?
injo503 said:
Ok so im running into a snag even though im following this guid exactly. Im at the superoneclick part.
In the left pane of superoneclick it says
Killing ADB server Killserver 0.10s *server not running*
Starting ADB server Startserver 4.30s *daemon not running. starting it now on port 5...
In the right pane it says
*Daemon not running. starting it now on port 5037*
*daemon started successfully*
But its just sitting there forever. Nothing is happening. I have an hour glass for a mouse cursor. I have usb debugging on the phone turned on.
In my previous attempt to root my phone (following some other guide) i did use superoneclick and it said its been rooted but then wasnt. Or at least i couldnt do a su command (or whatever) from a terminal app on my phone. Could this previous attempt be messing with it?
Click to expand...
Click to collapse
Yes, it could mess with it. Did you reboot your device before trying this? It is recommended that you reboot your device after every root attempt.
I have definitely rebooted several times since the last attempt.
So, i just tried a factory reset and then tried super one click again with the same results. I of course enabled usb debugging and to allow non market apps.
What should i try next?
injo503 said:
I have definitely rebooted several times since the last attempt.
So, i just tried a factory reset and then tried super one click again with the same results. I of course enabled usb debugging and to allow non market apps.
What should i try next?
Click to expand...
Click to collapse
When using Superoneclick, did you follow all of its instructions correctly (especially disabling and enabling USB debugginig many times)? See here: http://forum.xda-developers.com/showthread.php?t=803682 and read the "Read me" for 11/10/2011.
Yeah i have disabled and reenabled usb debugging on the phone while superoneclick it trying to root like 10-15 times.
injo503 said:
Yeah i have disabled and reenabled usb debugging on the phone while superoneclick it trying to root like 10-15 times.
Click to expand...
Click to collapse
Okay. Try this method instead: http://forum.xda-developers.com/showthread.php?p=4314039.
Ok, ill try that method next. But i just tried a previous version of superoneclick and its giving me the same results except it also says waiting for device.
If i look in my device manager on windows xp pro the only thing i have for drivers says android phone and if i expand that it says android composite ADB interface.
Is this right? Or do i need mytouch drivers on my pc? Are these drivers i am seeing part of the android sdk program?
injo503 said:
Ok, ill try that method next. But i just tried a previous version of superoneclick and its giving me the same results except it also says waiting for device.
If i look in my device manager on windows xp pro the only thing i have for drivers says android phone and if i expand that it says android composite ADB interface.
Is this right? Or do i need mytouch drivers on my pc? Are these drivers i am seeing part of the android sdk program?
Click to expand...
Click to collapse
You do need drivers for your device installed on your pc. Yes, they could be for that (but you still need your device specific drivers).
Another thing is im using a mini usb cord but the plug on the mytouch is shaped differently. But it fits anyways and works for charging and file transfers.
Where can i find device drivers for my mytouch 3g? I havent seen any anywhere.
I've spent at least 6 hours today trying to figure this out. I've (tried) following numerous guides. I've never used ADB and I am have a lot of trouble with that. I've tried using the one-click tool, that doesnt work. This seems extremely complicated. More complicated than any other phone I've rooted and unlocked. Is it a Windows 8 issue?
I did it, it was a pain however I had other issues with win8 such as all large file downloads would freeze up then my dl speed would skyrocket then appear to be downloaded and were corrupt. Ive since reverted to win7 and my s3...DNA wasnt cutting it for me but ill return to DNA later on down the road, what issue you having? getting adb? I had to change my usb drivers
nolimitzr2 said:
I did it, it was a pain however I had other issues with win8 such as all large file downloads would freeze up then my dl speed would skyrocket then appear to be downloaded and were corrupt. Ive since reverted to win7 and my s3...DNA wasnt cutting it for me but ill return to DNA later on down the road, what issue you having? getting adb? I had to change my usb drivers
Click to expand...
Click to collapse
Yes I am having trouble getting ADB. How did you change the USB Drivers?
art0605 said:
Yes I am having trouble getting ADB. How did you change the USB Drivers?
Click to expand...
Click to collapse
for me, to get the drivers to work i had to install htc sync.
If you plug in your phone, you should have 2 virtual cd's, one of them HTC sync.
After you get it installed, open a command prompt using administrator privileges (even though i am admin on my pc, i had to do this anyways)
and try running the command ADB devices and see if your phone shows up. that's what i had to do to get it to work.
Cdoan34 said:
for me, to get the drivers to work i had to install htc sync.
If you plug in your phone, you should have 2 virtual cd's, one of them HTC sync.
After you get it installed, open a command prompt using administrator privileges (even though i am admin on my pc, i had to do this anyways)
and try running the command ADB devices and see if your phone shows up. that's what i had to do to get it to work.
Click to expand...
Click to collapse
I am pretty sure I did the exploit correctly. But when trying to submit the token, I get Error Code: 160.
Try right clicking on the root program if there is an AIO and select compatability and chose windows 7
Sent from my SCH-I535 using Tapatalk 2
Hello, when I go to use the ioroot for my LG G2 LG-D800 (Kernel Version 3.4.0) (Build Number KOT49I.D80020u) (Software Version D80020u) I click on the rar file, then click on the ioroot folder, then I click on the ioroot.bat and the cmd comes up and says:
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I have the LG suite installed, debugging enabled and accepted RSA key fingerprint. I put it on PC software to try it and It doesn't recognize that my phone is even hooked up or anything. Wondering what is going on. It's like it's having a communication issue. I think I have covered everything to ask.
Samsung Galaxy Legend said:
Hello, when I go to use the ioroot for my LG G2 LG-D800 (Kernel Version 3.4.0) (Build Number KOT49I.D80020u) (Software Version D80020u) I click on the rar file, then click on the ioroot folder, then I click on the ioroot.bat and the cmd comes up and says:
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I have the LG suite installed, debugging enabled and accepted RSA key fingerprint. I put it on PC software to try it and It doesn't recognize that my phone is even hooked up or anything. Wondering what is going on. It's like it's having a communication issue. I think I have covered everything to ask.
Click to expand...
Click to collapse
If the PC did not recognize the phone then the RSa key wouldn't have shown up. Check your device manager for any other driver issues.
Having trouble rooting LG G2
es0tericcha0s said:
If the PC did not recognize the phone then the RSa key wouldn't have shown up. Check your device manager for any other driver issues.
Click to expand...
Click to collapse
I checked in device manager and there is no problems with any drivers anywhere. Now when the RSA key comes up, does it only show on the phone or does it show on the computer also?
Phone. The g2 can be finicky showing it sometimes. It can come up quickly and get hidden behind the Charge / MTP / PTP interface. You only need to do it once until you reset or revoke permissions in the Developer Options. If it came up, then your connection works. It will not pop up otherwise.
Having trouble rooting LG G2
es0tericcha0s said:
Phone. The g2 can be finicky showing it sometimes. It can come up quickly and get hidden behind the Charge / MTP / PTP interface. You only need to do it once until you reset or revoke permissions in the Developer Options. If it came up, then your connection works. It will not pop up otherwise.
Click to expand...
Click to collapse
Well I know it did come up and I check the little box and hit okay but why does it show in cmd all this stuff?
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I tried hitting enter and nothing happened. ADB should already be enabled unless it isn't and I have to enable it some where and I have already accepted the RSA. I even tried reinstalling the LG suite but that didn't help. I have rooted tabs and a few other phones before but this one is a pain but then again I am pretty much a newb tho. I even tried Kingo Root and that failed also.
Samsung Galaxy Legend said:
Well I know it did come up and I check the little box and hit okay but why does it show in cmd all this stuff?
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I tried hitting enter and nothing happened. ADB should already be enabled unless it isn't and I have to enable it some where and I have already accepted the RSA. I even tried reinstalling the LG suite but that didn't help. I have rooted tabs and a few other phones before but this one is a pain but then again I am pretty much a newb tho. I even tried Kingo Root and that failed also.
Click to expand...
Click to collapse
That's just the default stuff - like a check list. I don't think there is an issue with your adb connection because you saw the RSA key on the phone. That does not come up with out the adb connection. What mode are you on the phone? It should be charge to start.
Forget. All reply. Use. On. PC root genius. And install. USB. Driver. And. Adb. Installer. That. He. Are. Rotted
munish1 said:
Forget. All reply. Use. On. PC root genius. And install. USB. Driver. And. Adb. Installer. That. He. Are. Rotted
Click to expand...
Click to collapse
You have any proof that it actually works for the G2? They don't have a list of surported devices. Also, many people aren't comfortable with using Chinese rooting tools that don't have much documentation. It's irresponsible to suggest methods that aren't listed as known working without a disclaimer at least. As long as they are using the right version of ioroot (25) then it'll work.
Having trouble rooting LG G2
munish1 said:
Forget. All reply. Use. On. PC root genius. And install. USB. Driver. And. Adb. Installer. That. He. Are. Rotted
Click to expand...
Click to collapse
Root Genius did not work, neither did Kingo Root......WTF here is going on?
Samsung Galaxy Legend said:
Root Genius did not work, neither did Kingo Root......WTF here is going on?
Click to expand...
Click to collapse
Because those programs aren't the ones to root your device. You have the right program. You need ioroot v 25. I reread the first post and it seems that you are trying to run the program from inside the rar file. Did you extract it from the rar first??
Having trouble rooting LG G2
es0tericcha0s said:
Because those programs aren't the ones to root your device. You have the right program. You need ioroot v 25. I reread the first post and it seems that you are trying to run the program from inside the rar file. Did you extract it from the rar first??
Click to expand...
Click to collapse
I'm having trouble tho trying to find ioroot v 25?
Samsung Galaxy Legend said:
I'm having trouble tho trying to find ioroot v 25?
Click to expand...
Click to collapse
What version were you using??
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
But using the right tools will make life much easier and less frustrating.
Having trouble rooting LG G2
es0tericcha0s said:
What version were you using??
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
But using the right tools will make life much easier and less frustrating.
Click to expand...
Click to collapse
Using just named ioroot from XDA.
Recently picked up a refurb G watch. However it appears to be in some debugging mode with a hidden menu of debug type tests. So I went into the about device section of the watch and something didn't seem right.
Software version: KKWT
Build number: platina-userdebug KKWT OPENMASTER eng.yjyj.kim.20140818.1125 39 test-keys
This doesn't seem like what I though it should say normally.
So I tried factory resetting the watch and after I got it set up again, I went into the settings and nothing was different.
Any ideas on how I can revert this back to the correct version of android wear or something?
Here is a link to the dump https://www.dropbox.com/s/vyp4ejxnipkjlnm/wearable-bugreport-2015-06-05-08-30-25.txt?dl=0
I figured it out. Once the device is connected to the dock and shows USB debug on the screen, you need to go to the hidden menu and find the port settings. There are four different options. The first and third are the same type of connection. You should be able to choose the first or third. Pay attention to the Device Manager, you should see ADB Interface, G Watch and CDC Serial. If you see that, then install the LG United Mobile Driver. After that you should be able to use the tool from XDA http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. Once you use the tool and get to the bootloader screen you will get another driver prompt in device manager for ADB Bootloader. Once the driver is installed you can completely use the XDA LG G Watch tool and Bob's your uncle!
tha_bigga78 said:
I figured it out. Once the device is connected to the dock and shows USB debug on the screen, you need to go to the hidden menu and find the port settings. There are four different options. The first and third are the same type of connection. You should be able to choose the first or third. Pay attention to the Device Manager, you should see ADB Interface, G Watch and CDC Serial. If you see that, then install the LG United Mobile Driver. After that you should be able to use the tool from XDA http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. Once you use the tool and get to the bootloader screen you will get another driver prompt in device manager for ADB Bootloader. Once the driver is installed you can completely use the XDA LG G Watch tool and Bob's your uncle!
Click to expand...
Click to collapse
I too got one of these watches. Unfortunately, all of them have a pre-production software version (KKWT). Because this was pre-production software it was never meant to be updated and cannot be updated
tha_bigga78, I tried what you said but something isn't happening right. To be clear, I tried this on two different computers: one that already had Android SDK on it and I have successfully used for ADB connections with my phone before, and one that had never been used for any adb/android software before.
The first time I got what you said, the three things in Device Manager: ADB, G Watch, and CDC. I installed the LG United Mobile Driver. I then downloaded rootjunky's tool from the link you provided and was able to see the device and to unlock the bootloader. Brilliant. But then after the watch rebooted rj's tool would never see the watch again. It sees my phone just fine. I made sure the watch has USB debuging enabled. After beating my head for an hour I did a fresh install on the 2nd, virgin, PC and got the same thing - it doesn't see my watch but if I plug in my phone and run rootjunky's tool I can see my phone show up in the list of devices just fine. Of course, on both PCs I did at rj's tool said and reinstalled the ADB driver through menu option 1. It didn't make a difference in either.
So now I am stuck with a watch that can't be updated and now won't communicate properly with my PC. I am left with a stripped down, pre-production phone and no way (that I know of) to fix it. Any ideas on what to do next would be great appreciated. Thanks!
intron1 said:
I too got one of these watches. Unfortunately, all of them have a pre-production software version (KKWT). Because this was pre-production software it was never meant to be updated and cannot be updated
tha_bigga78, I tried what you said but something isn't happening right. To be clear, I tried this on two different computers: one that already had Android SDK on it and I have successfully used for ADB connections with my phone before, and one that had never been used for any adb/android software before.
The first time I got what you said, the three things in Device Manager: ADB, G Watch, and CDC. I installed the LG United Mobile Driver. I then downloaded rootjunky's tool from the link you provided and was able to see the device and to unlock the bootloader. Brilliant. But then after the watch rebooted rj's tool would never see the watch again. It sees my phone just fine. I made sure the watch has USB debuging enabled. After beating my head for an hour I did a fresh install on the 2nd, virgin, PC and got the same thing - it doesn't see my watch but if I plug in my phone and run rootjunky's tool I can see my phone show up in the list of devices just fine. Of course, on both PCs I did at rj's tool said and reinstalled the ADB driver through menu option 1. It didn't make a difference in either.
So now I am stuck with a watch that can't be updated and now won't communicate properly with my PC. I am left with a stripped down, pre-production phone and no way (that I know of) to fix it. Any ideas on what to do next would be great appreciated. Thanks!
So, I think that the problem isn't with my PC
Click to expand...
Click to collapse
I think I may have left a part out....
Once you get the bootloader unlocked and the watch rebooted, you have to get the watch to the bootloader again from a powered off state. Follow the instructions here: https://www.youtube.com/watch?v=ftSCH7qihRI
Put it back on the cradle and see if it is showing ADB Bootloader in device manager. Install the drivers and continue from there.
tha_bigga78 said:
I think I may have left a part out....
Once you get the bootloader unlocked and the watch rebooted, you have to get the watch to the bootloader again from a powered off state. Follow the instructions here: https://www.youtube.com/watch?v=ftSCH7qihRI
Put it back on the cradle and see if it is showing ADB Bootloader in device manager. Install the drivers and continue from there.
Click to expand...
Click to collapse
Thanks! I will give this a try when I get home tonight.
This worked. Thanks a bunch!
I bought the same watch and same problems. Mananged to unlock the bootloader in windows. Just couldn't complete the proccess so I switched to linux and chose "restore" from "[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool" menu and now its like a new watch. Maybe should have just started in linux but its fixed now anyway.
Hi all,
I'm having some trouble with this, so I wanted to consolidate another thread into a main post. Here is my previous work. Any help would be appreciated or let me know if something doesn't make sense.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
Update 2 : working on it again today and couldn't get it to connect. Ignore what I said about it needs to be in PTP mode... it does not appear that way, but if you use a certain version of adb.exe floating around it will not connect. Look for one that is around 800KB... the one I'm using is 815,104 bytes. The other is around 500KB.
It also seems to be necessary to set adb.exe to "Run as Administrator" in compatibility mode (I also set run as XP SP3 for good luck). I have also been using an elevated cmd window, so hopefully this stuff is all legit
Yesterday the device did not actually fully get rooted so I started over. I am going to try running the "root" script line by line rather than the whole thing at once because it gets stuck somewhere and there is no indication of what happened.
Click to expand...
Click to collapse
Eh, I gave up... after two full days I'm confused about why I'm even doing it... Also, coming from an iPhone, this thing is already so open lol.