[Q] help android sdk - HTC EVO 3D

sorry, but i need help, all day i have been trying to install android sdk and run on my windows 7 laptop. I went to youtube and followed everything but still can't get it. I installed 3 things. and I placed them in the c drive. now i have a file c:\android-sdk\tools.....now when I go into cmd and type that in it says invalid path...I tried d drive says device not ready....my evo is on debugged. someone please help me out.

In cmd try typing cd\
That will take u to root directory, now try c:\android-sdk\tools and assuming that is the valid path you should now be in that folder. If that does not work you may have an extra folder like android\android-sdk\tools.
I am assuming in the files u installed included were the drivers for the evo. These need to be installed otherwise once in tools dir u will get device not found when trying an adb command.

i tried cd then c:\android-sdk\tools....it says invalid internal external command. also I did download the driver for evo 3d but what do I do with it....where do i put it.....thanks for help in advance......im getting very frustrated.

"Cd\" without quotes then press enter. Then try specifying path for the tools folder which you say is c:\android-sdk\tools.
If that doesnt work you can type dir\w and that will show you all the folders in the directory. Make sure you type folder names exact.
As for the drivers just run the install and make sure u get right version. U msentioned windows 7 but 32 bit or 64 bit? If your phone has debugging on and the drivers are installed correctly you should be able to plug you phone in without being prompted to install new device.

Typed in c:/dir/w. It said volume in drive c has no label. Volume serial number is eore-14a9...also when I put my usb cable in laptop sees it.

Related

Update USB Drivers?

