Hello,
I have a problem with my FP3. When I flash the Magisk zip with TWRP or when I flash the patched boot image through Fastboot mode, Magisk is not completely installed. I need to boot et click on the "Magisk app" with a standard icon to install it and to access Magisk Manager. Without this, Magisk is not really installed since "su" or magisk executable are not in /sbin.
I need a way to manually install/upgrade Magisk through recovery (TWRP) to obtain the su. In my context, I have constraints preventing the installation through GUI.
Have you already done this before ?
Related
hello xda,
This tutorial shows you that how to make your device fully functional with root.
but most of the peoples question is to pass SafetyNet, make their device status "Official" and also to work with Private Mode after root and with custom kernel. And here is the answer ,
BEFORE BEGIN, BACKUP YOUR DATA AND DOWNLOAD CORRECT FILES. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSE TO YOUR DEVICE BY THIS PROCEDURE!!!
1. Download and flash stock oreo firmware via ODIN.
2. After boot, Turn on developer mode and turn on OEM Unlock.
3. turn off your device and get in to download mode.
4. Flash latest TWRP recovery via ODIN.
6. Get in to twrp recovery and format data and again boot into twrp.
7. first flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk", thirdly flash "TGP kernel v6.8.0".
8. After boot, update magisk app itself ( Latest v17.1 ).
9. download and install any root browser app ( root explorer recommanded) and give the root permission.
10. Navigate to /system/priv-app/PersonalPageService and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
11. Navigate to /system/app/sysscope and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
12. Reboot the device.
13. Now you can check SafetyNet, System Status and private mode.
NOTE :
DO NOT ATTEMPT TO INSTALL SYSTEM UPDATE. BECAUSE YOU MAY HAVE INSTALLED CUSTOM RECOVERY. SO THE UPDATE WILL PROBABLY FAIL.
YOU CAN OBTAIN UPDATE PACKAGE AT "/data/fota".
YOU CAN ALSO RIDE WITH BANKING APPS AND OTHER APPS WITH ROOT.
CAUTION :
●DO NOT FLASH CF SU.
●DO NOT ATTEMPT TO FLASH SYSTEM UPDATE.
●DO NOT INSTALL XPOSED FRAMEWORK. THIS WILL TRIGGER SAFETYNET.
KNOWN BUGS : NOTHING YET. TESTED ON GALAXY S7 (EXYNOS).
Files
( sysscope, PersonalPageService ) : https://drive.google.com/folderview?id=1ekOXMNMYGhaMke58y_xkVMFiAvP-Ncpm
no-verity-opt-encrypt-6.0 :
https://androidfilehost.com/?fid=817906626617949632
TGP Kernel v6.8.0 :
https://androidfilehost.com/?fid=1322778262903992351
Systemless magisk :
https://www.google.lk/amp/s/forum.x...-magisk-v7-universal-systemless-t3473445/amp/
second method:
Download (e.g. with SamFirm (v0.3.6)) and flash stock oreo firmware via Odin
After boot, Turn on developer mode and turn on OEM Unlock.
Turn off your device and get in to download mode.
Flash latest TWRP recovery via ODIN.
Get in to twrp recovery and format data and again boot into twrp.
First flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk"
After boot install latest magisk manager
In magisk manager install the module Xposed Framework (SDK 26) systemless
Install XposedInstaller_3.1.5-Magisk from https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
In XposedInstaller-App install Firefds Kit [Oreo]
Start Firefds Kit [Oreo] and enable in Security hack "Fake system status"
Now the system status is official and you can download the OTA-Update.
To get ctsProfile: true and basicIntegrity: true you have to deactivate Xposed in the XposedInstaller-App (disable Xposed Status) and disable the module in magisk manager
But the interessting question would be how to install OTA updates without loosing root.
Because, if you go in the xposed method, It will probably trigger SafetyNet. So you couldn't be able to ride with updates, banking apps and etc.
This is why I placed modified Sysscope in order to make official.
And yes, stock private mode checks for custom binary or custom kernel. So the best way to modify the apk to work with custom binary.
Unfortunately, you cannot be able to install system updates via recovery. But, you can extract the fota.zip and place those files manually at your own risk. But I recommend you not to do.
DO NOT INSTALL XPOSED. IT WILL TRIGGER SAFETYNET. EVEN THOU SYSTEMLESS METHOD WOULDN'T HELP.
What should I do to get root again after the OTA?
Reflash magisk to regain root access
Are there any news to this topic?
If you install twrp recovery then it is very easy to install magisk manager.
just go on your twrp recovery mode
Select advanced and select install root.
Reboot your Phone .
See magisk manager install successfully.
Any help about mi cc9 magisk manager just coment here. I will be ready for replay just like you want.
.
Or Download this file and install through twrp recovery.
Latest stable magisk manager zip [flash file]
https://drive.google.com/file/d/1j6EWKPt1ZNzW7QgtILkgW5xphCzzcKNH/view?usp=drivesdk
Magisk manager apk
https://drive.google.com/file/d/1Hzvi5f2bZcUPyzWx-ETfqZanQjLCJHGq/view?usp=drivesdk
Lijlp0/02plppp000p7 lu6pppp?0lpl
Ul u?????//6000
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
I need unlock BL to flash the modded boot.img?
RazrBR said:
I need unlock BL to flash the modded boot.img?
Click to expand...
Click to collapse
Yes, first unlock BL to be able to enter fastboot mode. Apply to unlock bootloader with Mi account, please follow guide on how to unlock the bootloader.
eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
Hi. Did you do these passages also on MIUI 12? Because I installed Magisk app, but it showed Ramdisk: no, and now I don't know if I should install it in recovery partition or not
there's twrp and orangefox that can be used for cc9 meitu/vela. Unlock bootloader, enable adb, flash custom recovery by fastboot. After that use custom recovery to install magisk. I'm sorry I don't use cc9 anymore since last weekend because miui12 notification and permission is too aggressive, have to restart app everytime so that can get contact info.
After installing some Magisk modules on my P3 it doesn't boot anymore. It does boot if I flash the unpatched boot image, but not the one patched with Magisk. TWRP is not possible at this time on Android Q. adb shell does not work in recovery. Cannot access /data without root (so cannot delete modules manually and cannot create .disable_magisk)
Any ideas on how to enable Magisk but disable all the modules before the boot?
See this. https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
You could use DFE (If you want unencrypted data) or use magisk module for recovery. to remove unwanted magisk modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
There is magisk module which check on start of the phone if any module makes a bootlop and disable it. Magisk Bootloop saver on github
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
Power phone off completely. Power on and when MIUI logo shows on screen hold volume down button until phone boots, this will disable all magisk modules you have installed. It's called magisk safe mode. You can now enter magisk app and enable modules one by one until you find the culprit.
Sidenote: I upgraded from xiaomi.eu 12.0.6 to 13.0.3 using fastboot. TWRP was unable to decrypt when I booted to recovery to install magisk after update. I rebooted back to MIUI and disabled pin and fingerprint. Rebooted back to TWRP and was able to access data and install magisk from the downloads folder. So try disabling screen lock and see if TWRP is working then.
Well orangefox has magisk manager built in, so modules can be removed with a swipe
you can navigate to data/adb/modules folder in twrp file manager without decryption needed and delete module folder.
worked for me on android 12.
I got stuck at Xiaomi logo after installing some module. The storage is encrypted on Android 12, decryption in recovery is not possible at the moment. So using OrangeFox or deleting /data/... is not possible.
The only solution that worked for me was accessing the safe mode and running this command from adb shell.
magisk --remove-modules
Hi,
I finally got Palladium GSI installed (Android 11)! I rooted my Pixel in the past with Magisk 25.2. Now on my Samsung Galaxy A50 that I installed Palladium, I cannot get root. Here are the steps I did.
RAMDISK=NO in Magisk.
(1) Download Magisk 25.2
(2) extract recovery.img from TWRP 3.6 (that I installed originally)
(3) Open Magisk->Install with recovery mode checked ->NEXT -> select and patch a file -> pick recovery.img -> "let's go"
(4) copy the Magisk patched image to my SD Card
(5) boot into TWRP
(6) Install->Image-> pick the Magisk patched (recovery) image -> select 'recovery' partition -> 'swipe to confirm flash'
(7) reboot to recovery once flashed
(8) open Magisk app, no root
what did I do wrong?
I also tried installing Magisk in TWRP by renaming the extension to 'zip' and flashing, rebooting into recovery... I saw that as another method - didn't work either
I'm soo close trying the two methods above I saw in other XDA forum posts. Did I miss a critical step?
Installation
The Magic Mask for Android
topjohnwu.github.io
^ do I need to do the vbmeta steps too? Unsure how I would do that in TWRP though...
vbmeta is afaik patched from maigisk, but you can download vbmeta.img.empty pack it into tar archive and flash from Odin3 as it might still required for twrp in case magisk doesn't work.