This is mainly for the users of my animations who were asking! - Have fun guys!
If you are rooted:
1. Download a root explorer app (ES File Explorer is suggested and free)
2. Enable root directory (in ES File Explorer hit menu, go to settings, and check "Up to Root", then go farther down and check "Root Explorer". Accept any Superuser requests.
3. Go back to your explorer and navigate to where you downloaded the "bootanimation.zip" file. Copy (or cut) it.
4. Navigate as far up as you can into your root directory, and then to /data/local/
5. Paste your "bootanimation.zip" file into /data/local/ (it MUST be named bootanimation.zip)
6. Reboot and enjoy!
Alternatively, you can put it in /system/media, HOWEVER, make sure you back up your stock bootanimation.zip (rename it to bootanimation.zip.bak or move it to your sdcard somewhere) in case something goes wrong.
If you are not rooted (or rooted, this method works with both)
**PC only! I'm not sure how to set the Max OSX terminal to accept "adb" commands by default!**
Setup:
1. Download the newest Android SDK
2. Click the start menu, right click "Computer", and click "Properties"
3. Click "Advanced System Settings" on the left (On Win7)
4. In the advanced tab, click "Environment Variables"
5. In the system variables window, find "Path", select it and click "edit"
6. At the end of the bottom line, paste:
For 64-bit users:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
For 32-bit users:
Code:
;C:\Program Files\Android\android-sdk\platform-tools
7. Click OK.
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device)
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe"
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code:
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
4. Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
NOTE: Alternatively for part 2 you can type "adb push ", open windows explorer, and drag the file infront of the command which will give you the path without having to type it in or navigate to it.
5. Be patient, when it is done it will say something like "X kb/s (X bytes) in X seconds"
6. You can test to see if you did it correctly by rebooting manually or entering
Code:
adb reboot
7. If you no longer want a custom bootanimation, just enter
Code:
adb pull /data/local/bootanimation.zip C:\
Remember to look in your main HDD directory and delete the bootanimation.zip file if it in fact did show up there for some reason.
Note: if it STILL does not revert to the stock boot animation after doing this step, type
Code:
adb shell
cd /data/local
rm bootanimation.zip
**If you have adb problems or questions, I'm not the one to ask, Google is
Thank you for thanking me!
I was completely unaware you could change your boot animation unrooted, thanks
Sent from my Transformer Prime TF201 using Tapatalk 2 Beta-5
Thanks for this.
I thought it could not be done without a un-rooted Prime.
Thanks for this! Wasn't planning on rooting my Prime just yet and it's great that I can change the boot animation!
If you do copy a bootanimation.zip to the data/local directory do you have to do anything to the Original bootanimation.zip in the system/media Directory?
Sent from my Transformer Prime TF201 using Tapatalk
RonH54 said:
If you do copy a bootanimation.zip to the data/local directory do you have to do anything to the Original bootanimation.zip in the system/media Directory?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Nope! It stays there safe and sound and will start playing again as soon as you remove the one from /data/local!
Nolam20 said:
Nope! It stays there safe and sound and will start playing again as soon as you remove the one from /data/local!
Click to expand...
Click to collapse
Thanks. I had always just renamed my bootanimation.zip file and copied new one to the system/media directory but with these Bigger File size bootanimation.zip I was getting error that there not enough room to copy some of these bootanimation.zip files to the system/media directory.
Thanks
lovit
Awesome Workaround, but I have a little problem
I'm trying to get this working, but when I type in the commands in cmd, it says the adb is not recognized as a command. Help?
theManchur said:
I'm trying to get this working, but when I type in the commands in cmd, it says the adb is not recognized as a command. Help?
Click to expand...
Click to collapse
Make sure you've correctly done steps 3-7 of setup, otherwise cmd.exe will not know what to do with adb commands.
i always put my bootanimations in system/media and make sure your permissions are set like this
Uploaded with ImageShack.us
blaxican25 said:
i always put my bootanimations in system/media and make sure your permissions are set like this
Uploaded with ImageShack.us
Click to expand...
Click to collapse
His problem appears to be something different.
Can't get past the CMD command section. more detail help for us no bodies
Nolam20 said:
This is mainly for the users of my animations who were asking! - Have fun guys!
If you are rooted:
1. Download a root explorer app (ES File Explorer is suggested and free)
2. Enable root directory (in ES File Explorer hit menu, go to settings, and check "Up to Root", then go farther down and check "Root Explorer". Accept any Superuser requests.
3. Go back to your explorer and navigate to where you downloaded the "bootanimation.zip" file. Copy (or cut) it.
4. Navigate as far up as you can into your root directory, and then to /data/local/
5. Paste your "bootanimation.zip" file into /data/local/ (it MUST be named bootanimation.zip)
6. Reboot and enjoy!
Alternatively, you can put it in /system/media, HOWEVER, make sure you back up your stock bootanimation.zip (rename it to bootanimation.zip.bak or move it to your sdcard somewhere) in case something goes wrong.
If you are not rooted (or rooted, this method works with both)
**PC only! I'm not sure how to set the Max OSX terminal to accept "adb" commands by default!**
Setup:
1. Download the newest Android SDK
2. Click the start menu, right click "Computer", and click "Properties"
3. Click "Advanced System Settings" on the left (On Win7)
4. In the advanced tab, click "Environment Variables"
5. In the system variables window, find "Path", select it and click "edit"
6. At the end of the bottom line, paste:
For 64-bit users:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
For 32-bit users:
Code:
;C:\Program Files\Android\android-sdk\platform-tools
7. Click OK.
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device)
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe"
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code:
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
4. Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
NOTE: Alternatively for part 2 you can type "adb push ", open windows explorer, and drag the file infront of the command which will give you the path without having to type it in or navigate to it.
5. Be patient, when it is done it will say something like "X kb/s (X bytes) in X seconds"
6. You can test to see if you did it correctly by rebooting manually or entering
Code:
adb reboot
7. If you no longer want a custom bootanimation, just enter
Code:
adb pull /data/local/bootanimation.zip C:\
Remember to look in your main HDD directory and delete the bootanimation.zip file if it in fact did show up there for some reason.
Note: if it STILL does not revert to the stock boot animation after doing this step, type
Code:
adb shell
cd /data/local
rm bootanimation.zip
**If you have adb problems or questions, I'm not the one to ask, Google is
Thank you for thanking me!
Click to expand...
Click to collapse
riorancho said:
Can't get past the CMD command section. more detail help for us no bodies
Click to expand...
Click to collapse
What specifically are you having trouble with?
Section 7 and down. I am not that dos smart to understand what you substitute in the cmd screen and I don't even know if my zip file is correct. I had it on my desktop then in c: adk\tool folder but I can't get any further than completing line 6 set up. Compressed with no compression using winzip.
And I really don't know if my txt file is correct?? My image size is 960 x 540
Using a Razr Maxx. site won't let me download the win zip file
Nolam20 said:
What specifically are you having trouble with?
Click to expand...
Click to collapse
riorancho said:
Section 7 and down. I am not that dos smart to understand what you substitute in the cmd screen and I don't even know if my zip file is correct. I had it on my desktop then in c: adk\tool folder but I can't get any further than completing line 6 set up. Compressed with no compression using winzip.
And I really don't know if my txt file is correct?? My image size is 960 x 540
Using a Razr Maxx. site won't let me download the win zip file
Click to expand...
Click to collapse
I'm not really sure how exactly I can help you, I'd go over the guide a few more times and google your problem.
I need specific problems like errors or what you don't understand.
Also, I don't know the size for a Droid Razr, but you can probably find it via a quick search.
I get lost here
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device) OK
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe" OK
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code: LOST RIGHT HERE WITH THE PROPER COMMAND
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
what command do I put in in cmd at this point?
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
and then:
Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
what is this command above??
Where do I save my boot zip file to??
Nolam20 said:
I'm not really sure how exactly I can help you, I'd go over the guide a few more times and google your problem.
I need specific problems like errors or what you don't understand.
Also, I don't know the size for a Droid Razr, but you can probably find it via a quick search.
Click to expand...
Click to collapse
riorancho said:
I get lost here
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device) OK
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe" OK
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code: LOST RIGHT HERE WITH THE PROPER COMMAND
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
what command do I put in in cmd at this point?
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
and then:
Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
what is this command above??
Where do I save my boot zip file to??
Click to expand...
Click to collapse
Ok, so, for example, if your file is in user/Fred/Documents and named bootanimation.zip, then you need to type:
Code:
cd users
then
Code:
cd Fred
then
Code:
documents
then type
Code:
adb pull /data/local/bootanimation.zip
Then
Code:
adb push bootanimation.zip /data/local
part of the problem may be that I have a mac and use windows under parellas so the files are not the same
in c: Users\DT\Documents DOCUMENTS IS WHERE ZIP FILE IS LOCATED
get error message: "adb" is not reconized as an internal or external command operabtle program or batch file
Nolam20 said:
Ok, so, for example, if your file is in user/Fred/Documents and named bootanimation.zip, then you need to type:
Code:
cd users
then
Code:
cd Fred
then
Code:
documents
then type
Code:
adb pull /data/local/bootanimation.zip
Then
Code:
adb push bootanimation.zip /data/local
Click to expand...
Click to collapse
riorancho said:
part of the problem may be that I have a mac and use windows under parellas so the files are not the same
in c: Users\DT\Documents DOCUMENTS IS WHERE ZIP FILE IS LOCATED
get error message: "adb" is not reconized as an internal or external command operabtle program or batch file
Click to expand...
Click to collapse
Then you didn't follow steps 2-7 correctly.
2. Click the start menu, right click "Computer", and click "Properties"
3. Click "Advanced System Settings" on the left (On Win7)
4. In the advanced tab, click "Environment Variables"
5. In the system variables window, find "Path", select it and click "edit"
6. At the end of the bottom line, paste:
For 64-bit users:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
For 32-bit users:
Code:
;C:\Program Files\Android\android-sdk\platform-tools
7. Click OK.
This guide is for windows, if you're having problems getting it to work on Mac or a virtual Windows machine, I'm sorry but I can't help you.
Related
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.
Hi guys,
I take no credit for this, as this method was already described in this forum:
http://forum.androidcentral.com/bar...ow-download-install-honeycomb-nook-color.html
The only thing I did was apply this to regular APK installs and they've been working well thus far.
Here's what you do (windows users):
1. Make sure the NC has ADB access, check the Honeycomb thread for more on this
2. Have the APK you want to install readily available.
3. Open a command prompt, Start -> Run -> "CMD" (No quotations) (Make sure you're admin when doing this)
4. cd into your android-sdk file by typing in the file directory, mine looks like this:
cd..
cd..
cd android-sdk\tools
Click to expand...
Click to collapse
This is because my android-sdk is in C:\android-sdk
5. Now type in the following commands:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push [YOUR APK HERE] /system/app
Click to expand...
Click to collapse
Where [YOUR APK HERE] is the file name of the APK you want to install. I've found the easiest way to do this is to type in "adb push" then drag and drop the file into the command prompt for easy access.
6. Finally, type in
adb reboot
Click to expand...
Click to collapse
7. Enjoy your APKs! I can't guarantee how well they'll work, so far Pulse reader is working well for me
I also have to point out, that for many apps, the "adb install "program.apk" works well - its how i installed my copy of quadrant and dolphin HD.
Divine_Madcat said:
I also have to point out, that for many apps, the "adb install "program.apk" works well - its how i installed my copy of quadrant and dolphin HD.
Click to expand...
Click to collapse
This is true, for that all you have to do is:
adb install [YOUR APK HERE]
Click to expand...
Click to collapse
Thanks, Divine_Medcat!
newer versions of the SDK moved the adb to /platform-tools/ folder
Where are the APKs on the NC to pull them from?
nm: read the post more thoroughly. It's /system/app
This requires root and ADB knowledge. The method will work for any boot animation, reference Xoom forums for additional resources.
I'm not responsible if you brick your Galaxy Tab 10.1!!!!! This has only been tested on a USA White 16GB Galaxy Tab 10.1
ADB METHOD:
Code:
Download bootanimation.zip from the bottom of the post, and copy it to your directory where adb.exe is located. The included boot animation is a stock honeycomb from the Xoom animation.
adb push bootanimation.zip /sdcard/bootanimation.zip
Next, get into ADB shell and mount system as writeable:
adb shell
mount -o remount,rw /dev/block/mmcblk0p4
Here is where it gets funny, in order to make the bootanimation.zip play correctly you will need to rename the program which calls the default animation to "playsoundBACKUP" and then copy/rename bootanimation to playsound. MAKE SURE YOU BACKUP JUST AS I TELL YOU TO:
cd /system/bin
mv playsound playsoundBACKUP
cp bootanimation playsound
Okay, now all that is left is to copy the bootanimation.zip to the proper directory:
mv /sdcard/bootanimation.zip /system/media/bootanimation.zip
ROOT EXPLORER METHOD, thanks Berner:
Code:
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
TO REVERT:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p4
cd /system/bin
rm playsound
mv playsoundBACKUP playsound
cd ../media
rm bootanimation.zip
Go ahead and reboot your tablet, and enjoy the boot animation. There are literally hundreds of animations available, and if you search through the Xoom forum you can download whichever.
Edit: Attached are the two files which are being manipulated, for those who accidentally delete playsoundBAK and want to revert. Note, "playsound" is the actual modified file where playsoundBAK is the original stock file.
Also too, the following animation is unbelievably awesome:
http://youtu.be/TxQ1DZHi1OA
download here : http://www.mediafire.com/?6aen7nlgelzgu6j
thanks for this ... fun to play with ...any link/intro to the animation file (video) format ? just curious if ican make one of my own ..
Sent from my SHW-M110S using XDA App
Instructions work fine. ADB not required -- everything can be done with Root Explorer. Thanks for the post.
Thanks for this, mang I've been dying to mod my boot screen!
it says failed cross device link...
actually i got it but i accidently delete the playsound can you hook me up with yours?
its weird, i still get the samsung bootloader........sits for a good minute then for like 5 seconds the stock honeycomb comes up and plays then lockscreen shows up. should the samsung screen be up that long if at all?
Riztnack said:
its weird, i still get the samsung bootloader........sits for a good minute then for like 5 seconds the stock honeycomb comes up and plays then lockscreen shows up. should the samsung screen be up that long if at all?
Click to expand...
Click to collapse
Please run these commands and post the file as an attachment in your reply:
Open up windows command prompt, navigate to the directory which contains adb.exe,
adb shell
cd /
echo system.media >> /sdcard/LOG/BootAnimation.txt
ls /system/media > /sdcard/LOG/BootAnimation.txt
echo system.bin > /sdcard/LOG/BootAnimation.txt
ls /system/bin > /sdcard/LOG/BootAnimation.txt
G1_enthusiast said:
it says failed cross device link...
Click to expand...
Click to collapse
Where does it say this? Please post some type of screen shot and method to reproduce. What operating system are you using, what folder are you located in when you're executing adb.exe, what Galaxy Tab are you using?
G1_enthusiast said:
actually i got it but i accidently delete the playsound can you hook me up with yours?
Click to expand...
Click to collapse
I've attached it to the OP, both playsoundBAK (original file, which executes stock boot animation) and playsound (modified file). Please be careful in the future to make a backup
anyway to get rid of the samsung begining? it still show up but after that it show your custom booot animation
Berner said:
Instructions work fine. ADB not required -- everything can be done with Root Explorer. Thanks for the post.
Click to expand...
Click to collapse
Hey man, if i'm doing this with root explorer what do i do with the playsoundBACKUP file in the /system/bin folder? His adb commands arent very clear if using root explorer. Also what do i do with the copied bootanimation playsound? Any help would be greatly appreciated.
wesbalmer said:
Please run these commands and post the file as an attachment in your reply:
Open up windows command prompt, navigate to the directory which contains adb.exe,
adb shell
cd /
echo system.media >> /sdcard/LOG/BootAnimation.txt
ls /system/media > /sdcard/LOG/BootAnimation.txt
echo system.bin > /sdcard/LOG/BootAnimation.txt
ls /system/bin > /sdcard/LOG/BootAnimation.txt
Where does it say this? Please post some type of screen shot and method to reproduce. What operating system are you using, what folder are you located in when you're executing adb.exe, what Galaxy Tab are you using?
I've attached it to the OP, both playsoundBAK (original file, which executes stock boot animation) and playsound (modified file). Please be careful in the future to make a backup
Click to expand...
Click to collapse
http://img.photobucket.com/albums/v643/Riztnack/1.jpg
I am using windows 7
jman391 said:
Hey man, if i'm doing this with root explorer what do i do with the playsoundBACKUP file in the /system/bin folder? His adb commands arent very clear if using root explorer. Also what do i do with the copied bootanimation playsound? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
G1_enthusiast said:
anyway to get rid of the samsung begining? it still show up but after that it show your custom booot animation
Click to expand...
Click to collapse
What do you mean? The initial Samsung Logo
Berner said:
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse
Thanks bro, I've never used Root Explorer. I'll add this to the OP.
Riztnack said:
http://img.photobucket.com/albums/v643/Riztnack/1.jpg
I am using windows 7
Click to expand...
Click to collapse
Very strange. I've never seen that error on any of the 30+ Android devices I've rooted.
Please confirm, are you on a 10.1 or 10.1v (as I really don't know the differences yet).
Please try the following:
adb shell mount -o remount,rw /dev/block/mmcblk0p4
adb push bootanimation.zip /system/media/bootanimation.zip
Berner said:
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse
Very cool man! Thanks for putting it in laymen's terms for dummies like me.
I don't know what I'm doing wrong but I can't get it o work. I've changed the files and copied the bootanimation.zip to /system/media. The original is gone however the bootanimation is just the default android boot. The one with "android" (i.e the animation we get when using the android emulator)
EDIT: Got it to work, just needed to set the permissions.
[X][X][X]
[X][O][X]
[X][O][X]
I would also like to know if there is a way to remove the initial samsung animation the one where the sound used to play. Since the new animation plays afterwards where the bland samsung logo used to play.
Same here......
I also get the original 'blue circling-Samsung' followed by the white 'SAMSUNG' letters on my screen...Then only do I see the HC bootanimation.
Also - only after I set the permissions to 755 - maybe you should include this in your OP ?
Thanks anyway!
bert269 said:
I also get the original 'blue circling-Samsung' followed by the white 'SAMSUNG' letters on my screen...Then only do I see the HC bootanimation.
Click to expand...
Click to collapse
I renamed the bootsamsung.qmg file to bootsamsung.backup and that seemed to get rid of it, but the custom animation still only shows for the few seconds when the tablet buzzes before the lockscreen comes up.
I viewed the zip file and that is not the one that plays I set permissions but still no honeycomb boot animation! any ideas? will this work on custom rom?
step 4,5,6
use rootexplerer but somehow lose in step 4,5,6 thanks
my ADB will not work at all in command prompt i get this message 'adb' is not recognized as an internal or external command,
operable program or batch file.
thats what i get when i enter adb devices in the command prompt whether i have a device plugged in or not
I'm assuming that since you're asking about adb, you already have the Android SDK installed (or) you have a folder that you downloaded from somewhere with adb.exe, fastboot.exe and some other exe's in it. The reason you're getting that message is because your computer doesn't know where to look for adb.exe, unless you open command prompt in the folder itself. To be able to use the command universally in cmd, you need to add it to the Windows PATH system variable.
1. Control Panel->Search 'environment variables'->Click on 'Edit the system environment variables' with the administrator icon.
2. Click on 'Environment Variables' at the bottom, find Path (or) PATH under 'System variables', and click Edit.
3. Here, you need to provide the path to where the tools and platform-tools folders of the Android SDK are located, or to the location of the folder which contains adb.exe (if you have it that way instead of the SDK). There will already be some paths here for other stuff, each separated by a semicolon. Make sure that the previous path has a semicolon at the end before putting in your path. For example, the end of my path variable is - <previous paths>;F:\Programs\adt-bundle-windows-x86_64\sdk\tools;F:\Programs\adt-bundle-windows-x86_64\sdk\platform-tools
4. That's it. Now adb and fastboot will work in cmd anywhere from your computer (no need to be in the adb folder).
sashank said:
I'm assuming that since you're asking about adb, you already have the Android SDK installed (or) you have a folder that you downloaded from somewhere with adb.exe, fastboot.exe and some other exe's in it. The reason you're getting that message is because your computer doesn't know where to look for adb.exe, unless you open command prompt in the folder itself. To be able to use the command universally in cmd, you need to add it to the Windows PATH system variable.
1. Control Panel->Search 'environment variables'->Click on 'Edit the system environment variables' with the administrator icon.
2. Click on 'Environment Variables' at the bottom, find Path (or) PATH under 'System variables', and click Edit.
3. Here, you need to provide the path to where the tools and platform-tools folders of the Android SDK are located, or to the location of the folder which contains adb.exe (if you have it that way instead of the SDK). There will already be some paths here for other stuff, each separated by a semicolon. Make sure that the previous path has a semicolon at the end before putting in your path. For example, the end of my path variable is - <previous paths>;F:\Programs\adt-bundle-windows-x86_64\sdk\tools;F:\Programs\adt-bundle-windows-x86_64\sdk\platform-tools
4. That's it. Now adb and fastboot will work in cmd anywhere from your computer (no need to be in the adb folder).
Click to expand...
Click to collapse
ive done all that im just going to erase everything and run usbdeview and start over
you need to add the location of adb.exe to the path in your windows. with a default android sdk install, I added ";C:\Users\pat\AppData\Local\Android\android-sdk\platform-tools" to the end of my system path. then you need to reboot. (change the pat part to whatever your username is)
This guide will help you to get rid of Kaspersky and unlock your locked mobile phone in case you don’t remember your pin/unlock code. It describes how I've done this when forgotten unlock code. Everything wrote below is based on online search and experiments with my phone. You just need basic computer knowledge and follow steps below. It works great on my Samsung Galaxy S3 Mini (GT-I8190N) with Android 4.1.2 onboard. Good luck.
IMPORTANT !!!Search online how rooting may affect your mobile phone warranty and do not continue if warranty is more important for you then your data. Phone can be unrooted as well, search online…
Using this method WILL NOT delete any other of your data, apps, contacts, SMS, etc.
Getting root access
Steps listed below are based on this website (sorry, can't post links, please send me PM if you need them). There are also links to necessary software but my advice is to search online for latest version. You need SD Card to install software and for system backup (more GB card has more backups you can make).
Software needed
1. Download Samsung USB Drivers and install them on your computer
2. Download Android SDK and unpack to your hard drive
3. Download ClockworkMod ROM Manager
4. Download ODIN and unpack to your hard drive
5. Download SuperSu
Getting root access (it is more convenient to open phone for better access to battery)
6. Pull battery out and refit (or switch phone off)
7. Press and hold Volume Down + Home button + Power button for few seconds to enter software download mode
8. Press Volume Up button when you see warning message screen to continue
9. Connect USB cable to your phone and computer
10. Unzip (if necessary) ClockworkMod ROM Manager to have .md5 file
11. Run ODIN. Make sure Auto Reboot and F. Reset Time options are ticked. ODIN should show the message confirming connection to device (bottom left) and COM port ID (top left) if not repeat steps 6-9
12. Press PDA button and browse to unzipped .md5 file and then press Start button
13. Phone should reboot after software installation is complete
14. Copy SuperSu .zip file to SD Card, pull battery out and enter card into the phone. Refit battery
15. Press and hold Volume Up + Home button + Power button for few seconds to enter ROM Manager (ClockworkMod Recovery)
16. Select install zip from sdcard ==> choose zip from external sdcard ==> browse to SuperSu zip file and confirm installation when prompted
Backup and software modification (based on this website, sorry can't post links, please send me PM if you need them)
17. Repeat step 15 if needed to run ROM Manager than choose backup and restore ==> backup to external sdcard and wait till process is finished (this is copy of all your existing software, data, SMS, etc.)
18. Choose mounts and storage option then select mount /data (if you need go back option is always at the bottom of menu)
19. Press Win+R or Start-->Run… and type in cmd to run console
20. Browse to adb.exe file (it is located in SDK folder ex. C:\adt-bundle-windows-…..\sdk\platform-tools\) using cd folder name command ex. cd platform-tool
21. Type in adb shell and press ENTER
22. Navigate to /data/app folder using cd /data/app command
23. List files using ls –a –p command (press ENTER after each command used in console) and find kms file (I have com.kms.free-1.apk file)
24. Delete kms file using rm com.kms.free-1.apk command
25. Navigate to /data/data folder using cd /data/data command
26. Repeat step 23
27. Delete kms folder using rm –r com.kms.free command (make sure –r parameter is entered in command)
28. Navigate to /data/dalvik-cache folder using cd /data/dalvik-cache command
29. List files using ls –a –p command and find kms file (I have [email protected]@[email protected] file)
30. Delete kms class file using rm [email protected]@[email protected] command
31. Navigate to /data/system folder using cd /data/system command
32. List files using ls –a –p command and find locksettings.db files
33. Delete locksettings files using rm locksettings.* command
34. List files using ls –a –p command and find packages.list and packages.xml files
35. Run new console window (step 19) and navigate to adb.exe file (step 20)
36. Type in adb pull /data/system/packages.list and press ENTER (file will be copied form your phone to PC's hard drive into …\platform-tools\ folder, always where adb.exe file is located)
37. Type in adb pull /data/system/packages.xml and press ENTER (file will be copied to same folder as in step 36)
38. Open folder with packages files and edit them using any of text file editor (Notepad, TextPad, etc.)
39. Inside packages.list file search for kms and delete each row containing it. Save file when done
40. In packages.xml file search for kms and delete each row containing it. IMPORTANT!!! In this file you will find sections starting with <package> tag and ending with </package>. One section includes kms. Select and delete entire kms section including corresponding <package>…</package> tags. Save file when done
41. Switch to second windows console opened in step 35 and send files from PC into phone using adb push packages.xml /data/system and adb push packages.list /data/system commands
42. Press reboot system now in your ROM Manager or pull out and refit battery to switch phone off and then switch it on
Enjoy and NEVER GIVE UP!!!
If you have any questions please post them and I'll try to help as much as I can.