hi guys
i rooted my phone but unfortunately i can only use it in ro mode and i can not change to rw does anyone know what to do?
root method:magisk v23
recovery: orange and twrp
rom build:12.5.8
file manager:root explorer and es file manager
We can either try doing modification in recovery or use a magisk module which points to required location in system
Related
Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!
Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root
Stay with magisk, it is better than SuperSU
PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !
Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob
SM-A520F flashed with Russian (SER) 7.0 A520FXXU2BQH4_A520FOXE2BQG7
Rooted with with SuperSU
Steps followed in TWRP:
1. Factory Reset (To start fresh)
2. Flashed no-verity-no-encrypt_ashyx
3. Format data
4. Flashed SR3-SuperSU-v2.82-SR3-20170813133244.zip
5. Reboot
Root checker shows Rooted.
However, it isnt properly rooted , it seems, because:
1. AdAway shows a *SU Binary Could not be found*
2. ES File Explorer 's Root explorer isn't working: *Sorry, test failed* message pops up.
Any idea how to get properly rooted?
EDIT:
More info: It seems the root is working for certain apps like Droidwall which I use to block internet access.
The system is not properly Writable (has read access only) which is causing the issue with some root apps. So, I guess I need a solution to make the System Writable.. Help?
Hi, I have the same problem on Italy ITV Nougat.
The phone seems to be rooted ("Check Root" give sucessfully rooting), but when I try to delete app from "App Remover Root" it doesn't work and the same if I try to uninstall/delete the apk from ADB.
Any idea?
Hi,
I'm running CyanogenMod13 on my galaxy S4 with TWRP 3.1.1.0 and I wanted to flash XPosed. The xposed page says that it's only compatible with SuperSU so I installed latest Stable SuperSU 2.82 and deactivated root access on CM13 in developer options. Then I tried flashing Xposed framework zip but it complained about /system beeing a read-only file system and I realized that TWRP didn't ask me anymore if I want read-only file system (which it always did before I installed SuperSU) anymore. Looking into "Mount" I see that "system" is not mounted by default but also making a checkbox there doesn't change anything even if "Mount system read-only" is not checked. BTW: Do I have to apply the mounts somehow or is activating the "checkbox" actually enough. Maybe my problem is just that system is not mounted r/w which is my current guess but I don't know how to mount it r/w now that SuperSU is installed.
Then I though, ok if mounts are incorrect in TWRP let's use FlashFire. So I selected to mount system r/w in option for flashing and started the flash. Again even if I selected mount system partition r/w flashfire reported read-only file system. I also tried downgrading to SuperSU 2.79 but same effect.
What the hell is going on since I flashed SuperSU. Is my root now partially broken? The Apps all are working fine, it's just modifying system partition is somehow not possible neither in TWRP nor FlashFire....
Any help or insight will be greatly appreciated.
marcelser said:
Hi,
I'm running CyanogenMod13 on my galaxy S4 with TWRP 3.1.1.0 and I wanted to flash XPosed. The xposed page says that it's only compatible with SuperSU so I installed latest Stable SuperSU 2.82 and deactivated root access on CM13 in developer options. Then I tried flashing Xposed framework zip but it complained about /system beeing a read-only file system and I realized that TWRP didn't ask me anymore if I want read-only file system (which it always did before I installed SuperSU) anymore. Looking into "Mount" I see that "system" is not mounted by default but also making a checkbox there doesn't change anything even if "Mount system read-only" is not checked. BTW: Do I have to apply the mounts somehow or is activating the "checkbox" actually enough. Maybe my problem is just that system is not mounted r/w which is my current guess but I don't know how to mount it r/w now that SuperSU is installed.
Then I though, ok if mounts are incorrect in TWRP let's use FlashFire. So I selected to mount system r/w in option for flashing and started the flash. Again even if I selected mount system partition r/w flashfire reported read-only file system. I also tried downgrading to SuperSU 2.79 but same effect.
What the hell is going on since I flashed SuperSU. Is my root now partially broken? The Apps all are working fine, it's just modifying system partition is somehow not possible neither in TWRP nor FlashFire....
Any help or insight will be greatly appreciated.
Click to expand...
Click to collapse
Try my SuperSU systemmode from here.
Thanks for the link and it also gave me hint what to google for. It seems that my SuperSU is running in systemless mode, so I would need Systemless Xposed too. Unfortunately this also requires Magisk to be installed and Magisk doesn't work with adoptable storage which I can not live without. So I will give your SuperSU version a try and run it in System Mode and try to install official xposed too. Hopefully this works.
Edit:
I had a hard-time switching from systemless mode to system mode cause you have to completely unroot and restore the patched boot image fully (just un-rooting and restoring doesn't do the trick) fortunately I had a nandroid backup from prior to rooting with untouched backups of "boot" and "system" which I could restore. Finally I was able to install the system mode SuperSU (although I didn't use your package, but created a .supersu file with SYSTEMLESS=false) and flashed it.
This now enabled me to run latest Xposed in system mode which was failing when trying to flash in systemless mode. I would have needed magisk (which is incompatible with adoptable storage) to run it systemless. I tried using the old 86.2 systemless xposed but that always resulted in a boot loop whenever I activated one of the xposed modules). Now it's working fine., Thanks for the hint ho led me find out what system mode and systemless really is.
So actually my problem is solved, just couldn't find out how to edit the thread title....
Hi everyone. So like the title says I finally got my P10 running EMUI 9.0.1.186 and got the pie version of Resurection Remix installed and working smoothly. So now I am trying to get root back which is annoying because currently there is no TWRP for EMUI 9+. So I followed the tutorials on installing magisk without custom recovery using the recovery_ramdisk partition which I finally did get figured out.
What I did:
I downloaded stock firmware (Exact same version as the one installed on my phone) and then extracted the RECOVERY_RAMDIS file and transffered it to my phone, then in Magisk Manager I installed and selected the option to edit a file. Selected the RAMDIS file and then transffered the file back to computer. I did the fastboot flash of recovery_ramdisk and then reboot my phone and it says installed on both Magisk and Magisk Manager. Safetynet check all green aswell. Basically everything that should be green is. I then installed directly because it gives you that option now and after booting the phone again I tried some root required apps but nothing was asking for root permission and I cant use the apps. In the Supersu section of Magisk Manager there are no apps coming up to allow me to enable supersu for the app or not. I can install Modules though and that does work as I tested it by downloading and installing the busybox static module. I then went to root checker pro and did a check and it says busybox is installed correctly. When I do the check for root status it comes back as follows:
Feedback Mode: Install Root
Issue: Not installed superuser app and su binary, and unable to access root user account.
Feedback: Locate a guide for root installation on a Kirin Treble device.
Stage 1 - Superuser App: Not Installed
NOT installed: SuperSU by chainfire, Superuser by ChainsDD, or Superuser by Koush
Stage 2 Superuser Binary Files: Not Installed
Alternative Location
Command: ls-l /sbin/su
Result: lrwxrwxrwx 1 root root 8 2019-12-29 13:49 /sbin/su-> ./magisk
Version: 20.1:MAGISKSU
Analysis:
The rest of the Alternative Locations came back as "does not exist"
Stage 3 - Root User Account Error
Error: Timeout of 27 seconds on 2 attempts
Optional - ADB Shell User
Status: Checked /default.prop for ro.secure setting: No world/other read access to fault.prop
Additional - SELinux
Status: Unable to determine due to lack of permission, no world/other read access to /sys/fs/selinux/enforce
Please help me figure out why I dont have full root access, Thankyou very much!
(I would also like to note that I did try uninstalling by just restoring the partitions via Magisk Manager Uninstall option and then reinstalling and this time not using the direct install feature and nothing changed)
Hello everyone, I have a problem with root my A33M variant, my problem is that it won't let me mount r/o in root explorer and in any explorer, does anyone else have this problem? I want to debloat
First you have to flash Magisk.zip with your custom recovery to get root succesfully then you can use lucky patcher to debload or uninstall system apps