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

Search This thread

mushfiq20

Senior Member
Jan 14, 2012
133
14
Dhaka
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. :D

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. :D
what am i doing wrong?
 

Attachments

  • adb.jpg
    adb.jpg
    247 KB · Views: 287

redmon

Member
Sep 21, 2010
48
0
Wen i try to install new firmware, i get this error: Download boot fail. And now it can't start anymore. In RkBatch is stuck in maskrom mode. A little help? Thank you.
 

Abuhuraira007

Member
Mar 20, 2020
7
2
Hello.

I am trying to use a rooted Android device, using Terminal Emulator, to manually root another Android device, which is stuck in a bootloop. Both devices are running Android 4.2.2 JellyBean.

Because the target device is stuck in a bootloop, I cannot root it using a root app such as KingoRoot, Kingroot, or similar apps. Thus, I can only root it manually using adb.

I see where someone wrote that this thread is obsolete, but because the device i am trying to root is running Android 4.2.2, it shouldn't be obsolete for that device.

I have tried this method, but i have encountered an obstacle.

Everything works until I get to the line:
./psneuter

I get the following response:

Failed to set prot mask (Inappropriate ioctl for device)

I have read the thread, and I see where others have previously received this error message, but I don't see where anyone posted how to fix or address this problem.

Any assistance would be greatly appreciated.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    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. :D

    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. :D
    1
    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. :p )

    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.



    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.
    1
    ./psneuter
    Failed to set prot mask (Inappropriate ioctl for device) ??
    1
    Ohw buddy calm down don't be a badass. Sure cool for your IT friends. You must be new right to showoff to be c00l on the 1337 d3v t34m.
    The reallity is no, you're not.

    Point is this must be copy/paste work and/or if it is the same get it approved? You don't know how many people try to backdoor **** with payloads that gain root and in that way subscribe to services what cost load of f*cking $ g!

    FYI
    Android.Lotoor.A: A Trojan that attempt to exploit vulnerabilities in the Android operating system to gain root privilege.

    I have to reserve engineer your crap first before i will even execute it. I aint trust nobody. It could easily be backdoored, not saying that it is because i wont waste my spare free time on this. But it could be!
    Wondering how you got that **** flagged like a Lotoor must be c/p work and not your own stuff if you have no good excuse. Anyway you did a good job on that part ;)

    And yea of course i know they flag it because this could be used in android malware too. But if it is compiled, what do you want to do? USB debugging must be enabled and adb is needed? And yes it is true public stuff that behaves like often gets flagged too.

    English must not be your strong suit, eh? It does say right in the OP that I was mostly just rewording another tutorial based on my personal experience and a little bit of extra knowledge from the ROM I've released on a weekly basis for the past year or so.

    You had to reverse engineer it, eh? Good. Good for you. I'm very proud of you. It was pointed out that it's a pretty commonly used exploit. Be paranoid. But Google is also this pretty handy website that came out a few years ago that lets you look up stuff before you go being a tool on a post where somebody was trying to help others.

    I'm going to go cry in a corner now. I hope you're satisfied.
    1
    please link me to those binaries as I have the same issue you had. Thanks!

    http://liliputing.com/2013/03/koush...superuser-app-for-rooted-android-devices.html has a link to download the zip file. Just copy the Superuser.apk and armeabi/su on top of the ones you already have.

    This assumes you do have the same issue as me, specifically that you do in fact have root over adb (otherwise you wouldn't be able to just copy the files).

    I don't remember if I also had to set permissions on the files, You might want to check the permissions on the existing versions of the files first.