I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
joshw0000 said:
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
Click to expand...
Click to collapse
download htc sync that should fix ur problem , it did for me
Yes HTC sync updated mine as soon as your phone is acknowledged by HTC sync it should update your usb drivers
FYI HTC sync did NOT work for me on Windows 7. I had to do some pretty annoying stuff to stop windows from installing the regular drivers automatically. If HTC sync doesn't work I can try to help.
If HTC Sync doesn't help, try the following steps.
1. Unplug your Eris from the PC
2. Open Device Manager and delete the Android device
3. Reboot your PC
4. Once in Windows, connect your Eris
5. The drivers should load automatically, if not point it to the SDK drivers folder
Good luck!
Any more ideas
First I tried downloading HTC Sync on my laptop (running Vista) and that didn't do it. Then I deleted the drivers and tried to manually download them back with the ones in the USB folder of SDK and still it wouldn't work.
So I started over and downloaded SDK and Java to my pc (Windows 7) and tried to update the drivers with the ones found in SDK and it wouldn't let me. So I deleted the drivers, unplugged my phone, and plugged it back up. Before I could attempt to direct it to download the intended USB drivers, Windows 7 had already updated with the drivers of it's choice. I can't win for losing.
If you don't mind using one of those "Live" Linux CDs, you could install the recovery using fastboot.
No need to install anything on the PC, and no drivers are needed for Linux, no SDK, no Java, no adb; just make sure to run fastboot as root.
The downloads of fastboot and the Amon_RA recovery are small, so they will easily fit in /tmp.
bftb0
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
When you have your phone plugges in do you have it set to "charge" or "sync"? I know all the how to's say yo have it set to charge only but the inly way my computer ever finds my phone is if it us set to sync.
-------------------------------------
Sent via the XDA Tapatalk App
I set it to charge. I was finally able to install the correct driver. I selected a Google driver from the list it gave me (which my computer did not like) then went back and updated the drivers with those found in the tools usb folder of SDK. IT FINALLY LET ME!
Now I have a new problem. I'm using the command prompt and trying to create a custom recovery. I set it to the tools directory in SDK (where the flash and recovery images are) and I'm entering the commands exactly like the "how to" instructions have them. I keep getting "adb: not found" errors.
Can anyone tell me what I'm doing wrong?
joshw0000 said:
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
Click to expand...
Click to collapse
Well, in the long run it is probably a good idea to resolve the driver install problems you are having on your PC, because it is very useful to have "adb" around, even if you are already rooted and have the ROM of your choice installed.
But, if you would like to do this, here's an outline below. Note that the point of the "Live" CDs is that you are not installing Linux on your machine, you are just booting it directly from the CD - the OS and hard drive on your PC are untouched.
1) Download an ".iso" file from your favorite Linux distro [ 3 ] for their "live" CD. (BIG download, usually 600+ MB)
2) Burn the .iso file to a CD as a bootable CD. (Most decent CD/DVD burner programs know what an .ISO file is, but might refer to them as a disk image).
3) Boot your PC off it! (You might need to hit a key on your PC right after you power it on to go into a boot menu, or the BIOS setup to change the boot order so your PC will try to boot from the CD/DVD before it tries the hard drive).
4) Copy the fastboot [ 1 ] executable for Linux and the Amon_RA recovery image [ 2 ] to /tmp "somehow" - you could just download it using the Linux browser if your network come up automatically (wired ethernet), or you could put them onto a USB key beforehand, and plug that in after Linux has booted; it should mount automatically.
5) Then, open up a terminal window and become root. (Type either "su" or "sudo /bin/bash" - depends on the Linux distro)
6) Attach your (well-charged) phone to the phone via USB, and power it up in fastboot mode (Send+End simultaneously)
cd /tmp
chmod 755 fastboot
md5sum recovery.img (check file sig)
./fastboot devices (check to see you are connected)
./fastboot flash recovery recovery.img
Obviously, if you need to look something up on the internet, it is useful to be networked, so you can use a web browser. The Linux boot will try to autoconfigure network interfaces automatically, but this is going to be most straightforward with a wired connection (Ethernet). Alternatively, if you have another PC or laptop nearby, you could use that.
Good luck.
Edits:
[ 1 ] Find Linux version of fastboot from HTC midway down this page - md5sum 9851bb6ad29cd4b60c9ba9d011ba9efd
[ 2 ] Amon_RA's recovery is located on this XDA page - md5sum e3932991f097993602af3c7a4b61a4f8
[ 3 ] Ubuntu's Current (x32) CD for v10.04 this page
NOTE: This CD is both a "Live" CD and an Install CD. You DO NOT WANT TO INSTALL ANYTHING; you are using the "Live" CD function - see the "show me how" link under Item #3 ("Try It!") on the above linked page
[ 4 ] Various OpenSuSe 11.2 Live CDs
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
joshw0000 said:
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
Click to expand...
Click to collapse
First, relax and take a deep breath; everything's going to be fine.
In the recovery main menu, there is an Item called something like "MS-USB toggle" or something like that. It does not use the adb driver, it uses a standard "Mass Storage Device" USB driver already on the PC. The purpose of this function is to make the SD Card mount on the PC when the Amon_RA recovery is running.
Try that - it should work.
Then, download a conservative ROM such as Ivanmmj's Official 1.0 alpha, or Jcase's "Plain Jane", and copy it to your SD card.
After you have done that, make sure to check the MD5 sum of that .zip file on the SD card. (You should be doing this already).
Then, cleanly dismount the USB drive from the PC with the "Safely Remove Hardware" thingamabob, and toggle "off" the MS-USB toggle on the phone. Return to the main menu, wipe /data, and then flash the "conservative" ROM.
Then boot the conservative ROM just to verify everything is OK.
Next, Backup anything from the SD card that you don't already have (this step might be optional), and boot into recovery, and unpartition your SD card so that the only thing that is there is the VFAT partition.
For the moment, I'll give you some advice: f*ck A2SD. You need to gain some familarity with how the various versions of a2sd work before you start using it..
Very likely you were just stuck in a boot loop created by the re-partitioning you performed after initial configuration of a ROM that uses a2sd. Frankly, it is easy to create conditions for this, especially if you switch between ROMs that use different versions of a2sd, and/or don't understand that certain versions are not correctly backed up with Nandroid at the moment (e.g CLB).
bftb0
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...

