Hey, guys. Redmi note4x (mido) After installing supersu using twrp to get root successfully, but then I found that using USB to connect the computer has a problem: USB can not be used, connect USB after the phone shows charging. Including USB debugging, mtp can not be used. Is this the reason for the kernel?
Please forgive me for bad English
Wrong place. But I think disabling adb fixes mtp. Not sure. Worth trying though.
Sent from my Redmi Note 4 using Tapatalk
Hawkeye007 said:
Wrong place. But I think disabling adb fixes mtp. Not sure. Worth trying though.
Click to expand...
Click to collapse
All MIUI stable version I have tried, almost all have this problem.
Now I have found a solution: do not use supersu. I downloaded and installed the latest beta magisk su. At present everything is normal, but the shortcomings are obvious. There are a lot of applications can not identify su files. Even if the use of magisk comes with the su get root but still prompted no root privileges. Probably this is the problem of compatibility bars
Andy，xu said:
All MIUI stable version I have tried, almost all have this problem.
Now I have found a solution: do not use supersu. I downloaded and installed the latest beta magisk su. At present everything is normal, but the shortcomings are obvious. There are a lot of applications can not identify su files. Even if the use of magisk comes with the su get root but still prompted no root privileges. Probably this is the problem of compatibility bars
Click to expand...
Click to collapse
No problem just go to /device /system and edit build.prop and add these lines
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
And save then restart also enable USB debugging ,it will solve ur issue.
Related
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.
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.
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable. Instead, I was greeted with the same Error 40 that everyone with a rooted device got. It took me a couple of days of researching and playing and reflashing and..., but I've finally figured out the simple(r) method to bypass this stupid root check for DirectTV Now (AKA Error 40, QP1005)
This applies to the TX5Pro, but it should work on any s905x based AMLogic SoC running Marshmallow 6.0 (A95X, CQ9, TX5, TX3, X96, NEXBOX, +many more.) As I understand it, they all have similar Android builds using the p212 board and firmware. I also have a M8S s812 running Kit-Kat 4.4.2 that I'll work on breaking, next.
First things, first: If possible, find your firmware and do a clean flash. Not a requirement, but if you've been playing with this for a while and you've ended up here, you've probably mucked up your /system files in some way or another. I managed to screw up my su binary location a few times and couldn't get it back without a lot of work. Reflashing was a three-minute, headache-free task.
That said, you'll want to adb over tcp/ip as these devices don't like to play the USB cable game.
Code:
adb connect deviceipaddress:5555
Follow up with
Code:
adb shell
and
Code:
su
to get into a root shell (if you don't get one by default.) Mine came with SuperUser from ClockworkMod preinstalled as a system app. Mount your system folder
Code:
mount -o rw,remount,rw /system
and edit your build.prop file with Vim.
Code:
vi /system/build.prop
If Vim is new to you, search the interwebs for a Vim cheat sheet.
Here's the trick with this... DirecTV Now's shared object file in lib/armeabi/libdrmagent_downloadable_jni.so looks for a few keywords within a few properties. Those properties are:
Code:
ro.build.product
ro.build.tags
ro.build.type
ro.build.display.id
...and the keywords are:
Code:
"release-keys, OnePlus2, OnePlus, Z26CL, STUDIO_C, user" are keywords that it favors, while "cm, cyanogen, cyanogenmod, debug, userdebug, A0001" are disqualifying keywords. Supposedly, "test-keys" is a bad word, too.
In my case, I needed to edit my build.prop to eliminate any sign of the bad words. Example:
Code:
ro.build.display.id=p212-userdebug 6.0.1 MHC19J 20160909 test-keys
to
ro.build.display.id=p212-user 6.0.1 MHC19J 20160909 release-keys
Run through the file and replace anything that says userdebug with user and test-keys with release-keys until you get to "#end build properties" Then save and reboot.
After reboot, install Hide My Root (I used the one from Amphoras) and hide the Su binary. This is where things might be getting tricky for some of you... on the TX5Pro, the SuperUser app is a system installed app, meaning it can't be uninstalled (it can, but it's not exactly a simple task for everyone) so you'll need to go into settings -> apps -> superuser and disable the app from there. Reboot again. Now, with the su binary hidden and the app's manifest not showing up in the system, the error 40 message should go away. This option will allow you to quickly restore su and SuperUser without needing a bunch of additional steps. You'll still need to set the device location service to "battery saving" (or use mock locations) but that's a simple task anyone can figure out.
The app is a choppy on high def feeds for some reason. I can't tell if this is processing/memory issue or a feed (wifi) issue. By default, the app doesn't work on ethernet, meaning you'll have to use wifi until you can fix that issue. But hey, one thing at a time, right? Anyway, I hope this helps anyone with this particular headache.
Thanks for pointing me in the right direction...
Got DirecTV NOW working on my nexus 6 running pure nexus ROM... I just did the edits with super su root and root explorer. Then disabled super su and rebooted.
Now to update the the build.prop files on the lineage os 13.0 nexus 10, and my wife's kltevzw (on ting gsm network) running lineage os 14.1
hi please help i flashed wrong twrp recovery i think now my amlogic smartbox failed to boot in recovery mode and the main problem is my smartbox Encryption Unsuccessful Factory reset, when i click factory reset nothing happend please guide how to solve this
Sent from my SM-N910G using Tapatalk
jameson.donaghy said:
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable.
Click to expand...
Click to collapse
Any chance that you tried this out with Data Free TV/"Sponsored Data" with an AT&T wireless account? i.e. running the box through a Cellular Hotspot or tethered to your phone. I've been looking at if one could use one of therse Android TV Boxes to basically get Data Free TV.
my live tv app detect root try with magisk also but no success in my s905x help me guys
Sent from my SM-N910G using Tapatalk
is anyone help me out
Sent from my SM-N910G using Tapatalk
I edited my build.prop files to try and "hide" the root and I still get the error. I also tried root cloak with xposed and still nothing
Thanks so much
This really helped. I used Xposed module to hide those keywords. Worked a charm!
Hello guys,
Been lurking here for ages and already benefited tons from the help posted here. However, this is one issue that I can't seem to figure out.
I have the MTK variant of the RN4 and I'm trying to enable the Camera2 API so that I can take RAW pictures, use Google HDR+ etc.
I am rooted on MIUI 9 (though as it's MTK, it is still Android 6.0) and I edited the build.prop file using ES Explorer (I added the persist.camera.HAL3.enabled=1 line). I've rebooted the device, used checker apps and Lightroom to check if there's RAW support, but without luck.
Do you guys have any other ideas as to how I can enable Camera2 API support?
I don't have bootloops, I don't have any issues other than the fact that there's no Camera2 API support. Restarting the device does not erase my mods to the build.prop file.
Any help is appreciated!
Forget about it since GCam is supposed to work on Snapdragon devices only.
Kavute said:
Forget about it since GCam is supposed to work on Snapdragon devices only.
Click to expand...
Click to collapse
I wouldn't mind using other apps such as Lightroom if I can get RAW to work. Any ideas as to whether that's possible?
I've had a similar problem before, but MIUI would revert my changes to the build.prop. I solved it by using a systemless root via Magisk.
What I did:
1. Unroot your phone
2. Flash Magisk using TWRP (link to Magisk thread).
3. Download the "camera2api-enabler.zip" from this thread
4. Add the zip (Module) using the Magisk Manager app that comes installed after you flash Magisk
5. Reboot, and you should see the camera2api enabled.
If you do run into a boot loop after installing Magisk, you may need to flash the LazyFlasher zip file after Step 2.
yohyah said:
I've had a similar problem before, but MIUI would revert my changes to the build.prop. I solved it by using a systemless root via Magisk.
What I did:
1. Unroot your phone
2. Flash Magisk using TWRP (link to Magisk thread).
3. Download the "camera2api-enabler.zip" from this thread
4. Add the zip (Module) using the Magisk Manager app that comes installed after you flash Magisk
5. Reboot, and you should see the camera2api enabled.
If you do run into a boot loop after installing Magisk, you may need to flash the LazyFlasher zip file after Step 2.
Click to expand...
Click to collapse
Thank you! I'll look into Magisk. I have to admit that I'm tempted if only to get this and Super Mario Run working.
But I do like having sys root access, I've just fixed the Cell Standby battery drain with an edit to the build.prop file, as MIUI 9 doesn't have the option to disable VoLTE.
So I'll give it a thought.
Thank you! and if anyone has any other tips, preferably something that doesn't alter my setup too much, it'd be ace.
rottensong said:
Thank you! I'll look into Magisk. I have to admit that I'm tempted if only to get this and Super Mario Run working.
But I do like having sys root access, I've just fixed the Cell Standby battery drain with an edit to the build.prop file, as MIUI 9 doesn't have the option to disable VoLTE.
So I'll give it a thought.
Thank you! and if anyone has any other tips, preferably something that doesn't alter my setup too much, it'd be ace.
Click to expand...
Click to collapse
Hi!
If it isn't work, you should try out this:
Go in Engineer mode https://forum.xda-developers.com/showthread.php?t=2313812 or download the Engineer mod apk from play store. (It's working just on stock ROM)
Swipe left to Hardware testing, and there will be the Camera option.
I think, after you find this, you can get through the settings (where will be a raw capture option)
Hey there,
I've rooted my OnePlus 7t Pro with an autoinstall jar, in cause of the twrp isssue (that twrp isn't available yet for android 10)
After doing this root tutorial, my device got rooted and magisk has been installed properly. So today I just thought about changing my
bootanimation like I did several times before, but when I tried to mount System as Read&Write it told me that this is Read only...
So after searching google for hours I maybe found the issue of my problem, because I had activated in Magisk "Preserve AVB 2.0/dm-verity" which helps to prevent
rootkits from breaking into the system. But I also heared that you block to remount your root filesystem with this option. So they told me to run following command:
"adb disable-verity". Buuut I've also read that this will crash my phone and will make it unaccessable. So before I do something weird and regret it after I wanna ask more
experienced people if they can help me..
MrLufus said:
Hey there,
I've rooted my OnePlus 7t Pro with an autoinstall jar, in cause of the twrp isssue (that twrp isn't available yet for android 10)
After doing this root tutorial, my device got rooted and magisk has been installed properly. So today I just thought about changing my
bootanimation like I did several times before, but when I tried to mount System as Read&Write it told me that this is Read only...
So after searching google for hours I maybe found the issue of my problem, because I had activated in Magisk "Preserve AVB 2.0/dm-verity" which helps to prevent
rootkits from breaking into the system. But I also heared that you block to remount your root filesystem with this option. So they told me to run following command:
"adb disable-verity". Buuut I've also read that this will crash my phone and will make it unaccessable. So before I do something weird and regret it after I wanna ask more
experienced people if they can help me..
Click to expand...
Click to collapse
Be for that try this first https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
System is now permanent read only in Android 10,Y ou can't change that.
Best way to change something is a magisk module.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
System is now permanent read only in Android 10,Y ou can't change that.
Best way to change something is a magisk module.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Yeah, you might be right with that, do you have a solution for this issue, because I'm not able to flash my new bootimage via Magisk and I also want a full
file system access again, like I had before