Mac OSX root Nook Color - Nook Color Android Development

Adapted from pokey9000's original instructions and the instructions of macndroid along with many others posts and just expand on some areas for the inexperienced like myself. Some was also lifted from the nookdevs site too. This was just my detailed step by step process that worked.
1. Get any sized microsd card that you don't mind trashing the data on.
2. Download pokey9000's micro sd .img files from here:
http://www.mediafire.com/?cfddu9wt9d8dunl
3. To install .img onto sd card, put micro sd card into a reader into your usb port (not sure the steps if you are just using your Nook Color to write the image onto the micro sd.
4. To write images to disk on mac osx, you need to do the following:
-Find which drive the sd card is mapped to: type in the terminal this:
diskutil list
-Now unmount that drive typing this:
diskutil unmountDisk /dev/disk<#> (My computer is was disk2)
-It should say: Unmount of all volumes on disk<#> was successful
-Type: dd if= nooter_sdcard_40mb.img of=/dev/disk<#>
-Everything needed should copy right over to the card.
3. Plug the usb cable from your NC (Nook Color) into your computer. Make sure your NC is powered on and you see the drive mounted normally.
4. Take card out of the sd reader and put it into your NC.
5. Hold down the power button for 15 seconds.
6. Let go and wait 2 seconds then hold the power button for 2 more seconds. Let go.
7. After a little bit you will get a window that says, "New network interfaces have been detected". The image is as follows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Hit Cancel.
9. Once the devices show up, wait 30 seconds and remove the card from the NC device.
10. Hold down the power button for 15 seconds again, let go, wait 2 seconds and then hold the power button for 2 more seconds, then let go again.
11. Everything should now be installed and you should be at your normal screen and your NC volume will be mounted normally.
12. Now you need to install android SDK onto you mac if you don't already have it.
13. Download it from the following site: http://developer.android.com/sdk/index.html
14. To get adb working on my terminal, I just went to the directory android-sdk-mac_x86/tools I double clicked android and it opened the terminal and seemed to install what I needed. (somebody more experienced can edit this area if there is a better way to install what is needed for the computer to run adb commands)
15. I was now able to use adb commands in the terminal.
16. For the computer to recognize my NC as a device I typed the following into the terminal:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"
17. To verify if I was now connected, I typed in: adb devices and it showed me a number for the device.
18. Now that the device is recognized, I installed an .apk file.
19. I typed:
adb install /<full directory to file>/<file name>.apk
20. I ejected the mounted disk like I normally would from finder.
21. I rebooted my nook once unplugged.
22. Check the extras area of NC and the program was now installed.
23. To remove a program first plug your NC in like normal until disk mounts
24. I first had to find out the exact name of the .apk file installed.
-Type: adb shell ls /data/app (This gives a list of all .apk files installed and their exact names)
25. Once I had the exact name I could remove the file.
-Type: adb shell rm -r /data/app/<full name of file>.apk
26. The file should now be gone. I didn't have to reboot, I just unmounted the drive and checked the extras section of the NC. It was gone. Some suggestions were to reboot to make sure the file was gone. Might be required but I didn't have to)
27. I now feel fully confident to install and uninstall .apk files as I like.
This all worked for me and everything is running smooth. It took me a few hours to get all this together as I have very little experience with this and had to seek out info for every little step. I tried to keep it as dumb as possible so people like myself would be able to do this.

Thanks for putting everyhing together. Anyway to cut the complication of uninstall apps through ADB out, I would recommend doing in through Astro File Manager. It's capable of Application Management too.

Great tutorial. I am a total noob and you have helped me successfully root my nook...so big ups. Next question I have is that there is a thread on how to install apk's without ADB. I believe it can be done simply through the browser. They have posted how to do it but not for Mac. Can someone post how to do that via OSX in a very detailed manner as done above for the root process? Thank you soooo much!

This was going great until I had to install the Android SDK. My only computer is a PPC, & apparently the SDK only works on an Intel machine.

Wow. I had no idea that it didn't work with PPC and only with Intel.

so my issue...
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"
when I type this into terminal it asks for my password
and then comes back and says that
sh: adb: command not found
sh :adb: command not found
Am I supposed to edit that command with some paths? I can't tell if I'm being daft. Thanks!

