for some reason when i type the adb shell command in cmd i get a device not found message. how can i fix this problem?? i want to unlock nand..
Have you followed part 1 of toast's method of rooting your phone? Have you installed android sdk?
you could also check out this guide: http://forum.xda-developers.com/showthread.php?t=701004
yes i did i followed all the instructions to the T... I downloaded sdk for windows, i downloaded java jdk. I also downloaded all the files required to do the rooting and unlocking of the device. right now im using an omj rom but i would like to check out others. anyways everything else seems to work for me in the cmd accept when i get to that part
Type in adb devices and see if your phone's serial number displays. If that displays okay, then you should be good to go. Other than that, you should have user debug checked on.
thanks ill check it out.
My W7 64-bit machine had no problems, but on my W7 32-bit machine I had a similar issue to what you are describing. If I did "adb devices" nothing was showing up.
I followed this guide to fix it:
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Related
Ok, I have a T-Mobile locked and branded Desire and so trying to create a Goldcard but it just gives me Permission Denied when trying to get the CID, what am I doing wrong? I have followed the steps to the T
try the goldcard program?
YES!! Please seriously need help aswell with this. Have a sim free desire and I get to the line of code in the command prompt with
"ADB shell cat/sys/class/mmc_host/mmc1/mmc1:*/CID" and it just says device not found.
I am new to android so i'm pretty clueless with this. Any help would be greatly appreciated.
Kleptomaniac said:
... and it just says device not found.
I am new to android so i'm pretty clueless with this.
Click to expand...
Click to collapse
So about 'device not found'. I had this 'issue' when rooting mine a few weeks ago, so here's what I had to do.
When rooting, you're gonna be using the ADB tools to interface with your phone through USB. This would mean that the computer needs specific drivers for ADB to work properly, which for some reason, did not install well. I'm running Win7 x64 and had a hard time setting it up initially.
SO what you want to do is to first go to Device Manager on the PC and uninstall the drivers for anything related to the phone - it'd probably show up under 'Other devices' with a driver issue. Do that and unplug the phone.
Next, go to install PdaNet. Just run the exe and it will install the drivers you need for ADB to work! Once this is all done you can uninstall the PdaNet program if you don't use it - the drivers will still remain.
When you plug in your phone (it might prompt during the installation, I don't remember) and head to device manager now, you'll see a new entry at the top called Android Phone, with a device called Android ADB Interface. Once you see this, then you're good to go with the rest of the goldcard instructions you were following.
Just to be sure, reboot the PC and go to the Android SDK\Tools in a cmd prompt and type in adb devices. It should return with the serial number of your phone.
That's it, hope it helps!
Thanks alot man its nice to know people here are willing to help. I didn get the drivers but I used HTC sync instead to get them up and running, then after awhile of it still not working I found the goldcard program and it worked! Now all I have to do is wait for this root download to finish...
I'm having a problem that is affecting two different computers, both of them gives me a 'adb device not found' message and it won't list my G2 when I typed in 'adb devices', the only difference between them is that in my laptop it gives me a message that it couldn't successfully install 'ADB'(Windows 7 Home 64 Bit) while my older Windows XP SP3 desktop gives me no such message.
Before replying, please note that I have Checked USB debugging and have done everything in the ADB for dummies thread, which includes the adding the tools part to Path and I have reinstalled my drivers more than five times (with and without USBDeview), each time with a different method. I am not mounting my SD card. I have also tried the PDAnet method. I have modified the android_winusb.inf file and reinstalled it. Tried uninstalling my USB Root Hub's as suggested by another. I have updated my USB Driver in SDK to rev 4. There aren't any yellow checkmarks in my Device Manager, however I have noticed that I only have 'Android Phone' and the subcategory 'Android Composite ADB Interface', I've heard that I should see another category like 'ADB Device Driver'. I have tried to fix this problem for five hours to root my G2, any help would be appreciated very much.
Where did you get your drivers from ? In the guide at http://forum.xda-developers.com/showthread.php?t=865685 I suggest getting them from the HTC Sync software, not the SDK.
I walked a guy with Win 7 through this the other day, and it worked fine for him.
I know it sounds like a stupid question but is the adb.exe file in your tools folder? If not, try running an advance search and only in the titles search for "drivers". You should only get about 10 returns. The top one should have some files attached named tools. Download them and extract the files to your tools folder. Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
I second getting the drivers from HTC Sync and remember the desire z is the same a G2 so run the seach for desire z for htc sync.
Sent from my HTC Vision using XDA App
ddgarcia05 said:
Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
Click to expand...
Click to collapse
adb has been taken out of the latest version of the SDK "Starter" package (the 2.3 one). It used to be there in the 2.2 version. So now you have to run SDK Manager to install the platform-tools add-on, then you get adb. This is all in my updated adb guide
ddgarcia05 - I didn't have adb in my tools folder, however I don't believe that you need adb.exe in that folder, just in the 'platform-tools' folder or in the system-32 fodler. Thanks for trying.
steviewevie - Thank you so much! I found your adb for noobs thread and it seems that installing HTC Sync after uninstalling my previous drivers via USBDeview worked like a charm. I also didn't see that you had to add 'platform-tools' in the Path in the various other threads, so I did that too. +1 Thanks to your helpful thread!
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
This helped me... http://www.droidforums.net/forum/dr...b-windows-7-64bit-should-also-work-32bit.html
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
me144 said:
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
Click to expand...
Click to collapse
I have an incredible and it worked for me...good luck.
me144 said:
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
Click to expand...
Click to collapse
Go here and follow her steps exactly....
http://www.droidforums.net/forum/dr...ow-root-stock-2-2-using-unrevoked-3-32-a.html
Sent from my Incredible using XDA App
Sorry, i know you must get this all the time guys, but i'm really struggling with rooting and such.
I'm on 1.72 and have no idea how to downgrade. I know you might say "read the guide" blah blah, but i don't understand it "Moron" i hear you saying. Anyway, Is there a complete noob guide for it anywhere? Like literally one that talks you through every step?
Also, my screen cracked, so i opened it up and replaced the screen myself, didn't have insurance or the £170 to have them fix it. Before the screen cracked it was doing this thing where it looked all psychedelic, Whites have blue coming off them, blacks have reds coming off them, that kind of thing. and its doing it again. This made me think it was a software issue, it happen to anybody else? I was thinking if i put a different rom on it, it'd stop, but i dunno. Anyway, thanks for any help anyone gives.
Does the screen replacement involve the flat ribbon cable between the screen part of the phone and the keyboard? I'm thinking it doesn't, but I'm certainly no expert. A damaged ribbon cable can cause colors to display improperly.
Nah, its attached to the screen so it was a new one.
The screen only comes with a small ribbon cable that connects to the pcb in the front half of the phone.
There is a larger ribbon cable that connects the two halves of the phone together, you can see it if you hold the phone halfway between open and closed. If this cable gets damaged, which happens easier than you may think then it can causes all sorts of things to mess up, including the colours on your display.
Unfortunately this cable is attached to the screen pcb so needs to be replaced as one unit.
So i'd need to replace my main pcb? Damn. Thanks for the help though! Could anyone help me with rooting?!
Sent from my HTC Vision using XDA App
at which point are you getting lost? sussed downgrading yet?
emdaftrave;14529179.Could anyone help me with rooting?! :D
.
Sent from my HTC Vision using XDA App[/QUOTE said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
Just have a search and there are numerous step by step guides, I was a total amateur and managed to do it, I think the hardest part to try learn would be using ABD (command prompt) and how to navigate to directories and push files but there are numerous guides on this forum so just pick your simplest and go for it!
elliott2705 said:
at which point are you getting lost? sussed downgrading yet?
Click to expand...
Click to collapse
Pretty much trying to install the sdk, i think im gonna reinstall it because its being a bit dodgy for me. But thanks for all the help guys!
Sent from my HTC Vision using XDA App
silverwind said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
can you use the SD card already in there as a gold card, or do you need a separate one?
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
emdaftrave said:
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
Click to expand...
Click to collapse
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
pmcqueen said:
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
Click to expand...
Click to collapse
ok, i've done it, thank you very much! now to just downgrade and root!
Ok so i'm using the XDA wiki guide on rooting, and i've got to the part where you move all the files onto the phone. Specifically, the files that aren't moving are:
$ adb push flash_image /data/local/tmp/
$ adb push su /sdcard/,
I'm getting a "Permission denied" error in command prompt. I also don't have an /sdcard directory on my phone, maybe thats why i'm getting an error?
EDIT: Never mind, i had the phone in Disk Drive mode when it wasn't supposed to be. Sorry for the double post.
I found as a few others that the Nexus works fine... but... Not having all the correct drivers makes it not possible for the computer to recognize the phone.
So, this is a posting to provide the missing drivers that are the common culprit for preventing the computer from seeing the phone.
You should have SDK installed and make sure it is updated. I am assuming you know this and have done so.
The next thing is to make sure you have the latest Samsung drivers. The Latest I could find is the 1.4.8.0 version and can be found here:
http://drivers.softpedia.com/get/MOBILES/Samsung/
If your phone is not being recognized by SDK (you can check by typing "adb devices" then it is likely you are missing one of the adb drivers.
This driver is equally important and can be found here:
http://pdanet.en.softonic.com/
Make sure you download the right version for your computer op system.
With those 2 installed the unlocking and rooting method by Paul O'Brien will work flawlessly and it can be found here
http://forum.xda-developers.com/showthread.php?t=1362957
The PDA driver seems to be the one alot of people are missing. This should help all of you that have been experiencing this problem of SDK/ADB not seeing the phone.
Finally, for those who are not familiar with SDK, this video for the ASUS EPad is a good visual tutorial for entering sdk commands... If you watch the part between 6 min to 7 min 40 sec this is the part that will show you the commands and syntax necessary to help you enter the commands correctly:
http://www.youtube.com/watch?v=WaZ4B60OWmY
Hopefully, this will assist some of the better postings on unlocking and rooting by providing us less experienced members with some additional sdk guidance.