my situation....please help

rooted via ubuntu and have recovery
i tried doing stuff in windows, but it wont install the drivers properly.
SO I NEED HELP!
what do i do to get this to work?
i want to be able to install 3rd party apps and get rid of att bloatware.
i have no idea where to start.
HELP!!!!!!!!!
thanx
ubuntu or windows...
download the Android SDK for Windows
http://developer.android.com/sdk/index.html
install and download ONLY THE USB DRIVERS
open cmd window, connect usb cable, navigate to the <folder>\tools where you installed, ie. c:\android\tools
paste the following into a small batch file, call it anything you want dot bat,
ie. c:\android\tools\yourname.bat
---cut here--
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
-- cut here--
ok i'll try right now
still must be missing something
what setting is my phone on when i plug it in? recovery? or just regular charge only or hard disk mode?
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
when i run that .bat file it says a bunch of things, but basically says device not found.
please start from step #0.
there is no one place that has every single step we need to do.
it makes it next to impossible to get this to work.
dh4645 said:
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
Click to expand...
Click to collapse
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
ocswing said:
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
Click to expand...
Click to collapse
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
dh4645 said:
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
Click to expand...
Click to collapse
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Shad0wguy said:
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Click to expand...
Click to collapse
so what is the point of the sdk...other than to have the tools folder to run that .bat? so i'm the only one that can't get the sdk usb drivers to work?
and by good to go, u mean i can install 3rd party apps?
how do i get rid of the the at&t bloatware?
There are other threads explaining how to install third party apps and remove ATT bloatware.
Sent from my HTC Liberty using XDA App
The problem with trying to do a step-by-step guide is that things like rooting, removing bloatware, and sideloading apps are all separate processes that require different steps and can be done in multiple ways. Some stuff requires you to be in recovery, some stuff doesn't, and other methods may require additional software. That's why there are specific separate threads that discuss them.
You've rooted your phone already, yay! Now you decide what you want to do next. Remove the bloatware? It's important that you don't lump everything together when trying to figure out what you need to do.
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
ocswing said:
....
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
Click to expand...
Click to collapse
thanks for the reply.
yeah i rooted via the ubuntu disc, but then all the other steps people were telling me were using the sdk, getting the drivers, htc sync, yada yada. via windows. so thats the method i've been trying.
is there a step-by-step guide on how to allow 3rd party apps using the ubuntu disc? or... removing bloatware?
is it the same steps, but you just dont have to worry about the drivers?
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
ocswing said:
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
Click to expand...
Click to collapse
ok cool thanks a lot!
i didn't even think to go back to linux to try this stuff until today at work.
i'll check it out later tonight after i mow the lawn and eat dinner....priorities...
i tried in windows one last time. it actually found the htc sync drivers (i in/uninstalled htc snyc earlier...i guess thats what did it)
adb devices command finds my phone, but when i try and run that .bat file, it goes through a bunch of things, but basically says:
remount failed: operation not permitted
failed to copy...
permission denied
all those types of things. then it says to hit enter and then it restarts my phone
???
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
b_atman said:
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
Click to expand...
Click to collapse
i said i did that above...that was the only way i got the usb drivers to work/recognize my phone...the sdk ones didnt work)
my phone is recognized when i run adb devices command
i'm having issues when i run the .bat file as i said in my last post
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
b_atman said:
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
Click to expand...
Click to collapse
uuu, no, whats that?
i thought i just had to open cmd and run the .bat file
so what did i miss now? ha
thanks for your help!
i ran this .bat file
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot

Im going CRAZY trying to root!

