If you was one of those who root their devices by using VRoot method and would like to remove chinese superuser and related files ...
You can now replace it easily with SuperSU by following these instructions :
1. Download and unzip "Replace_VRoot_With_SuperSU.zip" file
2. Copy the folder "mrw" to phone storage
3. In terminal type
Code:
su
4.
Code:
sh /sdcard/mrw/root.sh
That's all
This is not a method of rooting, it's just for replace vroot chinese superuser with supersu not more
You don't need to disable knox because my script will disable it
If you are going to use it, Please post which device does/dosen't work
File : http://www.mediafire.com/?ky9845gisnn3824
Video : http://www.youtube.com/watch?v=crLvs8ec0FE
Confirmed working on :
GT-I9505
SCH-I545
SGH-I337
...
Credit goes to chainfire for his rooting files
I can confirm GT-I9505 is working flawlessly on MJ7
Sent from my GT-I9505 using Tapatalk
MJ9 +
Does this block the software from connecting to the servers in China and sending data?
Boing7898 said:
Does this block the software from connecting to the servers in China and sending data?
Click to expand...
Click to collapse
It will remove it completely, no Chinese superuser, no connecting to the servers, no sending data.
Lost root
Funny, I lost root after following your guide. LOL
My device is Xperia Z1.
not working for lenovo s939
It is vital that I don't break knox. When you say your script disables it do you mean it changes it to 1?
Not Working on My Qmobile
Internal Storage?
Tried it and no luck. What exactly do you mean by 'Storage?' You mean place it at the root of the sdcard, yes?
Anxiously awaiting a reply.
Everyone who is complaining that this doesn't work do realise that this is the Galaxy S4 thread?
There is nothing vague here. Download the file. Unzip it. Place the folder called mrw that is in that zip into the root of your phone (internal) storage. Then use Terminal to run the commands given. It's really very easy.
There are a couple of things you should note. This was released nearly 5 months ago for JB 4.3 and the OP hasn't been back to confirm it works on KK 4.4.2. Also, this is specifically for changing the SuperSU when you have rooted using Vroot not for any other rooting process.
Sent from my GT-I9505 using Tapatalk
golagha11 said:
Funny, I lost root after following your guide. LOL
My device is Xperia Z1.
Click to expand...
Click to collapse
mee too on Lenovo s660
uninstall Vroot
Works on my Elephone P9, Android 4.4.2, but with lost su. Now I will find better tool for rootig this tool
Works on Elephone P8 mtk6592 - clone (myefox)
Confirmed working on :
GT-I9505
SCH-I545
SGH-I337
P8 mtk6592 5.7".
Credit goes to chainfire for his rooting files[/QUOTE]
it works perfectly with my lenovo A10 , thanks
Bad experience with KitKat 4.4.2 on MTK6582. It didn't install the SuperSU and also caused loss of existing ROOT privilege. Had to use iRoot again to ROOT it (as iRoot seems to be the only ROOTing solution for this device, even vRoot fails).
Thanks to @Mr.W0lf for the script
I know this thread is about Galaxy S4, but I think general info about "chinese superuser app" (superuser installed with vRoot, RomasterSu, iRoot, Kingroot... all of them install same kinguser app) could be useful for anyone who wants to replace this app.
I tried to post in his forum some doubts How to Remove/Replace Chinese VRoot superuser with SuperSu, where I think there is an updated version 28-Jun-14 : upload new version to fix issue for non Samsung devices and delete more VRoot folders and files (not tested yet, waiting feedback ...). ... Replace_VRoot_With_SuperSU_V2.zip
but I finally managed to solve it and managed to replace kinguser with superuser (opensource, com.koushikdutta.superuser), so I have a clean system.
I share here some info, I hope it helps someone or maybe helps to make a generic script.
I found similar script in another XDA thread VRoot to SuperSU Installer
- First attempt: trying to install whatever new superuser app (superSU, superuser from Chainfire, superuser from Koush) over kinguser did not work: app installs ok, but it fails when trying to update su binary, and kinguser keeps controling superuser requests.
For example with superuser from Koush app message was "There was an error installing Superuser. Please send a log of the error to the developer"
- Second attempt: After googling I found this script, and I tried to change it for my phone (M-HORSE N9000W, android 4.2.2)
(First original, as comments with #, second replacement)
Code:
#/system/bin/rm /system/app/Superuser.apk
/system/bin/rm /system/app/Kinguser.apk
#/system/bin/rm /data/app/com.mgyun.shun.apk
#/system/bin/rm /data/app/com.mgyapp.android.apk
/system/bin/rm /data/app/com.kingroot.kinguser-1.apk
#/system/bin/rm -r /dev/com.mgyun.shua.su.daemon
#/system/bin/rm -r /dev/com.mgyun.shua.su
#/system/bin/rm -r /data/data/com.mgyunapp.android
/system/bin/rm -r /data/data/com.kingroot.kinguser/
#/system/bin/rm -r /data/data/com.mgyun.shua.su
#/system/bin/rm -r /sdcard/android/data/com.mgyun.shua.su
#/system/bin/rm -r /sdcard/mgyun
#/system/bin/rm -r /sdcard/mgyapp
#/system/bin/rm /data/dalvik-cache/[email protected]@com.mgyun.shua.su.apk.classes.dex
/system/bin/rm /[email protected]@[email protected]
More things checked
Code:
[email protected]:/ #ls -l /system/etc/inst*
lrwxrwxrwx root root 2015-01-21 01:37 install-recovery.sh -> /system/bin/install-recovery.sh
-rw-r----- root root 85328 2014-12-23 16:30 install-recovery.sh-ku.bak
lrwxrwxrwx root root 2015-01-21 01:37 install_recovery.sh -> /system/bin/install-recovery.sh
[email protected]:/ #more /system/etc/install-recovery.sh
#!/system/bin/sh
/system/xbin/ku.sud -d &
/system/etc/install-recovery-ku.sh
/system/etc/install-recovery-kr.sh
Is the same content for /system/bin/install-recovery.sh
I also found /system/xbin/kugote, and I tested with strings these files are binaries related with kingroot
So I think I should add:
Code:
/system/bin/rm /system/xbin/ku.sud
/system/bin/rm /system/xbin/kugote
/system/bin/rm /system/etc/install-recovery-ku.sh*
I am not sure if it is mandatory to install busybox (some lines of the script do that), as I have it already installed
I tried that... but it did not work
Somehow kinguser allows to do anything as root ... except remove himself!
For example I was able to remove and write in /system after rw mount, but trying to remove or replace su binary fails ! so this script was not working.
And yes, I do have root access: I was tired to find post saying that if you can't delete a file in /system is beacuse you are not root or you have not rw mounted it ...
Code:
[email protected]:/ # id
uid=0(root) gid=0(root)
[email protected]:/ # uname -a
Linux localhost 3.4.5 #1 SMP PREEMPT Tue Sep 30 16:51:10 CST 2014 armv7l GNU/Linux
- Third attempt: I have an idea. I started a root adb shell, and being root, I unistalled kinguser (it has the option to return phone to "unrooted" state), ... I should have a root shell where I could be able to install a package through "pm" android utility ... no luck
- Fourth attempt and sucess: I have a new idea. As I realized I was able to replace kinguser with superuser in some phones, I thought that maybe some old kinguser app where easier to replace, so I tried to install old romastersu versions
I found that old versions did not work if wifi is disabled!? and with RomasterSu_1.1.4_140611_1000.apk I was able to use a simple Google Play com.koushikdutta.superuser was installed without error and replaced ok kinguser. New superuser requests were managed with new app.
I uninstalled kinguser with titatinum backup, and I made some cleanup
Code:
/data/data/com.kingroot.kinguser/
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 app_crash
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 app_tomb
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 applib
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 cache
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 databases
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 files
lrwxrwxrwx install install 2015-01-26 22:58 lib -> /data/app-lib/com.kingroot.kinguser-1
drwxrwx--x u0_a114 u0_a114 2015-01-26 23:02 shared_prefs
A helpfull advice
my mobile is xolo q2500
its my advice to backup the chinese superuser (kinguser) with es file explorer before trying this method.
when i tried this method it seems to like working on my phone but when i check the root-checker it said "u have no root access" then i got upset
then i restore the kinguser then i get root access again
in short before replacing the chinese superuser, please backup the previous one because it will uninstall the previous one
but now the same problem - HOW TO REPLACE CHINESE SUPERUSER?
because this superuser is not giving permission to every app. it dose give permission to "GameCIH" and when i start "gamekiller" app it gives root access after 10 to 15 minutes.:crying:
Elephone P3000s
Works with Elephone P3000s.
BUT I now have a flash of red border when exiting settings and some other screens. Not visible with all menu screens.
Wonder if anyone knows a fix for this?
Working on MT6589 - SM-G900H
Thank You!
Related
This is tested and working on NSZ-GS7 REL10 for US
Thanks to the guys with gtvhacker making the temp root. we are now capable of having a static root.
i have now achieved static root, changing the /system
# pwd
pwd
/system/xbin
# ls -l
ls -l
-rwsr-xr-x root root 1062992 2013-07-23 20:06 busybox
-rwxr-xr-x root shell 70604 2008-08-01 14:00 dexdump
-rwxr-xr-x root shell 11736 2008-08-01 14:00 fw_loader
-rwxr-xr-x root shell 67736 2008-08-01 14:00 hciconfig
-rwxr-xr-x root shell 189380 2008-08-01 14:00 hcidump
-rwxr-xr-x root shell 40736 2008-08-01 14:00 hcitool
-rwxr-xr-x root shell 31432 2008-08-01 14:00 hidd
-rwxr-xr-x root shell 10360 2008-08-01 14:00 mfgbridge_trigger
-rwsr-xr-x root root 91992 2013-07-23 20:06 su
Click to expand...
Click to collapse
I have used the starting point from entonjackson making the root for Acer A1-810, using dd to seek through the mmcblk0 to write a modified /system
see more details on that approach here
the big secret to writing the new filesystem:
1. follow gtvhacker instructions to get temp root on your box. (find instructions on temp root here
2. as root do a chmod 777 /dev/block/mmcblk0 ; chmod 777 /dev/block/mmcblk0p11
3. dump the filesystem: /data/local/tmp/busybox cat /dev/block/mmcblk0p11 >/mnt/media/usb.E234-1928/system.fs
4. on a linux box: mount the dumped filesystem (system.fs) with -oloop to be able to modify it.
ie. mount -oloop /tmp/system.fs /tmp/1
5. copy your busybox and su to the /system/xbin/ folder where you mounted the system.fs (use files attached to this post)
5a. remember to set permissions on both files, owner - root/root, permissions 4755 on both files and you are safe.
6. umount your dumped filesystem from location you mounted it.
7. write back the newly modified filesystem (i renamed it now to system.with_root) .
/data/local/tmp/busybox dd if=/mnt/media/usb.E234-1928/system.with_root of=/dev/block/mmcblk0 seek=149248 bs=4096
thats is awesome Dexter congrats!!, i have a question: how much should be the size of the dump system.fs?
bovoro said:
thats is awesome Dexter congrats!!, i have a question: how much should be the size of the dump system.fs?
Click to expand...
Click to collapse
should be 1 GB
mmm, is a 3.99GB system.fs for me, and I inserted su and busybox to /xbin/, but i forget to give permits :S. is neccesary?
i flashed back system.rooted , but is 3.99 GB and appear no free space in device :S maybe for 3.99GB file
bovoro said:
i flashed back system.rooted , but is 3.99 GB and appear no free space in device :S maybe for 3.99GB file
Click to expand...
Click to collapse
instructions updated in post #1, sorry.
bovoro said:
but i forget to give permits :S. is neccesary?
Click to expand...
Click to collapse
its important that su command has correct suid permissions (4755) and ownership (root)
Dexter_nlb said:
1. follow gtvhacker instructions to get temp root on your box.
Click to expand...
Click to collapse
And these are?
Appreciate the work this obviously took. Might be over my head, technically. Going to need to give it some study.
BELASCO said:
And these are?
Appreciate the work this obviously took. Might be over my head, technically. Going to need to give it some study.
Click to expand...
Click to collapse
i have updated post #1 with reference on how to get temp root.
ill attach my su + busybox used in post #1 now.
Thanks so much buddy!!!, I was able to root , now what? , What kind of access we have with this type of root? all folders? can i install Superuser Apk ?
bovoro said:
Thanks so much buddy!!!, I was able to root , now what? , What kind of access we have with this type of root? all folders? can i install Superuser Apk ?
Click to expand...
Click to collapse
maybe this one works now on our device? xposed installer, i do not think it needs to modify /system. but since my box is bricked until i get REL10 or REL11 to fix it, i cannot experiment much.
modifying the build.prop, and changing to a more old version, it would be possible to reinstall an update? or protect for future automatic updates?
Are we able to mount the / system folder as rw?
* adb shell mount-o remount, rw / system
I made a copy of my build.prop, that security is only that blocks to downgrade?, "firmware is too old." message
# ro.build.product is obsolete; use ro.product.device
ro.build.product=NSZGS7
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=S052913/M12_OTA/HC_3.2_Localhost,release-keys
ro.build.fingerprint=sony/NSZGS7_C02_MX2/NSZGS7:3.2/MASTER/20130529185822:user/release-keys
ro.build.characteristics=tv,nosdcard
# end build properties
bovoro said:
modifying the build.prop, and changing to a more old version, it would be possible to reinstall an update? or protect for future automatic updates?
Are we able to mount the / system folder as rw?
Click to expand...
Click to collapse
/system can only be changed if we can modify root partition, which i did and semi-locked my box, until i reinstall root filesystem using REL10 update. so until more experiments are done, i would say no to this. /system is fine, root partition is a no go.
i believe so.
maybe you can actually help if you are willing to spend time writing another /system.
1. download the REL07 from the gtvhacker wiki
2. copy the build.prop from REL07 to your existing /system
3. install it and reboot once, so the new build.prop takes effect. (i believe you need to set proper permissions on it ie. permissions 644)
4. search for an update, you should get the REL10 downloaded
5. as you got root, you can easily extract it from the /cache partition where i hope its placed, otherwise its somewhere in a /data folder.
6. i am also told you can see the full path to where it is downloaded from google, in the logcat. so if you can dump logcat when searching and downloading update. that of course is easier to share.
7. then write back your old /system with root. and leave it.
possible?
yes man , really works , im downloading from my gtv REL10 MX region but what I did was use my system.fs old, mounted in linux and replace the build.prop file REL07 and voalá downloading system update REL10 , this can be work for change region im MX region , i can change to a US .
bovoro said:
yes man , really works , im downloading from my gtv REL10 MX region but what I did was use my system.fs old, mounted in linux and replace the build.prop file REL07 and voalá downloading system update REL10 , this can be work for change region im MX region , i can change to a US .
Click to expand...
Click to collapse
can you share the REL10 (or just the link to the clients.google.com site with the REL10 build) ? would really appreciate it, so i can get my box up and running again.
of course man, but is the mexican version, right now im try to change build.prop us instead MX and instal alogcat for sharing the US link
---------- Post added at 01:01 AM ---------- Previous post was at 12:47 AM ----------
bad news man,I have not updated yet, but when I reboot my box came the boot animation, and then went into a loop of a blue circle, is that how you did your box? I will enter recovery mode since I have the build.prop REL08 think I can upgrade to unbrick (i hope)
update:
I could not capture the OTA link, but I can share the zip, I'll upload it to dropbox
---------- Post added at 01:48 AM ---------- Previous post was at 01:01 AM ----------
bro here is the US ota http://android.clients.google.com/p...REL10_NSZGS7_U2_2203_133772_20130529_URSC.zip , i dont know if i can post links here, if not i will delete inmediatly
bovoro said:
I could not capture the OTA link, but I can share the zip, I'll upload it to dropbox
Click to expand...
Click to collapse
thanks very much appreciated , i hope it works as i am told it would with the same release installed
edit: downloaded and installed.. my Box is back in business!
Dexter can you please post a video on how to I new this root but have the slightest idea where to start thanx in advance
Dexter_nlb said:
This is tested and working on NSZ-GS7 REL10 for US
Thanks to the guys with gtvhacker making the temp root. we are now capable of having a static root.
i have now achieved static root, changing the /systemI have used the starting point from entonjackson making the root for Acer A1-810, using dd to seek through the mmcblk0 to write a modified /system
see more details on that approach here
the big secret to writing the new filesystem:
1. follow gtvhacker instructions to get temp root on your box. (find instructions on temp root here
2. as root do a chmod 777 /dev/block/mmcblk0 ; chmod 777 /dev/block/mmcblk0p11
3. dump the filesystem: /data/local/tmp/busybox cat /dev/block/mmcblk0p11 >/mnt/media/usb.E234-1928/system.fs
4. on a linux box: mount the dumped filesystem (system.fs) with -oloop to be able to modify it.
ie. mount -oloop /tmp/system.fs /tmp/1
5. copy your busybox and su to the /system/xbin/ folder where you mounted the system.fs (use files attached to this post)
5a. remember to set permissions on both files, owner - root/root, permissions 4755 on both files and you are safe.
6. umount your dumped filesystem from location you mounted it.
7. write back the newly modified filesystem (i renamed it now to system.with_root) .
/data/local/tmp/busybox dd if=/mnt/media/usb.E234-1928/system.with_root of=/dev/block/mmcblk0 seek=149248 bs=4096
Click to expand...
Click to collapse
@Dexter_nlb
Hi dexter,
I was wondering if you can help, i have a copy of the file system and I have mounted it using the command you specified,
mount -oloop /tmp/system.fs /tmp/1
but it mounts it as a read only file system. therefore I cant copy over the su and busybox. Can you help.
Update.
got it fixed. now fingers crossed will flashback to system.
What superuser app are you using with the box. Tried chainfire version but it did not work.
Is the su you posted chainfire version?
Cheers
Optimal
Files System corrupt
Problem Resolved
Woot has this box on sale today, can't wait to get mine and try this. Why doesn't XDA have a section for gtv?
Hii GuyZz... I had a problem and wanna help from you.
My problem is that I had rooted my Karbon A6 From VRoot Software but It gived me a Chinese Superuser.
I had installed supersu from market and then removed the Chinese one. But nothing happened. I had losted my Root access and have to reroot my device via the VRoot Software.
And again that Chinese superuser camed.
Kindly plz help me to change my superuser app.
Thanks In Advance.....
ShubhamDubey said:
Hii GuyZz... I had a problem and wanna help from you.
My problem is that I had rooted my Karbon A6 From VRoot Software but It gived me a Chinese Superuser.
I had installed supersu from market and then removed the Chinese one. But nothing happened. I had losted my Root access and have to reroot my device via the VRoot Software.
And again that Chinese superuser camed.
Kindly plz help me to change my superuser app.
Thanks In Advance.....
Click to expand...
Click to collapse
Here we have 2 scenarios; the first is easy and the second is salty..!!
I hope you got the first scenario; since the second one is handy..!!!
The first scenario: you got custom recovery too:
If so, just get cwm SuperSU from here and flash it in cwm.
Other scenario if you didn't had custom recovery:
- Keep the previous root.
- Download SuperSU with su binary from same thread in previous scenario.
- Extract the content in a folder (we will call it SS so you could follow the procedure) and move it to your sdcard. The SS folder contains su and Superuser.apk).
- Download Terminal Emulator from Google play.
- Open Terminal Emulator and write this code:
Code:
su
mount -o remount,rw /system
dd if=/sdcard/SS/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
Remember to hit enter in between those lines. Don't close Terminal Emulator now, just hit home button to minimize it.
- Now by any root explorer, go to /system/app and delete the Chinese superuser (don't do normal uninstall, you need to delete the apk from /system/app).
- Return back to Terminal Emulator which is still running and write these codes:
Code:
dd if=/sdcard/SS/Superuser.apk of=/system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
- Now reboot your device.
Is there any easy method Coz I'm beginner in programming.....
Please help me I don't understand which file to download from previous scenario as I open the thread I don't understand which file to download... if you can share the link..
Thanks in advance.
I updated my motorola xoom to 4.4.2 3 weeks ago
(thread []http://forum.xda-developers.com/showthread.php?t=2593757&__utma=248941774.598456778.1394750856.1394750856.1394750856.1&__utmb=248941774.2.10.1394750856&__utmc=248941774&__utmx=-&__utmz=248941774.1394750856.1.1.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=22130616 ) -
all was excellent I got my xoom functioning like new - received update for my OS 3 or 5 days ago (Version from Screenshot of my Xoom http://imgur.com/ekkKd0J ) which i did to update the current 4.4.2 and worked like a CHARM;
just opened Titanium Backup said device NOT ROOTED. used root checker Pro, Supersu, Superuser and all show device not rooted.
Downloaded TWRP and reinstalled but did not hlep.
ROOT CHECKER PRO gives the following analysis so please hope someone can help me. (I can see a solution in the analysis below but dunno wot to do) Cheers, Roger
Root Checker Pro:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 71140 2008-08-01 16:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn
TheKicKer69 said:
I updated my motorola xoom to 4.4.2 3 weeks ago
(thread []http://forum.xda-developers.com/showthread.php?t=2593757&__utma=248941774.598456778.1394750856.1394750856.1394750856.1&__utmb=248941774.2.10.1394750856&__utmc=248941774&__utmx=-&__utmz=248941774.1394750856.1.1.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=22130616 ) -
all was excellent I got my xoom functioning like new - received update for my OS 3 or 5 days ago (Version from Screenshot of my Xoom http://imgur.com/ekkKd0J ) which i did to update the current 4.4.2 and worked like a CHARM;
just opened Titanium Backup said device NOT ROOTED. used root checker Pro, Supersu, Superuser and all show device not rooted.
Downloaded TWRP and reinstalled but did not hlep.
ROOT CHECKER PRO gives the following analysis so please hope someone can help me. (I can see a solution in the analysis below but dunno wot to do) Cheers, Roger
Root Checker Pro:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 71140 2008-08-01 16:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn
Click to expand...
Click to collapse
I see that you have omni. Have you tried reflashing the root from omni thread?
Until now I only followed to the letter that Thread and this is how i jumped from 4.2 to 4.4.2; and in that thread it clearly says if u r upgrading from that update u won't need to wipe so when i got the notification 4 or 5 days ago there is a newer update to 4.2.2 I did and it went smooth only thing that went berserk is it says device ain't rooted.
Dunno wot else to do (I reinstalled like i said above latest TWRP [used to use CWM but if i need to update i will have to wipe everything as the thread says] and Supersu)
tx for the help,
Roger
I think I can help you
TheKicKer69 said:
Until now I only followed to the letter that Thread and this is how i jumped from 4.2 to 4.4.2; and in that thread it clearly says if u r upgrading from that update u won't need to wipe so when i got the notification 4 or 5 days ago there is a newer update to 4.2.2 I did and it went smooth only thing that went berserk is it says device ain't rooted.
Dunno wot else to do (I reinstalled like i said above latest TWRP [used to use CWM but if i need to update i will have to wipe everything as the thread says] and Supersu)
tx for the help,
Roger
Click to expand...
Click to collapse
Hi Roger,
Boy, I don't know how to stress this enough. Before doing anything, make a backup. After you are finished, you should reinstall your programs from the backup manually. Don't do an automatic reinstallation as there are some CM11 Program files that would make the Omnirom installation go into an endless loop.
CM11 has the Su built into it. If you use Omnirom you should first clear your Dalvik Cache and Cache, preferably doing a factory reset before installing your Rom as I mentioned about looping above.. You might want to install a newer Gapps file, as well as flashing a Superuser file-this last is a must with Omnirom
These 3 files should all be installed from your external sdcard. Just be careful not to format either of your sdcards.
k, I did a full install just like in the thread and for some strange reason it is still NOT rooted! wot gives lol. (remember the first time i did it i got my xoom working flawlessly.
is there any other thread that also provides kitkat for my xoom - i really don't care about omni or any other developer just need to have my xoom with latest kitkat.
tx,
Roger
TheKicKer69 said:
k, I did a full install just like in the thread and for some strange reason it is still NOT rooted! wot gives lol. (remember the first time i did it i got my xoom working flawlessly.
is there any other thread that also provides kitkat for my xoom - i really don't care about omni or any other developer just need to have my xoom with latest kitkat.
tx,
Roger
Click to expand...
Click to collapse
keeps getting weirder and weirder! This is from Root Access Pro! wth is going on? (remember did complete reflashing and followed all steps that i did the 1st time when it worked flawlessly - and yes i did d/l Superuser and SuperSu and also reflashed SuperSu that comes with the thread for updating)
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 104800 2014-03-28 14:52 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn
[Q] Big Part&OMNI no more root (need 2 backup 2 change my Xoom to SAMSUNG Q9050 12.2
since I changed to BIG PART and OMNI i have 4.4.2 which is awesome but my Xoom Verizon doesn't show rooted anymore for Titanium Backup or any other Root app (even root checker pro tells me i am not rooted)
anyway my question is:
i am thinking of buying Samsung Q9050 (12.2" Tablet) how can i backup all of my games and apps and even system (like my wallpapers etc...) since i cannot use Titanium Backup
i know i can dump all of the Xoom on my PC but how to restore them and how to know which apps to restore since i can't see the folders containing my games , apps, etc..)
hope to get help.
Cheers,
Roger
P.S.: wot do u think about the Samsung Q9050 2.3 Ghz 12.2"?
You need to flash SU in recovery, once that is done you will be rooted and can backup with titanium backup. OmniROM doesn't come with root included
I did flash SU many times (SU 1.86) it actually comes in the OmniROM thread where i flashed my XOOM
http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=22130616
is there an SU u recommend? btw i cannot seem to download an SU i can only Install an SU (from google play store) - where can i actually D/L an SU in order to b able to place on SD and flash?
(in the thread we download:
Download Root
UPDATE-SuperSU-v1.86.zip)
tx a lot for the help;
and another dumb question - if i'm able to use titanium backup i can basically restore any backed up app on any android device right? whether it's a fone or tablet right? reason i ask is my xoom is the only android i use
Root Checker Pro Result:
Root Access is not properly configured or was not granted.
Super User Application Status: (SUPERSU 1.94 IS INSTALLED I MARKED IT)
SuperSU application - version 1.94 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 71140 2008-08-01 16:00 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn
matt4321 said:
You need to flash SU in recovery, once that is done you will be rooted and can backup with titanium backup. OmniROM doesn't come with root included
Click to expand...
Click to collapse
Solved! D/L http://forum.xda-developers.com/showthread.php?t=1538053
SuperSU 1.94 fixed it while the V1.86 didn't!! maybe i should post also there if someone has/had my problem
Ladies and Gentleman,
I was able to root the HD8 6th Gen using Kingoroot while in airplane mode. I download the executable and ran it directly from my computer. My Fire tablet is on version 5.3.1.1 and was never registered with Amazon. I can run su in adb but the SuperUser app is not working on my tablet. I am looking into replacing the KingoRoot SuperUser app with SuperSU. I suggest you block updates as soon as you achieve root.
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Decided to try this on 5.3.2.1, ran Kingroot for PC few times (version 3.4.0 build 1142). Did not work. Hope it works for you 5.3.1.1 guys.
I believe 5.3.2 can be downgraded to 5.3.1.1 but I also believe 5.3.2.1 is confirmed to not be downgradable.
I was lucky and got my BF unit with 5.3.1.1 and blocked OTA right away
I register to reply this thread and tell everyone that 5.3.1.1 CAN BE ROOT using KingoRoot(not KingRoot)
blocked OTA and planning to place Kingoroot with Supersu now.
go kingoapp.c0m(replace 0 with o) and download the PC one.
Tried APK one but seems stuck at 90% or not enough patient?
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
chemie99 said:
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Click to expand...
Click to collapse
my device is registered with amazon and it works
Detailed instruction on post#38
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
chemie99 said:
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
Click to expand...
Click to collapse
honestly I dunno, I'm new to android, just bought the kindle to start playing with android...
but I found it difficult to replace the kingoroot with supersu, when I type su in terminal, it show nothing, can't give root permission to terminal emulator.
I replaced kingoroot with supersu following instruction from androidforums.com/threads/script-replace-kingoroot-with-supersu.919175/
After it's done, supersu doesn't prompt for root access. So I set 'default access' to 'grant' in supersu settings, and it seems to be working.
g4ry12 said:
Decided to try this on 5.3.2.1, ran Kingroot for PC few times.
Click to expand...
Click to collapse
I was not paying attention, it's KingoRoot, not KingRoot. Downloaded KingoRoot for PC (v1.4.9), and tried on 5.3.2.1. Rooting failed, unfortunately.
I ran the PC kingo and rooted.
I then tried to remove and replace with supersu and it failed
I lost root
I tried to rerun Kingo PC but it wanted debugging enabled even though it was
tried the apk kingo (from kingoapp.com; playstore it is a adware hack)
got stuck at 90%
exited and kindle was really sluggish; maybe something to do with my novalauncher or something?
power off reboot and stuck in boot up (Fire image). Now can't boot.
Message is be careful with kingo when removing....will try restore now.
Edit: wiping data and cache did not help. Did brick recovery to 5.3.1.1 (which is what it was on when I got it), and managed to recover. Glad I don't have to send this one back to Amazon!
I will now restart kingo root effort and if it works will report back steps (including supersu replacement).
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. For example, Titanium BackUp is unable to detect "Su and Busybox" so no go.
I am able to pm disable the firelauncher for example but that is about it
chemie99 said:
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. I am able to pm disable the firelauncher for example but that is about it
Click to expand...
Click to collapse
I soft-bricked once, stuck at fire logo, sideload adb and resumed normal.
I didn't use the root checker to check, the superuser included will crash when I launch it,
but I can su in adb shell..
@2ig2ag's way not work for me either,
I cannot run the script, it said permission denied, then I try to run it manually,
I can remount /system, it do not show any error, but I am stopped at "cp ./su /system/xbin/daemonsu",
it said "daemonsu" text file in use.
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
chemie99 said:
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
Click to expand...
Click to collapse
I am using a file explorer called "ES File explorer", it cannot view the system file when it is not root.
After Kingoroot, I can view them, but I still cannot create file in /system by using that File explorer.
However I can successfully create a dir in /system in adb shell, shown below.
[email protected]:/system # mkdir 123
[email protected]:/system # ls
123
app
bin
build.prop
data
etc
fonts
framework
lib
lib64
lost+found
media
priv-app
recovery-from-boot.p
sbin
security
sqfs
tts
usr
vendor
xbin
[email protected]:/system #
I have made progress...with kingo install I did this:
copy the files of the kingo root removal to sdcard/kingo
adb shell
su
mount -w -o remount /system
cd /sdcard/kingo
cp ./su /system/xbin/daemonsu
fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so
with adb window still open, run PC program and remove root
then
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
./step1.sh
got some errors
then sideload the supersu apk via ES file explorer
then allow supersu to do it thing and reboot.
Now I have supersu running!''
edit:
but do I have root?
Titanium backup still fails but ultra explorer does say it has root
now adb shell su fails.....
chemie99 said:
I have made progress...with kingo install I did this:
copy the files of the kingo root removal to sdcard/kingo
adb shell
su
mount -w -o remount /system
cd /sdcard/kingo
cp ./su /system/xbin/daemonsu
fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so
with adb window still open, run PC program and remove root
then
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
./step1.sh
got some errors
then sideload the supersu apk via ES file explorer
then allow supersu to do it thing and reboot.
Now I have root with supersu!
Titanium backup still fails but ultra explorer does say it has root
Edit: hmmm..
now adb shell su fails.....
Click to expand...
Click to collapse
I cannot run the step1.sh, still show permission denied.
I tried manually, but got another permission error...
[email protected]:/sdcard/Kingo # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # daemonsu -d &
[1] 8434
[email protected]:/sdcard/Kingo # ./step1.sh
sh: ./step1.sh: can't execute: Permission denied
[1] + Done daemonsu -d
126|[email protected]:/sdcard/Kingo # cp ./su /system/xbin/su
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/ku.sud
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/supolicy
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo #
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device.
Supersu does manage to install itself but root checker still says I do not have root.
chemie99 said:
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device
Click to expand...
Click to collapse
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
phpbb88 said:
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
Click to expand...
Click to collapse
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
chemie99 said:
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
Click to expand...
Click to collapse
Kingoroot PC asked me to grant root access to it by pressing OK on my device's pop up when my device is under root,
but my device wouldn't show anything.
Is there any problem on fire OS that wouldn't show this pop up?