i rooted my nook color and have been trying to get my ADB to recognize my device but my results have not given me the same results i have seen on the http://nookdevs.com/NookColor_USB_ADB
instead of
* daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached [YOUR NOOKCOLOR SN] device
i get this
#######-MacBook-Pro:~ rumitg2$ Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz1A7LtTuTP
Under Creative Commons License: Attribution Non-Commercial Share Alike
/usr/bin/Read: line 4: read: `more:': not a valid identifier
#######-MacBook-Pro:~ rumitg2$ adb devices
List of devices attached
I get 16 #s here device
is this supposed to happen
The 16#'s your getting is your serial number which is what your suppose to get so it worked.
Related
why when i write in CMD adb devices it returns me this
C:\Users\Niki>adb devices
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
Try entering task manager and killing all instances of adb.exe
If not possible reboot pc and phone.
If still not working have a look at this: http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
When it works come tell me I am cool and press thanks button.
it works that way
Hello ill post the log here
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
695 KB/s (585731 bytes in 0.823s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
Waiting ...
error: protocol fault (no status)
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT righ
.
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Waiting ...
adb server is out of date. killing...
* daemon started successfully *
Jeasus please help me somebody via tv i cant do this **** it wont go 807 286 319 pass is 123456 ILL KEEP IT ON
nikolai4os said:
Jeasus please help me somebody via tv i cant do this **** it wont go 807 286 319 pass is 123456 ILL KEEP IT ON
Click to expand...
Click to collapse
check your antivirus
nikolai4os said:
Jeasus please help me somebody via tv i cant do this **** it wont go 807 286 319 pass is 123456 ILL KEEP IT ON
Click to expand...
Click to collapse
Open Task Manager on PC. Just Ctrl+Alt+Del and END process “ADB.exe”; if its running.
As CnC-ROCK said as above..Turn of all kind of Antivirus. Anything. Even a malware checker should be turned off..
These can help..step by step tutorial
http://ijustutter.com/guide-flashing-naa-kernel-custom-rom-x8-w8-x10-mini-pro
http://ijustutter.com/step-by-step-guide-to-unlock-bootloader-of-x8-w8-x10-mini-x10-mini-pro
CnC-ROCK said:
check your antivirus
Click to expand...
Click to collapse
I dont use any.
Try to get new versions of ADB
Do it thought flashtool
Install drivers
Go to plugin/unlock/then the program it will ask you to connect your device(disabled) in flash mode with pressed back button in usb port/then will ask you to switch on your device/then when the Sony Ericsson logo appears connect again your device one more time in usb to complete the unlock(THIS IS IMPORTANT) method
This method always work even with antivirus on
Tip:
If you have issues with SHOW flashmode drivers install also and the Gordons gate
Hi Guys,
Been having a bit of trouble connecting phone via ADB. I can get the connection to work, but it takes a bit of TLC and sometimes a sledgehammer.
Thought we could compile a list of ADB troubleshooting techniques?
If you have any further suggestions, please share.
c:\Fastboot>adb reboot recovery
* daemon not running. starting it now *
* daemon started successfully *
error: device offline
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Click to expand...
Click to collapse
Resolution: Kill all adb.exe processes from task manager and rerun the command. May need to do this a few times.
Edit: I should mention that I'm using adb.exe on Windows 8.1
Hello,
I have following problem. maybe someone has a solution.
Using CM12 -Temasek Builds on D405n.
When i start adb shell always get following error:
Code:
C:\ADB>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[COLOR="Red"]error: device not found[/COLOR]
On stock image 5.0.2 this working fine.
hi I've a kindle fire hd 7 demo store and I 've created a fastboot cable, but when I reboot into fastboot mode, Kindle Fire does not provide USB Driver for Android Debug Bridge (adb) usage (although correctly installed in windows):
HTML:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\adbfastboot>adb kill-server
C:\adbfastboot>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
This is the procedure that I followed:
1) Install Android SDK Development Environment and google usb driver
2) Open android_winusb.inf with notepad.
Insert these 3 lines at [Google.NTx86] and [Google.NTamd64].
;Kindle Fire HD 7
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
3) Open adb_usb.ini with notepad.
Key in 0x1949. (don’t copy and paste)
Save it.
4) Browse my computer for driver software and manually install it
No error in control panel but adb don't work..
Is there another way that I can use? Please help.
I think the ADB drivers are disabled on kindle, what I do not understand is that, if I do not have the ability to enable them, how can I proceed?