lanfearl said:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"
when I type this into terminal it asks for my password
and then comes back and says that
sh: adb: command not found
sh :adb: command not found
Am I supposed to edit that command with some paths? I can't tell if I'm being daft. Thanks!
Click to expand...
Click to collapse
You can go into the AndroidSDK/tools directory and replace "adb" with "./adb" in the commands listed. This is if you don't have the path added already which seems like what's happening.

thanks for the step by step!

scratchfury said:
You can go into the AndroidSDK/tools directory and replace "adb" with "./adb" in the commands listed. This is if you don't have the path added already which seems like what's happening.
Click to expand...
Click to collapse
I'm having the same problem. Cannot get past the ADB step (step 16 listed above).
What on earth am I doing wrong? (BTW, I'm not a terminal kind of guy, so cardboard book-type direction is appreciated)...
http://i51.tinypic.com/2vtuuxi.png

ericshmerick said:
I'm having the same problem. Cannot get past the ADB step (step 16 listed above).
What on earth am I doing wrong? (BTW, I'm not a terminal kind of guy, so cardboard book-type direction is appreciated)...
http://i51.tinypic.com/2vtuuxi.png
Click to expand...
Click to collapse
so here was my way around the adb step.
you type in the sudo sh command as normal untill you get to the adb kill-server and adb devices part.
in your finder navigate to the folder that the adb file is in. it supposed to be where ever you extracted the android sdk.
android/tools/
Instead of typing adb kill-server you are going to drag and drop the adb file it self from the finder to the terminal window. in my case it looks something like this.
/Users/<my home folder>/android/tools/adb
your path will look different depending on where in the drive you have it located.
so now step 16 is going to look something like this.
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; /Users/<my home folder>/android/tools/adb kill-server; /Users/<my home folder>/android/tools/adb devices"
so every time you use the adb command you have to link it to the path on your hard drive. i know theres a way to change directories so that you just type adb and it finds it. but im not that knowledgeable with linux. and im sure someone that is could help us out with that.

rluzania said:
so here was my way around the adb step.
you type in the sudo sh command as normal untill you get to the adb kill-server and adb devices part.
in your finder navigate to the folder that the adb file is in. it supposed to be where ever you extracted the android sdk.
android/tools/
Instead of typing adb kill-server you are going to drag and drop the adb file it self from the finder to the terminal window. in my case it looks something like this.
/Users/<my home folder>/android/tools/adb
your path will look different depending on where in the drive you have it located.
so now step 16 is going to look something like this.
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; /Users/<my home folder>/android/tools/adb kill-server; /Users/<my home folder>/android/tools/adb devices"
so every time you use the adb command you have to link it to the path on your hard drive. i know theres a way to change directories so that you just type adb and it finds it. but im not that knowledgeable with linux. and im sure someone that is could help us out with that.
Click to expand...
Click to collapse
hmmm im stuck on the same step too... it seems when i do that it doesn't respond at all. and when i type in adb devices to check whether it's connect, it won't do anything.... sry..im a total noob ~_~

i would love to help you but if nothing is coming up i have no idea where to begin. i almost want to say that maybe the sd card didnt work on the nook. but im not sure if thats it either. or do you have the android sdk app launched? i know that opens up another terminal window that when you type in to doesn't do anything. umm let me know what you find.

r8? no adb
sdk is now at r8, not sure if that has anything to do with it. But in tools folder there is no adb.

newton1666 said:
sdk is now at r8, not sure if that has anything to do with it. But in tools folder there is no adb.
Click to expand...
Click to collapse
It has been moved to a new folder named "platform-tools" instead of "tools".

scratchfury said:
It has been moved to a new folder named "platform-tools" instead of "tools".
Click to expand...
Click to collapse
Thanks for that, I feel very silly.

rluzania said:
so here was my way around the adb step.
you type in the sudo sh command as normal untill you get to the adb kill-server and adb devices part.
in your finder navigate to the folder that the adb file is in. it supposed to be where ever you extracted the android sdk.
android/tools/
Instead of typing adb kill-server you are going to drag and drop the adb file it self from the finder to the terminal window. in my case it looks something like this.
/Users/<my home folder>/android/tools/adb
your path will look different depending on where in the drive you have it located.
so now step 16 is going to look something like this.
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; /Users/<my home folder>/android/tools/adb kill-server; /Users/<my home folder>/android/tools/adb devices"
so every time you use the adb command you have to link it to the path on your hard drive. i know theres a way to change directories so that you just type adb and it finds it. but im not that knowledgeable with linux. and im sure someone that is could help us out with that.
Click to expand...
Click to collapse
I wanted to thank you for this, as I was getting frustrated changing my bash profile. Anyone else in this boat don't forget you need to drill down (cd) to where the adb is, in my case downloaded sdk just recently it's in platform-tools folder, to do the adb install.
If you just upgraded from an earlier version of the sdk and don't see adb, even in platform-tools, just run an Update All... under Installed packages. Hopes this helps others.

hey people. I really appreciate the work that has been done so far.
I'm trying to format a micro SD card with dd. Here's the problem: I was able to unmount the SD card in terminal but then it won't find the nooter disk img:
Code:
sh-3.2# diskutil unmountDisk /dev/disk1
Unmount of all volumes on disk1 was successful
sh-3.2# dd if=nooter_sdcard_40mb.img of=/dev/disk1
dd: nooter_sdcard_40mb.img: No such file or directory
what am I doing wrong? I have the file in question, and this isn't a complicated step. Thanks for any help.

plariers said:
what am I doing wrong? I have the file in question, and this isn't a complicated step. Thanks for any help.
Click to expand...
Click to collapse
My bad, figured it out. In case anyone else runs into this, in OSX you can drag and drop files into terminal to insert accurate file paths
worked perfectly

You are my hero!!!!!!!
I've been banging my head against a wall for HOURS UPON HOURS trying to get the adb to work. And you fixed me up in a few minutes. I love you so much right now. Seriously.

It lists my device # after step 16, but I can't install the packages then.
I got this far, and then when I try the command to adb install the app, I get
-bash:adb: command not found
any tips?

Related

ADB Push Nautilus Script?

Is there an ADB push nautilus script out there?
That'll be handy, but i'm no scripting expert. I suspect it'll be bit tricky since adb is terminal only, I'm sure someone will have to figure out a way to pipe the output from terminal to GUI pop up dialog box to display progress bar, with success or failure message.
this one seem to work but no progress bar or success/fail message tho. YMMV
Code:
#/bin/sh
adb push $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS /sdcard
save this as adb_push.sh
be sure to set this file with permission:
Code:
chmod a+x adb_push.sh
think of this as rough draft, not perfect. Above code will push straight to sdcard. Suppose you could create few scripts like this..
ADB - Push to System APP
Code:
#/bin/sh
adb remount
adb push $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS /system/app
ADB - Install APK
Code:
#/bin/sh
adb install $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS
EDIT: Forgot to mention this, it'll work only if you've already set path to Android's SDK tools folder in .bashrc
awesome, thanks! I'll test it in a minute
Simple scrip to push files to your android device.
Just put it in your Nautilus script dir (HOME/.gnome2/nautilus-scripts) and make it executable (chmod +x Push\ sdcard). also set path for ADB inside script (ADB=...)
I did something similar a while back for both Konqueror and Dolphin in KDE, but I realized, I just don't use a file manager since I prefer the command line instead. I had a working ADB zsh completion script, but somehow forgot to back it up before my previous hard drive failure.
https://code.google.com/p/send-to-android/
this is interesting

adb / push /pull not found help

Hi guys, I am trying to move some files into ext partition. I want to do it via adb but ...
It came to my attention that adb shell isn't the solution for adb push or adb pull. I need to do it via windows but whenever I do adb remount or adb kill-server and adb pull or adb push . When I input and press enter it shows an arrow I press enter cuz I dont know what I could input. It just tells me "push not found" or "adb not found" if I say adb push.
Please don't ask me what I do exactly just tell me the exact steps ^^
I would like to move Htc ime mod by jonasl by example.
Hope you will help me out guys
copy tools adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the .../windows/system32/
Thank's but doesn't seem to work
I tried doing : cd C:\Program Files\Android SDK
adb push C:\Program Files\Android SDK\tools\su-2.1-e-signed\system\xbin\su \system\xbin\
but this just gives me all adb commands.
Doing this inside adb shell gives me the adb : not found
Any idea/ workaround? (< only adb plz I dont want to install linux)
Code:
cd C:\Program Files\Android SDK
adb remount
adb push tools\su-2.1-e-signed\system\xbin\su \system\xbin\
Give that a try.
You can't use push or pull with shell.
The biggest problem you sill face is having spaces in the PC side path names, try moving the SDK to c:\Android_SDK if the above fails
Try this:
Code:
cd C:\Program Files\Android SDK\tools
adb remount
adb push C:\Program Files\Android SDK\tools\su-2.1-e-signed\system\xbin\su /system/xbin/
AH great, by removing the space beetwin android and sdk I managed to get out but now I am facing Out of memory error
Damn I have like 1.5 gb of memory on my ext2 partition
Where can I check the remaining memory?
EDIT : su is 22ko so I dont think memory is the big deal. However I would still like to know what is left
Maybe my microSD is dying... Any idea?
Mister-Tea said:
yy whatever, if you don't want to answer then don't but don't look high on me.
lol......
Click to expand...
Click to collapse
1/ he already answer your question
2/ it's android DEV section, your question if far away from DEV
3/ You have to learn how to use command-line application (Windows suck at this, so you should try on a linux OS)
BTW: a little how-to
cd: a great command, you'll be able to change directory (yes you have "adb" on your harddrive, but you have to tell your computer where is it)
cp : copy
mv: move
ls: list content of working directory
pwd: print current working directory
Now: let say "adb" (adb.exe) is located here: /home/carbonyle/androidSDK/tools/
launch a terminal (WindowsKey + r on windows host, then type "cmd")
Yyour working directory maybe "C:" , or whatever (/home/carbonye/ for me)
now use "cd"
Code:
cd /home/carbonyle/androidSDK/tools/
<. of course adapt this to your environnment
(use ls / pwd to convince you what you're doing)
Code:
./adb reboot recovery
<- for linux user
Code:
adb reboot recovery
<- for Win**** users
Of course this will reboot your phone into recovery mode, just adapt command to your need
Right, this thread has gone far enough with enough flaming for today.
To all of you, im disappointed and you should all know better.
PLease refrain from further flames, tidy up in progress. I am also moving this to QnA.
@ Mister-Tea
You are equally responsible for the flaming by flaming yourself.
@ you all, quit it or i will take further action.
THanks.

[HOWTO] Archos Gen8 2.0.71 ADB in Ubuntu 10.10

I've been struggling with this for about six hours. Now, I have finally worked out a solution.
Hopefully it works for you. I will do my best to tell you exactly what I did so that if you don't entirely understand how to do stuff (for lack of a better phrase) in Linux, you can get this working.
Step 1: Go download the android SDK
http://developer.android.com/sdk/index.html
When it is done downloading, unzip the file into your home directory. Make sure to rename the folder androidsdk
Open up the newly unzipped folder and go into the tools directory. run the android shell script.
NOTE: WHEREVER IT SAYS "androidsdk" AS A DIRECTORY IN THIS GUIDE, YOU WILL HAVE TO REPLACE THAT WITH WHATEVER YOU NAME THE FOLDER. (I would suggest just naming it androidsdk)
Go to "available packages" and select all of the boxes. Once they are all selected, click on "Install" in the bottom right corner.
Go grab a cup of hot chocolate. That is an order.
Go into the platform-tools directory in the sdk directory (androidsdk) and right click on adb. Go to "properties" then the "permissions" tab and make sure the box that reads "allow executing file as program" is checked.
Go to the "open with" tab and add "autorun prompt."
Step 2: Get your paths in order
Go to your home folder and hit ctrl H to show all of the hidden folders and files.
Find bashrc and open it with the text editor. Copy and paste the following text at the very top.
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
Open up your terminal and type:
export PATH=$PATH:/androidsdk/tools
gksudo gedit /etc/udev/rules.d/51-android.rules
#When it opens up the file 51-android.rules, copy and paste this into it, then save the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Plug in your Archos Gen8 Tablet via USB.
https://dl-web.dropbox.com/get/AndroidFiles/LINUX_SDK_ADB_INSTALLER.zip?w=b4bd354e&dl=1
(The credit is in the code)
Download that and extract the zip to your home directory.
Go to the home directory and run the LINUX_SDK_ADB_INSTALLER shell script
It will download and install the drivers for ADB.
Step 3: Nautilus-ize it
Open up another terminal and type in:
sudo nautilus
(If you don't have nautilus like i didn't, just type in: sudo apt-get install nautilus)
once a window pops open that says "root", go ahead and navigate back to the filesystem (one folder up)
navigate to /usr/local/androidsdk/tools and make sure that adb is still an executable and is set to open with the "autorun prompt" (like in step 2)
close the window that nautilus opened up and shut down the terminal to end the root session.
Step 4: Finishing touches.
Go to the .Android directory in Home (it is hidden, you will have to put ctrl H to make it show) and find a file called adb_usb.ini ( if there isn't one, then you just have to create a text file and save it as adb_usb.ini )
Copy and paste
"0x0e79" >> ~/.android/adb_usb.ini
Into the adb_usb.ini file
Step 5: Run ADB.
Open up a terminal and type:
cd /usr/local/androidsdk/tools/
Type:
echo "0x0e79" >~/.android/adb_usb.ini
./adb kill-server
./adb start-server
type in ./adb devices
your Gen8 Tab should show up now as A70-3FAXXXXX-XXXXX-XXXXX device (the X's are your serial number. Don't freak out if you don't get a bunch of X's)
you can now run all of the adb commands by typing:
./adb kill-server
./adb reboot
./adb etc... etc...
(Those are examples. you dont have to actually type them in)
Voila. You are now all connected via ADB.
If you have any questions or something isn't working, we can troubleshoot in the comments.
I hope i was able to help those using Ubuntu 10.10 that need ADB.
(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)
~ClothoBuer6293
~PokeJake2002
I get error 403 when i try to download the file.
http://forum.xda-developers.com/attachment.php?attachmentid=448536&d=1290585848
There. That is the link to the original location of the file.
I guess i need to work on making dropbox links.
There's a couple of things wrong, since it's mixing terminal commands with doing things entirely via the GUI (Step 4 more precisely). It also seems it's mixing guides from different sources, there's a couple of redundant steps. I don't think you've done these steps as they stand, they wouldn't have worked
This is my suggestion:
Step 1. Download SDK and extract it
Step 2. Run android shell script in extracted_folder/tools (just double click and choose run in Ubuntu). If you just want adb then it's sufficient to mark only "Android SDK Platform-tools revision 1" for installation. The adb executable ends up in extracted_folder/platform-tools, and already has the exacutable bit set.
Step 3. For the device to show up with adb you need to do the udev step above, that is:
gksudo gedit /etc/udev/rules.d/51-android.rules (in a terminal) and paste this in the file
Code:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
In the same terminal, enter
gedit ~/.android/adb_usb.ini
and paste this in the file (or add at the bottom, if you already have it)
Code:
0x0e79
Step 4. Enable USB Debugging on the Archos (Settings -> Applications -> Development) and connect it to the computer
Step 5. Navigate to extracted_folder/platform_tools and run
./adb devices
(if nothing shows up, run ./adb kill-server followed by ./adb start-server and then ./adb devices again)
So what needs to be fixed in the guide is:
* the redundant step of downloading adb separately
* step 4 is really messed up, it's pasting terminal commands in the adb_usb.ini file and if it worked for you, it's because after pasting the terminal command you actually in Step 5 also echo the vendor ID to the end of file. Also, step 4 uses relative paths (./) to the adb executable, which indicates that the path step hasn't been done. Actually, come to think of it you get "no such file or directory" error if you enter ./adb if you don't happen to be in the right directory, so adding the adb folder to PATH isn't going to help.
Personally, I think the path step can be skipped altogether, but if people really want to be able to enter the adb command when they open a terminal window they should make sure the put the folder somewhere they plan to keep it. The best thing is for people to know how the basic terminal command works, as that is what they are using for adb anyway.
Thanks. This is pretty much my first walkthrough so i appreciate your assistance.
Sent from my A70S using Tapatalk
It's a good first attempt, you're detailed in your steps which is good. One thing which is nice though, is describing why something is done too, for example the case with adding the udev rule etc. Speaking of that, thanks a bunch for the info on that, wouldn't have gotten my Archos to show up without it
Thanks. Haha.
I was really confused and I think most of what I did to get it to work was on accident.
I just didnt see any particular howtos on getting ADB for Archos Gen8 working in Ubuntu so I thought I would type one up based on how I got it to work and hope that smarter developers would correct me and help me to polish it.
The only way I have been able to connect to the Archos is to run as "root". Is this the purpose of the "nautilus" instruction? I thought the MODE="0666" would make the device accessible to all users. If I try this as a normal user, the device appears with "no permissions".
How do you fix this?
pokejake2002 said:
I've been struggling with this for about six hours. Now, I have finally worked out a solution.
Hopefully it works for you. I will do my best to tell you exactly what I did so that if you don't entirely understand how to do stuff (for lack of a better phrase) in Linux, you can get this working.
Step 1: Go download the android SDK
http://developer.android.com/sdk/index.html
When it is done downloading, unzip the file into your home directory. Make sure to rename the folder androidsdk
Open up the newly unzipped folder and go into the tools directory. run the android shell script.
NOTE: WHEREVER IT SAYS "androidsdk" AS A DIRECTORY IN THIS GUIDE, YOU WILL HAVE TO REPLACE THAT WITH WHATEVER YOU NAME THE FOLDER. (I would suggest just naming it androidsdk)
Go to "available packages" and select all of the boxes. Once they are all selected, click on "Install" in the bottom right corner.
Go grab a cup of hot chocolate. That is an order.
Go into the platform-tools directory in the sdk directory (androidsdk) and right click on adb. Go to "properties" then the "permissions" tab and make sure the box that reads "allow executing file as program" is checked.
Go to the "open with" tab and add "autorun prompt."
Step 2: Get your paths in order
Go to your home folder and hit ctrl H to show all of the hidden folders and files.
Find bashrc and open it with the text editor. Copy and paste the following text at the very top.
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
Open up your terminal and type:
export PATH=$PATH:/androidsdk/tools
gksudo gedit /etc/udev/rules.d/51-android.rules
#When it opens up the file 51-android.rules, copy and paste this into it, then save the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Plug in your Archos Gen8 Tablet via USB.
https://dl-web.dropbox.com/get/AndroidFiles/LINUX_SDK_ADB_INSTALLER.zip?w=b4bd354e&dl=1
(The credit is in the code)
Download that and extract the zip to your home directory.
Go to the home directory and run the LINUX_SDK_ADB_INSTALLER shell script
It will download and install the drivers for ADB.
Step 3: Nautilus-ize it
Open up another terminal and type in:
sudo nautilus
(If you don't have nautilus like i didn't, just type in: sudo apt-get install nautilus)
once a window pops open that says "root", go ahead and navigate back to the filesystem (one folder up)
navigate to /usr/local/androidsdk/tools and make sure that adb is still an executable and is set to open with the "autorun prompt" (like in step 2)
close the window that nautilus opened up and shut down the terminal to end the root session.
Step 4: Finishing touches.
Go to the .Android directory in Home (it is hidden, you will have to put ctrl H to make it show) and find a file called adb_usb.ini ( if there isn't one, then you just have to create a text file and save it as adb_usb.ini )
Copy and paste
"0x0e79" >> ~/.android/adb_usb.ini
Into the adb_usb.ini file
Step 5: Run ADB.
Open up a terminal and type:
cd /usr/local/androidsdk/tools/
Type:
echo "0x0e79" >~/.android/adb_usb.ini
./adb kill-server
./adb start-server
type in ./adb devices
your Gen8 Tab should show up now as A70-3FAXXXXX-XXXXX-XXXXX device (the X's are your serial number. Don't freak out if you don't get a bunch of X's)
you can now run all of the adb commands by typing:
./adb kill-server
./adb reboot
./adb etc... etc...
(Those are examples. you dont have to actually type them in)
Voila. You are now all connected via ADB.
If you have any questions or something isn't working, we can troubleshoot in the comments.
I hope i was able to help those using Ubuntu 10.10 that need ADB.
(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)
~ClothoBuer6293
~PokeJake2002
Click to expand...
Click to collapse
I thought the instructions from Archos were pretty clear. I've never had an issue with ADB in Linux.
Code:
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
foh1981 said:
There's a couple of things wrong, since it's mixing terminal commands with doing things entirely via the GUI (Step 4 more precisely). It also seems it's mixing guides from different sources, there's a couple of redundant steps. I don't think you've done these steps as they stand, they wouldn't have worked
This is my suggestion:
Step 1. Download SDK and extract it
Step 2. Run android shell script in extracted_folder/tools (just double click and choose run in Ubuntu). If you just want adb then it's sufficient to mark only "Android SDK Platform-tools revision 1" for installation. The adb executable ends up in extracted_folder/platform-tools, and already has the exacutable bit set.
Step 3. For the device to show up with adb you need to do the udev step above, that is:
gksudo gedit /etc/udev/rules.d/51-android.rules (in a terminal) and paste this in the file
Code:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
In the same terminal, enter
gedit ~/.android/adb_usb.ini
and paste this in the file (or add at the bottom, if you already have it)
Code:
0x0e79
Step 4. Enable USB Debugging on the Archos (Settings -> Applications -> Development) and connect it to the computer
Step 5. Navigate to extracted_folder/platform_tools and run
./adb devices
(if nothing shows up, run ./adb kill-server followed by ./adb start-server and then ./adb devices again)
So what needs to be fixed in the guide is:
* the redundant step of downloading adb separately
* step 4 is really messed up, it's pasting terminal commands in the adb_usb.ini file and if it worked for you, it's because after pasting the terminal command you actually in Step 5 also echo the vendor ID to the end of file. Also, step 4 uses relative paths (./) to the adb executable, which indicates that the path step hasn't been done. Actually, come to think of it you get "no such file or directory" error if you enter ./adb if you don't happen to be in the right directory, so adding the adb folder to PATH isn't going to help.
Personally, I think the path step can be skipped altogether, but if people really want to be able to enter the adb command when they open a terminal window they should make sure the put the folder somewhere they plan to keep it. The best thing is for people to know how the basic terminal command works, as that is what they are using for adb anyway.
Click to expand...
Click to collapse
It's important to ad ADB to your PATH. Many aapt tools and the like use it. And you can't just put ADB in every directory you want to work in. I do framework stuff in a framework folder, os stuff in others, etc. I'm not going to use the full path every time I type.
pokejake2002:
All that is really needed in this tutorial is "Download the SDK, extract, run ./tools/android and download the ADB driver. Add vendor id to .android/adb_usb.ini, then create udev rule /etc/udev/rules.d/51-android.rules. Add export PATH=$PATHdownloaded directory)/android-sdk/platform-tools to bash.rc"
That's it. I'm not sure what all that extra stuff is. You've done almost every step twice, and some are incorrect, such as the export path, you did it twice, and the actual path should be platform-tools, not just tools, and you echoed the vendor ID twice as well.
Also, nautilus is included by default in ubuntu > 7.0, so i'm not sure how it wasn't installed on 10.10.
Also, all the "./adb" lines should just be "adb" if you exported the path correctly, which like i said, is supposed to be platform-tools, not just tools.
Just FYI, not trying to flame, I can tell you don't have much experience, it's not a bad thing. But also, "(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)" I don't know any developers who haven't had adb working from day one.

USB transfer workaround

For the past couple of days I have issues with transferring files over usb as no support is built into to the ics kernel for the usb transfer unless a physical sdcard is detected. I tried the mtp, thing and for some reason that wont show the files. Here is what I found that works best for transferring files rather than installing sketchy Chinese programs.
Note all commands are in quotes, do not type the quotes
Setting up and checking files in directories​
1. Install androidsdk
2. open a command prompt and cd to where your adb tools are. They are typically in C:\android-sdk-windows\platform-tools
3. "cd C:\android-sdk-windows\platform-tools" after you download the pack through the platform tools pack through the sdk manager. Yours may be in a different place depending on install. If you have set the system variable for adb skip to step 4.
4. Set your touchpad to go into android debugging mode when plugged in, under developers options
5. Type in "adb devices" to make sure your touchpad is seen by computer
6. Now access your devices by typing "adb shell" (if you have the ghost emulator 5554, use adb -d shell)
7. From there type "cd /sdcard/"
8. Type "ls" to receive a list of all files on your touchpad (note l is an L)
9. From there simply use the cd command to get in and out of directories
Transferring Files​
When you want to transfer files to and from the touchpad, open a new command prompt and get back to the location with your adb files.
To copy to touchpad
Use the adb push command, example of adb push:
"adb push C:\users\stephen\downloads\example.apk /sdcard/"
The format is adb push local directory to remote directory.
To pull from touchpad
To pull something from your touchpad use adb pull command. The format is adb pull remote directory to local directory.
Example: "adb pull /sdcard/getjar.apk c:\users\stephen\desktop"
I installed DroidSSHd for root GUI. and for GUI file transfer/install I use AirDriod.
edit: course, all this is done on the air.

[Solved] How to adb pull to any other directory than platform-tools?

Hi there,
The device is rooted.
I tried
Code:
adb pull /dev/block/mmcblk0p43 > /users/wenyuan/desktop/android/43.img
(mmcblk0p43 is userdata partition).
But the command was just stuck there and did not produce any results.
Would it be possible to adb pull partition (ex. userdata) to any other location than under platform-tools directory?
Would it be possible to adb pull partition even to an external disk?
Thanks.
-- Solution for internal disk--
The right code:
Code:
adb pull /dev/block/mmcblk0p43 /users/wenyuan/desktop/android/43.img
Remove ">"
do not use ">" in the command
CXZa said:
do not use ">" in the command
Click to expand...
Click to collapse
Thanks. It worked.
But would it be possible to adb pull a partition to an external disk?
I tried
Code:
adb pull /dev/block/mmcblk0p43 /Untitled/wenyuan/43.img
Untitled being the name of the external hard disk.
It did not work.
it works like this. maybe the external hard disk is not ready. also take care of fat32 file system only accept files < 4gb
if "Untitled" contains whitespaces you must quote path
aIecxs said:
it works like this. maybe the external hard disk is not ready. also take care of fat32 file system only accept files < 4gb
if "Untitled" contains whitespaces you must quote path
Click to expand...
Click to collapse
Given that,
1. in
adb pull /dev/block/mmcblk0p43 /users/wenyuan/desktop/android/43.img,
/users is under Macintosh HD; and
2. "Untitled", as an external hard disk, has the same status as Macintosh HD,
there should be some code indicating the location to "Untitied" hard disk, (ex. cd).
I tried
Code:
adb pull /dev/block/mmcblk0p43 cd /untitled/android/43.img
and it did not work.
type 'adb help' for usage
Code:
device commands:
adb push <local>... <remote>
- copy files/dirs to device
adb pull [-a] <remote>... <local>
- copy files/dirs from device
(-a preserves file timestamp and mode)
cd is cmd to change dir (unrelated to adb), don't invent fantasy usage.
btw "it did not work" is no meaningful error message. I am pretty sure the shell replied with something you can google for...
CXZa said:
do not use ">" in the command
Click to expand...
Click to collapse
Am I right in saying that
">" can not be used in "adb pull" but should be used in "adb shell su" and "adb exec-out", in case of pulling partitions? Or in any other circumstances?
Oh no, adb help and google search were no help.
https://bash.cyberciti.biz/guide/Standard_output
https://www.cyberciti.biz/faq/redirecting-stderr-to-stdout
aIecxs said:
https://bash.cyberciti.biz/guide/Standard_output
https://www.cyberciti.biz/faq/redirecting-stderr-to-stdout
Click to expand...
Click to collapse
Thanks for the links.
But I meant adb help and Google search did not help on how to adb pull device partition directly to an external disk.
refer to post #6
there is only one exact usage for adb pull
Code:
adb pull [-a] <remote>... <local>
where <local> is valid path to any directory on PC (whatever it is)
in case the command failed it will output meaningful error message. search for that error message (or post here)
what else do you expect to know?

Categories

Resources