I followed the instructions in this thread and opened the file to confirm the changes (0x54c) was there, but my Sony S1 still isn't showing up in my Android Device Chooser when I run my applications. Rebooted computer, Eclipse, Tablet...
If I can't get it to show up, I'll be sending it back for a Galaxy 10.1, so bit of a time window here. Any ideas greatly appreciated.
Sorry for posting this here, but I'm not allowed to comment in the dev threads yet.
So I made it to the Sony Android Developer Program site and download and downloaded the development kit. Followed instructions in the very poorly made guide... no dice.
Talked with Sony support who said I should talk to Eclipse. At my wits end here, might just send it back and get a Galaxy Tab.
Those of you who have gotten the Tablet to connect with Eclipse - what version of OSX are you on? I'm on Lion and it seems some others have had similar issues since upgrading.
Ok, so I finally got it working! After adding 0x054c to your adb_usb.ini I had to kill ADB and restart it. However ./adb kill-server and then trying to ./adb start-server was giving me errors and refused to start. I had to do ./adb nodaemon server ADB_TRACE=ALL
After this, the tablet is FINALLY showing up in Eclipse.
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 just recently rooted my CDMA Hero using the unrevoked method and I had a lot of trouble figuring it out. I some how got the adb drivers to install on my phone (I was so annoyed by the time they installed I wasn't even paying attention when they did) but now they have disappeared (I think because I downgraded the phone to get it out of a booting screen loop) and I can't get them to re install no matter what I do. Im running on windows 7 64 bit and even when the bubble pops up and says that new drivers are installing when I go to type in
Code:
adb devices
it tells me that no internal or external paths can be found. Any tips for installing these would be greatful. I want to still use adb in the future.
Yeah nevermind. I was charging my phone via computer and an installing drivers bubble just so happened to pop up after I had been tinkering with loading themes. Figured I'd go ahead and give a shot to see if it was the drivers I needed turns out it was.
No idea what really went down but I'm glad i got adb working properly lets hope it's more permanent
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
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.
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