I have rooted my phone once before like a year ago, and it worked like a charm - but when the official 1.6 came out it apparently unrooted me (I assume thats what happened?) All I know is now when I try to run root required apps it tells me I'm not rooted.
So I figured to just start over from the beginning. I downgraded to RC29 no problem, but when I get to the telnet step it shows a pattern of question marks in diamonds, with boxes separating them. Like this:
<?><?>[]<?><?>[]<?><?> <?><?>[]<?><?> #
I run the commands anyway, (with the Recovery Image and HardSPL on the root of my SD card) - with each command returning two hash marks # #. But the commands don't seem to do anything, because even when I finish ROM Manager tells me I'm not rooted.
Back in Telnet, I can 'ls' to see my directories, including a root folder - but I'm not sure that means anything.
Not sure where to go from here - any help would be greatly appreciated...
-TQ
........................................
The following Observation was made :
Wrong Section. Belongs in Q/A
K so when u go in adb and type adb shell do you see # or $
Please let us know.
Apologies for posting in the wrong forum. And thanks for moving it.
I can't connect to my phone via ADB - I just get 'device not found' even though I have the USB drivers downloaded. If I do 'adb devices' it shows a blank list.
I've looked into how to resolve this, but with no luck. The phone shows up in device manager under the 'Disk Drives' category as "HTC Android Phone USB Device" when everywhere I read says it should show up under the ADB interface section as "HTC Dream Composite ADB Interface".
I've tried USBDeview to reinstall it properly - no dice. And I tried manually updating the driver with ones I downloaded, but windows says I already have the best driver installed.
I don't know what to do now...
Related
I HAVE SEARCHED AND THIS WAS NOT POSTED IN ANY DREAM FORUM, SO DELETING ISN'T NECESSARY. Also if you are going to delete another one of my threads PM me why it was necessary.
Now then. I recently bricked my G1 after losing root and trying to regain it. I was sent a new one and everything is peachy (I have root and a flashy new build) but adb will not recognize the device. Could this be because it's a new device? Considering it worked with the old one. Any help would be appreciated. And for the record I have the newest radio and spl.
uninstall the drivers, the dream adb interface and the usb composite device associated with the phone. unplug the phone, download the 1.5 compatable drivers, plug the phone back in and you should be golden. if that doesnt work, check the adb guide in the development forum. theres about 50 pages of troubleshooting in there.
I understand everything you are saying but I have a couple of questions. First, it always baffled me how to figure out which composite device went with what usb device in DM. Also, I was not aware there was a different set of drivers for 1.5 devices and where might I find a link. And thanks for the help.
Just look under ADB Interface (under Device Manager) and uninstall any drivers under there. Then once that is done, plug in your device and wait for the new device window to pop up. Once there, select to browse for the driver and navigate to the USB drivers that come with the Android SDK. Once you have selected the correct folder, uncheck show only compatible devices on the window and it should show 3 different drivers. Select HTC Dream. Install the drivers and everything should be just peachy again. Good luck.
Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.
Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .
Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)
Glad I could help .
OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???
Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .
for the past 18 months I have been able to access my G1 via USB. I could mount it easily and ADB was set up correctly. for some reason this week, it stopped working. now when I plus it in, I get the "USB Not Recognized" error in XP, and my device no longer shows up as an adroid phoen in Device Mgr. It now says unknown device.
I have tried updating the driver with no luck.
Any ideas would be great,
Thanks
Something similar happened to me. After trying to mess around with Live Wallpapers and DroidExplorer, my phone doesn't show up. I get the "Error: Device not found".
I have the latest USB driver, but yet device manager keeps saying that it's up to date when I try to reinstall (however under Driver Details, Vista says the location of the drivers are on System32 and they're Microsoft drivers....)
Edit: after searching Google for answers, I stumbled on a Google Group and found that someone fixed their issue (similar to mine) by installing HTC Sync. I did, and voila! ADB works again.
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
OUTSTANDING!! That did it. Thanks a bunch, and thanks for the link!
fixed for real now
So the above didn't do it for me, here's what I did:
download and extract USBDeview
Open it up and remove the 3 or 4 entries that say "android phone"
Unlplug (if its plugged into USB) your phone and replug it in, the "found new hardware" window should pop up and be sure to install the drivers that came with the SDK.
That took care of my USB mounting situation, but I still couldn't get adb or fastboot to see my device. Turns out I had adb.exe and fastboot.exe in my WINDOWS/System32 folder as well as in the SDK/tools folder (prolly from when I updated the SDK). Having them in 2 spots seemed to cause problems so I removed them from the SDK/Tools folder. Alternatively I could have removed the other set, but I didn't want to go to my SDK folder every time to use them, this way I can access ADB from any folder on my computer.
This is all from memory so if something's not clear, lemme know. All I know is ADB and Fastboot are working now.
Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?
Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.
Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App
Get ADB wireless, it works great.
I've had zero luck using usb adb, but adb wireless works great!
I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.
Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.
can someone link me to a link on how to use/setup adb wireless
beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?
beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!
Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP
Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.
I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.
This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!
THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
oceanisbleu said:
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
Click to expand...
Click to collapse
Double check your path...
"Now type cd\AndroidSDK\tools\"
My path is c:\android-sdk-windows\tools\
I've renamed the file to AndroidSDK & placed it directly in C:/ so for me it's C:/ AndroidSDK/tools/
doesn't work...
-I plug the phone in and it's recognized as "Android ADB Interface" in device manager
-I open easy tether on the phone then right click on the pc & click connect then it says connection established via Android ADB.....
-I open CMD
-I type cd\
-then cd\AndroidSDK\tools\
-then adb devices & this is where I want to break everything because I can never get past this part and all I see is 'adb' is not recognized as an internal or external command.......
I hate this phone lol & wish I had the money to get the evo so I can put this thing in the trash, I just want to setup firerat's and that's the main reason why I want to establish ADB, is there any way it can be done without ADB????
thanks for trying to help, I hope someone can still figure this out for me
If you downloaded the newest SDK, then the problem might be that you are looking for adb in the wrong directory. It is no longer located in \tools. It was moved to the \platform-tools directory
Sent from my HERO CDMA using xda premium
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
I have just added this exact directory to the end of my PATH
;C:\AndroidSDK\platform-tools\
rebooted, opened cmd, typed adb devices and still I get ADB is not a recognized command.
I went to HTC's site & downloaded the latest hero sync software (new version just came out 2 days ago) when I plugged my phone in it re-installed the drivers, tried it again and nothing!!
I did notice that after the HTC Sync installation in device manager the phone is no longer Android ADB Device, now it says MY HTC, did Sync ruin my ADB drivers?
Ok. So were you at with this???
Shoot me a pm if you still need assistance.
Edit: From reading your post I think your not changing the directory first.
So open up the cmd window. And type cd\ "then hit enter"
Thenn type.
cd\AndroidSDK\platform-tools\
And hit enter.
Then type. "adb devices" without the quotes. And see if that will show your serial number.
If that yeilds no results then try
cd\android\SDK\tools\
And hit enter.
Then type "adb devices" without the quotes. And hit enter and see if that will return your serial number.
Locked & Loaded
" Shooter on Deck"
Thanks guys for all the help you have provided, I have finally figured it out using this guide;
http://forum.xda-developers.com/showthread.php?t=532719
slightly different than the first guide I followed, instead of editing the PATH a new Environment Variable was created also a slightly different CMD code to get to ADB;
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
I hope this helps anyone else who might have the same issue.