Heres the deal. I have a MAC with a newly installed hard drive. On my old hard drive I had everything setup with SDK and Adb but that was when I had an HTC Hero. My problem is this: When in terminal my damn computer keeps prompting me for a password but it doesnt allow me to type anything except control C which aborts the program. It never was like that with the old hard drive.
2. Ive dl SDK for MAC unzipped it and saved it to my desktop and my hard drive.
3. When I click on tools it says "adb_has_moved.txt"
4. It says the adb tool has moved to platform-tools/ and if you dont see this directory in your SDK, launch the SDK and AVD manager and install "android SDK Platform-tools and also update my path environment variable to include the platform-tools/ directory, so I can execute adb from any location. What the heck does this mean and how do I fix it. Also how do I know if SDK is installed correctly.
5. I DL some version of eclipse that was recommended from SDK but I dont know how to use that either.
6. I have tried all the root methods shown here in XDA except the on with the Dock since I dont have a dock.
7. Also ADB does not recognize my device and my debug is selected. I cannot get it to find my device.
8. One last question when some instructions say unzipped and move the root exploit to /data/tmp/ is that the file labeled under sdcard/data or is it the one inside the Android Folder listed as "data"
Please anyone help if possible.
let me try that
Stupid question but How do I launch SDK?
laraiza said:
Stupid question but How do I launch SDK?
Click to expand...
Click to collapse
Make sure your phone has USB Debugging Mode enabled. Otherwise, adb will not recognize your device.
Check this thread: http://forum.xda-developers.com/showthread.php?t=879701
However, you will have to modify for MAC.
In my opinion the easiest way to root the Photon is still using the dock method. Otherwise, try the One Click Root method (Torpedo) as mentioned above. Then you don't have to worry about issuing all the commands.
I got it done I got it done. What I did was borrow my daughters windows netbook and the one click method worked on the first try. Thanks to all who replied. I will definitely hit your thanks buttons.
Sent from my MB855 using XDA App
im sorry.. my tool was a one click i dint think i needed to give it instructions.. especially teh part of how to run it on your computer... just fyi.. when invoking sudo (to do things as admin/root) on your computer. you are asked to enter in your password.. as a privacy/security feature it will NOT display any characters.. ergo it looks blank...
as you arent teh first one to run into this issue ill add instructions for mac users ( i know anyone running linux can figure out how to run a bash script, and windows users have a bat file after installing 209387249087 drivers... but they still figure it out ;P)

[Q] Please help me use the command prompt with SDK. . . .

I don't know how to use the cmd prompt. I've looked at the other posts on this forum and on other sites but their solutions don't seem to work for me. If I copy and paste this C:\Program Files\Android\android-sdk\SDK Manager.exe I get a reply saying it is not recognised as an internal or external command, operable program or batch file. Now if I copy and paste this "C:\Program Files\Android\android-sdk\SDK Manager.exe" it opens up SDK manager but I'm unable to input anymore text into the cmd prompt window.
I can't get my system to recognise adb devices but I have installed all the drivers for my Nexus One and I can identify my N1 through windows. I've also installed Eclipse.
I'm wanting to install another ROM on my handset( unlocked ) but if I can't get my device recognised via the cmd how can I do that? ?
I'm sure that I'm doing something wrong but I can't figure out what! Can you please advise me?
I'm still trying to figure it out but getting nowhere fast! ?
EUREKA!
At last it works, or, At last I can do it!
My device now shows up when I use cmd fastboot devices. I reinstalled the sdk direclty to C:\ . . . . don't why that would make any difference.

[Q] SDK and ADB

