boot img for december update, patched it with magisk 21.4 :
https://yasmar.net/xda/patched_boot_11.0.16.0_214.img.gz
thanks to @a1291762
Spoiler: magisk 20.4
Xiaomi Mi A2 Lite 11.0.16.0 / Magisk 20.4
or
{
"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"
}
Seems that Magisk 21.3 was declared stable. I have upgraded and it seems fine.
If anyone's looking for a 21.3 patched boot...
https://yasmar.net/xda/patched_boot_11.0.16.0_213.img.gz
... and now we have 21.4
https://yasmar.net/xda/patched_boot_11.0.16.0_214.img.gz
yhanks you, updated the post
I'm experiencing an isue after instal·ling Magisk.
Ringtones (notifications, and so on) are not working, and if I try to change them through the setup menu, it freezes for a while and has no effect).
I was a bit lost until after repeating the flash procedure I identified it happens only after Magisk has been installed. Flashing again stock solves the problem.
I've tried:
- with twrp: Magisk 21.4
- with twrp Magisk canary 21.4
- fastboot flash boot @a1291762 patched boot image
- fastboot flash boot my own patched boot image
- fastboot boot patched boot image
I've read of someone with the same issue, but have not found any solution.
Any idea?
Thks!
xabier-bo said:
Ringtones (notifications, and so on) are not working, and if I try to change them through the setup menu, it freezes for a while and has no effect).
Click to expand...
Click to collapse
That's a bit odd... I don't see this on my phone.
There was an issue I ran into on Pie where having the phone in do not disturb meant notifications couldn't be changed. And another on 10 where Outlook notifications couldn't be changed. But neither of these should affect changing the ringtone on 10.
a1291762 said:
That's a bit odd... I don't see this on my phone.
There was an issue I ran into on Pie where having the phone in do not disturb meant notifications couldn't be changed. And another on 10 where Outlook notifications couldn't be changed. But neither of these should affect changing the ringtone on 10.
Click to expand...
Click to collapse
I hadn't seen this before either. But I have reproduced the process, and at least on my device, I have verified that it is installing Magisk that generates the issue, and uninstalling it eliminates the problem.
I will search better in the forums, to see if I can locate the message describing the same or quite a similar problem.
Thanks, by the way!
maybe one of your modules. what if you deactivate all modules and reinstall magisk?
Thanks!
I'll try it, I have very few and basic ones, but I'll tell if it works
Any improvement on this update?
Kaimilo said:
Any improvement on this update?
Click to expand...
Click to collapse
IMO This phone is never going to get better. The updates are mandatory (for Xioami) security updates but that's it. Seems pretty clear they are not trying to fix bugs, they're just bringing the security patches over.
xabier-bo said:
Thanks!
I'll try it, I have very few and basic ones, but I'll tell if it works
Click to expand...
Click to collapse
I promised feed back.
Just in case anybody finds him/herself with this odd issue: your suggestion worked. What I did:
- I removed magisk manager
- ran the magisk uninstaller (booting in twrp)
- installed magisk 21.4 with twrp as well
And it did it!
Thanks again...
PS. The only module I had installed was the systemless one
Oh... I never did my change analysis for this version.
It's the usual(ish) suspects for a security update...
media stuff (av1, mediaplayerservice), DNS, bluetooth, wifi, qti (qualcomm?) libs.
a bunch of camera libs changed (iface, imglib, mct, sensor_modules, stats_modules).
Related
I updated my pixel 2 to the Android 10 stable release this evening .
First thing I did afterwards was root with magisk .
I pulled the boot file, patched it and flashed it.
I opened magisk everything is checked , used Root check app. That came back positive.
However when I try to modify my host file and install my custom host file I get error messages saying " Can't delete file" .
I tried both root explorer and solid explorer both apps have root access . But can't modify the system files.
I'm starting to thing that I'm getting a false positive on root or something has changed in Android 10 and we can no longer modify system files.
I tried both the stable version and canary version builds of magisk . Both say that I'm rooted but the issue persists .
{
"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"
}
Sent from my Pixel 2 using Tapatalk
I saw on another thread after you boot twrp in adb, mount everything as read only and then reinstall twrp and magisk zips thru the recovery. I used most recent versions of twrp and magisk and didn't need to alter the zips in any way. I'll see if I can find the thread....
Couldn't link the thread, so here's a ss
donlu30 said:
Couldn't link the thread, so here's a ss
Click to expand...
Click to collapse
Thanks for the quick reply I don't have. Install a custom recovery in a 2 years lol but it thats what's required to get root to work on the pixel 2 with Android 10 then I'll have to do it
Sent from my Pixel 2
I'm having no problem with IanMacd Magisk repo, link below, check readme on bottom of page for instructions on how to configure Magisk for a custom repo.
https://github.com/ianmacd/MagiskBuilds/
ACHILLES R32 said:
Thanks for the quick reply I don't have. Install a custom recovery in a 2 years lol but it thats what's required to get root to work on the pixel 2 with Android 10 then I'll have to do it
Sent from my Pixel 2
Click to expand...
Click to collapse
You can just boot the recovery if you don't want to install it permanently.
Sent from my Pixel 2 using Tapatalk
Thank you for all the replies, turns out I was rooted but I just couldn't write to system. I ended up installing energized pro module for magisk to modify my host file. No more ads lol
Sent from my Pixel 2
I could also root my pixel 2 with canary_magisk but, although its says rooted, some apps say couldn't find the root binary's. Going back to Android 9
So I seem to have an issue with solid explorer. I go in and remove gmail and other google stuff I don't use typically. Solid gets permissions and when I go to delete the gmail folder it errors out. Not certain if this is a root issue with Magisk or perhaps more likely an issue with apps that need root...
Prerequisites
Magisk root
Debloat (Terminal Emulator) Magisk module
Termux or Terminal Emulator
Any file manager with root access
Rename /data/india/india.img to india.img.BAK
Download import-debloat.txt.
Open Terminal. Type the following commands, one by one
Code:
su
debloat
i
Enter the complete path of import-debloat.txt. For example,
Code:
/sdcard/Download/import-debloat.txt
Reboot
Credits to Tomatot Debloater. The attachment below is based on Tomatot's Light Script, with a few apps removed.
Can you add "/system/etc/usb_drivers.iso" or how i do it?
Just add usb_driver^= /system/etc/usb_drivers.iso to the txt?
Here are more info about debloating apps
https://forum.xda-developers.com/on...ol-tomatot-debloater-basic-script-to-t3869427
Sh0X31 said:
Can you add "/system/etc/usb_drivers.iso" or how i do it?
Just add usb_driver^= /system/etc/usb_drivers.iso top the txt?
Here are more info about debloating apps
https://forum.xda-developers.com/on...ol-tomatot-debloater-basic-script-to-t3869427
Click to expand...
Click to collapse
Yes, that is correct
remewer said:
Prerequisites
Magisk root
Debloat (Terminal Emulator) Magisk module
Termux or Terminal Emulator
Download import-debloat.txt from the attachment below.
Open Terminal. Type the following commands, one by one
Enter the complete path of import-debloat.txt. For example,
Reboot
Credits to Tomatot Debloater. The attachment below is based on Tomatot's Light Script, with a few apps removed.
Click to expand...
Click to collapse
This should work on a PC with adb you think?
qbanlinxx said:
This should work on a PC with adb you think?
Click to expand...
Click to collapse
The terminal commands? Yes, it should.
Anybody else got a semi-bricked phone after using this? I used this on oos 10 (added some more apps from the tomatot debloater script) and my phone would only boot to a black screen with only power button working. Deleting/uninstalling the module in twrp didn't disable debloating. Even reflashing oos10 in twrp didn't work. Only way to get a working phone again was to use the fastboot rom flash method to get a clean phone.
Edit: I used this debloater on oos 9.0.9 without issues. Only now on 10.0.3 I'm getting stuck.
Edit 2: After using the debloat text file from the Git repo eveything works as expected on OOS 10.0.3. Must've been an entry I added myself that caused the issues.
Koeties said:
Anybody else got a semi-bricked phone after using this? I used this on oos 10 (added some more apps from the tomatot debloater script) and my phone would only boot to a black screen with only power button working. Deleting/uninstalling the module in twrp didn't disable debloating. Even reflashing oos10 in twrp didn't work. Only way to get a working phone again was to use the fastboot rom flash method to get a clean phone.
Edit: I used this debloater on oos 9.0.9 without issues. Only now on 10.0.3 I'm getting stuck.
Edit 2: After using the debloat text file from the Git repo eveything works as expected on OOS 10.0.3. Must've been an entry I added myself that caused the issues.
Click to expand...
Click to collapse
Yes, there's an issue with the list I provided, but I'm not quite sure which package was the culprit. However I made a new import-debloat.txt file which works with 10.3.0.
Any changes? Do it work with OOS 10.3.0?
I'm on a Oneplus 6T and on 10.3.2, and it says "Invalid file" for me.
meetlogan said:
I'm on a Oneplus 6T and on 10.3.2, and it says "Invalid file" for me.
Click to expand...
Click to collapse
After upgrading to 10.3.2 my debloat still works flawlessly. I didn't even have to rerun any scripts.
Koeties said:
After upgrading to 10.3.2 my debloat still works flawlessly. I didn't even have to rerun any scripts.
Click to expand...
Click to collapse
Then what could I be doing wrong? I have installed the magisk module, have busybox installed if that matters, am using termux, have downloaded the file from the pastebin link, entered the correct file path, still invalid file.
{
"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"
}
Maybe the file is corrupt or something? Not sure how that could happen when just downloading.
I attach the debloat.txt that I use (which works well for me). Go through it to make sure you're happy it's what you expect and then try it out. Hopefully it will work for you. :good:
One thing I found: after debloat some system apps would still be on the phone. If that happens to you, you can just uninstall them as you would a normal app. Don't worry, if you remove the Magisk module or restore the debloated apps, they'll re-appear.
Good luck!
The file was the problem indeed, yours worked perfectly like you said, some hidden app appeared like google auto, and I just uninstalled them. Thank you for the help man.
i do this and my device doesn't start! Stuck on the screen that says The boot loader is....
Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
{
"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"
}
Cocomug_ said:
Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
Click to expand...
Click to collapse
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Slim K said:
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Click to expand...
Click to collapse
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Cocomug_ said:
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Click to expand...
Click to collapse
how did you flashed it?
Okay so I went to the Asus website
https://www.asus.com/supportonly/ROG Phone 5 (ZS673KS)/HelpDesk_Download/
Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method with the OnePlus 8 pro same process worked for me I downloaded the firmware from the website put it in the root of my phone, the phone detected the update immediately I got to pop up on the screen and it started installing the update. Then it asked if you want to reboot or reboot later "do not reboot" then go into magisk, then go into "install"
{
"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"
}
it will give you an option to keep root after an OTA. So once you choose the option as you can see on the screenshot let it patch and do its thing and reboot. I hope this helps somebody.
Whenever i dump payload.bin using payload dumper to get boot.img and patching it using magisk when i flash it causes bootloop! So i can't root it. I think it's payload dumper's issue. Btw can you give me the patched boot.img?
sorankira said:
Whenever i dump payload.bin using payload dumper to get boot.img and patching it using magisk when i flash it causes bootloop! So i can't root it. I think it's payload dumper's issue. Btw can you give me the patched boot.img?
Click to expand...
Click to collapse
What formal version were you in before? Would you like to try my patched boot image?
chairman011 said:
What formal version were you in before? Would you like to try my patched boot image?
Click to expand...
Click to collapse
I just bought the Rog 5 and upgraded to last firm and never had problem to dumpa boot img ( my phone before Rog 5 was Nubia Redmagic 5G). Yes I like to try your boot img, my last firm is WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46. Thanks!
chairman011 said:
What formal version were you in before? Would you like to try my patched boot image?
Click to expand...
Click to collapse
Yes i would like to use your patched boot.img
And anyway to disable HardwareStub Service notification? V
how to solve this ? i follow your method to upgrade my rooted firmware to latest version , but my safetynet not passed ? before uograde my firmware , the safetynet passed without error
Quiinny said:
how to solve this ? i follow your method to upgrade my rooted firmware to latest version , but my safetynet not passed ? before uograde my firmware , the safetynet passed without errorView attachment 5400203
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
twistedumbrella said:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
already installed it. but still not passed the safety net
Quiinny said:
already installed it. but still not passed the safety net
Click to expand...
Click to collapse
Clear Data of Google Playstore and Play Services.
Ensure Magisk hide is enabled and Magisk app is hidden with a different package name.
OP your advice worked perfectly for me.
I wanted to note that my phone didn't see the update file right away, but I was prompted immediately after exiting my adb shell session and unplugging the phone from my laptop.
Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"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"
}
Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/
Thank you and please excuse my stupidity.
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.
deleted
Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.