Database Info

How to ninstall default windows driver for Android Device

Ok so i am trying to install the ADB USB drivers and having some issues. i have pluged my mytouch into my VIsta ultimate 64 bit machine before (the day i got it actually) so i could transfer files and of course now that im trying to install the ADB USB 64 bit driver windows wont let me and says i have the latest drivers.
currently im loooking in my Device manager and i see my device under 2 locations:
Disk Drives - HTC Andriod Phone USB Device
Portable Devices - Android Phone
i go into my CMD shell and type ADB DEVICES and it says:
list of devices attached
it is blank instead of showing a serial number
so im assuming that the drivers that windows has assigned to my device are not cuting it.
i have tried uninstalling the drivers but every time i do that as soon as i plug the device back in windows just assigns those drivers to it again and every time i choose UPDATE driver and browse to the AMD64bit driver it says y drivers are already up to date.
any thoughts on how i can get around this?

what i did was download an application called usbdeview and then uninstalled any htc drivers from there. then i unplugged my phone, and plugged it back in, and pointed windows to the drivers in the sdk folders.

momohammed20 said:
what i did was download an application called usbdeview and then uninstalled any htc drivers from there. then i unplugged my phone, and plugged it back in, and pointed windows to the drivers in the sdk folders.
Click to expand...
Click to collapse
that worked like a dream thank you!
now on to seeing i i can root this mytouch lol

sweet!! good luck

momohammed20 said:
sweet!! good luck
Click to expand...
Click to collapse
you wouldnt happen to know what im doing wrong here would you? im mking my gold car and downloded Terminal Emulator but it looks like it was designed for physical keyboard devices so i downloaded Better Terminal Emulator and finally have the soft keyboard and typed in "cat /sys/class/mmc_host/mmc1/mmc1:*/cid " but nothing happens. im supposed to get a code to write down but i hit enter and the terminal does nothing.
am i missing something? even the email feature doesnt work (i assume it means it would email you the results)

i was having that problem too, so what i did was i just typed that command in through adb. so i did it via the computer. and make sure you have the card that you want to make into a gold card inserted into your phone.
so....
1) insert soon to be gold card into your phone
2)open command prompt, and change directory to where your tools folder is from the android sdk
3) type in adb
4) type in the command cat /sys/class/mmc_host/mmc1/mmc1:*/cid , then it should output your CID

momohammed20 said:
i was having that problem too, so what i did was i just typed that command in through adb. so i did it via the computer. and make sure you have the card that you want to make into a gold card inserted into your phone.
so....
1) insert soon to be gold card into your phone
2)open command prompt, and change directory to where your tools folder is from the android sdk
3) type in adb
4) type in the command cat /sys/class/mmc_host/mmc1/mmc1:*/cid , then it should output your CID
Click to expand...
Click to collapse
got it thanks so much again.
i was able to use the hex editor to modify the soon to be gold card with the CID hex info and re saved it. then i removed my SD card and plugged it back in and i was able ot open it no problem via My Computer in windows. i went ahead and copied the SAPPIMG as well and now i assume it is a gold card.
just working on downloading the other files i need from rapidshare probably have to finish this up tommorow as its getting late. this wll give me some more time to do more research and read up as well as decide which ROM i wwant to flash..
thanks man again!

no problem, glad to help. I'm still a noob at this myself, i'm still learning. I currently have cyanogens rom on my phone, it's pretty solid. good luck, let me know how everything goes.

[Q] I think I bricked it??

I think I bricked my Viewsonic G Tablet. I was running VEGAN perfectly then I decided to jack around with Ubuntu the Karmic link found here on XDA under "Ubuntu on G tablet" Did everything the best I could, failed, failed.. booted into clockwork, went to factory reset, no back up found anywhere, formatted EVERYTHING (data, cache, rom) If I plug the USB cable into my laptop it reads as H drive but when I click on H drive it says "please insert a disk in H:" if I put anything on the sd external, I can't get my tablet to even read the external. Every time I click on "mount SD ext" it just says failed. Without clockwork, I just get big red letters "Magic value mismatch" Please tell me I didn't brick it good...
I can get the roms or the zip files etc on the external SD but without being able to boot to or from it, I'm lost.
Thanks

http://forum.xda-developers.com/showthread.php?t=861950
Start there. If you need more help search for "nvflash" and you'll find lots of helpful posts.

Thank you for your quick reply! I am afraid to say that I am SOOOO ignorant on this stuff. I followed the link and it had a lot of information on running the nvflash (I think when you didn't have clockwork installed??) It said stuff about lots of stuff I don't understand, I am SO SORRY to be so basic. I do run Linux Ubuntu 10.10 and Windows 7 on a dual boot with my machine so we can work in either environment. I donwloaded the prereqs from the drop box so I have the files along with two different ROMs, but I can't get the Viewsonic tab to even recognize (via my laptop) the internal SD card. Then the External SD card either so I do not know of a way to get any of these files to the tablet?
Please continue to help me in the MOST basic way you can, if you will. I would be so VERY grateful and give kudos, thanks, or whatever needed. I just want to make it work.

If you are able to boot into recovery then go to advance, then select the option to partition your sd card then select 2048 then 0. See if that helps to get your internal sd card recognized. That has helped me before.
Just an idea. No guarantees it will work.

Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.

THANK YOU THANK YOU A MILLION times thank you! I can donate to you or XDA via paypal, please let me know how to repay you all! You are wonderful!

No problem. Here to help when I can. If you really feel the need then donate to roebeet (the author of the original instructions).
Have a great day.

K J Rad said:
Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.
Click to expand...
Click to collapse
THANK YOU!!!!! Man, I thought I had a $400 brick on my hands! I couldn't even boot into recovery! I'll donate to whoever I need to at this point!

These machines are incredibly hard to brick. I've tried ;-)
If you'd like to donate pick one of worthy developers from the GTablet Android Development section and support their work. I use Roebeet's TnT Lite and those instructions above were first written and posted by him as well, so...
Glad you got it working. Have a great day!

Bricked phone build.prop missing

Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.

to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea

@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot

cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again

ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.

usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail

isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.

fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.

cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )

[Q] ADB, RSA, Android 4.2.2, Android Commander

http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.

Did you find a solution? I am having the same problem.

I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......

I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488

Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.

Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!

lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!

[Q] Problems updating to Lollipop

Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!

iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend

Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?

You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start

Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.

iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.

iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly

Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.

Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.

Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?

iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.

this is what I pasted:
;c:\adb_fastboot
?

iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.

Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...

Oy vey
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse

OK so my path is broken so I won't be able to run adb commands?

Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands

Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?