When i try to run adb in command prompt it says not a valid win32 application, any ideas people.
Just a guess, "that" adb is a linux app.
http://www.androidguys.com/2010/11/23/adb-android-debug-bridge/
adb
Thanks Moscow you are always quick to help i'm tearing my hair out with this desire
Did you downloaded the android SDK, with the additional platform tools? (Your OS version, of course). Otherwise it won't work.
It,should be in the link I sent him.
The whole package
gavstan79 said:
Thanks Moscow you are always quick to help i'm tearing my hair out with this desire
Click to expand...
Click to collapse
Not a problem, anytime
(although my answers are not always correct)
adb
I am re-downloading the windows version now and installing the packages
adb
I cannot get into android os will it still work through fastboot.
This I can't answer. But try
(didnt know you couldn't get to the OS)
Usually debugging should be turned on.
adb
Phone will not boot at all just htc logo,can't get into recovery either i have made a gold card.flashed a ruu, nothing working, so i'm hoping i can use adb to sort the recovery out, i'm just learning bits about android but it is all still pretty new to me so apologies if my questions seem daft
Not a problem. My advice usually gets more daft as the pints go down. Fortunately a non drinking week for me.
When you flashed, did you wipe all the cache memories before flashing?
Which ROM?
If it was Leedroid, your sd card has to have certain partitions. If they get hosed, phone will never boot.
Can you get into fastboot mode?
If yes try this
http://forum.xda-developers.com/showthread.php?t=823315
Related
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
*--*--* I am not responsible for any damage that may occur to your phone by following this guide or any other guide. If you are at this step, your warranty is already void, and if you lie to Verizon to get a replacement, an angry bear will break into your house and molest you quite thoroughly. Those people are the reason why Verizon is forcing locked bootloaders, and why I had to wait two months to root my Inc2. Don't be one of those people. You might be a noob, but that doesn't excuse you from doing research. In short, anything that happens is your own damn fault, and you can't blame anyone else. /rant *--*--*
Now that that is out of the way, the steps:
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe and adbwinapi.dll, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Boot into fastboot by powering the device off, then powering back on while holding the volume down button on the side. It should boot to a white screen, similar to what you saw when you first rooted it. Plug your phone into usb if you haven't already.
6. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot".
7. Rooting the phone is only the beginning. You still need a rooted kernal, and su and busybox. Without these, rooting does you little practical good. To that end, follow RMK's guide here: http://forum.xda-developers.com/showthread.php?t=1160745. That will get you all set up to start enjoying root fully. I would recommend installing ROM Manager from the market and using it to flash the latest CWM (4.0.0.8). ****NOTE that you need to already have CWM to flash the su and then flasht he new CWM. I know, it seems silly, but that's the way things are. Also, a disclaimer: a few people have had problems with the newest CWM not working properly for them. It worked for me, though, and there is a fix on page four of this thread.
Credit goes to attn1 for the modified CWM, xgunther for posting it/original instructions, and crazythunder of Android Community for the original instructions for using fastboot with a G1. Hope this helps
Some information from supersonic that those trying this on linux will find useful. Thanks!
supersonic2.5 said:
Download this recovery: http://forum.xda-developers.com/showthread.php?t=1134520
BTW, if you havn't installed fastboot, download it here.
http://developer.htc.com/adp.html
1.First rename your android sdk folder to "sdk" just like that. Dont use quotation marks on anything fyi.
2.Next step is to move the sdk folder to your home folder.
3.Move adb, fastboot, and the recovery image from the link above into the tools folder of the sdk.
4.Open up terminal and type or copy this in there.
"cd sdk/tools" hit enter.
5. "./adb kill-server" hit enter.
6. "./adb start-server" hit enter. should look something this. (below)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7. "./fastboot" hit enter.
8. "./fastboot flash recovery cwm-recovery-vivow.img" hit enter
give it some time to flash.
9. "./fastboot reboot" hit enter
10."./fastboot adb reboot recovery" hit enter
And there you go, wait for your phone to reboot and what not and you should have CWM installed. I would immediately do a nandroid of the stock rom. after that i didnt bother messing with superuser on stock froyo because who the hell wants to be on froyo!? lol, so i installed the GB ota rooted version with superuser already because its very stable....found here http://forum.xda-developers.com/showthread.php?t=1161411 as i wait for a stable version of rewind,you can then install and update CWM through rom manager to the current version once you've done this.
there you go buddy sorry so long. if you encounter any problems let me know so i can boot into ubuntu and help out. i'd give you a little more details but im on my mac right now. hit the thanks button if i was any help
Click to expand...
Click to collapse
devator22 said:
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe, adbwinapi.dll, and ddms.bat, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot". And you should be done.
Credit goes to attn1 for the modified CWM, and xgunther for posting it/original instructions. Hope this helps
Click to expand...
Click to collapse
Just a heads up, if you are S-Off, you can enjoy these instructions on Mac, Linux, or Windows. ADB and fastboot give you options for all! <3
Here is another link i found to help out!
http://forum.xda-developers.com/showthread.php?t=1122694
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
b0gman said:
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
Click to expand...
Click to collapse
Dumbest solution ever... I was having the same problem. As long as you've installed the jdk file from the link it shows on the initial error on sdk install...
Just click 'back' then 'next' again on the SDK installer... It worked for me.
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Grouper said:
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
Click to expand...
Click to collapse
Guess I forgot to mention that this is for the people with problems with the automatic installer, including myself.
Sent from my Incredible 2 with Xda app
Clutch McWinner said:
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Click to expand...
Click to collapse
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
devator22 said:
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
I was, but it turns out I didn't have the HTC sync drivers. S-Off, Rooted, and running overclocked CM7 now!!!!!!!
This must be in Fastboot USB mode while doing?
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
SHAKEJONES said:
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
Click to expand...
Click to collapse
Should HTC Sync be opening? I think you're supposed to uninstall HTC Sync, but leave the drivers. AlphaRevX provided a link to the drivers only, so it might be easier to just completely uninstall everything and then reinstall the provided driver instead.
Just tried that and its still stuck... I'll mess with it more tomorrow
Yeah i've been having the exact same problems with the drivers. I have a completely fresh install of windows 7, and it still wont work. I installed the HTC Sync, and it still doesnt recognize my device. I tried using Ubuntu, however it makes absolutly zero sense in my mind, so unless i have a detailed instuctional text, windows is my only choice really. Its funny, this thread is for noobs, yet i can't get even do this, but other phones i've rooted without any problems, and they we're much harder for me. Blah.
I've tried all variations of connection modes, triple checked I had all the files in the right spot, and tried different usb ports and it still wont work... does someone have a more detailed guide for this?
Seriously frustrated about this. S-Off was no problem. I'm triple booted with OSX, Win XP Pro and Linux. Used linux to get s-off but didn't get a CWM install. Window won't allow the driver to install and Linux is a mystery. Anybody have luck with OSX or Linux and want to write it up?
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
devator22 said:
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
Click to expand...
Click to collapse
Thank you kind sir hahaha I JUST got done doing that and it worked like a charm! this thread will be a great help to anyone else ---> http://forum.xda-developers.com/showthread.php?t=1122694
The directions for fastboot are in the OP
Haha, yea. I guess I am a noob when it comes to writing guides. I updated the OP with an extra step for booting into fastboot.
I am trying to sync my DInc with Windows 8 Pro to unlock it through the HTC developer site. Unrevoked wont work due to the version of my baseband being 2.15.10.12.20. Software version 2.3.4.
I have USB debugging enabled, fastboot off, performed a factory reset, cleared cache through HBOOT, and the computer DOES reckognize the phone and I am able to select open files and do whatever I need to do with the phone... it just wont display on HTCSync so I can go through the process of rooting it and getting JB on it.
I have also tried running HTCSync in compatability mode. I have been working on getting this working for days now, and have searched this and many other forums for solutions to no avail.
Any ideas would be greatly appreciated, and any more information you need will be provided asap.
Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.
PonsAsinorem said:
Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.
Click to expand...
Click to collapse
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?
cyborggold said:
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?
Click to expand...
Click to collapse
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I can connect the phone and browse files through Windows explorer, I guess I'm just not familiar with adb yet, ill try to find more information on that and give it a try, thanks!
Still Lost
PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!
cyborggold said:
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!
Click to expand...
Click to collapse
How To Set Up Android ADB & Fastboot On Windows [Tutorial]
The only note on this guide I'd make, is not to use the C:\ drive. It's always a bad idea to put stuff in your root directory. Myself, I installed the sdk (which installed itself to C:\Program Files) then I added that to the system path. Also, you might have to reboot (or at least log off and log back on) to reset your PATH.
Kinfauns guide is excellent, I've gained a lot of knowledge so far and hoping for know-how to come.
Kindle Fire For Beginners by Kinfauns
Still though, I've ran into a wall
I have no idea the severity of the issue, (fingers crossed on an easy fix)
I believe with certainty that the drivers are installed correctly on my host computer, going through device manager,
it shows both **Android phone> Android ADB Interface, and also Android phone> Android Composite ADB Interface**
but the device doesn't respond to [adb] commands.. fastboot does work although
I'll do my best to keep this short and sweet;
Essentially I ended up (hopefully Soft-) bricking my kindle fire on semi-accident, I went to wipe my device clean in a RageQuit type scenario, and I believe I checked off every partition check-box in TWRP's advanced wipe, swiped and closed my case and set it far away from me -- It still has 1.4 FFF, and TWRP v2.6 -- but no OS, or Rom.. and missing '/system/bin/sh' appears when running KFU and Unbrick utilities v1.1.
[and mount doesn't work in TWRP, suspect to adb not working]
So far, my only actions have been trying to use KFU and Unbrick Utilities v1.1
I now have SkOrPN's jig-- and a microSB to female USB.
From what I've read so far, these two plugs should be the cornerstone to restoration.
Please help, I'm trying to reveal the next few steps needed to take!
-- and thanks, :good:
Since you have a fastboot cable, and you can send fastboot commands, let's start with the easiest solution and install COTR recovery, or an early version of TWRP (preferably 2.2 or lower), then boot into recovery and try your adb commands again.
ok, i found openrecovery-twrp-2.2.0-blaze.img
and did:
Code:
fastboot flash recovery openrecovery-twrp-2.2.0-blaze.img
and it sent to 'recovery'
lol, it was like a needle in a haystack just finding 2.2
derpzhat said:
ok, i found openrecovery-twrp-2.2.0-blaze.img
and did:
Code:
fastboot flash recovery openrecovery-twrp-2.2.0-blaze.img
and it sent to 'recovery'
lol, it was like a needle in a haystack just finding 2.2
Click to expand...
Click to collapse
Now, do your adb commands work?
um, not so good-- running c:\kfu\tools>'adb devices' <-- didn't list anything.
ahh, had to go into recovery to get device into composite adb interface.. round 2.
yeah we're gold now, ADB detected my device
now to search up the next step
actually, would this have fixed my 'system/bin/sh' issue? and if not--and how to squash that situation?
couldn't I just run KFU's run.bat and begin the process over fresh?
(darn these captchas!! ahh)
derpzhat said:
actually, would this have fixed my 'system/bin/sh' issue? and if not--and how to squash that situation?
couldn't I just run KFU's run.bat and begin the process over fresh?
(darn these captchas!! ahh)
Click to expand...
Click to collapse
All you need to do at this point is use adb to push a ROM to your sdcard, factory reset, then install it. If you want to stay stock, install MoDaCo.
soupmagnet said:
All you need to do at this point is use adb to push a ROM to your sdcard, factory reset, then install it. If you want to stay stock, install MoDaCo.
Click to expand...
Click to collapse
ok I think I got it. AHH!! thanks so much ya, top shelf!
oh yeah, MoDaCo is sharp, like a cleaned up Stock mode
ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.
Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.
did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons
thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.
I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
robopilot99 said:
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
Click to expand...
Click to collapse
I had the same issue. Tried it on windows (though I hate windows ) and it worked on windows. I am STILL trying to figure out how and why?
I had the same problem on Ubuntu 15.04, and I fixed it by uninstalling the outdated version of fastboot in Ubuntu's repositories and replacing it with the binary from the Android SDK platform tools.
The fastboot protocol may have changed slightly with Lollipop, and Ubuntu's fastboot and ADB packages say they're from 4.2. Remember to run fastboot as root unless you have the udev rules set up. Hope that helps!
yes i had a similar issue on ubuntu with the repo version. I actually got an error message saying i needed a newer version
Thanks. Using the version I got from the internet worked fine. I'm now getting and error about fingerprinting and stuff. Looks uke I'll have to wait for a way to unlock the bootloader on the latest version.
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
bhoth said:
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
Click to expand...
Click to collapse
You will want the Android SDK tools. Here is the download page:
https://developer.android.com/sdk/index.html#Other
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
joel.maxuel said:
You will want the Android SDK tools. Here is the download page:
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
Click to expand...
Click to collapse
yeah that's what I ended up doing. It's a pain to find it in the huge download but it's kinda your only option.
im currently on the same problems as you too.. cant use fastboot on ubuntu 14.04 lts.. but i found this article online, didnt test it yet since im on my windows right now to use fastboot.. who knows this may help in updating to latest adb bin..
http://bernaerts.dyndns.org/linux/74-ubuntu/328-ubuntu-trusty-android-adb-fastboot-qtadb
Click to expand...
Click to collapse
wait i was wrong, the cmd there is to update adb to latest version and not for fastboot.. cant help anyway, unless download the whole android sdk as mentioned above..