Related
I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU CAUSE!
So you are stumbling around XDA and you really want some kind of app or something, but you think you cant because you have a Mac, well I am here to tell you wrong.
The biggest and most used mistake for mac users when trying to use ADB is this:
HTML:
Inas-iMac:~ Hans$ /AndroidSDk/tools
-bash: /AndroidSDk/tools: is a directory
Inas-iMac:~ Hans$
Well this is how you do it!
Watch this!
http://www.youtube.com/watch?v=GLAMG4xU_lE
To make your phone go into debug mode go to settings/applications/development and check debug
DO NOT MOUNT PHONE! Just let it be
I did not go to deep into the process because this is made for complete beginners!
Why not follow the official SDK install instructions and add the path to bash_profile..
developer.android.com/sdk/installing.html#Installing
In my opinion that's not too hard for a newbie.. (i managed to do that) And after doing that you don't need to change directories with cd command, you can just type adb whatevercommand from your home dir which is the default location when you open the terminal.
Drag and drop is a little a fail.... one can add "alias" (linux can do it, probably mac too)
Little How-to:
Code:
$ nano ./bashrc
add and adapt the following line to bashrc:
Code:
alias adb="/home/carbonyle/android-sdk-linux_86/tools/adb"
now you just have to type "adb" from a terminal emulator to run it, eg:
Code:
$ adb shell
# reboot recovery
or
Code:
adb install ./Download/myFavortiteApp.apk
and so on...
ps: we don't need to "adb remount" at worst we can just "adb kill-server" then "adb start-server" if the device is not accessible
SOLVED! Followed the Guide in Post #5, than kept getting an error saying libncurse.so.5 cannot be found. I than opened the Package Manager and downloaded everything in the sun-java6-sdk and anything related to it. Than searched for anything of libncurse and installed those. than got a libc++ (or similar) missing than went back to Package Manager and download anything with libc++ in it. Afterwards, ran fine.
One quirk, as I'm sure this will be general knowledge to any Linux user but I am still a newbie at it. In root # i had to do ./adb to run the command, running just # abd gave me errors, exiting root back to $ alowed me to just use $ adb and not have to do ./adb
I know it's pretty shoddy, I think i downloaded 250MB of stuff I'm not sure I need. lol. I searched for the libncurse.so.5 file and had a lot of em, i think the package that actually did the trick was a ncurse32bit package, as I am on a 64 bit system. So take that into consideration
downloaded the android sdk, extracted it, however, when i use terminal and goto the tools folder and use adb
i get...
[email protected] /usr/bin/android-sdk/tools $ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
Click to expand...
Click to collapse
I read something about adding it to path, and i went into my .profile and added in the :/usr/bin/android-sdk/tools after the $PATH yaddayadda but it still didn't work.
Any help is appreciated. This is really the only thing keeping me from wiping the 120gb partition for Win7 and using Linux only(which only has a 21gb partition)
Nrre said:
downloaded the android sdk, extracted it, however, when i use terminal and goto the tools folder and use adb
i get...
I read something about adding it to path, and i went into my .profile and added in the :/usr/bin/android-sdk/tools after the $PATH yaddayadda but it still didn't work.
Any help is appreciated. This is really the only thing keeping me from wiping the 120gb partition for Win7 and using Linux only(which only has a 21gb partition)
Click to expand...
Click to collapse
Since the android sdk doesn't actually install on your computer but placed there by you, you must make sure everything is in place for it to work properly. I am relatively new to linux myself, but this is what i've done to get it working properly:
create /etc/init.d/adbd
you will need to do this as root.
Code:
gksu gedit /etc/init.d/adbd
paste this into the file
Code:
#!/bin/sh
#
# For ADB deamon (Android Device Bridge)
#
case "$1" in
start)
/usr/bin/android-sdk/tools/adb start-server
;;
stop)
/usr/bin/android-sdk/tools/adb kill-server
;;
*)
echo "Usage: $0 start|stop" >&2
exit 3
;;
esac
now run this:
Code:
sudo ln -s /etc/init.d/adbd /etc/rc2.d/S10adbd
What you just did there was make sure adb daemon started as root whenever you booted (if you don't start it as root you will get errors later on down the road)
I'm not sure about mint, but on ubuntu its easier to just add the tools folder to your /etc/environment file.
Code:
gksu gedit /etc/environment
the file should look something like this:
Code:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/bin/android-sdk/tools"
go ahead and reboot just to make sure everything sticks. You should be good from then on.
You could add the path to your profile, but then if you have to run something as sudo, or if you have another user trying to do something similar, it could be a headache. If you don't have a /etc/environment, or if the above still doesn't work, go ahead and see if you have a ~/.bashrc.
edit that:
Code:
gksu gedit ~/.bashrc
add this to the bottom:
Code:
export PATH=${PATH}:/usr/bin/android-sdk/tools
let me know if this works, and if there are any more experienced linux users out there who notice any mistakes of mine, or have better advice please chip in. I just know I went through a huge amount of frustration to get adb to work properly, through much trial and error. this is the culmination of what i went through that was easiest for me. BTW i stole that code for the daemon to startup as root from somewhere else.
EDIT: I just realized my daemon is still not starting on boot? although, with the above script i can start it via:
Code:
sudo service adbd start
someone smarter than me, chip in and tell me what i'm doing wrong?
OP, you can always start the daemon yourself as root by typing
Code:
sudo /usr/bin/android-sdk/tools/adb start-server
EDIT: woops. I fixed the code above, as well as fixed my problem. on creating a link to rc2.d i typed "s10adbd" originally and it should be "S10adbd".
OP, this is a great example why paying attention to capital/lower case letters are super important when learning linux.
i changed my link and everything works on my system.
think i'm still doing it wrong. i didn't have a .bashrc file but i did have a bash.bashrc file.
i know linux mint is based off ubuntu.
here is my command line after doing everything above
richard-laptop richard # /usr/bin/android-sdk/tools/adb start-server
/usr/bin/android-sdk/tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop richard # sudo service adbd start
adbd: unrecognized service
richard-laptop richard # adb shell
adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
think i'll take the laptop into work and mess with it tonight.
If you don't setup a your bash file, you can issue adb commands by using standard terminal commands from the /tools directory:
user:~$ ./adb start-server
Click to expand...
Click to collapse
To setup your .bash file, right from Google:
# On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ directory to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:<your_sdk_dir>/tools
Click to expand...
Click to collapse
From terminal, you can run
user:~$ gedit ~/.bashrc
Click to expand...
Click to collapse
Nrre said:
think i'll take the laptop into work and mess with it tonight.
Click to expand...
Click to collapse
Please follow these instructions (source = wiki.cyanogenmod.com):
Ubuntu: Android SDK, ADB, Fastboot.
There are various great tutorials online to help you set these options up for Windows, but the process of setting this up in Ubuntu Linux is rather fragmented across various different forums, and can be rather confusing! This is a tutorial I have put together after having real trouble setting it up myself, after trawling through numerous forums, and getting help from many very helpful folks on various forums including this one!
Tutorial: This will show you how to complete the basic set up of the Android sdk, and then how to enable the 'adb' and 'fastboot' connections so as to allow you to issue commands from the terminal directly to your phone.
Disclaimer: As always, you follow this tutorial at your own risk, nobody is forcing you to! I take absolutely no responsibility for damage to your computer / mobile phone etc. This is the process I have followed, and it is working fine!
Basic Android sdk installation and set-up:
You will need to download the following files before you start:
android_sdk_r05-linux_86.tgz [1]
Fastboot [2]
1. Extract the 'android_sdk_r05-linux_86.tgz' file to your 'Home' folder and rename it to 'sdk' to make things easier later on.
2. Move the fastboot file in to the 'Tools' folder inside the 'sdk' folder.
3. Now right click on both the 'fastboot' and 'adb' files (inside the tools folder) and choose 'Properties' and then the 'Permissions' tab, and ensure they both have the 'allow executing file as program' box is ticked...Now reboot the computer, sorted!
Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal
1.Open your 'Home' folder. Press 'Ctrl' & 'H' at the same time to view hidden files, and then open the '.bashrc' file and add the following text to the top of the file:
#AndroidDev PATH
export PATH=$PATH:/home/username/sdk/tools
2.Obviously you will need to replace 'username' with your own...Save the file and exit.
3.Now log-in as root.
3. Navigate to the following directory in the root filesystem: /etc/udev/rules.d/
4. Create the following empty file:
(ubuntu 10.04)
99-android.rules
(ubuntu 9.10)
70-android.rules
(ubuntu 7.10/8.04)
51-android.rules
5. You then need to edit the file with the following text (depending on your version of ubuntu):
ubuntu 7.10/8.04/9.10:
SUBSYSTEM==”usb”, ATTRS{idVendor}==”0bb4”, MODE=”0666”
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1”, MODE=”0666”
SUBSYSTEM==”usb”, ATTRS{idVendor}==”22b8”, MODE=”0666”
ubuntu 6.06:
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”0bb4”, MODE=”0666”
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”18d1”, MODE=”0666”
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”22b8”, MODE=”0666”
6. Save this file, and then open the terminal and enter the following command:
chmod a+rx /etc/udev/rules.d/70-android.rules
Change the '70' to '51' depending on your version of ubuntu.
For a list of the vendor ID's go here: VendorID's [3]
7. Now reboot the computer.
8. Open Terminal, and issue the following commands:
su
cd /home/username/sdk/tools/
./adb kill-server
./adb start-server
You will now be able to open a terminal and carry out 'adb' and 'fastboot' commands directly.
Credit and thanks to:
koalaboy, Apostasy, Cloverdale, wddglr, JgeZau.
EDIT: I have followed this tutorial to the letter myself today on my laptop to prove it works, for both yours the reader, and my own peace of mind as the writer! Enjoy, it works flawlessly!
Click to expand...
Click to collapse
I have followed these directions more than once and each time they work flawlessly. This should work with Linux Mint, since Mint's based off Ubuntu.
For Part 4, use Ubuntu 10.04 when creating the empty file and for Part 5, use this SUBSYSTEM: SUBSYSTEM==”usb”, ATTRS{idVendor}==”0bb4”, MODE=”0666” and paste that into your 99-android.rules file.
followed to a T.
not sure how to log in as root, so i just 'run as administrator' i can't find anything on root for this.
i still get the following after i do that entire guide
richard-laptop richard # cd /home/richard/sdk/tools
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop tools # ./adb start-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
Nrre said:
followed to a T.
not sure how to log in as root, so i just 'run as administrator' i can't find anything on root for this.
i still get the following after i do that entire guide
Click to expand...
Click to collapse
To login in as root, you enter:
Code:
sudo su
As for the "error while loading shared libraries: libncurses.so.5" -- I've never seen that error before. Might be Linux Mint problem? I currently run Ubuntu 10.04 32 Bit.
when i do SU it asks my password and the $ becomes a #
i assume that is root? i dont have to do SUDO i just did SU
yeah if i do SUDU SU i get a 'SUDO command not found'
gonna post this over on the linux mint forums see if they can help me to.
Nrre said:
when i do SU it asks my password and the $ becomes a #
i assume that is root? i dont have to do SUDO i just did SU
yeah if i do SUDU SU i get a 'SUDO command not found'
gonna post this over on the linux mint forums see if they can help me to.
Click to expand...
Click to collapse
Wait... wait.. are you trying to do following instructions on your phone or on your computer?
If you run su on your phone, sure you'll get root (# sign). But the command, sudo su was meant for your computer. The instructions I listed are for your computer with Linux Mint installed.
yeah i'm doing it on my computer =P
if i do SUDU SU it gives me that error, but SU gives me #
so...i was hoping it'd all be teh same since Mint is based off ubuntu and half my updates are ubuntu files.
[email protected] ~ $ sudu
No command 'sudu' found, did you mean:
Command 'sudo' from package 'sudo' (main)
Command 'sudo' from package 'sudo-ldap' (universe)
Command 'tudu' from package 'tudu' (universe)
sudu: command not found
[email protected] ~ $ SUDU su
SUDU: command not found
[email protected] ~ $ SUDU SU
SUDU: command not found
Click to expand...
Click to collapse
so, not sure what else to do.
sudo
not sudu
elegantai said:
sudo
not sudu
Click to expand...
Click to collapse
balls, well i still get the same result after i go through and make all the changes and use SUDO SU instead of just SU, i get the same prompt with #
this is still my end result.
richard-laptop richard # cd /home/richard/sdk/tools/
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop tools # ./adb start-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
makes me feel like i'm missing a file somewhere. i did download the newest android sdk and not the older version that is in the guide. but i still installed the packages for android 2.1 and 2.2
suppose i'll delete it all and start over.
EDIT: Went through, put in proper vendor IDs and noticed i put Richard in the Path and not richard, still, says it's missing the same "libncurses.so.5" so...not sure what to do. =/
I don't know that error either, but looking at this thread:
http://bbs.archlinux.org/viewtopic.php?id=66878
sounds like it could be a java issue? Didn't think to ask, have you installed the java sdk? which version of java are you running?
now that i think about it...i don't believe i downloaded a new java...
the worse news is my win7 got corrupted somehow =P so now i only have Linux so time to dig in and try this out.
I'd download the stuff now but I'm tethering through my phone so i'm lucky to get 600kbps download speeds in this reception area.
I could step 10 feet outside and hit 1200kbps though. So i formatted the HD and reinstalled Linux Mint. Once i get home I'll look into the JDK as that makes sense now that I think about it to.
EDIT: Should I install Eclipse also? Installing Android SDK and Java6 JDK right now. I really just want to use ADB for now to send commands to phone etc.
No need for eclipse.. That's just for actual development
ADB Error: /home/richard/sdk/tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
'adb start-server' failed.
Click to expand...
Click to collapse
this shows up int he Android SDK/AVD manager as i install all the packages...
EDIT: opened up software manager, and downloaded every sun-java package, than installed everything that showed up when i typed libncurses ... once it's done will reboot and try again =P
2nd EDIT: i decided to search for libncurses.so.5 and i have 3 of em, one in usr/lib, /lib64 and something else.
so..not sure where else to put it, went into synaptics thing or something and downloaded ncurses32bit as i noticed none of my lib32 folders had it...giving it a go.
btw... my .bashrc is .profile, i copied .profile and renamed it to .bashrc and my prompt stopped showing up in terminal...linux is so weird.
3rd EDIT: Just isn't meant to be. got to ./adb kill-server and instead of missing the libncurse.so.5 i am now missing..
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
off i go to hunt this package down
it's working...finally
however...
richard-laptop tools # adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
richard-laptop tools # ./adb devices
List of devices attached
HT*********** device
Click to expand...
Click to collapse
i have ot do ./adb and not just adb
EDIT: exit su, and in $, lets me just do adb.
THANK YOU EVERYONE <3 Wish I could +rep or Thanks your post here.!!
changed title to reflect it. was a good 'thrown under the bus' into linux. now to read up more on it. w/out losing half my CCNA knowledge i've gathered...ha
Enjoy Linux. You'll enjoy it once you get used to it.
Sent from my PC36100 using XDA App
Nrre said:
it's working...finally
however...
i have ot do ./adb and not just adb
EDIT: exit su, and in $, lets me just do adb.
THANK YOU EVERYONE <3 Wish I could +rep or Thanks your post here.!!
changed title to reflect it. was a good 'thrown under the bus' into linux. now to read up more on it. w/out losing half my CCNA knowledge i've gathered...ha
Click to expand...
Click to collapse
Since this has been solved, I would advise posting the resolution on the first page -- so new users are aware of what exactly you had to do to fix it.
Hey all,
another member just sent this to me regarding JesusFreke's work on adb usb:
mdall said:
This might interest someone : http://pastebin.com/jAV9ixNx (about adb over usb)
Click to expand...
Click to collapse
But the conversation segement is incomplete. I'd really appreciate knowing if anyone ever got ADB USB working with the nook, and if so how we can get it working.
I'm on amd64 debian based linux so I don't get to use the fancy looking windows driver package . And im sure this would help others.
BTW Nookdevs ADB over USB instructions for nook color do not work with the touch.
Thank you,
Endor
I have made a uRamdisk removing the service.adb.tcp.port property in default.prop and I have installed it but adb can't see my device over usb ...
Does anyone know what should I do to have adb over usb ?
Here are the steps I've taken to enable ADB over USB on the NST 1.0.0 (noogied+gapps).
Prerequisites:
SuperUser, I used 2.3.6.3
adbWireless, I used 1.4.1
1. Boot NST to your launcher, with USB cable plugged in
The computer may show "volume NOOK mounted"
2. Unmount the NOOK volume from the computer to get rid of the "USB Mode" dialog on the Nook
3. On NST, start adbWireless
If asked, grant SU
You should see a message like "adbWireless is on!"
4. Now stop adbWireless
USB debugging is still enabled!
The computer may show "volume NOOK mounted"
5. Unmount the NOOK volume just to avoid a "not cleanly unmounted" warning after the next step
6. On the computer, enter the command "adb usb"
You should see a message like "restarting in usb mode" or "daemon not running. starting it now..."
To verify, enter the command "adb devices" and you should see your plugged-in device.
Good luck!
voluntarytestsubject said:
Here are the steps I've taken to enable ADB over USB on the NST 1.0.0 (noogied+gapps).
6. On the computer, enter the command "adb usb"
You should see a message like "restarting in usb mode" or "daemon not running. starting it now..."
To verify, enter the command "adb devices" and you should see your plugged-in device.
Good luck!
Click to expand...
Click to collapse
hi,
i tried your guide to use ADB over USB, but i got stuck at step 6. In fact, when i run "adb usb" i got the error: "error: device not found". And "adb device" returns an empty list.
Do you have any clue?
Thanks
You need the adb drivers for adb over USB, there's multiple guides on how to get ADB over USB for the nook color, if I remember correctly from my conversation with JesusFreke it's basically the same drivers/setup.
mdall said:
I have made a uRamdisk removing the service.adb.tcp.port property in default.prop and I have installed it but adb can't see my device over usb ...
Click to expand...
Click to collapse
I did exactly that, and it works for me.
Commented out that line in /default.prop, rebuilt the uRamdisk, copied it over the one in the /boot partition.
On the Linux side, I only have the 0x2080 line in ~/.android/adb_usb.ini,
and a standard udev-rule like this:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", ATTRS{idProduct}=="0003", MODE="0666", OWNER="xor"
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"
I'm attaching my uRamdisk file. Just rename to uRamdisk, and use at your own risk, obviously. Works fine here.
xor_ said:
I did exactly that, and it works for me.
Commented out that line in /default.prop, rebuilt the uRamdisk, copied it over the one in the /boot partition.
Click to expand...
Click to collapse
hi,
i did exactly the same (rebuild uRamdisk) and it works also for me.
I'm running on a Windows box, so it was slightly more difficult with ADB driver installation, in my case helped the driver pack found on another Nook-Color thread (link).
I don't know why i had in any case to manually update a device driver afterward, in any case, after installing the correct drivers, this time using Nook Touch driver pack (Composite ADB device), now USB ADB works like a charm.
Regards
xor_ said:
I did exactly that, and it works for me.
Commented out that line in /default.prop, rebuilt the uRamdisk, copied it over the one in the /boot partition.
On the Linux side, I only have the 0x2080 line in ~/.android/adb_usb.ini,
and a standard udev-rule like this:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", ATTRS{idProduct}=="0003", MODE="0666", OWNER="xor"
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"
I'm attaching my uRamdisk file. Just rename to uRamdisk, and use at your own risk, obviously. Works fine here.
Click to expand...
Click to collapse
Thank you
That is what I did and it didn't work but strangely I have done it again with your uRamdisk and following http://nookdevs.com/NookColor_USB_ADB and now it works
traycold said:
I'm running on a Windows box, so it was slightly more difficult with ADB driver installation, in my case helped the driver pack found on another Nook-Color thread (link).
I don't know why i had in any case to manually update a device driver afterward, in any case, after installing the correct drivers, this time using Nook Touch driver pack (Composite ADB device), now USB ADB works like a charm.
Click to expand...
Click to collapse
hmm can someone try if it will work on windows with the following driver (from xboxexpert)?
http://forum.xda-developers.com/showthread.php?t=1125094
After reading this thread and the wiki entry for the nook color i finally figured it out to obtain adb via usb:
1. install the uRamdisk created by xor_ from here
2. create ~/.android/adb_usb.ini with the line 0x2080 and restarted the adb server:
Code:
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb start-server
3. add a new udev rule to /etc/udev/rules.d/*-android.rules and reload the udev rules:
Code:
echo 'SUBSYSTEMS=="usb", ATTR{idVendor}=="2080", MODE="0666", GROUP="plugdev"' | sudo tee -a /etc/udev/rules.d/*-android.rules && sudo udevadm control --reload-rules
4. connect the nook to usb
5. and finally you should see the nook
Code:
adb devices
Thank you xor_ and mdall.
traycold said:
hi,
i did exactly the same (rebuild uRamdisk) and it works also for me.
I'm running on a Windows box, so it was slightly more difficult with ADB driver installation, in my case helped the driver pack found on another Nook-Color thread (link).
I don't know why i had in any case to manually update a device driver afterward, in any case, after installing the correct drivers, this time using Nook Touch driver pack (Composite ADB device), now USB ADB works like a charm.
Regards
Click to expand...
Click to collapse
I installed USB driver on Windows XP using the driver pack from that same link and using the attached android_winusb.inf file which was modified adds NSTR PID (which is 0003) to the USB supported list.
Hope it helps
No need to use 3'rd party driver packages for this.
All that is needed is the standard USB driver that comes with the Android SDK and then edit android_winusb.inf and add the following to both [Google.NTx86] and [Google.NTamd64] sections:
Code:
;B&N Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01
And ofc edit adb_usb.ini in your .android folder and add:
Code:
0x2080
That's it
ros87 said:
No need to use 3'rd party driver packages for this.
All that is needed is the standard USB driver that comes with the Android SDK and then edit android_winusb.inf and add the following to both [Google.NTx86] and [Google.NTamd64] sections:
Code:
;B&N Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01
And ofc edit adb_usb.ini in your .android folder and add:
Code:
0x2080
That's it
Click to expand...
Click to collapse
That's exactly what that package does: install the standard USB driver that comes with Android SDK with a modified android_winusb.info and add that line to adb_USB.ini
Is it possible to have USB ADB and WiFi ADB at the same time?
zeepzorp said:
Is it possible to have USB ADB and WiFi ADB at the same time?
Click to expand...
Click to collapse
Yes, just use the uRamdisk with the USB-ADB and something like the adbWireless app for ADB over Wifi.
Has anyone experienced the issue that, despite the NST showing up as an ADB device under Windows, adb.exe doesn't list it as a device? The NST is also showing a "USB Mode" screen, but there's no NOOK drive to eject since there's no NOOK drive showing up.
EDIT: Scratch that. Windows needed a slap on the wrist, now it's all fine.
ros87 said:
And ofc edit adb_usb.ini in your .android folder and add:
Code:
0x2080
Click to expand...
Click to collapse
How do I add that?
using text editor?
or extract this archive into your home folder (e.g. under C:\Documents and Settings\<yourusername>\)
So I can't get this to work at all. I'm running Ubuntu 12.04, adb works fine on my nexus but I don't even get so much as a 'device not recognised' on my nook. I've copied over the pathed uRamdisk (thank you very much) and verified that after a reboot my default.prop contains the necessary lines. I've added the udev rules, modified with my username, and I've tried running adb as root (which I believe should sidestep any udev issues?). I've re-triggered udev, and restarted my PC. I've verified both my usb cable, and the port on both ends work, as I can see the nook from my PC if I have automount enabled. With automount disabled I don't see storage devices, but I still don't see anything with adb devices. I've tried adding the code to .android/adb_usb.ini (doesn't make a difference) and also tried 'android update adb' (interestingly, updates adb_usb.ini to an *empty* file).
I've also tried the suggested trick of toggling adb konnect on/off, and I've tried with the debugging menu's adb checkbox on and off.
Any other suggestions?
Edit: rooted using nookmanager, fw 1.2.0. The reason I want wired USB when wireless is working is that I have occasional soft-reboots and can't find anything relevant in the logcat. I'm hoping that maybe there is something last-minute that doesn't make it through the wireless adb tubes before the reboot happens, but which would show on wired.
For those of you with Mac OSX or Linux, you can root it using this method:
Step 1. Go to Settings->More->Device and make sure “Allow Installation of Applications” is checked “ON”.
Step 2. Connect your Kindle Fire to your computer via micro-USB cable. And hit “Disconnect” to turn off the USB disk drive mode.
Step 3. Download KindleFireRootMacLinux.zip and unzip to the root directory of your hard disk such as c:\KindleFireRoot.
Download KindleFireRootMacLinux.zip
Step 4. Open up a terminal.
Step 5. Browse to the KindleFireRootMacLinux directory by typing:
cd Downloads/KindleFireRootLinux
Step 6. Type:
mkdir ~/.android
cp adb_usb.ini ~/.android/.
*Note – You might have to add “sudo” for Ubuntu
Step 7. Type:
For Mac:
./adb-mac kill-server
./adb-mac devices
For Linux:
./adb-linux kill-server
./adb-linux devices
If you get a bunch of numbers and letters, that means you are good to go.
Step 8. Type:
For Mac:
sh runmemac.sh
For Linux:
sh runmelinux.sh
Step 9. Your Kindle Fire should do its rooting and reboot.
You can verify you have SuperUser app by going to Settings->More->Applications->All Applications.
Yay!
I do not have anything show up when I do the devices command. I am running a mac.
soundslikemitch said:
I do not have anything show up when I do the devices command. I am running a mac.
Click to expand...
Click to collapse
What do you get?
Did you do this step?
cp adb_usb.ini ~.android/.
soundslikemitch
I had this issue as well and zedomax is correct, you have to make sure that this file resides in your own $HOME/.android folder. While cp adb_usb.ini ~.android/. works you may want to try 'cp adb_usb.ini $HOME/.android` as well. I also had the issue where my fire wasn't being shown while executing ./adb devices which required me to reboot and then it seemed to start getting picked up without issue.
Hope this helps and thanks zedomax for the tutorial
There's a problem with the original instructions: adb needs to be restarted after editing adb_usb.ini. You need to run
./adb-mac kill-server
or
./adb-linux kill-server
to make it work without rebooting your computer.
SifJar said:
There's a problem with the original instructions: adb needs to be restarted after editing adb_usb.ini. You need to run
./adb-mac kill-server
or
./adb-linux kill-server
to make it work without rebooting your computer.
Click to expand...
Click to collapse
thanks forgot to put that in the instructions, fixed!
Moving it to my home folder in .android worked!
But apparently this broke the video store.
No-go for me. Tried all above instructions and nothing shows up in devices. The thing that had me thrown off a bit is the instructions don't exactly match.
I want to follow exactly so is step 6 necessary since the zip file already has the android directory with the file already in it?
soundslikemitch said:
Moving it to my home folder in .android worked!
But apparently this broke the video store.
Click to expand...
Click to collapse
I figured out how to fix the video store. Amazon seems to be looking for the existence of the file /system/bin/su so just rename it if you want to watch videos.
i.e.
Code:
mv /system/bin/su /system/bin/su2
reboot
I am still able to type "su2" and get root and I am able to play videos.
Another solution is installed voodoo OTA rootkeeper (free) from the market place. Once installed you can temporarily remove root, then restart the amazon video service and voila. Once the service is started you can re-enable root for the duration that the service is active (not rebooted) you will have root and amazon video.
you have "mkdir ~.android"
The more common syntax, and what worked for me as your syntax didn't, is:
mkdir ~/.android
This is under Mac OS X 10.6.8
None of these instructions have worked for me, I have spent countless hours trying to do this via Windows (the windows tutorial) and on mac. My device never shows up and it does not root. I have tried restarting my fire, unplugging and plugging back in, etc. I am running Lion 10.7.1. Please help, if possible, pm me so we can chat via Google Chat or something.
Also had the same problem (with Lion 1.7.2 ): Waiting for device...
I used this commands to get it working: (first you have to follow instructions from zedomax step 1-5)
cd downloads/
cd KindleFireRootMacLinux/
mkdir ~/.android
cp adb_usb.ini ~/.android
./adb-mac kill-server
./adb-mac devices
after device is shows up enter:
sh runmemac.sh
After this the KF will reboot and get rooted!
The OSX instructions did not work for me either. I ended up busting out my Windows Laptop and followed the guide and programs from rootkindlefire.com
masterc1111 said:
Also had the same problem (with Lion 1.7.2 ): Waiting for device...
I used this commands to get it working: (first you have to follow instructions from zedomax step 1-5)
cd downloads/
cd KindleFireRootMacLinux/
mkdir ~/.android
cp adb_usb.ini ~/.android
./adb-mac kill-server
./adb-mac devices
after device is shows up enter:
sh runmemac.sh
After this the KF will reboot and get rooted!
Click to expand...
Click to collapse
Doesnt work, it still does not show up under devices and the command runemac.sh just says it is waiting for the device.
I don't know why this may work, but try adding a trailing slash to the cp command; cp adb_usb.ini ~/.android/
Also, this works great under (Sabayon) Linux. Very great little script you have here. Only way it could be easier would be if it did the copying and all that on its own.
The problem I had was that the terminal kept saying "waiting for device." I originally downloaded the "KindleFireRootMacLinux" folder to my desktop. I substituted "desktop" for "download" in the prompts. I tried to root it at least 10 times with no success. The terminal never recognized my kindle. Then I moved the "KindleFireRootMacLinux" folder to the "Downloads" folder and it worked the first time. I'm assuming that some of the code is looking in the downloads folder. Try to move it there and see if that works.
bsoplinger said:
you have "mkdir ~.android"
The more common syntax, and what worked for me as your syntax didn't, is:
mkdir ~/.android
This is under Mac OS X 10.6.8
Click to expand...
Click to collapse
Dude! Thanks so much for pointing out the syntax issue. I tried to do this for nearly an hour... couldn't get it to see my device. But after adding the "/" as you so cleverly suggested, voila. Success!
Thanks a million!
root ran ok
should su show up in apps? Nevermind found it
I searched for the voodoo file and it doesn't show up in the app store. If its on the Android Market then I guess you'd have to download and install that first right?
EDIT: which is explained here - how to get market on fire
http://forum.xda-developers.com/showthread.php?t=1349902
Hi friends,
a short tutorial for rooting Ventos 10.1 from simple user Linux Ubuntu, when ADB doesn't recognise the device using Root_with_Restore_by_Bin4ry_v33 from this thread.
Disclaimer: The following rooting guides take software from third-party sources and are not products of danjde. I cannot be held responsible for any effects on your device resulting from this rooting guides. Please attempt only after reading through and understanding the guide(s) and proceed with caution.
ATTENTION: TABLET BATTERY MUST BE CHARGED!!
ALL FROM LINUX CONSOLE/TERMINAL WITHOUT EXTERNAL APPLICATIONS
1) edit from super user editor and add the correct USB Ids to /var/lib/usbutils/usb.ids:
2207 RocketChip
now lsusb should show the device properly
lsusb
Bus 001 Device 012: ID 2207:0010 RocketChip
2) add udev rule in /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"
3) restart udev service
service udev reload
4) optionally add vendor id in ~/.android/adb_usb.ini or in the same adb location
0x2207
5) extract the content of Root_with_Restore_by_Bin4ry_v33 and give executions permission to all fro semplicity (compessing whith zip have lost attributes)
chmod -R 755 "extracted-folder"
6) cd into the utility "Root_with_Restore_by_Bin4ry" directory
cd stuff
7) restart adb server
./adb kill-server
./adb start-server
8) connect Ventos and enable usb debugging.
9) now adb devices shows the device.
./adb devices
224DDD88E8722FA848300A20B9F8XXXX device
10) run as normal user
./RunMe.sh
[IMPORTANT: if you obtain on 64bit linux machine: "/stuff/adb: error while loading shared libraries: libncurses.so.5..."
install lib32ncurses5: apt-get install lib32ncurses5 and try again]
11) select normal mode
12) wait until 5 minus
finish!
tested :good:
Dear Danjde,
I habe a Trekstor Surftab Ventos 10.1 that I would like To root.
It appears, however, hat there exist At least 2 Version oft the tablet.
In Android settings it is called ST10216-2A.
Can you confirm your Version?
Also, is it possible To root the device fron a local shell via the same commands AS in the *.SH file?
Thank you so much!
Andreas
Hi der.einstein,
I confirm that two are the ventos 10.1 versions,
mine is the second, and from my research the method shown applies to both models.
For the second question the answer is: no
ciao!