how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
ekin_strops said:
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
Click to expand...
Click to collapse
ah i see, thanks!
Veid71 said:
how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
Click to expand...
Click to collapse
Settings > About Device > Version > Build Number
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure you've done all the OEM Unlock, etc first
djsubterrain said:
Settings > About Device > Version > Build Number
View attachment 5587231
Make sure you've done all the OEM Unlock, etc first
Click to expand...
Click to collapse
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Veid71 said:
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Click to expand...
Click to collapse
Jump in here :
Magisk
Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.
forum.xda-developers.com
Just Incase anyone else runs into this issue on that magisk forum there's a universal safetynet fix (UNSF) that you can download and it'll fix it
Related
Flash these in TWRP if you want a smaller LTE Data Icon. I also have one for removing it completely. These will also be in my next updated Aroma installers.
Oct Pie
https://www.androidfilehost.com/?fid=1322778262904023071
Oct Magisk
https://www.androidfilehost.com/?fid=1322778262904023073
DP3 uploaded
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thought you might want to see how it looks.
Big improvement over the large LTE stock P version.
Thanks for your hard work and releasing it us!
I uploaded new Magisk versions just now. Updater-script problems.
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Phalanx7621 said:
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Click to expand...
Click to collapse
Flash TWRP
Phalanx7621 said:
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Click to expand...
Click to collapse
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.
liam_davenport said:
If it's a Magisk Module go into Magisk > Modules and the + icon go to where the zip is located and install it
Click to expand...
Click to collapse
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.
Tulsadiver said:
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.
Click to expand...
Click to collapse
Thanks for clarification
Cause bootloop on DP3.
Queentus said:
Cause bootloop on DP3.
Click to expand...
Click to collapse
Which one did you flash?
Tulsadiver said:
Which one did you flash?
Click to expand...
Click to collapse
Sorry for not making it clear back then. I flashed the older mod which I believe was made for DP2, and it caused system ui crashing.
No problems with the DP3 updated one and thanks for the awesome work!:good:
Magisk installation failed on DP3, Magisk 16.4.
Log below.
Removes Lockscreen wallpaper dimming tint and the notification pulldown tint as well. Flash in TWRP. For stock roms.
DP4
https://www.androidfilehost.com/?fid=5862345805528052629
DP4 Magisk version
https://www.androidfilehost.com/?fid=5862345805528053144
8.1 July update
https://www.androidfilehost.com/?fid=5862345805528052627
8.1 July update Magisk version
https://www.androidfilehost.com/?fid=5862345805528053136
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk version fails
prot- said:
Magisk version fails
Click to expand...
Click to collapse
Could you elaborate some? Which one, fails how?
Tulsadiver said:
Could you elaborate some? Which one, fails how?
Click to expand...
Click to collapse
Yeah sorry dude
Log attached.
Also would like to know why it's trying to do all those things?
I mean that is a huge log of changes.. wow..
This is the magisk one on Android p
prot- said:
Yeah sorry dude
Log attached.
Also would like to know why it's trying to do all those things?
I mean that is a huge log of changes.. wow..
This is the magisk one on Android p
Click to expand...
Click to collapse
It is flashing the systemuigoogle.apk. Are you completely stock?
Edit:. Also, are you on magisk 16.3 or higher? I just flashed this on my Pixel and it works fine.
Appreciate the effort though dude I hate that tint
Will this work on dp5?
Tulsadiver said:
It is flashing the systemuigoogle.apk. Are you completely stock?
Edit:. Also, are you on magisk 16.3 or higher? I just flashed this on my Pixel and it works fine.
Click to expand...
Click to collapse
Stock latest 16.7 magisk.
Same issue on dp5
prot- said:
Stock latest 16.7 magisk.
Same issue on dp5
Click to expand...
Click to collapse
I don't know why some people have problems and some don't on Magisk. My suggestion is to remove Magisk, reroot, use regular one to get where you want to be, then install Magisk manager.
anyone updated to the latest update care to comment, thanks in advance
I can't do it (on a rooted device: Note 9 Pro)
The update file is 616.8MIB
miui-blockota-joyeuse_global-V12.0.2.0.QJZMIXM-V12.0.3.0.QJZMIXM-41e0213a6b-10.0.zip
Impossible with the MIU installer or with TWRP 3.5.0_10-0
Always a error message
I also need some help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vin100 said:
I can't do it (on a rooted device: Note 9 Pro)
The update file is 616.8MIB
miui-blockota-joyeuse_global-V12.0.2.0.QJZMIXM-V12.0.3.0.QJZMIXM-41e0213a6b-10.0.zip
Impossible with the MIU installer or with TWRP 3.5.0_10-0
Always a error message
I also need some help
View attachment 5296013
Click to expand...
Click to collapse
I'm not sure where this OTA update could be used with custom recovery. even for the stock recovery it seems the whole recovery flash image is required
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
vin100 said:
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
Click to expand...
Click to collapse
i think so, although i havent done that myself
vin100 said:
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
Click to expand...
Click to collapse
no
just know that fastboot and recovery update methods are not the same
Thanks @koshikas, I know. That's why I'll wait some more experienced people here. I'm afraid to loose some data in the operation. If you've a good link for a ultra safe backup & easy restore I'll love it
vin100 said:
Thanks @koshikas, I know. That's why I'll wait some more experienced people here. I'm afraid to loose some data in the operation. If you've a good link for a ultra safe backup & easy restore I'll love it
Click to expand...
Click to collapse
MiFlash has options to flash with & without wiping. You can backup with the built-in tool or try Alpha Backup on play store.
Your recovery is outdated and is the reason for the failed flash. Try orangefox or dungphp's TWRP/Pitchblack.
Finally you can force a download of the full rom and not just the update from the updater app. It's in the menu at the top right. If you don't see it tap the 'currently installed' text a bunch.
Or just click here to download
Does anyone have a link to this, please?
Magisk patched:
HD65BA_OxygenOS_11.0.0.2_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.0.2_stock.img
drive.google.com
THank you mate, much appreciated
jatson said:
Magisk patched:
HD65BA_OxygenOS_11.0.0.2_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.0.2_stock.img
drive.google.com
Click to expand...
Click to collapse
Hi,
Would you please be so kind and help us out with the recent version 11.0.1.1 HD65BA? May thanks for your support!
Otherwise I cannot update as I need root from my usage...
By the way: Is there a ways to patch the boot-image myself? How to extract it to let Magisk Manager do the job?
Hi,
Sorry for the delay. Here you go.
Magisk patched:
HD65BA_OxygenOS_11.0.1.1_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.1.1_stock.img
drive.google.com
joegreat said:
Otherwise I cannot update as I need root from my usage...
Click to expand...
Click to collapse
If you already updated to Android 11 and rooted your device, you can easily update to the newer revs and keeping your root access. Check here how to do that.
A usefull tool for the updates (if you did not know it yet): https://oxygenupdater.com/
joegreat said:
By the way: Is there a ways to patch the boot-image myself? How to extract it to let Magisk Manager do the job?
Click to expand...
Click to collapse
Actually yes. I'm doing the same way like you mentioned. I'm using Payload Dumper to get the boot file from the image. You can find the details here.
When you got the needed boot.img file you can simply "ask" magisk to do the job for you:
- Select Magisk install in the app
- Choose "Select and Patch a file"
- select the boot.img you want to patch
- click "let's go"
Hope I could help.
Does anyone have the patched 11.0.2.1 image please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can someone make a magisk patched image of this version? (Indian)
thanks in advance
jatson said:
Magisk patched:
HD65BA_OxygenOS_11.0.0.2_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.0.2_stock.img
drive.google.com
Click to expand...
Click to collapse
I Have flashed the patched one. But it doesn`t work. the phone stop after reboot an stand still display black.
After flash the stock rom, the phone boot normal but bootloop.
atnoword said:
I Have flashed the patched one. But it doesn`t work. the phone stop after reboot an stand still display black.
After flash the stock rom, the phone boot normal but bootloop.
Click to expand...
Click to collapse
Do you have a screenshot about your actual version running on your phone?
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse