Database Users

How to push files through ADB

Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish

usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556

Great post, very easy to follow, thank you.

yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help

this also works for the samsung Galaxy S in recovery mode.

mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline

hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx

yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)

just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers

Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?

{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.

Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App

Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey

Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo

pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA

Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons

Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !

Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination

Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...

rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?

Droid X Rooting problems after updating to official 2.2

I ran the rage exploit and afterwards, i can't get into adb shell. Gives me an error, device is not connected, but adb says it is

To further clarifiy, we were running the Sebastian Krahmer root process using the rageagainstthecage-arm5.bin. After running the rage step, we ran into trouble because the device no longer connected.

darkonion said:
To further clarifiy, we were running the Sebastian Krahmer root process using the rageagainstthecage-arm5.bin. After running the rage step, we ran into trouble because the device no longer connected.
Click to expand...
Click to collapse
same thing happened to me. however, i restarted the phone and the computer, and then adb would see the device again. i didn't get the # prompt, so i had to run ./rage... again. surprisingly, the second time it worked like a charm.

did you do kill-server?

had the same issue and can confirm the second time around worked no issues

mortodestructo said:
same thing happened to me. however, i restarted the phone and the computer, and then adb would see the device again. i didn't get the # prompt, so i had to run ./rage... again. surprisingly, the second time it worked like a charm.
Click to expand...
Click to collapse
I had a similar experience, however, part of it has to do with having the proper USB drivers and then to that same end, once it does it's first go round, there is a point where you truly have to wait for the phone to show back up in the taskbar before proceeding - otherwise, the next time you are attempting to do the "adb devices" it doesn't recognize that there's a phone there...it's all a matter of waiting for the USB driver to bring the phone back "into existence" from there, you are well on your way to the # prompt. (Trust me on this, I'm a total NOOB and just did this for the first time using the step-by-step method. I was scared as s**t with each command I typed but I was determined to go on...once I saw the #, I knew I was out of the woods..

Stuck big time!!
I'm stuck. I can't get PC Mode to show up with debugging icon (even though debugging icon shows up in all other modes) yet adb devices shows my device correctly, and I can adb shell to it fine and end up with unrooted on 2.2 froyo at the $ after I updated to OTA 2.2 from rooted 2.1
so I follow the guide to the T but as you can see this is my results and I have not yet been able to fix the issue.
$ pwd
pwd
/data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 rageagainstthecage-arm5.bin
Unable to chmod rageagainstthecage-arm5.bin: Operation not permitted
Click to expand...
Click to collapse
I have no idea how to fix this issue, I've rooted before on the leaked 2.2 without any problems both via the long adb method and via the easyroot method before OTA was released.
I tried the one click method and it hangs in the .bat and tries to pkil the process but there is no process to kill since the chmod 0755 rageagainstthecage-arm5.bin didn't work and thus it can't load ./rageagainstthecage-arm5.bin
%!~#$%~ Any help to get past this would be greatly appreciated! I would already have downgraded to 2.1 if I knew it was safe, but I'm seeing it bricks droid X staying at M logo on the forums if tried and thus we need a new sbf for 2.2 to be leaked.
EDIT: I've also tried via the Charge Only mode with debugging on as recommended by some people on the forums for other people stuck... I still end up with the same results using that mode. :/
EDIT 2: Looked up my default.prop and saw this:
$ more default.prop
more default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
Click to expand...
Click to collapse
and what it needs to be is:
$ more default.prop
more default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Click to expand...
Click to collapse
Unfortunately I don't have a way of changing it. Already tried copying modifed to sdcard and then using adb to copy it over... unfortunately don't have the permissions!
$ cp /sdcard/default.prop /default.prop
cp /sdcard/default.prop /default.prop
cp: /default.prop: Read-only file system
Click to expand...
Click to collapse

what about benchmark test with the froyo update,how much it scores?

Steebs77 said:
I'm stuck. I can't get PC Mode to show up with debugging icon (even though debugging icon shows up in all other modes) yet adb devices shows my device correctly, and I can adb shell to it fine and end up with unrooted on 2.2 froyo at the $ after I updated to OTA 2.2 from rooted 2.1
so I follow the guide to the T but as you can see this is my results and I have not yet been able to fix the issue.
I have no idea how to fix this issue, I've rooted before on the leaked 2.2 without any problems both via the long adb method and via the easyroot method before OTA was released.
I tried the one click method and it hangs in the .bat and tries to pkil the process but there is no process to kill since the chmod 0755 rageagainstthecage-arm5.bin didn't work and thus it can't load ./rageagainstthecage-arm5.bin
%!~#$%~ Any help to get past this would be greatly appreciated! I would already have downgraded to 2.1 if I knew it was safe, but I'm seeing it bricks droid X staying at M logo on the forums if tried and thus we need a new sbf for 2.2 to be leaked.
EDIT: I've also tried via the Charge Only mode with debugging on as recommended by some people on the forums for other people stuck... I still end up with the same results using that mode. :/
EDIT 2: Looked up my default.prop and saw this:
and what it needs to be is:
Unfortunately I don't have a way of changing it. Already tried copying modifed to sdcard and then using adb to copy it over... unfortunately don't have the permissions!
Click to expand...
Click to collapse
Have you tried rebooting your phone?
How about this, go check out the original 25 step process to root the Droid 2. Instead of pushing rageagainstthecage-arm5.bin, rename it to something else and then run the exploit. Of course after making changes to the commands else where.

My build.prop doesn't have either of those properties. That makes me wonder what you did that changed your build prop if you have no root.
You should have been upgrading from vanilla 2.1 to avoid problems.

android_master said:
what about benchmark test with the froyo update,how much it scores?
Click to expand...
Click to collapse
I got a quadrant score of 1375
Sent from my DROIDX using XDA App

I have a problem that my computer does not reconize adb after i download and extract all the zips files. it gives me adb not reconized as a command

Uilliam said:
I have a problem that my computer does not reconize adb after i download and extract all the zips files. it gives me adb not reconized as a command
Click to expand...
Click to collapse
ADB is an "external" command... i.e. its not native to windows. So you need to either be in, and stay in, the folder/directory where ADB.EXE resides to execute it, OR add that folder to the Windows PATH variable so windows knows where to find it to execute it.
and this was part of Brian's problem (in the OP) after talking with him via Gtalk.
if you want to add it to the path, then you need to do the following...
First you need to know the exact location of your ADB.EXE (for example: c:\android-sdk-windows\tools or c:\sdk\tools or ???)
he had Win7 but the steps are very similar in XP AFTER you know the folder/directory where ADB.EXE is. (tip, you can use Windows Search to find it, when found right click and select properties. On the general tab it will have the location).
Find where your ADB.EXE actually is. You need that for the following steps. Since I don't know where you unzipped to, lets say for the purpose of these steps, your ADB.EXE is located in C:\android-sdk-windows\tools
In windows, right click computer... select properties...
click advanced system settings (from along the left)
click the environment variables button
from system variables at the bottom.. scroll down and highlight path
click the edit button
use the right arrow key on your keyboard to get to the end of the line (it should unselect everything, and still keep the text there..)
on the end of that line...
type the following....
;c:\android-sdk-windows\tools
(yes, you need the semi!! and that line should be exactly where your ADB.EXE really is... remember I'm only using c:\android-sdk-windows\tools as my example!!!)
click OK
and ok
after doing that, when you are at a command prompt, no matter what folder/directory you are in, if you type ADB it should recognize it and run it.

[Help] ADB for the Epic

Ok. I had the android sdk installed before and was able to easily "adb shell" "su"
but a few months ago my phone stopped being recognized by the pc (stock cable) so i uninstalled it since i couldnt use adb nor odin (i thought it was my phone though)
but now i got a BB cable and the drivers all installed wonderfully and there was no headaches so now i believe the hype with getting a new usb cable because the stock one sucks.
So i followed the "Setting up Android SDK for beginners" by bthomas and i ollowed it to a t because i couldnt remember how to set up the sdk, and after setting it up, when i type in adb shell, it gives me a "~#" (which never happened before) and then when i type "su" it gives me a "sh-3.2#"
Im not sure what couldve went wrong except for the fact that before i would install everything (1.5sdk, 1.6, etc.etc) because i didnt know any better, but the guide showed me that all we needed to get adb to wrok was the platform tools one, but its not working.
I need advice because i dont wanna mess up anything in my phone since ive never seen those prompts
TL;DR
ADB gives me a "~#" when i adb shell, and i dont know why
Also, im running urban regeneration with genocide 2.0

The '~' means you are in your home directory. The '#' means you already have root so the 'su' command is not necessary. Sounds like your rom has a non-stock shell installed and is kernel rooted?

machx0r said:
The '~' means you are in your home directory. The '#' means you already have root so the 'su' command is not necessary. Sounds like your rom has a non-stock shell installed and is kernel rooted?
Click to expand...
Click to collapse
but i cd to the sdk directory (Cd:/ android/sdk/platform-tools) so idk why it would think im still in the home directory (that would be cd: users/etc, right?)
and yes the kerna is rooted. its Genocide v2.0 and im undervolted.
im also ext4 if that makes a difference...as for the rom idk its Urban Regeneration
im such a noob now i never had problems before i was forced to stop using my phone with my pc

A_Flying_Fox said:
but i cd to the sdk directory (Cd:/ android/sdk/platform-tools) so idk why it would think im still in the home directory (that would be cd: users/etc, right?)
and yes the kerna is rooted. its Genocide v2.0 and im undervolted.
im also ext4 if that makes a difference...as for the rom idk its Urban Regeneration
im such a noob now i never had problems before i was forced to stop using my phone with my pc
Click to expand...
Click to collapse
After you 'adb shell' it's showing you the filesystem on the phone, not your computer. I assume the the cd platform-tools command you are mentioning is what you are doing in a Windows command prompt to get to where your adb.exe is located.
Edit: Do this, it's safe, 'pwd' shows your current directory (in Linux/Android)
adb shell
pwd
cd /
pwd
Chances are it will show your home directory and then /
http://en.wikipedia.org/wiki/Pwd

machx0r said:
After you 'adb shell' it's showing you the filesystem on the phone, not your computer. I assume the the cd platform-tools command you are mentioning is what you are doing in a Windows command prompt to get to where your adb.exe is located.
Edit: Do this, it's safe, 'pwd' shows your current directory (in Linux/Android)
adb shell
pwd
cd /
pwd
Chances are it will show your home directory and then /
http://en.wikipedia.org/wiki/Pwd
Click to expand...
Click to collapse
yeah adb.exe is in platformtools
but anyways, this is what happened
adb shell
~# pwd
pwd
~ # cd /
cd /
~ # pwd
pwd
/
and then i exited lol
could it be a problem with my computer? like the place i saved it or something?

A_Flying_Fox said:
could it be a problem with my computer? like the place i saved it or something?
Click to expand...
Click to collapse
I don't think you have a problem it's just different than what you remember. Probably because of a difference in your mod. The prompt itself can be modified with environment variables (it's the PS# variables, you can look with 'set') so I wouldn't worry about that. My pwd output on stock looked very similar to what you pasted.
My PS# variables on stock:
# set
set
.
.
.
PS1='# '
PS2='> '
PS4='+ '

machx0r said:
I don't think you have a problem it's just different than what you remember. Probably because of a difference in your mod. The prompt itself can be modified with environment variables (it's the PS# variables, you can look with 'set') so I wouldn't worry about that. My pwd output on stock looked very similar to what you pasted.
My PS# variables on stock:
# set
set
.
.
.
PS1='# '
PS2='> '
PS4='+ '
Click to expand...
Click to collapse
i typed that in and i got a whole list of things and under them PS1='\w \$ '
PS2='> '
PS4='+ '
PWD=' '
TMPDIR= '/data/local/tmp
how would i get it back to #? Im willing to go back to stock odin if i have to, but im getting more intrigued by this as you help...

A_Flying_Fox said:
i typed that in and i got a whole list of things and under them PS1='\w \$ '
PS2='> '
PS4='+ '
PWD=' '
TMPDIR= '/data/local/tmp
how would i get it back to #? Im willing to go back to stock odin if i have to, but im getting more intrigued by this as you help...
Click to expand...
Click to collapse
Ok so you can see how your PS1 environment variable is different than mine. Depending on the shell you are using it might support escape characters such as \w which should display the current directory and \$ which should show # if you are root or $ if not. Here's some non-Android specific info on the subject http://www.cyberciti.biz/tips/howto-linux-unix-bash-shell-setup-prompt.html (stop at the colors part, no clue about which if any character are supported in the stock android shell, just using to give the basic idea)
To temporarily change the command prompt you could do:
PS1="# "
But most likely your shell has a settings file that sets the default prompt when you login. Unfortunately I do not know where this is located. Going back to stock would certainly undo any custom shells or settings your current rom has set if you don't like it.

i think that directory might be sbin/sh. because it calls to it whenever i enter something like ADB REBOOT it says sbin/sh.: adb not found
but when i type in adb shell
and then reboot recovery, etc it works
i dont think i need to go to stock, i just need to not type certain things before commands i guess...
but thanks alot! youve enlightened me quite a bit hahah i wish i had more thanks to give

[TUTORIAL] How to Manually ROOT your RK3066 Device (UG007, iMitio MX1/2, mk808?)

These are instructions for rooting Android devices that utilize the RK3066 chipset (Cortex A9 Dual Core, MALI Quad-Core GFX).
I have tested and verified that these instructions work for the UG007 Android-on-a-stick...they *should* work with any other devices that utilize the same USB chipset. I can almost guarantee this will work on the Imito MX1/2 as you can swap ROMS from this device.
(Basically, if you have the right ADB drivers, you should be good to go)
As per every other thread you read on this site - I TAKE NO RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE TO YOUR DEVICE.
This is a fairly risk-free mod, but you know...$hit happens.
Okay. Let's start.
THIS TUTORIAL ASSUMES YOU HAVE ADB AND KNOW HOW TO USE IT, and that you're in a Windows environment. There are numerous places on the web where you can find this info...and I ain't yo mamma.
1. Download all the files attached to this thread.
2. Attach your RK3066 device to your computer via it's microUSB port. You'll need to have it hooked to a display too.
3. Once booted, go to system settings. Under settings > developer options, enable USB Debugging. Under settings > USB, click "connect to computer" (This may vary depending on your ROM configuration. The point here is to have debugging enabled and your computer to recognize the stick in device manager as something other than USB storage)
4. Extract the right drivers for your system (x86/x64)
5. Go to device manager on your computer. Look for the new "unknown device". Right-click, pick "update driver software"., "browse my computer".
6. Browse to wherever you extracted the drivers in step 4. Click Next. Confirm that you want to install.
7. Open a command window in the directory where you have ADB. Type "adb devices". Still nothing, right?
8. Navigate to C:\users\MYUSERNAME\.android, where "MYUSERNAME" is your User Name. (Duh?)
9. Create a file called adb_usb.ini
10. Open it in a text editor. Add the following string and save (This tells ADB to look for our Vendor ID:
0x2207
11. You should now be able to type "adb devices" at CMD and see your device.
12. Now for the fun. Extract the stuff from "pushme" to the same directory as ADB.
13. Enter the following commands (note: The "$" and "#" symbols do not get keyed in):
Code:
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
14. Psneuter should run and close shell when done. Enter MOAR commands:
Code:
adb kill-server
adb devices
adb shell
15. Take a good look. Is there now a "#" sign? Good. You now have root access. You may continue. If not, then proceed to go yell at me in the comments. If yes, then proceed to enter the last batch of commands to make your newfound privileges permanent:
Code:
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
After a reboot, download a root app from Play Store to see if it worked! I find Root Checker is boffo for this sort of thing:
https://play.google.com/store/apps/...tcheck&feature=nav_result#?t=W251bGwsMSwyLDNd
THANKS/CREDITS:
Aaron Orquia @ Pocketables.com for the original "universal" root method.
AMJtech's tutorial where I found working ADB drivers and the adb_usb.ini bit to get it recognized.
The guy(s) who make Super1ClickRoot for putting all the necessary files in one easy-to-find spot.

Thanks for this tutorial.
A couple of notes:
Wow !! That's a lot of extra steps for you Windows users. Mac and Linux users start at step 11 (but if you are a Mac or Linux user, you already knew that. )
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Is step 13 necessary? adb remount works on mine. (not sure if I had to adb root first or not) but I can have a root shell via adb without psnueter.
If adb remount succeeds, skip step 14, and continue with the 3rd line of step 15.

Linuxslate said:
Thanks for this tutorial.
A couple of notes:
Wow !! That's a lot of extra steps for you Windows users. Mac and Linux users start at step 11 (but if you are a Mac or Linux user, you already knew that. )
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Is step 13 necessary? adb remount works on mine. (not sure if I had to adb root first or not) but I can have a root shell via adb without psnueter.
If adb remount succeeds, skip step 14, and continue with the 3rd line of step 15.
Click to expand...
Click to collapse
Thanks for the input! Yes, yes, I know windoze makes more work. It's also pretty widespread for folks.
For step 13 - I think it depends on the device. It would be nice for others to weigh in and let me know if it's needed. If not, I can totally remove it.
Also, in the other ROM thread, I made, it's even easier to root - you just grab one of the pre-rooted ROMS and drop it in SD card...the system does the rest. Mind you, this is for the UG007.

Links UG007
If you Bluetooth connection is not working properly, try to install this custom ROM: http://blog.geekbuying.com/index.php/category/android-tv-stick-tv-box/ug007/
How to install CWM-based Recovery: http://androtab.info/clockworkmod/rockchip/
Both worked for me. I was able to connect my BT Keyboard/Mouse Pad combo

./psneuter
Failed to set prot mask (Inappropriate ioctl for device) ??

nice tutorial.. while finding the best way to work my ug007 i stumbled upon this thread via armtvtech.com
currently i only knew this tutorial to root the device, but looking at yours ill give it a try first.
digitalhigh said:
Also, in the other ROM thread, I made, it's even easier to root - you just grab one of the pre-rooted ROMS and drop it in SD card...the system does the rest. Mind you, this is for the UG007.
Click to expand...
Click to collapse
you cant install custom roms without flashmode, cant do flashmode without opening device.. or did i get it wrong!? talking about the ug007
actually you can install a custom rom once you are rooted without opening the device, here
Linuxslate said:
(Hint: It may not be /just/ the udev stuff.)
Click to expand...
Click to collapse
ehm.. im still preparing to root, i guess you hint at the android sdk?
if not ill holla back at you and complain why you didnt write it out in first place
but very good to know that i skip alot by "almost" only installing ubuntu to a vm

I may be missing something, but I couldn't get this to work on my UG007
psneuter didn't work for me, gave me an error about 'invalid ioctl' or something. But the strangest thing is that "adb shell" already shows the # in the prompt.
To confirm my suspitions, I also typed "adb root", which returned "adb is already running as root".
So I proceeded with the rest of the instructions. No errors appeared, installed Superuser and I can see su and busybox in system/bin
But when I download root checker it says it wasn't properly rooted. installing terminal and type "su" says permission denied - and that's it.
Am I missing something? I'm new to this rooting thing, so please don't be angry with my noobish questions

I managed to do it - but *not* by following this tutorial.
I used this: armtvtech.com/armtvtechforum/viewtopic.php?t=28 (Cant post links yet, sorry!)
Only ran the "TPSarky-VonDroid-Root" bat, and presto! I had root on UG007.
I even fixed the changing MAC address problem with wlan.ko from armtvtech.com/armtvtechforum/viewtopic.php?f=69&t=632&start=10 (link on page 2). I just copied it to /data/local/tmp, set permissions as rwr--r-- and then used root explorer to copy it to /system/lib/modules - now I have wifi signal every time I boot the device, and don't need to mess with my router config every time
I also manage to get xbox360 wired controller working. xpad.ko on /data/local/tmp and then insmod /data/local/tmp/xpad.ko - just connect the joystick after that, and it will be recognized. Only problem is, after a reboot I have to insmod again.
I tried doing the same thing I did with wlan.ko, but nothing happens - system won't load it on boot. Am I missing something here?

The psneuter is broken
I'm on Linux, running a RK3066, and psneuter gives "Failed to set prot mask (Inappropriate ioctl for device)". Running Ice Cream Sandwich 4.1.1, kernel 3.0.8+, build RK30_anpei10w1am-r4.0.57.20121207, A10-2 cpu.

SLotman said:
I may be missing something, but I couldn't get this to work on my UG007
psneuter didn't work for me, gave me an error about 'invalid ioctl' or something. But the strangest thing is that "adb shell" already shows the # in the prompt.
To confirm my suspitions, I also typed "adb root", which returned "adb is already running as root".
So I proceeded with the rest of the instructions. No errors appeared, installed Superuser and I can see su and busybox in system/bin
But when I download root checker it says it wasn't properly rooted. installing terminal and type "su" says permission denied - and that's it.
Am I missing something? I'm new to this rooting thing, so please don't be angry with my noobish questions
Click to expand...
Click to collapse
Try renaming old "su".
Check permissions on the su and busybox you installed.

MK808, MK809 [model T002], and the MK802 III anyone?
Hi,
Thanks OP for this information.
I have a Samsung S3 [my first android device] which I rooted with no problem, but am a total noob when it comes to these android sticks.
One can say they are very similar, so I wont be completely in the dark. OK, now that we got that out of the way...
Can anyone please confirm whether they have used this with the MK808, MK809 [model T002], and the MK802 III,
I have ordered these from 1 from amazon and 2 from ebay and am expecting delivery shortly, therefore I just want to make sure before I go bricking them one by one...
I notice that they all have RK3066 Cortex A9 chips but are manufactured by different companies. The ones I see on eBay, although they all bear the same code MK8xx, they all look very different! I presume the MK8xx code is a universal model?? just like 80486 was to the PC? given the case does this method work universally?
I intend to set them up with XBMC media centres and to use with a Xbox controller. Any advice on the best way for achieving this would be nice too.
Thanks
:good:

Linuxslate said:
Thanks for this tutorial.
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Click to expand...
Click to collapse
Linuxslate, I have an MK808 that shows up in lsusb as 2207:300a when I put it in "flash mode" but it never shows up via "adb devices".

I got mine the other day and it turned out to be rooted already?
I decided to install SuperSu and that's how I found out it was rooted.
Immediately, installed Busybox, System Tuner Pro and Titanium Backup.
Rob
Rob sent this from his SPH-D710 via Tapatalk

So would this possibly work on this - http://www.zoostorm.com/Products/357-zoostorm-sl8-3305-1030-tablet-pc.aspx
States it's a Rockchip RK3066 Cortex A9 Dual Core 1.5GHz, running 4.1.1 Jelly Bean, quite interested in getting one & root would be a bonus.

psneuter broken
Hello,
the psneuter attached to the first post doesn't do anything to my ug007. I have the same error others have posted here and haven't gotten a reply about.
To unlock, I used the script that's mentioned in a post above, TPSarky-VonDroid-Root. If you google that, you'll find a download link amongst the results.

Thank u very much...:thumbup:
................................................................................................

Linuxslate said:
Try renaming old "su".
Check permissions on the su and busybox you installed.
Click to expand...
Click to collapse
Can you elaborate a little bit what you mean by renaming "su"?
I'm having the same issue..
Both su and busybox are having the same permission -rwsr-xr-x.
Sent from my Transformer Prime TF201 using XDA Premium HD app

I configured one of these at work. Upon using the terminal app and typing in su I got the # sign. They seem to come from the factory rooted already.
Sent from my Nexus 4 using xda app-developers app

ageerer84 said:
I configured one of these at work. Upon using the terminal app and typing in su I got the # sign. They seem to come from the factory rooted already.
Click to expand...
Click to collapse
Not exactly: this particular su can be used only from adb console, or at least that how it was on my tablet. So you need to replace it with a Superuser apk's su to get all features of rooted android. You can get one e.g. from FDroid
--
blog

Not sure what u mean by on your tablet. Android devices don't typically come rooted but I was surprised to have root access via terminal emulator on this stick PC. I just took it out of the box and definitely didn't have to go through the adb interface on a computer to flash superuser or what have you. Is this just me or is this a typical experience with this particular device?
Sent from my Nexus 4 using xda app-developers app

[ROOT] With working PlayStore Google Apps + Custom Launcher + superSU

###YOUTUBE VIDEO WILL BE UP SHORTLY###
###ALSO THE GUIDE WILL GET MORE DETAILS AND INFORMATION IN A SHORT PERIOD OF TIME###
###Before you ask, i use Quote instead of Code to NOT cut of the Code###
Requirement:
- Fire Tab 6" or 7" 4th Generation
- be patient
- be Aware - things can go wrong, if ANYthing is unclear, please ask first!
- Around 30~ to 60~ Minutes
depending how fast you get ADB and everything else required to get to the initial Root.
IF you already using ADB with your Fire, Check Step 3, THEN go to Step 7
Hi there,
In this Tutorial you will learn how you can root your Amazon Fire HD 6" or 7" Tablet.
First we are going to root it using Kingroot, after thet we Sideload SuperSU Root.
Please note this Tutorial requires the 4th(!) Generation of Fire Tabs.
Error-Solutions are at the BOTTOM of this Document!
NOTE: This Tutorial includes:
-Install ADB using Android Studio (also Windows 8, 10)
-Disable Fire Tab Ads
-Connect to Google
-Install Google GAPPS
-Install Custom Launcher
-Replace Default FireLauncher with Custom Launcher
-Root Device
-Sideload superSU, replace Root
-Install Google Store
-Implement Google Service as System-Apps
-Block Google-Phone-Home, AutoUpdates
Step 1:
Download the required Files (~180 MB)
Link: https://drive.google.com/file/d/0B5zOo5KIf0WdSVZKUllhQm85alk/view
Step 2:
Get Android Studio (FULL Install ~800MB)
Check the Android Studio Dir this ZIP contains and execute "Get AndroidStudio.lnk"
Step 2.1:
- After installing Android Studio launch it, click "Configuration" and Select the SDK (first Option)
- Select "Tools" at the Top and click "Manage Add-on Sites"
- Click the "User Defined Sites" Tab and click on "New..."
- Paste this URL:
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
- confirm with "OK"
- Close this Window after and go back to the Mainwindow "Android SDK Manager"
Step 2.2:
- Scroll down until you see the "Extras" Folder, select "Kindle Fire USB Driver"
TIP: Click "Deselect All" first and reselect "Kindle USB Driver" so you don't have to install the Whole Package.
- Click "Install x packages..." after and wait until it's installed. After it's done you can close the SDK Manager Process.
Step 3:
- Open the Android SDK Main Dir wich is located for ex:
C:\Users\<USERNAME>\AppData\Local\Android\
Click to expand...
Click to collapse
- Enter "android-sdk\platform-tools"
- Copy the Content from "APT" Dir to this Folder, for ex:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- Go back to the Mainfolder and enter "sdk\extras\amazon\kindle_fire_usb_driver"
Step 4:
- Open your Devicemanager (Controlpanel > Devices > Devicemanager) and connect your Fire Tab to the Computer
- Open the Internal Storage of your Fire Tab and go to "Download" Dir at, copy & paste the whole Content from APK Dir to Fire Tab's Download folder.
Step 5:
- Open "Settings" at your Fire Tab Device and select "Applications"-Tab, enable Third Party Application.
- Go back to Settings and go to your Device Propertys, now tap the "Serialnumber" Field until you enable the Dev-Mode.
- Enter Developersettings and enable "ADB" at the "Debugging"-Tab.
Step 6:
- Now (you are still at the Devicemanager) select the "Fire", it should be displayed as a protable device.
- Rightclick it and select "Uninstall".
If there is any other Kind of "Fire" you should install them, too.
Do NOT close the Devicemanager now.
###
---If you use Windows 8 or 10 - go to the Bottom now to see what you have to do instead of the following---
###
- Unplug your Device now and Run (As Admin) the "KindleDriver.exe" at your Amazon Folder located at AndroidSDK
- Install it (should give you a green tick if everything was correct)
- After you installed it - connect the Fire Tab again.
- If your Fire Tab Fire is not marked as "ADB Device" repeat
Step 7:
- Now ADB and your Fire Tab are ready to get tested.
- Your Fire should already be connected to your device, if not, do so.
- Run a Command Prompt (Win+R and type "cmd" without ")
- now first go to your Android AD Location wich should be by default:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- After you found the correct dir, copy the Path, go to your Command Prompt, paste it with "cd " in Front of it.
cd C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
###NOTE: All ADB-Commands are single-lined Commands.
Even if there are empty lines between them, it's just for better orientation.
Each command has to be added, one by one!
Step 8:
- Now you should be at the correct Dir, write
adb kill-server
Click to expand...
Click to collapse
Then
adb start-server
Click to expand...
Click to collapse
- The Server should start now, after it's online write
adb devices
Click to expand...
Click to collapse
- Your Device should now be displayed at the Prompt, if it says "Unauthorized", check your Tab, accept the Message and type again
adb devices
Click to expand...
Click to collapse
- It should now be displayed as "device"
Step 9:
- Enter
adb shell
Click to expand...
Click to collapse
at your Command Prompt
- Now let's make connection with Google.
- Enter the following command and accept with Enter of course
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
Click to expand...
Click to collapse
---Optional: to Block Ads from the Lockscreen menu type this:
pm block com.amazon.kindle.kso
Click to expand...
Click to collapse
Step 10:
- Go to your device and run Amazon Appstore look for "ES File Explorer" and install it.
- After that, we are starting to Install GAPPS.
NOTE: After each App, REBOOT your device and install the next one!
- Open ES File Explorer and go your "Download" Folder.
- Install the Apk's in this Order, don't forget to reboot:
Google Account Manager
Google Service Framework
Google Play Services
Google Play Store
Click to expand...
Click to collapse
- Now you can Create your Account and Log-In if you like
- After this Step, you do not need to reboot after the next APKs.
Google Play Games (also Create Acc/Login if you like)
Aptoide
VireLauncherPro
RootChecker
KindleReader (The default one may not work anymore)
Click to expand...
Click to collapse
Step 11:
- Back to adb Shell Prompt, we are going to Block our Amazon Default Launcher, type
pm block com.amazon.kindle.otter
Click to expand...
Click to collapse
- Now just Launch VireLauncher and mark it as default if it asks for.
- Now we got what we need to proceed for our root.
-----------IMPORTANT: In order to make sure all Amazonapps are Still working after the initial Root
-----------It is recommend to run all Amazon Apps you are going to use even once (MOST important after factory Reset)
Step 12:
- UNPLUG your Fire Tab (IMPORTANT)
- Open your ES File Explorer at the Download Tab and install
KingRoot-4.0.0.233-release-201505071219_105001
Click to expand...
Click to collapse
- Run KingRoot and tab the blue button at the bottom
- Now KingRoot is going to root your device, the device restarts during this Process.
- After the Device restarted.
- Click the Check Button (Top right Corner) and scroll up, it should say rooted, if NOT - restart KingRoot again and Root again.
Step 13:
- Go back to our Commandprompt (if you are still in ADB Shell, type "exit" first) and now excecute those Commands
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
Click to expand...
Click to collapse
- Now simply type
su
Click to expand...
Click to collapse
- now the following commands one after another, remember each command is a single line!
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Click to expand...
Click to collapse
Leave the ADB Terminal for now and go back to your Device, open the KingUser App
Click at the Top Right Corner on the Screen, click the Root authorization Settings and Remove Root Permission.
go to Settings > Application > All Applications/Third Party and uninstall the other King Applications (KingRoot and a Chinese one)
Go back to ADB now and enter the following commands one after another:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Click to expand...
Click to collapse
Step 14:
- leave the ADB Terminal again and open your ES File Explorer
- Install superSU now, then run it and let it update after that reboot your Device
- Leave the Device for around 5 Minutes after Reboot.
- Now run your RootChecker and click the Checkbutton at the Top right, and scroll up again, it should say "rooted".
Step 15:
- Go back to ES File Explorer but leave ADB open as always, Install
SysAppConverter
Click to expand...
Click to collapse
- Open the SysAppConverter after and add the following things to your "System-Apps"
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Click to expand...
Click to collapse
Step 16:
- After you have done this, go back to ADB Shell and stop them from Phoneing home
pm block com.amazon.otaverifier
pm block com.amazon.dcp
Click to expand...
Click to collapse
Also enter the Playstore, top right corner -> uncheck autoupdate
Swipe to the right, click Settings and also disable autoupdates.
Finally, you are ready and your Device is rooted including Access to Google Playstore
IMPORTANT: If Apps or Playstore should not work because of reasons, there is a simple trick just reset your Google Frame Services.
Open SystemAppConverter
Browser for "Google Play-Services" (The Puzzle Piece) and hit the "System" button to the right.
Now select "Remove Updates". Now wait around a minute. Try if it works, if not - restart the Device.
Sometimes the Screen can Flash or the Tab will just shut down.
-------------------------------------------------------------------------
WINDOWS 8
Go to the Windows 8 folder, There is a tutorial how to install ADB on Win 8, then back to Step 7
WINDOWS 10
Click this Link: http://pdanet.co/a/
Download PdaNet+ "Version 4.18 installer for Windows" for ex.
If you haven't done yet, unplug your Fire Tab and install PdaNet.
After you installed it completly ADB should be ready now.
Go to Step 7
-------------------------------------------------------------------------
###VIRE SETTINGS###
#Launcher Settings#
Enable reflections - y
Lock Home screen - n
Themes - Stock
Home transition style - Crystal
Advanced Features - include Wallpaper - y
" - Full Screen Transitions - y
" - Enable Frame
" - Enable HD Shaders - y
" - Enable infinite Scroll - y
" - Homescreen - iconlabelsize - large
Icon
Show icon Shadow - y
Icon Style - none
Icon pack Settings - None
Homescreen - Add App - Vire App - Clock
Click to expand...
Click to collapse

thanks for this- tried to download the link in Step 1 but the google drive link is protected. I requested access- email has "ben" in it, just hoping to try this out on my hd7.

I'd REALLY like to be able to follow your guide here, but...
Unfortunately I can't advance past the first couple steps because the google drive link posted in STEP ONE containing all the necessary files requires permission from you before I can download it.
Once you fix this, this guide will really help everyone.

Hell i'm sorry i updated the Link! Going to edit soon, there are a lot of parts pretty undetailed.

thank you, it's downloading for me now

Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.

Step 7 CMD window - suggestion for noobs
vismxownz said:
Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.
Click to expand...
Click to collapse
Wow! Thank you SO much. Step 7 might be a little unclear. Not sure "first copy the Android ADB Location" -- copy from where?-- and then "write to your Commandprompt" cd (ADB location)" -- do you mean write "cd" (no ") and paste what you copied? Just a thought . . .
Think it would be simpler to just open CMD window from adb.exe folder::
1. Open the folder containing adb.exe. (Should be C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools)
2. Hold down the shift key and right-click a white space in the folder. Choose "open command window here."

also for step 2.1 i wasn't able to get the fire SDK listed in the android SDK manager until i added the following URL
https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml

I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...

bibikalka said:
I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...
Click to expand...
Click to collapse
First I want to say thank you for the instructions this is a more detailed version of the steps I was taking. I had full intention to clean up my guide once we solved the problems we are currently having. I'm pretty sure these steps above are the basic steps of getting the Playstore but we are still not without issues. I'd be interested to see how many people this is working.

After all that, i still dunno why People got still issues - in first place with PlayStore.
It's the 6th (and 5th Day) for both HD 7" - still everything is working - PlayStore, also downloads and Cache Cleaning like a charm.
Also the Tablet seems to work faster now, cause of disabled Amazon Startup-Apps.
Also bibikalka is right, there are less big downloads, also you can evade downloading the whole SDK if you do not like, to. But you safed it for Future uses and instructions.
Also my first DL is above 100MB because it also includes the GAPPS, they are working as said and still working after nearly a week of usage on 2 Fire Tabs.
Just wanted to help, not that pro in writing instructions as you may already know.

But after all this, is Play Store application working?

devicer said:
But after all this, is Play Store application working?
Click to expand...
Click to collapse
As said before, nearly a week without any problems. Applications updating fine (for sure execluding Google Apps, don't updating anymore) - they should work until there is a update wich REQUIRES a newer Version of any GAPPS. But as said they work.

Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.

droidnext said:
Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.
Click to expand...
Click to collapse
Yes the GoogleCode got Patchday and 034 got patched. BUT to evade you also can go to your SysCustomizer and Reset the Google Play-Service to "Systemdefault" so it resets back to the first installed version. Until this gets a problem you can do it over and over again, so it would take just like 1 minute to fix the issue. Also there is no error or fail in using an "outdated" Version. Thanks for your Sharing i updated my uploadings

Everything is working now, and does not self update, see here :
http://forum.xda-developers.com/fire-hd/general/root-play-store-short-disabled-self-t3113975

Anyone else have problems setting up supersu?
Sent from my LG-V480 using Tapatalk

I'm waiting for the tuto video
thanks for the work btw !!!

Wich Problems?
greetings

So if we want the Google play store, we won't be able to use the default launcher anymore ? damn it ...
is it an obligation ?