Database Users

root Tattoo with Mac

Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this

I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.

hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..

Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!

Mod. edit: not dev related, moved to general

Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help

well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3

Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"

Terminal: "adb remount", then push again

damn the next bad message "remount failed: Operation not permitted"

You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927

Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me

You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279

now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to

You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled

Okay thank you very much.
now it was successful

[Guide?] Fixes to common Kindle Fire rooting problems

Not sure if this will help anyone, but I had a problem when rooting my new kindle fire 6.2.1
If you tried the Burrito Root method, I saw some few mistakes that I've done or didn't see in the video.
1. Updating the Kindle Drivers
I had previously rooted my android phone before, so when I plugged the kindle fire on my windows 7 laptop, I noticed that the windows was already indetifying it as an android phone, and had already labeled it for ADB. This auto-driver update thing might work for some people, but I find much better success replacing that driver that your computer identifies Kindle as, with the one that the BurritoRoot driver provides.
2. Getting the Kindle Root in the Listed Devices of ADB in command prompt.
This was probably the biggest issue I had when rooting the Kindle Fire. I was scratching my head, thinking why my Kindle Fire wasn't listed in the command prompt after typing "adb devices." I knew I did everything right from the beginning. Or so I thought?
One way I found that fixed that was downloading the Kindle Fire Utility v0.9.1
Unlucky for me, the download link was gone....
LUCKY for me, a fellow member here uploaded a mirror.
I somehow got it to work, with just luck but figured out the exact steps that seem to work for me (on Win 7 64 bit here).
1) Open up command prompt again, do the cd c:\KindleADB etc... upto the point where you typed in adb devices. you should be seeing no listed devices on the cmd (if you have that problem). LEAVE IT OPEN.
2) DOwnload the kindle fire utility, open the run.bat , it should have a message saying daemon started sucessfully, THEN QUICKLY FOLLOW THE NEXT STEP.
3) When the daemon started successfully message popped up on the KFU, go back to your CMD where you typed in adb devices and quickly type in "adb devices" again. it should say something like, killing out of date, starting daemon, and something about successful (Sorry if I'm not that much of a help, I tend to forget what the exact message said).
4) It should list the device. if not type it again.
5) Walla ! it should show a bunch of numbers, under listed devices.
3. Rooting the Kindle Fire in command prompt ERRORS
This wasn't much of a problem as it really was my mistake. I kept getting error messages when i typed in ADB ROOT in the command prompt during the BurritoRoot rooting method.
1) You have to make sure you have the BurritoRoot app installed in your kindle fire before starting the CMD adb root part. The app will tell you when to start typing away in CMD!
2) If you're doing the burritoroot method, you have to make sure you got all the names and directory right.
3) When you're doing the CMD adb root part, copy and paste it usually the best way to do it in CMD to avoid mistakes and erorrs! And no, you don't press CTRL+V in CMD. Rather, you right-click the CMD , then click paste (after copying the line you want to input).
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
Notice all those commands above that you're suppose to type in (or copy and paste). The ones I bolded, people tend to make mistakes there. When you put those files you downloaded into KindleADB, PLEASE MAKE SURE IT IS NAMED com.noshufou.android.su-1.apk, otherwise when you get to the part
Code:
adb install [B]com.noshufou.android.su-1.apk[/B]
change it to :
adb install WHATEVER IT IS CALLED.apk that is Superuser.
The most important part is to push the SU file (that has no file extension).
I had my kindle rooted, with Superuser installed, but I couldn't get any pop-ups from Superuser asking permission for any apps! That is, until I found out I forgot to push the su file to /system/xbin/su and other steps to chmod it.
Anyways, I hope this helps anyone that goes through any problem like I did above. If not, sorry to waste your time! If you guys have any other problems, please leave a question below and perhaps I could or a fellow member here could help you.
Thanks again!

http://forum.xda-developers.com/showthread.php?t=1417234

[Q] Renamed framework-res.apk and bricked my Kindle Fire

