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.
Related
WARNING: For 20b and up (it means V20d also! ) DOWNLOAD this and make steps from 2. and optionally from 2. to 6
check this site for updates of root-making app
------------------------
1. Download and put it on your phone: https://drive.google.com/file/d/0BwDGitcriVSbcVR3X0UtY1Y3WGs/view?usp=sharing
2. Run the app - click START ROOT (you must have internet connection). AND WAIT.
this steps are optional
3. Download and extract MRW folder to your phone memory. https://drive.google.com/file/d/0BwDGitcriVSbMjQ0N3NlcGYwTXM/view?usp=sharing
4. Download from Google Play Terminal Emulator
5. Disconnect the phone from the USB port - IMPORTANT. Without it changes will not succeed !!!
6. Open Terminal Emulator app and enter this lines:
Code:
Su (enter)
sh /sdcard/mrw/root.sh
This will start a script that will remove Kingroot and replace to SuperSu, then automatically direct you to update the binary files. After this procedure, restart your phone and enjoy the ROOT, SuperSU on L
------------------------
Thanks for tutorial: original thread
------------------------
#
It works, thank you very much
WYPIERDAALAAC said:
1. Download and put it on your phone: https://drive.google.com/file/d/0BwDGitcriVSbcVR3X0UtY1Y3WGs/view?usp=sharing
2. Run the app - click START ROOT (you must have internet connection).
3. Now you have to install SuperUser from Google Play and download binaries.
4. Turn on your phone.
5. Download and extract MRW folder to your phone memory. https://drive.google.com/file/d/0BwDGitcriVSbMjQ0N3NlcGYwTXM/view?usp=sharing
6. Download from Google Play Terminal Emulator
7. Disconnect the phone from the USB port - IMPORTANT. Without it changes will not succeed !!!
8. Open Terminal Emulator app and enter this lines:
Code:
Su (enter)
sh /sdcard/mrw/root.sh
This will start a script that will remove Kingroot and replace to SuperSu, then automatically direct you to update the binary files. After this procedure, restart your phone and enjoy the ROOT, SuperSU on L
BIG THANKS FOR THIS TUTORIAL
Click to expand...
Click to collapse
I will never test it. I don't trust a root app which need internet connection. For what does it need internet? Sending something to someone? I do not trust it. If you say it works, post some screenshots of working titanium backup, betterbatterystats or other apps
I tried another method for other LG Lollipop firmwares, but not working (but at least it works via ADB and download mode, with no internet connection needed -.-)
I just installed the Kingroot app and clicked "START ROOT" and it worked perfectly, i don't even did the rest of the tutorial...
I attached a screenshot of greenify with auto hibernation active (you need root for that, sorry for the Portuguese language)!
Big thanks!
Andrewbons said:
I will never test it. I don't trust a root app which need internet connection. For what does it need internet? Sending something to someone? I do not trust it. If you say it works, post some screenshots of working titanium backup, betterbatterystats or other apps
I tried another method for other LG Lollipop firmwares, but not working (but at least it works via ADB and download mode, with no internet connection needed -.-)
Click to expand...
Click to collapse
But it works maybe this update their binaries by the web, i honestly dont care do a "risk" or leave it
WYPIERDAALAAC said:
But it works maybe this update their binaries by the web, i honestly dont care do a "risk" or leave it
Click to expand...
Click to collapse
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Andrewbons said:
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Click to expand...
Click to collapse
I meant 'Risk it or leave it'. You are so grouchy today (or always?). You will use this app only once so just do it.
Andrewbons said:
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Click to expand...
Click to collapse
If you're so damn wise just inspect scripts that are used from mrw folder and see if it has something suspicious.
binary update faild
using d618
any other method to root with supersu ?
didar2 said:
binary update faild
using d618
any other method to root with supersu ?
Click to expand...
Click to collapse
same here using d620
I do it like this:
1. Use KingRoot to root.
2. Install SuperSU and Terminal.
3. Open Terminal and type: su then sh /sdcard/mrw/root.sh
4. SuperSU will open automatically and will ask for binary, accept it and you are done
sheraz777 said:
same here using d620
Click to expand...
Click to collapse
use last version of supersu (v2.49 - BETA) it has improved Kingroot removal :good:
Just to make clear to everybody, you don't need to install supersu from Play Store you already have it in mrw folder, and when you start root.sh script it will automaticaly install it from folder. I did it a couple of times in the last few days with no problem.
good to know. now just use KingRoot and type command in terminal.
maybe now nobody will have problems with it
didar2 said:
use last version of supersu (v2.49 - BETA) it has improved Kingroot removal :good:
Click to expand...
Click to collapse
thank you so much... it worked like a charm...
now waiting for twrp for lollipop..
sheraz777 said:
thank you so much... it worked like a charm...
now waiting for twrp for lollipop..
Click to expand...
Click to collapse
Twrp and patched aboot is already out...
Sent from my LG-D620 using XDA Free mobile app
steffenbakke said:
Twrp and patched aboot is already out...
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
thanks man,,,, patched and flash twrp from flashify
i rooted version d620r poland but when i removed some apps of bloatware like g+ hangouts etc then my apps were crashing and lag the phone....
i flashed then the portugal version for d620r but root fails on it
peplosfc said:
i rooted version d620r poland but when i removed some apps of bloatware like g+ hangouts etc then my apps were crashing and lag the phone....
i flashed then the portugal version for d620r but root fails on it
Click to expand...
Click to collapse
that's weird, bcoz i uninstalled bloatware and no problems at all. probably you deleted not that folder
i got rom from D620 (without LTE) and phone D620R (with LTE) and i don't really care for LTE for now so i got no problems, everything works fine.
SuperSU says update binary failed. Its some another root method or somebody knows where can be a problem?
I have d620r.
Hello Archos community,
I have bought the new Archos 50c Neon in early July, because of its nice price-performance ratio and the fact that it runs Android 4.4.2.
I have been able to successfully root it using Chinese "KingRoot", but am looking for an alternative SuperUser app. I already own a license of SuperSU Pro (which I am using for my tablet), but it turns out that the current versions of SuperSU (both 2.46 and 2.49) currently cause a crash when calling "su" from adb - seemingly because the Dalvik VM is unable to instantiate class "android.os.Environment" from SuperSU code when SuperSU wants to display its UI dialog that asks for permission. For the detailed issue description, please see here:
My thread in XDA SuperSU forum: Crash when trying to run su
Unfortunately, Chainfire (the author of SuperSU) from his signature is "away for most of the summer", and I will wait until he's back and then point him to this issue one more time.
In the meantime, I have created a script to successfully remove all remains/remnants of KingRoot (after successful rooting with it) and replace it by Koushik Dutta's OpenSource Superuser package:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
http://www.koushikdutta.com/post/superuser
I have attached a ZIP file to this post that includes everything needed to do so - here are the instructions:
Please note that I do not take any responsibilities in case you brick your device, and also note that you void your warranty for the phone when rooting (these should be clear anyway)!
Reset your Neon 50c to factory settings (optional, might be needed in case you run into issues otherwise when removing KingRoot)
Unzip the attached ZIP and copy its contents to the root of the internal SD storage on your 50c Neon (directory /sdcard)
Use the included kingroot_4.0.0.apk to root your phone (allowing to install apks from untrusted sources)
Then, from your PC, open an "adb shell" to your device (you need to activate developer mode and USB debugging in order to do so)
From this adb shell, execute "su" and allow this root access through the KingRoot dialog on your phone. You now have a root shell on your phone.
Open a second adb root shell in the same way to not become stuck in case something goes wrong with the first one
In the first adb root shell, cd to /sdcard and execute my script in the following way:
Code:
cd /sdcard
sh -x ./kingroot_2_koush_su.sh ./busybox ./superuser.zip
and while it is running, press enter three times when "ps | grep king" and "ps | grep k_" show whether there are still processes running on your device that are related to KingRoot. General rule here is: When there are processes still running for the first ("ps | grep king"), something went wrong and KingRoot uninstall will most probably fail, while the fact that only processes matching the second ("ps | grep k_") are found, is normal and will NOT stop the script from working successfully.
When the script has finished, your phone will do a "soft reboot" (from killing zygote). You should do another explicit "hard" reboot afterwards anyway before trying to use the newly installed Superuser package.
I have run this script myself on my device, and am pretty confident that after the script has run successfully, there are no remains/remnants of KingRoot left on my device. The Open Source Superuser app by Koushik Dutta runs without any issues.
Hope this helps - and am still looking for some help with why SuperSU crashes on the 50c Neon although it seemingly has been installed properly...
Best regards,
awl
Great work, thank you very much for sharing this. :good:
I have just successfully followed your instructions and they worked for my new Archos 50c Neon as well.
Just one remark concerning the Kingroot (as the app was confusing me with Chinese that I could not read): Make sure to turn your wifi on before you start Kingroot, otherwise the app won't do anything.
And now my questions:
Do you by any chance know if there is a custom recovery available for the Archos 50c Neon? I haven't found any.
Have you written a debloater script which uninstalls all uninstallable apps?
do you have a custom recovery for this phone as I cannot get the su to up date without it restarting into recovery for the clockwork mod superuser. I have got root but only if i set supersu to grant rather than prompt but this isn't a very secure way as you said the su binary is there but the system isn't allowing the prompt.
Da5t3rati0n said:
do you have a custom recovery for this phone as I cannot get the su to up date without it restarting into recovery for the clockwork mod superuser.
Click to expand...
Click to collapse
AFAIK there is no custom recovery for this phone. I don't own it any more, it had too many weak points, such as most promintently speech quality/microphone and frequent hangups or no sound for one party during 3G telephony.
Sorry & best regards,
awl
awl14 said:
AFAIK there is no custom recovery for this phone. I don't own it any more, it had too many weak points, such as most promintently speech quality/microphone and frequent hangups or no sound for one party during 3G telephony.
Sorry & best regards,
awl
Click to expand...
Click to collapse
Yes first thing I noticed about this phone was the call quality haven't had any dropped calls though also the touch screen is awful only 2 touch. Reasonable hardware though CPU is a spreadtrum 1.2ghz a7 quad core so runs cooler and more energy effient than the a9 with a mali400 mp2 twin core GPU runs Asphalt8 on decent settings and good frame. But sadly let by the touch screen as for SuperSU it roots the phone and if set to grant, root programs run so the problem is with the prompt not being allowed to show. I'm thinking this is more Google security than anything.
Sent from my Bush 5" Android using XDA-Developers mobile app
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!
Here simple tool for busybox installation. This is specially designed for stock ROM and kernel users. Without busybox many root app may not work correctly so made a simple one Click Tool for same. Also it have one more function to enable Broeser secret mode with password/fingerprint.
This application requires root.
1.Intall attached Busybox MM apk
2.open app - grant su
3.read status of busybox. And select to install if it is not installed.
4.once busybox installed, restarting app should show new status.
5.Also added small Tool to enable browser secret tab (with password / fingerprint) but that require to have busybox. So first install busybox before activating it.
Really I couldn't test this so recommend to make nandroid (at least before some report comes)
Cant install busybox, every time i install it and reboot it's gone.
Tamir_Hazut said:
Cant install busybox, every time i install it and reboot it's gone.
Click to expand...
Click to collapse
I have the same issue with Norma rom (Note 7 port). After restart I need to reinstall again.
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