Not 100% true. This is so for brand devices: Google, Samsung etc. But many Chinese devices I've seen had either adb run as root or su run without limits.
Oh! then that's not like in mine.
Typical to many-many Chinese devices.
Regards!
[TUTORIAL] How to Manually ROOT your RK3066 Device (UG007, iMitio MX1/2, mk808?)
- Thread starter digitalhigh
- Start date
Regards!
Hello all, so i have a prestigio pmp7100d3g and it`s impossible for me to find the driver im looking for it for days now and could not find, so i cant root it via some program. But i can get into cwm (thats nice because i should be able to flash supersu through cwm) but when i tried to apply supersu.zip it failed to install, now thats what i dont understand. Im not a stranger to flashing, i have an i9000 for almost 2 year`s and i flash roms daily. Anyone have any ideas why i get an error trying to install super-su 1.04v and my tablet has android 4.1.1.
Last edited:
I still don't get it: which ROM you have problem with?
And driver you are writing about - is it the Windows driver for your tablet? Did you ask at your tablet's user group about it?
Sent from my S3 using xda app-developers app
There is no thread for my tablet yet, i meant Windows driver, and i contacted support, it seems i have some corrupted file and i should do a factory reset to fix the problem. And i said before that i
have cwm, but i was wrong i have stock recovery so i cant flash supersu.
Sent from my PMP7100D3G using xda app-developers app
1. About driver: I see your 10" tablet is RK3066-based. You should get any of the RK3066 drivers. It should work. Though I don't use windows, so unfamiliar with all its caveats.
2. When your device is seen without question mark in the Device Manager, you should do this to get adb working.
Good luck.
Guys, that's completely normal! psneuter is an exploit tool which uses a bug in the system to gain root priviledges, what did you think psneuter is?
Every normal antivirus will react on this executable file. Super One click root tool uses psneuter for GB devices, too.
Every normal antivirus will react on this executable file. Super One click root tool uses psneuter for GB devices, too.
I had to LOL when I finally noticed there had been activity in this thread and saw this post. I literally explained the thread and then your comment to one of my IT buddies, and he laughed is as$ off.
And heeeeeeeeeere's your sign.
Thank you. Your reply is much nicer than mine would have been.
Are you really posting on behalf of XBMC Android, or is that just a clever monicker? XBMC for android is, after all, the only reason I bought one of these. I've got over 1k movies, every one with XBMC-specific metadata and art.
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.
Last edited:
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.
Since when is a way of rooting a exploit, rooting in this way normally should be changing some permission and nothing more. And no have not read the OP because i don't need to know how to use it and stuff like that. Google, who doesn't know that spy-engine these days, must be new if he/she doesn't know it. I either use another search engine i don't like it if all my keystrokes get recorded for the government to check it out if they want at any time.
And once again English is not my native language. Deal with it.
You don't have to be proud on me or cry for me because that is nonsense. I was just making clear what MY opinion was. I'm not trying to say that you are LQ or something, because you're not, it was just my opinion. Try to be a bit more mature in your next reply too without all the crying stuff and nonsense, i want to avoid low quality off-topic trash. Such a waste of time and nobody makes a benefit out of it. Just totally not worth it.
For your information. I will leave this childish discussion, will no longer reply on it.This not worth my spare time.
If you want to talk to me about related subjects just shoot me a pm i'm ready to answer it. What i nicely ask from you is to reply without the BS.
That's all there is mate.
Have a nice day!
Thanks
my MK808 was also already rooted
Based on your post, I checked my MK808 and it also turned out to allow root access already. Saved me a bit of hassle..
Based on your post, I checked my MK808 and it also turned out to allow root access already. Saved me a bit of hassle..
There's another method (buried in a system specific forum on this site) at http://forum.xda-developers.com/showthread.php?t=1886460 . That method is even better because the exploit uses only adb restore so you don't need any specially compiled program such as psneuter at all.
I tried it on my Aoson M33 (RK3188-based) with 4.2.2 and as I reported in that other thread, it gave me root over adb but su and SuperUser wouldn't work. This turned out to be because the version of su/SuperUser supplied in that thread had a bug; since I did have root over adb, I could just replace them with other su and SuperUser versions that work.
The exploit will probably be fixed at some point, but I would imagine that's true for psneuter as well.
I tried it on my Aoson M33 (RK3188-based) with 4.2.2 and as I reported in that other thread, it gave me root over adb but su and SuperUser wouldn't work. This turned out to be because the version of su/SuperUser supplied in that thread had a bug; since I did have root over adb, I could just replace them with other su and SuperUser versions that work.
The exploit will probably be fixed at some point, but I would imagine that's true for psneuter as well.
Installing the Drivers failed
I have been following your steps the first problem I face is that my windows 8.1 don't regonize the driver files so i'm still not be able to install the drivers for my Ug007II chipset RK3066
Also Moborob won't find any.
Can u help me of give me some advice
Dear regards
Nightsun
I have been following your steps the first problem I face is that my windows 8.1 don't regonize the driver files so i'm still not be able to install the drivers for my Ug007II chipset RK3066
Also Moborob won't find any.
Can u help me of give me some advice
Dear regards
Nightsun
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.
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7These 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.1Thanks 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.
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.1Ohw 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
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.