I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
adb shell mount is not allowed
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;

renamedresfile said:
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
adb shell mount is not allowed
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
Click to expand...
Click to collapse
You should be able to mount the system r/w with the proper command, hopefully someone will be here soon to give you the commands.

do you have fff & twrp available ?
if yes boot to twrp - there you have full adb availabe and you can copy your backup framework-res to the kf

same thing happened to me,but I made it worse and the computer wouldn't even detect the KF.I had to return it.
Sorry): I know how it feels

renamedresfile said:
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
adb shell mount is not allowed
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
Click to expand...
Click to collapse
Try using 'adb remount' then try to rename it again.
if you get the 'Read-only file system' error again:
adb reboot
adb remount
try again
Sent from my Kindle Fire using xda premium

Kindle 7.2.3 Root Error: permission denied

Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.

CMD returned error "permission denied"
HarldOOOandSon said:
Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
Click to expand...
Click to collapse
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".

prokennexusa said:
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
Click to expand...
Click to collapse
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.

HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
I have the same exactly issue and I do run the .exe as administrator.... i don´t know whats going on....

HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Had the same problem. DL my package and see if you have any better luck:
http://www.mediafire.com/?t570mx55pqw5ezw
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.

bigtimer5 said:
Had the same problem. DL my package and see if you have any better luck:
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
Click to expand...
Click to collapse
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied

jose87413 said:
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
Click to expand...
Click to collapse
Same thing here. Doesnt matter which tutorial I follow. I get a permission or operation denied on anything that I want to do on the Kindle Fire.

echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.

prokennexusa said:
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
Click to expand...
Click to collapse
Thanks for the info (i'm having the same problem)
The 2nd download link does work (

Broken Link
Wilson157 said:
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Click to expand...
Click to collapse
2nd Download Link: Root_with_Restore_by_Bin4ry_v17.zip

thanks but no cigar
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.

Step 1
Wilson157 said:
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Click to expand...
Click to collapse
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?

prokennexusa said:
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
Click to expand...
Click to collapse
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
Click to expand...
Click to collapse
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion

Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
yea, just tried. no go. any other ideas?

Qemu ADB Update
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
After the first step, do not do anything to the Kindle, leave it alone after the reboot and proceed using the following updated Qemu program.
You may download the updated version here: https://dl.dropbox.com/u/54456659/Qmenu.zip
Extract to your desktop and run the RootQemu.bat file. Choose Option 1.

littleengin said:
yea, just tried. no go. any other ideas?
Click to expand...
Click to collapse
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root

Initialize Superuser.apk
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
Ahhh, almost there. This is a bug in Superuser.apk - go into your Apps folder, you will see Superuser, click on it. It will open, now go to File Explorer, see if you can run as Root. I prefer Root Explorer.

Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
sorry my bad! Es file explorer was set to access root. Now i can access it. Thank you thank you thank you
I would post a picture of my ankle but the mods might class it as porn

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
Since this thread had seen a lot of changes over the last couple of weeks, I decided it was time to consolidate everything again, so here it is the consolidated and updated link version as of 12/23/2012:
The problem "Device not Found" is usually driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Download Root MANY ANDROID! to your desktop. Extract to your desktop.
Download Qemu automated root to your desktop. Extract to your desktop.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk to /system/app. Using Root explorer app on the Fire (be sure it has Superuser Permissions). Change permissions on both to Owner: Read-Write, Group: Read and Others: Read. Install GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Gplay3.8.17.apk to upgrade the the android market to the current Google Play market.
Play Step 8 Download google_apps - unzip to /sdcard/download
Play Step 9 Install Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have also attached copies of these noted files to this thread.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle

I'm also trying to do what previous users have been doing in this thread: running Rootqemu.bat but I still get permission denied on the second step. I've tried navigating to the folder using an administrator command prompt and running it through cmd, still fails on the second step with permission denied:
/system/bin/sh: cannot create /data/local.prop: Permission denied.
Have no idea where to go from here any help would be appreciated.

[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