G'day,
I've tried to root a 8" PendoPad 4.1.1, but hit a snag. I've root access when using "adb shell", but when running applications such as "ROM Toolbox Lite" on the tablet, they complain about not getting root access, although "Superuser" is installed.
What is the mechanism for applicatons running on Android to gaining root access? My understanding is that this is done by the "Superuser" application. What am I missing? My goal is to have this table dual boot Android/Linux.
I would appreciate any help and pointers to appropriate documentation to solve this riddle.
cheerio Berndt
Sysinfo:
======
8 PendoPad 4.1.1
Model MR18
Android Version 4.1.1
Kernel Version 3.0.8+ SMP PREEMPT
Build Number rk30sdk-eng 4.1.1 JR003H 20130108.130525 release-keys
Try to update the su binary for superuser. Also you can try re-rooting you device. The issue may be due to improper root also
anthonythangaraj said:
Try to update the su binary for superuser. Also you can try re-rooting you device. The issue may be due to improper root also
Click to expand...
Click to collapse
Checked that su is installed, see below
[email protected]:/ # ls -l /system/xbin/su*
-rwsr-sr-x root root 22364 2012-01-03 08:23 su
[email protected]:/ # su -v
3.0.3.2
Version of Superuser application is 3.1.3
barossa said:
Checked that su is installed, see below
[email protected]:/ # ls -l /system/xbin/su*
-rwsr-sr-x root root 22364 2012-01-03 08:23 su
[email protected]:/ # su -v
3.0.3.2
Version of Superuser application is 3.1.3
Click to expand...
Click to collapse
Ok, I believe to have progressed somewhat. It appears I can place the device into bootloader mode using
adb reboot-bootloader
The device reboots into what I presume bootloader mode, althought the screen stays dark, but
the device number changed from 2207:0010 to 2207:300a. I've added this ID to /etc/udev/rules.d/51_android.rules, but fastboot doesn't see the device. Any other ideas?
Solved the SuperUser issue by using "bin4ry" instead of SuperOneClick. I now have full SuperUser access on the PendoPad.
Ubuntu is running in an chrooted environment withing Android. Next step is to find a procedure that shows me how to install Ubuntu on this device.
Just purchased a Pendopad 8" PNDPP8MT8.
To get 'Root' access, bin4ry worked for me and I also have google play installed (ditched 1Mobile Market) and CWM Recovery 6.0.3.1 running. I don't cook ROMs so this is as far as I go.
pbezza said:
Just purchased a Pendopad 8" PNDPP8MT8.
To get 'Root' access, bin4ry worked for me and I also have google play installed (ditched 1Mobile Market) and CWM Recovery 6.0.3.1 running. I don't cook ROMs so this is as far as I go.
Click to expand...
Click to collapse
How did u do that. I've got root but can't get gapps installed.
Sent from my PNDPP42DG10BLK using xda app-developers app
re-install superuser flashable zip from recovery.
Related
I recently won this developer tablet and I can't seem to get on-device root access. It came with su binaries installed. (very old ones but I updated it) It also has an unsecured kernel because ADB always runs as root. However I installed superuser and it can't get root access and when other apps attempt root access something seems to be denying access before the superuser prompt is even able to come up. Just curious if anyone has any ideas??
JBO1018 said:
I recently won this developer tablet and I can't seem to get on-device root access. It came with su binaries installed. (very old ones but I updated it) It also has an unsecured kernel because ADB always runs as root. However I installed superuser and it can't get root access and when other apps attempt root access something seems to be denying access before the superuser prompt is even able to come up. Just curious if anyone has any ideas??
Click to expand...
Click to collapse
This may seem like a stupid suggestion but I suppose you could try uninstalling the superuser app and use Chainfire's Super SU app to see if that might make any difference.
Tried that too lol. I was even able to go into old su app and toggle permission for super su to allowed and it still said fail when it tried to update binary. Thanks for the suggestion though. It seems to me the problem is that the chown and chmod commands are not sticking on the su binary. They appear to work but the actual ownership and permissions of the file don't change. Even when I do adb remount first.
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
JBO1018 said:
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
Click to expand...
Click to collapse
One way to get your games to work would be try side loading the Modern Combat 3 and Nova 3 APK's onto the device and installing them manually that way. Another way if that doesn't work is you could try modifying your build.prop and changing your product id to match the galaxy nexus that way the play store will think your on a galaxy nexus and it should say that the games are compatible then.
JBO1018 said:
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
Click to expand...
Click to collapse
I know this is an older post but I'm at the same point where I can't figure out how to allow superuser access. I'm using the 8064 for research and I need the root access but can't seem to figure out how to update the SU. Any tips?
mcforan said:
I know this is an older post but I'm at the same point where I can't figure out how to allow superuser access. I'm using the 8064 for research and I need the root access but can't seem to figure out how to update the SU. Any tips?
Click to expand...
Click to collapse
Do you have the Superuser.apk app installed along with the SU binary in the correct place /system/bin as mentioned by JBO1018? If you already had working root access before on the device and just need to update the SU binary you can open the Superuser app, then go under the info tab and tap on the SU binary version number this should then check for updates and then ask you if you want to install any found updates.
shimp208 said:
Do you have the Superuser.apk app installed along with the SU binary in the correct place /system/bin as mentioned by JBO1018? If you already had working root access before on the device and just need to update the SU binary you can open the Superuser app, then go under the info tab and tap on the SU binary version number this should then check for updates and then ask you if you want to install any found updates.
Click to expand...
Click to collapse
I have both the Superuser.apk and SU binary in the right place. Each time I open up an app that needs root access a toast message pops saying that the app has been denied Superuser permissions. I tried restarting both apps but its not working.
mcforan said:
I have both the Superuser.apk and SU binary in the right place. Each time I open up an app that needs root access a toast message pops saying that the app has been denied Superuser permissions. I tried restarting both apps but its not working.
Click to expand...
Click to collapse
Try going into the Superuser app and under settings and then security the default behavior is set to prompt not deny.
Sent from my SCH-I535 using xda premium
join have a tablet TIR 8960 is preloaded with windows rt, tablet says about the problems of the system,
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
ToBe_HH said:
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
Click to expand...
Click to collapse
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
sangalaxy said:
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
Click to expand...
Click to collapse
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
I don't think you can root without any pc
If your phone has recovery just flash the root files :thumbup:
Sent from my Xperia Live with Walkman using xda app-developers app
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
Have you tried looking in /system/bin/su instead of /system/xbin/su
If you was one of those who root their devices by using KingRoot App and would like to remove kinguser and related files, you can replace it with the well known SuperSU.
Here's a small script to remove Chinese kingruser, all related files and folders, and install SuperSU.
This script will do all the work for you without using PC, just by terminal, first of all, thanks to chainfire for his SuperSU files.
Before starting :
Download and install Terminal emulator appTerminal emulator app
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download and unzip "Replace_Kingroot_With_SuperSU.zip
http://tiny.cc/fo78zx
Steps :
Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
Open Terminal emulator and type :
"Su" (without "")
Allow root permission
Type :
" sh /sdcard/mrw/root.sh" (without "" , notice there's space between sh /sdcard.)
It might display some error, but wait for 30-40 seconds and at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Done !
I ran the script and it went thru to installing Super Su but I lost root and couldn't update binaries. I redownloaded King Root and opened it and I instantly had root back. Are there other files that King Root has installed that don't allow this script to work. If you have any insight it wouldbe appreciated. I know I am on a different phone but script seems to work up to a point. ZTE Z820 Android 5.1 Thanks
I can confirm this method works on Lenovo Vibe X2 running Android 5.0. New Kingroot 4.5, the one with crown icon, successfully replaced by SuperSU while root status remain intact. A process crashed upon Kingroot removal, however restart seemed to get rid of the problem.
Peacekeeper888 said:
I can confirm this method works on Lenovo Vibe X2 running Android 5.0. New Kingroot 4.5, the one with crown icon, successfully replaced by SuperSU while root status remain intact. A process crashed upon Kingroot removal, however restart seemed to get rid of the problem.
Click to expand...
Click to collapse
May I ask did you have busybox already downloaded and installed? I see that the zip contains busybox as one of the actions of the script. Maybe that's why it didn't work for me?? Also I have Kingroot 4.9.2 and I'm thinking that is the main reason the script fails for me.
Jsmor1313 said:
May I ask did you have busybox already downloaded and installed? I see that the zip contains busybox as one of the actions of the script. Maybe that's why it didn't work for me?? Also I have Kingroot 4.9.2 and I'm thinking that is the main reason the script fails for me.
Click to expand...
Click to collapse
I had KingRoot v.4.85, on a KitKat 4.4.
The script didn't work, so I plug the phone and connected to the computer, opened a console, executed the adb shell command and start to give each of the script commands manually one by one.
The failure was at pm uninstall com.kingroot.kinguser (com.kingroot.RushRoot wasn't installed anyway).
The packet manager wasn't able to uninstall Kingroot. I had to uninstall manually using the phone
Code:
H:\Development\adt-bundle-windows-x86-20140702\sdk\platform-tools>adb shell
[email protected]_z10:/ $ su
[email protected]_z10:/ # mount -o rw,remount /system
[email protected]_z10:/ # am kill com.kingroot.RushRoot
[email protected]_z10:/ # pm uninstall com.kingroot.RushRoot
Failure
[email protected]_z10:/ # am kill com.kingroot.kinguser
[email protected]_z10:/ # pm uninstall com.kingroot.kinguser
Failure
In the end the replacement was successful
details of manual uninstall
halnovemila said:
I had KingRoot v.4.85, on a KitKat 4.4.
The script didn't work, so I plug the phone and connected to the computer, opened a console, executed the adb shell command and start to give each of the script commands manually one by one.
The failure was at pm uninstall com.kingroot.kinguser (com.kingroot.RushRoot wasn't installed anyway).
The packet manager wasn't able to uninstall Kingroot. I had to uninstall manually using the phone
Code:
H:\Development\adt-bundle-windows-x86-20140702\sdk\platform-tools>adb shell
[email protected]_z10:/ $ su
[email protected]_z10:/ # mount -o rw,remount /system
[email protected]_z10:/ # am kill com.kingroot.RushRoot
[email protected]_z10:/ # pm uninstall com.kingroot.RushRoot
Failure
[email protected]_z10:/ # am kill com.kingroot.kinguser
[email protected]_z10:/ # pm uninstall com.kingroot.kinguser
Failure
In the end the replacement was successful
Click to expand...
Click to collapse
I have rooted my phone (Android 5.1) with kingroot 4.8.0, I also want to remove KingRoot and replace it with supersu.
I plan to execute the script line by line via an ssh session as root on my phone.
finally how have you uninstalled Kingroot manually ?
fabp said:
I have rooted my phone (Android 5.1) with kingroot 4.8.0, I also want to remove KingRoot and replace it with supersu.
I plan to execute the script line by line via an ssh session as root on my phone.
finally how have you uninstalled Kingroot manually ?
Click to expand...
Click to collapse
I modified the script in this way:
After
Code:
pm uninstall com.kingroot.kinguser
I've added
Code:
am start -a android.intent.action.MAIN -n com.buak.Link2SD/.Link2SD
echo "Press any key to continue"
read typedkeys
The first of the three added rows launches Link2SD app (that I've installed on my phone since I rooted it); the last line pause the script execution.
I used Link2SD to uninstall Kingroot.
Anyway I have to say that, even though the installation of SuperSU seems completed without errors, the apps that asks for root permissions didn't receive the answer from SuperSU and they aren't granted root permission, so... it still doesn't work.
it did not work, superSU can not update binary and can not uninstall the other root app (kingroot)
guys,I am telling you a working method which worked for me..
but you are going to need some version specific apps for first time..
things you need...
1. clean MICROMAX a311
2. kingoroot KingRootSetup_v3.2.0.1129 (i can upload it if you want)
3. Supersume.apk {MUST BE VERSION 6.4} (application used to change from kingroot to supersu)
note -- Pay attention to versions,messing with them will not allow you to achieve target.
steps..
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
[email protected]_Rocker said:
guys,I am telling you a working method which worked for me..
but you are going to need some version specific apps for first time..
things you need...
1. clean MICROMAX a311
2. kingoroot KingRootSetup_v3.2.0.1129 (i can upload it if you want)
3. Supersume.apk {MUST BE VERSION 6.4} (application used to change from kingroot to supersu)
note -- Pay attention to versions,messing with them will not allow you to achieve target.
steps..
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
Click to expand...
Click to collapse
Hello can someone give me a link to supersume 6.4apk please
Thanks
2010radams said:
Hello can someone give me a link to supersume 6.4apk please
Thanks
Click to expand...
Click to collapse
sure....it will be my pleasure.
ok !
download from attachment and install,then get rid of kinguser...:good:
[email protected]_Rocker said:
sure....it will be my pleasure..BTW it can be used on ANY phone to replace kinguser with supersu..
ok !
download from attachment and install,then get rid of kinguser...:good:
Click to expand...
Click to collapse
Just used this solution on a Vodafone Tab speed 6 (VF-1397).
Seemed to work fine but after updating superSU and rebooting the Tablet, screen went black when boot reached unlock screen and couldn't see or do anything except using the power button options.
After some reboots (lost count, ~5/6, and failed atemps to enter recovery), (and the removal of the sim card) the tablet finaly started to optimize all my apps as if the dalvik cache had been wiped.
Afterwards screen went black again and couldn't do anything again.
After some time was finaly able to enter recovery and i'am now trying to format everything.
Subray said:
Just used this solution on a Vodafone Tab speed 6 (VF-1397).
Seemed to work fine but after updating superSU and rebooting the Tablet, screen went black when boot reached unlock screen and couldn't see or do anything except using the power button options.
After some reboots (lost count, ~5/6, and failed atemps to enter recovery), (and the removal of the sim card) the tablet finaly started to optimize all my apps as if the dalvik cache had been wiped.
Afterwards screen went black again and couldn't do anything again.
After some time was finaly able to enter recovery and i'am now trying to format everything.
Click to expand...
Click to collapse
Sorry to hear that...
can you tell how you were UPDATING supersu ??
i also updated from 2.4.5 to 2.6.5 without any problems...
were you using genuine zip of supersu meant for your device ??
or just regular zip ??
don't you have backup of your tab....you were rooted..
1st thing you were to do was to make a full backup...why didn't you did that ??
Script didn't work for me, tons of errors because the path wasn't right. Fixed it to have exactly the same but still plenty of errors and SU binary would not update.
That supersume.apk thing though... MAGIC!!
Thanks heaps!!!
Device reboots
Any idea why the device reboots when I press enter at the last command? I did everything correctly, step by step like you describe it but instead of replacing the KingRoot with SuperSu the device reboots and the KingRoot is still there.
The device is Sony Xperia SP (C5303)
Any help would be great cause I used the exact same method some time ago in my tablet (Lenovo A8) and it worked perfectly. But not in the Xperia and I don't know if I should fully unroot it and try a different method or what.
Sahilsinghlodhi said:
If you was one of those who root their devices by using KingRoot App and would like to remove kinguser and related files, you can replace it with the well known SuperSU.
Click to expand...
Click to collapse
All is done how you describe, everything was just fine and now I have a Lenovo S850 with android 4.4.2 rooted with SuperSU Free 2.78
Thanks a lot.
Does it also work with Kingsroot 5?
Lemmi1 said:
Does it also work with Kingsroot 5?
Click to expand...
Click to collapse
I tried on kingroot 5, no success then unistall kingroot and try kingroot 4.9, again same errors.
It worked for me for kingroot 5.0 on lyf flame 8 through emulator method.
Sent from my SM-G900H using Tapatalk
I tried on kingroot 5 oppo f1s anf failed. Then tried kingroot 4.9 failed. Then tried kingroot 4.81 and super sume pro.. Works like a charm.
Hello community,
I'm new in the forum, It's 2 days I'm fighting with this problem: I want to root my BlackPhone 2 using TWRP and SuperSU (I think that this is the only method that works with BP2, since KingoRoot and others are patched for security)
I flashed the recovery TWRP, then I tried the following SuperSU versions:
SR3-SuperSU-v2.79-2017...zip
BETA-SuperSU-v2.74-2.zip
SuperSU-v2.79-2016...zip
UPDATE-SuperSU-v2.79-2016...zip
None of them works, in TWRP all goes OK, no errors and no warnings, but then when I open SuperSU apk it says "There is no SU binary installed... ...If you just upgraded to Android 5.0".
This is really crazy because I'm running on Android 6.0.1 (Silent OS 3.0.7) and using Total Commander I can see /su directory.
Using a root checker app it says that my device is not rooted, but the SU binary is present and also the busybox one.
The Silent Circle's Security Center in their "Privacy Meter" app warns me "Security alert, active root access detected! ...."
For install TWRP I had to switch these things on in Developer Options: "OEM unlocking", "USB debugging", then I enabled installs from unknown sources by ADB and SD card.
Any help will be great, Thanks guys
EDIT: sorry for the Thread title, I can't modify it, it should be SuperSU not sudo su (too much linux)
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
RAZERZDAHACKER said:
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
Click to expand...
Click to collapse
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Unfortunately they are in the same situation. But I admit that I did not install the TWRP permanently due to a possible bootloop phone. Has anyone found a solution to the root?
i have same problem i want unlock bootloader .............need help plz!!!
Koskha said:
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Click to expand...
Click to collapse
After you flashed the su zip, did you get the superuser app?
Blackphone 2 bootloader
RAZERZDAHACKER said:
After you flashed the su zip, did you get the superuser app
phone not flash with any file.....devices lock ....need to bootloader unlock.
Click to expand...
Click to collapse
A litle guide to increase bp2 performance
https://forum.xda-developers.com/an...e-make-bp2-t3735815/post75218344#post75218344