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.
Related
Hey, I've tried various methods of rooting my GSM Hero, and eventually found the method on this site entitled "VillainROM Roots 2.1 RUU for GSM Hero (Confirmed)". I got as far as trying to run runindos.bat, and this just returns the error as explained. If I run "adb devices" I get "List of devices attatched" and then just nothing after it. Strange.
Does it have anything to do with the fact that HTC Sync never picks up my phone?
Windows 7 64-bit
HTC GSM Hero
3 UK
Android 2.1
adb, drivers or usb debugging, check it
Sent from my HTC Hero using Tapatalk
USB Debugging is enabled, not sure how to check adb but what's the correct way to install the drivers? Is it by running the "SDK Manager" program in my SDK folder?
Moved to Q&A as not development.
Get the drivers via the sdk manager, and manually install them via device manager for the device.
Ahh, sorry about the wrong section. I assumed that Development would be things concerning roots.
SDK Manager only seems to let me install "SDK Platform Android X.X", I don't see any driver installations. Also, I'm not sure where it installs these to.
Edit:
Okay I tried to install "USB Driver" but Windows said that it was already up to date. Still not appearing in adb :/.
Hmmm. Search for drivers in dev forum, as I think I posted mine (or instructions to hack them) on one of the Froyd villain threads somewhere.
Also, I presume you have rebooted and tried adb right after reboot
Drivers for you
Thanks to you both, I'll try those later on today.
I'd rebooted both the PC and the phone and tried it. Nothing unfortunately. It just seems to be a big Windows 7 problem.
I use Win 7 without any problems.
Check out this epic guide by BTDAG,...
http://forum.xda-developers.com/showthread.php?t=776056
Good news and bad news. The drivers are now working, adb is working and runindos.bat is doing it's thing. Unfortunately, when it reboots the second time for recovery, there's just a red triangle with an exclamation mark in it.
I rebooted and got back to where I was, but how do I get the "Care Bear" boot screen? Am I supposed to have moved RA-Hero to my phone first or do I not need anything?
Thanks.
Hi Craig. I had to repeat process 4-5 times before it worked so make sure you have your new rom on SD for when it works. I had all same probs but it will get there. As pulser said on villain try changing directory to avoid echo. It seems to load a little more each time.
Sent from my living room.
Hmm, if the recovery thing with the phone in the background comes up, and has "apply:update.zip" as a selection, should I try that? I've tried a few times and that's usually what comes up, along with reboot phone and another couple of selections.
I've got it! Thanks very much for everything. I just kept doing it and it's working now. I got FroydVillain and I'm loving it! I never realized the Hero could be so smooth.
Also sorry for the double post, I'm used to auto-merging on formus.
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
Make sure that you've mounted USB as "None", you can do so by pulling down the notification bar. Hope that helps!
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
make sure usb debugging is ON, set usb connection to NONE. I'm assuming you have sdk installed in c:\ of computer. Then go to cmd prompt and type: "cd c:\android-sdk-windows\platform-tools" [enter]
Then, type: "adb devices" [enter]
Should detect device, or something is wrong.
Hell, just go install the CWM and install the mods that way. A lot of them are updated to now work with CWM. See here: http://forum.xda-developers.com/showthread.php?t=1019143
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.
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.
I've been trying to get ABD working mainly so can downgrade my fire 5th gen from 5.1.3 to 5.1.2 but at all the tutorials i get stuck at the ABD. i made sure to download the android SDK for abd, i set the paths and open up command prompt ABD is still unknown command. so i figure try ubuntu and ofcourse that crashes saying "upgrade motherboard or use force" and havent seen any new mobo updates.
then ofcourse to top that all off every single tutorial that shows how to get ABD drivers working for the thing stop at the part after i install fire drivers and abd drivers. at a point it is still not done becuase now you have to go into device manager and do option where you can select "android phone" but what if you don't have "android phone" as an option? i thught that the android studio would add that but i guess not.
so what do you do when get at these problems? tutorials i fallowed are:
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
and ugh cant find other right now but as can see nothing on what to do if get at my road blocks, i have also needed ABD for other things and it used to work fine for apk transfers on older kfhd on another PC 7 but drivers for flashing rom abd mode and just NOT installing nomatter what i do tried for whole day and a half trying to figure out this nightmare.
is for only apks?
Nightmare-Rex420 said:
I've been trying to get ABD working mainly so can downgrade my fire 5th gen from 5.1.3 to 5.1.2 but at all the tutorials i get stuck at the ABD. i made sure to download the android SDK for abd, i set the paths and open up command prompt ABD is still unknown command. so i figure try ubuntu and ofcourse that crashes saying "upgrade motherboard or use force" and havent seen any new mobo updates.
then ofcourse to top that all off every single tutorial that shows how to get ABD drivers working for the thing stop at the part after i install fire drivers and abd drivers. at a point it is still not done becuase now you have to go into device manager and do option where you can select "android phone" but what if you don't have "android phone" as an option? i thught that the android studio would add that but i guess not.
so what do you do when get at these problems? tutorials i fallowed are:
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
and ugh cant find other right now but as can see nothing on what to do if get at my road blocks, i have also needed ABD for other things and it used to work fine for apk transfers on older kfhd on another PC 7 but drivers for flashing rom abd mode and just NOT installing nomatter what i do tried for whole day and a half trying to figure out this nightmare.
Click to expand...
Click to collapse
for a donwgrade there is a forum for kindle fire already why not try it?
http://forum.xda-developers.com/amazon-fire/help/downgrade-fire-os-5-1-4-to-5-1-2-t3388323
good luck:cyclops:
Note: For transfer apk you can upload to google drive or dropbox from your pc and download a install from the same apk on your device.
CharlexDe said:
for a donwgrade there is a forum for kindle fire already why not try it?
http://forum.xda-developers.com/amazon-fire/help/downgrade-fire-os-5-1-4-to-5-1-2-t3388323
good luck:cyclops:
Note: For transfer apk you can upload to google drive or dropbox from your pc and download a install from the same apk on your device.
Click to expand...
Click to collapse
uhh that pretty much says i have to load the firmware downgrade with ABD, and ABD is the problem idk how that helps?
Letme ask, did you install jdk and relate tools for adb like the one one will need for and android studio or some other developer tool? If not try to install it over Google you can find several related guidelines.
yea i got the ADB working on linux but not on windows still, also i can;t get the ABD drivers working because there is no "android phone" or "adb device" option in device manager which may have somethign to do with it.
well crap it just started working, but i still can't send adb commands because the drivers are not working due to not being able to continue tutorial over "device manager - select android phone or abd devices" step.
your problem sound like a driver problem but you can check the next forums:
http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9