Ok, I'm just going to ask it...
How do I set up SDK and ADB on my 3rd generation HDX 8.9. I find quite a few sets of instructions from 2011 but nothing seems up to date. And android studio is installing the driver in amazon.com which seems weird.
This is the latest I tried--here
I've searched and searched--I've tried several of these with no luck getting the pc to recognize the kindle.
Please no hateful replies--I've been at this for 2 days and I or really wouldn't ask.
Links would be really useful.
Thank you
Unless you are developing, you do not need android studio, jdk, or anything else. All you need to to do is download the sdk.
From here I am going to assume you are on Windows. Probably win 8 or 8.1?
Extract the sdk to a folder where you have write access.
Now find the folder called platform-tools in the sdk folder.
Now, in the Windows explorer bar, select all the text and type cmd
If you do this right, it will open a command window in the platform- tools folder.
If that is confusing, you can go to the sdk folder and then open the command prompt from the start window. Then type cd and drag the platform-tools folder to the command window.
Right now, all the devs are crying, because these are lazy shortcuts, but they work and save you from adding this folder to your path which is better programmatically, but a bit more involved.
Anyway, now you are where you need to be so, type
Code:
adb devices
And you should see your device, but, you probably won't. Stay tuned...
Sent from my KFTHWI using Tapatalk
You don't need to install the whole Android Studio suite — just the SDK Tools will suffice.
As for the Kindle Fire drivers...
https://developer.amazon.com/appsan...ing-up-the-ADB-Driver-for-Kindle-Fire-Devices
So, hopefully you got either a printout of your device, or you got a blank line like...
Code:
List of devices attached...
This is because you do not have the driver installed. If you get another error, either you are in the wrong folder, or you did not enable and on your device.
Code:
To enable adb on your device, click on the serial number in settings>device options 5 times and it will give you the developer options. Enable adb is a toggle there.
Alright, now we need the driver. Go to device manager in your computer and delete anything that looks android or kindle in nature. Unhook your tablet and reboot.
Download the HDX toolkit from the developers error forum and try the install drivers tool in it.
Reboot.
Now, making sure you have enabled adb on your device, open up a command prompt in platform-tools, and try the command again.
Code:
Adb devices
You should see your serial number.
If you have any issues, report back. I may have skipped a step or two as I am giving these directions from memory.
Good luck.
~Leko
Whew! Thank you! Doing this now.
Will update
Did I say thank you?!!!!
Update...After extracting the sdk zip file, platform tools is not showing up.
Downloading the installer file now...
Update2...found platform tools
Oh, my bad, I'm on windows 7...
Update--
The kindle died..thanks for all the input! Greatly appreciated:good:
lekofraggle said:
So, hopefully you got either a printout of your device, or you got a blank line like...
Code:
List of devices attached...
This is because you do not have the driver installed. If you get another error, either you are in the wrong folder, or you did not enable and on your device.
Code:
To enable adb on your device, click on the serial number in settings>device options 5 times and it will give you the developer options. Enable adb is a toggle there.
Alright, now we need the driver. Go to device manager in your computer and delete anything that looks android or kindle in nature. Unhook your tablet and reboot.
Download the HDX toolkit from the developers error forum and try the install drivers tool in it.
Reboot.
Now, making sure you have enabled adb on your device, open up a command prompt in platform-tools, and try the command again.
Code:
Adb devices
You should see your serial number.
If you have any issues, report back. I may have skipped a step or two as I am giving these directions from memory.
Good luck.
~Leko
Click to expand...
Click to collapse
So I am stuck adb devices--the line is blank
--ADB is enabled
--USB debugging is checked
--kindle driver installed
--portable device deleted in device manager
--SDK is set up C:\Program Files (x86)\Android\android-sdk\platform-tools
The driver installed in a separate file in program files as amazon.com which looks odd to me.
Maybe my path is wrong?
Update I've tried the method found here but after 2 tries with reboots, I'm still getting MTP device and portable device->fire. Each time i see the last one I delete it, reboot plug in again and portable device appears.
I've also tried Amazon instructions here
Anyone have any ideas?
Thanks in advance!
It sounds like you are on the right track.
Unplug your kindle, delete the devices again, and try this file.
http://forum.xda-developers.com/showthread.php?t=2665683
Use it just to install the drivers. (That is all it can do for you).
Then open a command prompt.
And plug your device in.
.
If the drivers are installed correctly, the path only matters to get adb to work (which the blank line tells you it is).
Also, there is a chance the devices will show up the same after the correct drivers are used. Mtp is able to run aside adb, but on Win 8 anyway, not fastboot (don't worry about fastboot).

Categories

Resources