I have K20 pro (Miui 12 Xiaomi.eu 20.6.11) that is rooted with Magisk Ver 20.4
For some reason when I'm trying to go into my root folder I'm getting this message : "Directory is read banned"
Is there any way to solve it and to make the root directory accessible?
Tried with few different file managers but it's always the same result.
Download x-plore file manager from play store, give it root access and you will be able to access root directory.
MnMchill said:
Download x-plore file manager from play store, give it root access and you will be able to access root directory.
Click to expand...
Click to collapse
Thank you. Tried it and it resolved the problem.
Related
I used the automatic method to install root on my Fire HD 7. The issue is that SuperUser has not shown up even after multiple reboots. I've read that I could use ADB to install it manually but I have no idea what commands are needed to push an .APK. I've also ready that ES File Explorer could be used to install .APK's but whenever I click root settings it force closes then says unable to mount upon reopening.
I'm running 7.2.1 if that helps. Can anyone help?
Thanks!
NVM I've figured it out guys! Thanks!
I figured out the UID issue.
You must have a file browser capable of root permissions or know how to use the terminal
Go to /data/system and look for uiderrors.txt
open it and take note of all the files listed in there.
Go into /data/data/ and remove those folders.
Reinstall the apps that were in conflict and everything should be good
The same fix applies for error -24 from the play store when installing apps. The only difference is that the uiderrors.txt will not have the offending files listed. You will need to know the application package name i.e. com.speedsoftware.rootexplorer
KAsp3rd said:
I figured out the UID issue.
You must have a file browser capable of root permissions or know how to use the terminal
Go to /data/system and look for uiderrors.txt
open it and take note of all the files listed in there.
Go into /data/data/ and remove those folders.
Reinstall the apps that were in conflict and everything should be good
The same fix applies for error -24 from the play store when installing apps. The only difference is that the uiderrors.txt will not have the offending files listed. You will need to know the application package name i.e. com.speedsoftware.rootexplorer
Click to expand...
Click to collapse
do you know whats causing this ??
i had this with quadrant everytime i install a new rom or made a fresh install
this time i cant install quadrant standard and the last time i could not install quadrant advance
i cant delete the folder with root explorer ... any help ??
thanks
in adb on android i cant delete this file ... device or resource is busy .... i only can delete it in adb in recovery
is my phone broken (flash memory) or what is causing this ???
B-Man2005 said:
do you know whats causing this ??
i had this with quadrant everytime i install a new rom or made a fresh install
this time i cant install quadrant standard and the last time i could not install quadrant advance
i cant delete the folder with root explorer ... any help ??
thanks
in adb on android i cant delete this file ... device or resource is busy .... i only can delete it in adb in recovery
is my phone broken (flash memory) or what is causing this ???
Click to expand...
Click to collapse
I believe it is being caused by HTC backup restoring app data. You should be able to remove the folder with root explorer as that's what I used.
Sent from my m7 using Tapatalk 4 Beta
You can easily remove that folder when ur using TWRP recovery. In advanced menu is a file explorer. After deleting the folder you can install e.g. quadrant again via playstore
As of this morning, my kindle fire HD 7" was reset back vanilla launcher and un-rooted.
I have re-rooted but keep getting the error "com.estrong..fs.FileSystemException: Permission Denied" whenever I attempt to move my launcher files to system/app
My file explorer has root privileges and I do have my device rooted but it just kind of stumped me.
Does anyone know of a way around this; Has this happened to anyone else within the last 24 hours?
P.S:
My System Version is 7.4.3
File Explorer: ES File Explorer (With all root options selected)
Anyone have any idea?
I still have no idea what's causing the issue.
evildread said:
Anyone have any idea?
I still have no idea what's causing the issue.
Click to expand...
Click to collapse
which method did you used to root kfhd !??
try to root your kf again if the problem is still unresolved !!
first root with restore and after that root with qemu. it's been my way of doing it trough all the amazon updates. it NEVER failed
if you have problems with superSU, just uninstall it and install superuser from market.
phonexpert_alex said:
first root with restore and after that root with qemu. it's been my way of doing it trough all the amazon updates. it NEVER failed
if you have problems with superSU, just uninstall it and install superuser from market.
Click to expand...
Click to collapse
I feel like such an idiot..
It turned out the system folders weren't mounted.. So I was getting denied root access..
I had gotten the new version of ES File Explorer (Which I'm not used too), which was giving me the problems.. So I Downloaded FX File Explorer and saw that it wasn't mounted and just NOW finally found how to mount with ES...
Sorry for the post, I feel so freaking stupid.. =/
Greetings all i want to change my king root v3.4.5 wit hsuper su i installed iroot (vroot) on my pc my phone is samsung GTI8200 i have tried all methods to remove it but it ends up losing my root or nothing happned at all all what i want how to replace king user v 3.4.5 with the latest vesion of super su sorry for my english
thenewscreem said:
Greetings all i want to change my king root v3.4.5 wit hsuper su i installed iroot (vroot) on my pc my phone is samsung GTI8200 i have tried all methods to remove it but it ends up losing my root or nothing happned at all all what i want how to replace king user v 3.4.5 with the latest vesion of super su sorry for my english
Click to expand...
Click to collapse
this method is for vroot but work on kingo
5. Go to play store and install SuperSU.
6. Start SuperSU and you will be asked for permission by ???? 1.0.4, choose ??(means allow). (Should be the right side option.)
7. SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
8. Now,unistall king root with titanium backup
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
9. Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
10. After that, you are rooted with SuperSU and ???? 1.0.4 will not be there anymore.
I HAVE tried this but kinguswe wont let installation successfull always installation failed I have tried to remove
king user with titanium backup but it remove root permission so is there any way else to replace it and thank you
SU
Think I used this method:
1. Download and unzip "Replace_VRoot_With_SuperSU.zip" file
2. Copy the folder "mrw" to phone storage
3. Copy SU. apk to system folder using a root explorer and change permissions to match your other system apps.
4 Reboot and update binaries
5 Remove king user and associated apps.
There is a full instruction set somewhere but I believe that this was my adaptation of the method using only a root explorer. I used Xplore.
themountig said:
Think I used this method:
1. Download and unzip "Replace_VRoot_With_SuperSU.zip" file
2. Copy the folder "mrw" to phone storage
3. Copy SU. apk to system folder using a root explorer and change permissions to match your other system apps.
4 Reboot and update binaries
5 Remove king user and associated apps.
There is a full instruction set somewhere but I believe that this was my adaptation of the method using only a root explorer. I used Xplore.
Click to expand...
Click to collapse
It worked for me on my THL4000. I didn't need step 3, though, as the script, did it for me.
Thanks for sharing!
4.2.2
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.
I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.