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?
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
joemossjr said:
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
Click to expand...
Click to collapse
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
i.Design said:
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
This didn't work. I was able to at least see my storage now and installed OTA via TWRP > TWRP installer > Magisk to update Slot B now I'm having the same issue in both slots.
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
I have downloaded the 11 update via OxygenUpdater using VPN (Location is set to France)
Since i diden't get the update on my real location.
Rebooted to TWRP->Flashed 11 update->Flashed TWRP->Rebooted to TWRP>Flashed Magisk>Flashed Kernel>Rebooted to System.
Everything seems to be working.
Try this simple and straight forward method,
Download the full zip 9.5.11, not the update zip but full zip,
Transfer to phone storage,
wipe only dalvik cache and data, DO NOT WIPE SYSTEM OR VENDOR, OR INTERNAL STORAGE,
Flash the oos zip,
Flash twrp, Reboot recovery,
Flash oos zip file again followed by twrp,
Reboot recovery,
Flash magisk 19.3,
Now Reboot system,
Do not click on any slots in twrp let the system select the appropriate slot, system will take some time to boot also will Reboot itself, but will boot eventually,
hope this helps, cheers.
How this helps, worked for me, I don't have T-Mobile version
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
OP7PRO, stock ROM, stock kernel
This has been ABSOLUTELY working for me and how i was used doing it back in the days..
*After switching off all modules in Magisk and do a system reboot to apply this..
(Do I have to mention it's probably best, when updating to disable any password/fingerprint protection when rebooting AFTER FLASHING OTA, TWRP and Magisk in recovery?)
*I didn't use local update setting.
*What's on in developer options?
-OEM Unlock allowed
-Advanced reboot
-USB Debugging
*Don't know if having these developer settings otherwise would interfere, I just try to write it down as specific as of how i did this.
*Also: I didn't even bother looking at A/B partitioning and where to install what, please correct me if i could be wrong, but using this method worked for me and also when installing TWRP zip in recovery, the log showed A/B sloth solution success when installing.
*Not using substratum themes etc., but I want to say it's probably best to go as clean as you can anyway, since you can always go back being beautiful afterwards I guess?
So try remember where you left off being a makeup loving customiser and momentary revert being as clean as possible.. at least for maybe 20 minutes okay?
How I did it:
-Download the OTA update zip on your phone (full update file zip just shy of 2 Gb) using oxygen updater app in Google playstore.
(Don't install the systemsoftware zip from the oxygen updater once downloaded), you're going to install the systemsoftware.zip in TWRP recovery as opposed to update via Magisk to install the new systemsoftware).
-Download TWRP (INSTALLER!!) have this ZIP on phone (Find it by reading some posts about TWRP Installer zip or use link below)
*I used: twrp-installer-3.3.1-4-guacamole.zip
https://dl.twrp.me/guacamole/ (for TWRP zip)
-Download Magisk zip
*I used: Magisk-v19.3.zip
(So far 3 zip files, have them somewhere pretty obvious on your phone)
-Boot into recovery (I did this by using this option in Magisk manager)
Then:
-Flash the update OTA ROM.zip (just shy of 2Gb)
*DON'T REBOOT*!!!!
-Go back in TWRP recovery menu, Flash TWRP Installer zip
-Still in TWRP recovery menu go back, Reboot to recovery
-Back in TWRP, flash Magisk zip
-Clear Dalvik cache (not sure if this is actually still needed)
-Reboot system normally, enable Magisk modules you want, reboot system...
Updated to 9.5.10 works
Updated to 9.5.11 works
Updated to 10.0.0 works
I can't find the full zip for 9511 anywhere
joemossjr said:
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
Click to expand...
Click to collapse
I ended up having to reformat to deal with the encryption issue. After reformatting I was able to boot to slot b and am at .11 now!
I'm really hoping this ordeal fixed whatever the problem was so that future OTA's aren't this much of a headache. I'll keep the tips in mind. I'm just glad to have a working device at .11 with root even if I have to re-install all of my apps etc.
virtyx said:
I can't find the full zip for 9511 anywhere
Click to expand...
Click to collapse
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
smariob said:
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
Click to expand...
Click to collapse
just came up now
what i normally do is flash full zip
reboot
then reboot fastboot and boot twrp, then flash twrp then magisk.
i like the OS boot first time without twrp or magisk, just habit i guess
everything working fine, nightscape also
EDIT:
i think SWAP has been turned off in 9.5.11
it no longer displays in ElementalX app (with stock kernel)
What did I do wrong?
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
I don't know why people have such difficulty?
1. Get the full zip via Oxygen Updater or some other method.
2. Do a local install vis the settings. DO NOT REBOOT.
3. Install Magisk via the "Install after OTA" from Magisk Manager.
4. Reboot
5. You will now have the slot rooted that you updated.
6. Run the local install again. This will install to the other slot. It will fail the first attempt. Do it again.
7. Install Magisk via the OTA option and reboot.
You have now updated both slots and rooted them.
If you would like TWRP or custom kernels, follow those instructions.
If you install TWRP, you MUST install Magisk in the same slot or you will get a boot loop for that slot.
That is the reason why I keep both slots at the same OS level and rooted with TWRP installed.
What country guys you are from that you are getting update? Im in USA and still got nothing.
netgar said:
What country guys you are from that you are getting update? Im in USA and still got nothing.
Click to expand...
Click to collapse
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Krsmqn said:
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Click to expand...
Click to collapse
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
netgar said:
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
Click to expand...
Click to collapse
Yeah, meant magisk modules, sorry. But looks like you got it anyway. ?
All update methods to 11 failed.
I'm using the canary version of Magisk for the Q beta 6. Yesterday I tried to install a self made module to get rid of screenshot sounds (the one on the rep isn't working because Google changed the path. But as I installed it, I can only remember that the last line was "Magisk manager will be removed and your device will reboot in a moment" or something like that
Well, the manager is still installed, but Magisk itself got uninstalled. Besides the fact that I have no clue why that happened, now I can't install it. TWRP doesn't support Q. So I got the Q image from Google, extracted the boot.img and let Magisk Manager patch it (with preserve force encryption and Preserve AVB 2.0/dm-verity turned on) and flash it through Fastboot (fastboot flash boot magisk-boot.img) but it's still not installed. And without TWRP of course I can't flash the uninstaller zip (no clue what was actually removed).
Is there a way through adb or fastboot to find out what's left of the Magisk installation and remove that? Or any other solution I didn't think of?
Ok, via adb is not an option since both /data and /cache refuse permissions so I can't even get logs to find out what happened.
Does anyone have a working pre-patched boot.img? I don't know if that Manual method isn't working because patching isn't really working or because the Magisk files are still present and the module is still conflicting with Magisk. And I don't want to do a factory reset
Nevermind. It was a faulty Magisk database, I had to uninstall and reinstall it to solve the problem
As in the subject, I have a problem with the magisk on the Mi 10 Lite 5G.
I downloaded room miui_MONETGlobal_V13.0.2.0.SJIMIXM_f2b661bdf6_12.0
Due to the fact that on android 12 there is no TWRP working yet, I uploaded magisk 24.3, patched the boot.img file and uploaded via FASTBOOT, everything is loaded, I have root access but the application does not work as it should. When he wants to hide an application under the name of settings installed he gets the message: "Restore application magisk, this application cannot run as root has been lost. Please restore it to its original state." and here I have install at the bottom. after installing the application from scratch, I get another message "Your device requires additional configuration for the magisk to work properly" I click ok and I have the message "configuration failed."
I tried multiple times to patch boot.img and upload it via Fastboot but I have the same problem every time.
Anyone know the solution to this problem ???
I'm still on MIUI 12/A10, I haven't tried this out.
But - since the flash-script is just a fastboot script, you can do it a bit backwards.
Install any pre-A12-rom, after that, boot in to TWRP. Flash boot.img from the A12-rom. Then flash magisk.
Now you edit the fastboot.bat or fastboot.sh-script. Remove the line with fastboot flash boot images\boot.img. Boot in to the bootloader. Then run the script.
You should now have a fully working A12-rom with magisk.