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)
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?
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
@rovo89
@topjohnwu
https://www.didgeridoohan.com/magisk/MagiskHelp
I have added much more information.
Reinstall firmware???
LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe
So, I rooted my phone (OnePlus 7 Pro) a few months back and it was working fine before restarting but after that it says in magisk manager: magisk is not installed, trying to install it through "select and patch a file" gets a error: ! unsupported/unknown image format ! installation failed.
I looked from root checker pro and it says my superuser binary files aren't installed? everything else doesn't exist except alternative location which says permission restricted or denied access.
forgot to add
I don't have a "uninstall" button. I can't access Magisk Hide.
Hello! I'm sorry I am pretty confused right now, I installed the November OTA update after uninstalling all Magisk modules, but forgot to disable Magisk Hide. Here are the steps I've taken to try to get root back on my phone:
1. Went to Google's website
2. Downloaded the Factory image for this version of update
3. Extracted the boot.img file and patched it with Magisk 25.2 (25200) (33)
4. Sent back to computer, and opened adb
4. Used "adb reboot bootloader"
5. Tried both "fastboot boot (the patched img)", and "fastboot flash boot (the patched img)"
I got the message
Sending 'boot_a' (65536 KB) OKAY [ 0.412s]
Writing 'boot_a' OKAY [ 0.090s]
Finished. Total time: 0.506s
None of these options seemed to work after the phone restarted however, I tried using the hidden Magisk and it told me to reinstall the app, so I deleted it and reinstalled it from the Magisk github. However, it's still showing "Installed N/A" in Magisk. I'm not sure what to do, may I please have some help haha-
My steps taken on installing the OTA update:
1. Removed Magisk modules (but forgot to turn off Magisk hide!)
2. Tried clicking Uninstall in Magisk and "Restore Image" but was hit with the error ""stock image does not exist."
3. Flashed original boot.img file using FKM (Franco Kernel Manager)
4. Used Direct Install in Magisk and rebooted phone
5. Still had error "stock image does not exist."
6. Downloaded the OTA image from Google
7. Changed the name to OTA.zip and placed into platform-tools
8. Connected phone and opened ADB
9. "adb fastboot recovery"
10. "adb sideload OTA.zip"
11. confirmed that the update worked in phone settings
btw, these are some additional information about my phone
Pixel 7 Pro, updating from Android 13 October Update to Android 13 November Update
Similar problem...
An OTA caused a loss of root (pixel 6 pro, unlocked). Tried to go into a hidden magisk and disable modules, but everything greyed out, unable to. Tried to uninstall the manager (I was using an old MagiskAlpha build), and thought it worked, though it must have left something behind. Updating wouldn't work - would give me a failure.
Flashed new factory image, installed new magisk manager, patched boot.img in new magisk manager, loaded boot.img, and I have root; adb shell su works, all my old apps that worked with root work, but no magisk manager recognizing that I have root - and therefore no modules - working. So, no charging management, safetynet is borked, no lsposed, etc. Have uninstalled/reinstalled mm numerous times. No luck. Tried loading it from adb (version right now was downloaded from topjohnwu's github directly onto phone, then I manually added the canary URL, and updated to canary. No luck.)
I've dug through adb shell pm list packages and can't find anything that looks like an old version of magisk at all anywhere anymore. I think I had three different versions on the phone, but they are all gone. No luck with a freshly installed manager. Still can't see root even though it's there. Any ideas?
Of note: I have a work profile and two users on the phone. However, I can't find anything even using --user for all three users. Only thing even close I see is com.lsposed.manager still installed. That shouldn't be a factor, but I can't think of anything at this point.
TB checker, under "check root" gives pass for everything except SU binary, 2nd SU binary, root via native, and magisk specific.
Under Check xposed, I have fail for dual/work profile and xprivacyLua, and com.topjohnwu.magisk under PM Sundry APIs. Everything else is Pass.
I had never granted TB checker root before; Termux on the other hand works fine with su (as does adb shell), and Root Essentials shows root fine.
One other thing... /data/adb/magisk was dated; all the other directories in /data/adb were new, but magisk was from my last update of MagiskAlpha, and when I looked at util_functions.sh it was aligned to my old (uninstalled) magisk alpha build