I have followed the directions to the letter. I see my nook in device manager as Android Phone and then ADB interface, but when i go to command line and type ADB devices , it shows:
List of devices attached
and then it is blank. my server is running as i did that first, says successful. I have tried this on 2 different computers. Windows 7 64 bit.
Update - changed the drivers to the one with the script post and now i see it.
This isn't the Q&A section or general section.
Apply your question(s) in the proper sub-forum, cause you picked the wrong one.
Posting in the wrong forum might result in a temporary vacation
Related
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...
whats the next step after device manager recognizes android devices?
What program do i open up so I can start altering scripts, especially for adhoc?
thankx
specifically, which program in sdk android tools do i use for adb to alter scripts
specifically, which program in sdk android tools do i use for adb to alter scripts
This isn't the Q&A section or general section.
Apply your question(s) in the proper sub-forum, cause you picked the wrong one.
Posting in the wrong forum might result in a temporary vacation
Post moved to general forum.
Hey all,
I rooted my CN using autonooter and the instructions available at the nookdevs wiki (I'd post a link but I'm not allowed, yet). I also enabled adb over usb following instructions at the same site.
However, today I signed up as a developer on nookdeveloper.barnesandnoble.com and found that there is an official nook development kit which also provides adb access and a nice nook virtual machine to test stuff on.
My question is, if I use the official nook development kit as opposed to the drivers provided at the nookdevs wiki, do I lose any functionality? I'm guessing adb access is adb access no matter what, but then we all know what happens when one makes assumptions =P
I guess I'll know for sure when I try it out later, just thought maybe someone has been down this road already.
adb is part of the tools in the android sdk package. The Nook Color virtual machine is also a part of the sdk that can be downloaded (along with lots of other things). They are both part of the sdk and you would not get a 'different' adb.
Cheers
I'm trying to install the latest ROM - I have followed the instructions, but when I try and run setup to install the drivers, Windows tells me that it has found fastbook, I get the windows driver install prompt - I select next, it obviously looks for the driver - and then I get the message - Cannot Install this Hardware. This therefore means that the drivers do not install and I get the message "Please Plug-in your Device!!" I hit OK - it tells me the same again and again - and the rollsback the driver install. Any ideas on how I can overcome? Thanks.
leighv said:
I'm trying to install the latest ROM - I have followed the instructions, but when I try and run setup to install the drivers, Windows tells me that it has found fastbook, I get the windows driver install prompt - I select next, it obviously looks for the driver - and then I get the message - Cannot Install this Hardware. This therefore means that the drivers do not install and I get the message "Please Plug-in your Device!!" I hit OK - it tells me the same again and again - and the rollsback the driver install. Any ideas on how I can overcome? Thanks.
Click to expand...
Click to collapse
I really hope your on a mobile device that is auto correcting "fastboot" as "fast book":thumbdown:
You have to manually point windows to the folder you have the drivers unpacked onto your computer
Search the forums...... even read the stickies section. This has been described in full detail several times.
This took me a minute to search, copy, paste:
http://forum.xda-developers.com/showthread.php?t=1395964
There is a link there to install drivers, do some reading, the streak is not as common a development as other more popular devices.
The drivers should be located in the nvflash package you say you are trying to install. Again, point windows to the folder the drivers are in.
I will not provide step by step instructions as I myself and many before me have already done so. Give yourself a half hour of reading through the posts and you will more then likely find exactly what you are looking for.
Sent from my Galaxy Nexus using xda premium
ElfinJNoty said:
Give yourself a half hour of reading through the posts and you will more then likely find exactly what you are looking for.
Click to expand...
Click to collapse
you're being way too lenient with the n00bs, half an hour of reading through forums? seriously, this is the same guy who apparently put a 128gb sdcard in a streak 7 and made it apparently work, I deem this thread closed as the amount of others that contain information to the questions asked
Question answered above. Please search thoroughly in future before creating threads.
Thread closed.
For those having issues with Revone S-OFF for their One (as I did)
A little googling and I managed to resolve the issue but cant post it in that specific forum until I make 10 posts (rules are rules eh?)
Applies to Windows Machines as that's what I'm running and haven't tried my Linux box yet
Update your ADB Drivers and files using this link: "dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip" - direct copy of the platform-tools from the SDK but sometimes you don't need all the additional stuff that comes with the SDK
As an 'Old Skool Droider' I simply unpacked to 'C:Andriod' and ran my Command Prompt in there: 'adb devices' comes up clear as does pushing files to and fro etc etc etc.
Probably the simplest thing in the world tbh but I noticed that some folks were still running into issues, since its been a while since I last did some faffing with Android my drivers were older then the Ark
-H
p.s Cant post direct Links either