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
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.
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
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.
Please don't drop the "wrong thread" bomb on me. My experience in forums is, you ask a question and you get 50% told to reboot, 40% told you're in the wrong thread, 9.9% other nonsensical things, and the 0.1% would be an actual attempt at a solution.
Here's the thing. My v10 is not going to have its bootloader locked by running fastboot. I have tried every single solution. No matter what, the computer never sees my phone on fastboot. All the drivers are right, re-installed nearly twenty times now too. I've tried the light, minimal version of adb. The full version. That other version I didn't quite get why it was different. And in all permutations with all driver installation attempts.
Don't know if this has anything to do with anything, but the phone has never once successfully booted into recovery by holding down power and down-volume. Nor power and up-volume. Not once. I have only ever been able to get it to do so with the "adb reboot recovery" command, just as, before I installed the xPosed module, "Quick Boot," there was no way I could get into bootloader other than "adb reboot bootloader" command. Because of course bootloader sees the phone in all states except fastboot.
No, if I plug it in while on bootloader, nothing happens on the computer. Nothing installs. No little yellow triangle thingie shows up suddenly in my computer's Device Manager. Ever. So there's no way to make the driver upgrade to whatever it needs.
Only one time has "fastboot devices" ever shown this device, and that was the moment I unlocked it to root it in the first place.
And now that this device has proven to be without a doubt the worst thing I've ever, ever owned, and I am sick to death of all its problems and screw-ups, I have absolutely no way whatsoever to relock the bootloader and do something to exchange it. Unless anybody knows any other way for me to do this without the use of my computer. Anybody? Please help. I can't even stand looking at this phone any more, much less use it without it making me want to kill puppies and babies and throw exploding Samsung 7s at little old ladies just to watch them burn.
All help is appreciated. Except, as I said, what I usually get 99.9% of the time from forums. Thanks.
Oh, wait, mandatory emoji storm... sorry, almost forgot: :cyclops::good::silly::laugh:
Oh, before anything, I forgot to add...
I tried every USB port, with multiple USB wires, on both computers, one old and one new, one Windows 7 and one Windows 10, and again, in all permutations. There is no possible way this should be this frickin' difficult.
thestumblingblock said:
I tried every USB port, with multiple USB wires, on both computers, one old and one new, one Windows 7 and one Windows 10, and again, in all permutations. There is no possible way this should be this frickin' difficult.
Click to expand...
Click to collapse
Had the same problem. I highly suggest if you have even a 16gb flash drive to download and install Ubuntu onto it. It takes just a few minutes to get setup and fastboot will detect your device almost immediately. Launch Ubuntu in live boot (from the usb drive) and you can then try it out and it should work fine. This was the only option that worked for me after trying just about every option online I could find.
Once on Ubuntu right-click the desktop and open Terminal and put in the following without quotes around it: "sudo apt-get install android-tools-adb android-tools-fastboot" follow the prompt and within a few seconds you should be able to issue both adb and fastboot commands properly.
theinspector said:
I highly suggest if you have even a 16gb flash drive to download and install Ubuntu onto it..... Once on Ubuntu right-click the desktop and open Terminal and put in the following without quotes around it: "sudo apt-get install android-tools-adb android-tools-fastboot" follow the prompt and within a few seconds you should be able to issue both adb and fastboot commands properly.
Click to expand...
Click to collapse
Sounds like something totally new for me to learn, but I do have a pretty good size flashdrive. So, here goes something. I'll report back how it works. I'm glad to hear there's at least something to try because as you no doubt saw from my tone, I really felt like I'd been totally Kobiyashi Maru'ed here.
Because technology hates me in every way, I cannot get Ubuntu to work at all. I give up. I'm gonna go ahead with that puppy-kicking plan. I am just DONE.
Don't know much about fastboot and all that stuff, mainly because I have Verizon VS990 version with bootloader that can't be unlocked.
Having said that with Windows 7 or 10 did you install and open all that fastboot stuff as administrator? Because if you didn't do all the required steps as administrator that might cause this to not work on Windows.
beavis5706 said:
Having said that with Windows 7 or 10 did you install and open all that fastboot stuff as administrator?
Click to expand...
Click to collapse
Sir, if you came up with the answer to this (and that means me taking the time tomorrow to try it again) you will forever have me bowing down to you in the most embarrassing way imaginable. I'll letcha know how this goes.
Nope. Nothing. If I touch it, it refuses to work. I tried to make an Ubuntu boot stick, but every effort to do so gave me nothing but errors so I don't even know if that would work. Meanwhile the phone only gets worse, and I'm stuck with it, and out $600, and there's nothing that can be done. This is without a doubt the worst. And I am so f#$^%&^ing done with technology right now, you have no idea.
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