yashsingh1/xdaforums huggingface dataset:
[Magisk] manjaroid:
Browse the repo for the March 3 commit (2717feac)...

Commits · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com

Edited to avoid mishap
[Magisk] Nergal di Cuthah:
I believe you go to the commits and download the apk attached, but i tried that could only find stub apks and they didn't install (failed with error but can't remember what it was).

Edit: did not see the above post but still ran into stub which wouldn't install

Edit two: fround correct apk, boy is there a lot of clicking to get it. But the one i trailed from march 6 gave me 10
[Magisk] mochamoo:
but I can't find canary builds??
[Magisk] konfuzius4u:
Magisk-2717feac(25209).apk it says on my device.

I do still have all versions from 20207 until 20210 on my device.
[Magisk] zgfg:
IMHO, after the serious regression flaw in Canary 25210, not even the built-in Systemless hosts not working, they HAD TO release (service) 25211 as rolling back to the 25209 code (or even 25206 code)
[Magisk] mochamoo:
thanks I was thinking that would be the one. will see what I can do now.
[Magisk] Nergal di Cuthah:
I'd try the march 2nd one, march 6 (referenced as the right one above is 25210 according to the change made in the commit
[Magisk] Nergal di Cuthah:
Thanks for a file :)

Your comment seems not to be complete but maybe I'm missing something :(
[Magisk] zgfg:
Wanted to say that they should have released 25211 - making it easy for everybody to 'upgrade', where 25211 would just be a temporary 'new' version rolling back to the 25209 code - to assure that users could 'update' and thus easily fix the modules mounting not working

While it seems that proper fix, comparing back to the old 25206 (or 25207) code, whereafter some more issues with modules apparently went wrong, is taking time
[Magisk] manjaroid:
Pardon me o_O

981ccabb is 25210 (March 6)

2717feac is 25209 (March 3)
[Magisk] mochamoo:
I found the right one in github and have it installed. Currently having issue still with adaway and installing the acc module but will play with it some more. passes the integrity checks ok.
[Magisk] Nergal di Cuthah:
Did you reflash boot (is boot 25210)? I rolled back to 25209 by restoring image and reflashing root.
[Magisk] mochamoo:
I followed instructions in post 54654 which made sense to me. Seems that I was on 25206 before 25210 but am now on 25209

Pixel 7 pro which means I use init_boot rather than boot images

Edit: All is working fine again. Just need to remember not to update magisk until the fix is published. Thanks to all
[Magisk] Homeboy76:
Magisk Canary 25209
[Magisk] mochamoo:
I used the release vs debug version if that matters.
[Magisk] Nergal di Cuthah:
Debug is just *very* verbose the logs grow fast afaik
[Magisk] pndwal:
... For bypassing Magisk daemon version checks in order to downgrade with Magisk preserved:

Or simply, as I originally posted:

🤠 PW
[Magisk] badabing2003:
Anyone who wants older Magisk builds see @ipdev post here.

Just keep in mind that 25209 is not without issues.

Direct install works, but if you try to patch a stock boot, you don't get root.

You probably would need to patch a stock boot when the March release is finally out.

It's best to stay on 25206 (if you want canary) until a proper fix is released (hopefully 25211)
[Magisk] mochamoo:
Odd, I did patch stock init_boot with 25209 canary release build and flashed the resulting file via fastboot. I do have root and everything working as expected. (Pixel 7 pro)
[Magisk] m0han:
Do you guys use AdAway? Is it working for you? Are ads being blocked in browsers? Are you able to open download links on file hosting sites?

I ask because I've been having a lot of trouble with these situations. After reading the discussion here I am inclined to think this could have started after I updated from 25209. I am now on the latest Magisk Delta Canary.

So, will rolling back to 25209 or 25206 fix this? Can I do an 'Uninstall Magisk' from inside Manager app, then install 25209 or 25206 app and proceed to a 'Direct Install' of Magisk?
[Magisk] mumuli:
Little work but yes, Adaway works fine. Uninstall 25210, install 25206 magisk, flash 25200 pathed boot.img, direct install 25206, then reboot, install 25209 magisk, direct install and voila!
[Magisk] m0han:
Did you mean 25206 patched? Is this step required when booting an unrooted system (after uninstalling Magisk)? And, what should I stay on - 25206 or 25209?
[Magisk] zgfg:
I had boot.img patched by 25209, and flashed that

Then I uninstalled Magisk 25210 app and installed 25209 app, opened and it asked me it needed to finish the installation and to reboot.

After that, 25209 worked as before the episode with 25210

Actually, I even did not uninstall 25210 app (uninstalling app does not uninstall Magisk) since I have enabled on my phone to allow me to downgrade the apps - that way I just downgraded Canary 25209 over the installed 25210 app

Last week pndwall and me discussed here about the options to downgrade Magisk 25210 to 25209 (the app and the Magisk)
[Magisk] mumuli:
25200 Looks mine. I have OP9PRO EU, i take that boot img this forum. Mayby it is 25206 but some one name it 25200. And i was rooted whole time i do this. Uninstall app, Install older version magisk but not open it, then reboot bootloader, flash boot patched and reboot. Root over root kinda

Edit. Just wondering something. Last time, 25207/8 etc some phones have problem when try to open it, it crash. There was only few days when it fixed and we have new magisk version. Now we have this about week/s and still no fix
[Magisk] mumuli:
Try to go even more back, 25206, 25205 boot.img
[Magisk] zgfg:
No intentions. 25209 works fine for me

And it's my spare phone. On the daily, running Magisk Delta
[Magisk] iamthechickengod:
I uninstalled and used 25206. Had to extract the boot.img from the rom and repatch it though.
[Magisk] pndwal:
Canary

Folks, Canary has always been considered 'bleeding edge' Magisk... Canary is now produced as release because John doesn't want to discourage using it as a daily driver for those willing to test cutting edge changes. This includes those who may actually require a particular compatibility fix introduced in Canary for their device... That's because Debug builds (like earlier debug Canary builds) produce a performance hit due to verbose debug-logging etc, especially in older or low spec/low memory devices...

Despite being release builds, they are hot off the press and minimally tested at best... They haven't passed anything like the level of testing needed for Beta releases let alone Stable...

https://xdaforums.com/t/closed-dev-magisk-canary-channel-bleeding-edge-builds.3839337/post-77549897

This doesn't mean they won't necessarily be stable, but they're likely not to be; they're likely to contain regressions, effects of unresolved/unforseen function refactoring as well as a host of other bugs...

This does mean Canary users are necessarily testers and mavericks... or just gluttons for punishment! 😁...

John and Magisk Devs don't need to make any apologies if you elect to be in that elite group, or to supply quick fixes... Users are simply expected to be savvy enough to know how to recover from issues like inevitable bootloops as well as to be able to revert to working builds themselves...

There's also the opportunity for such users to be useful to Magisk and the Magisk community by reporting bugs (along with proper logs) in GitHub issues since they're already using the latest builds. (Simply direct install latest Debug build, which is always the same version as Canary if users update whenever new builds are pushed, before taking logcat/logs or reporting bugs.)

John has apologised on his Twitter when Stable builds have failed en masse and worn some responsibility, but Canary builds are an entirely different (and a much wider) animal...

We use these builds willing, at our own risk and with the full expectation that stuff will break, fixes may take some time, and that if we fail to take precautions (including understanding tricks and countermeasures that may be needed) that cutting/bleeding edge may nick us...

🤪 PW
[Magisk] wcaug02:
does anyone know how i would get the raw image file for my bravia tv ? the patch file magisk is requesting. i just cant find it
[Magisk] mumuli:
Good to know. This was new to me. Thanks!
[Magisk] Eysse:
I am unsure if I am in the right place, but I have a problem rooting my Samsung S9+. I tried to install the firmware, as I found it is needed to root the device. I asked for a CSC code. I searched for how to find it, but none of the workarounds work. I have already installed LineageOS, and it doesn't have it listed in the "About phone" section in settings (at least not to my knowledge). the phone dialer trick also doesn't work on lineageOS's default phone, Samsung phone app won't launch and the recovery mode of lineageOS doesn't show it either. How do I get my CSC code?
[Magisk] pndwal:
Not a Sammy user, but what is CSC code?... If you mean CSC binary for Odin flashing, you may see that if you have up-to-date Odin, but with LineageOS and pre Android 9 launch version device I believe you may not even need that...

By 'firmware' do you mean stock ROM?... Because with LOS installed you wouldn't use that at all...

Can you see/extract boot.img from LOS ROM package?... Patch that in Magisk App (try w/ stable 25.2)?... Flash the boot.img in LOS recovery?... PW
[Magisk] Eysse:
I looked online for firmware, and some sources told me I needed to install such firmware using special software, all of which ask for a CSC code. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root is my source. I would be very relieved to find I don't need my CSC code, as ChatGPT is convinced it is not available for my ROM?? It says I need to ask the developer of my phone.

EDIT: Forgot to say: Yep, I was trying to get a boot.img, for use with Magisk App. The sources I found told me I would get that using said software though, so I thought it was necessary. Is it not?
[Magisk] wcaug02:
No one?
[Magisk] pndwal:
So your link is to official installation instructions for SAR/2SI devices (launched with Android 9+)... Your device launched with Android 8, sorry this section doesn't apply except that some parts just might if your running Android version is A10+ because this means you devices boot-type has changed from legacy ramdisk to 2SI (which is a form of SAR)...

Anyway, I believe that for older devices you can simply patch and flash the AP binary without the other binaries in Odin, but this assumes you're using a stock ROM... Your not...

For custom ROMs, you already have 'firmware' package, is the LOS ROM... You simply need need to patch the boot.img in that and flash as mentioned above, or you can use Odin to flash it if you tarball (make a tar archive) it first AFAIK... Samsung users may confirm... PW
[Magisk] manjaroid:
25210 breaks systemless hosts and other modules, 25209 probably doesn't, 25206 may be a safer bet as it was the last known good setup for many of us. For now I'm using 25209 since rooting worked, modules work and Magisk hides. (Pixel 7)

To roll back uninstall Magisk and tell it to patch your boot file back to stock in an unrooted state. If there's a fumble the surest way to achieve this is manually flash a fresh stock boot. Install the Canary 25206 or 25209 apk with package manager, then patch and flash to root.
[Magisk] Eysse:
I downloaded a lineage OS compressed file now (not sure if that is right), extracted it, and patched the boot.img. It said "Successfully installed!", But the app still has "N/A on "installed" field. I also can't access substratium theme engine, which is more or less what I am rooting for. (Among others, like FontFix).
[Magisk] zgfg:
Without root, you cannot execute adb shell su -c dd if=...

If custom recovery is available (?), you could backup boot

Otherwise, you need to find the ROM, unzip, then possibly use Payload dumper

No idea where to find the ROM, supposedly you googled

But you will also need the unlocked Bootloader
[Magisk] pndwal:
So sounds like you patched in-app successfully... How did you flash it?... When did you see 'successfully installed'? PW
[Magisk] Eysse:
I clicked install in Magisk, selected the boot.img, and the prompt said Successfully installed. See attached screenshot.
[Magisk] zgfg:
Fine, but that is only the first step - you need to flash the patched boot IMG

For the installation instructions PLEASE READ the guide you will find on the Magjsk GitHub. Link to the GitHub is on the main screen in the Magjsk app

Good luck👍
[Magisk] Eysse:
Ahhh there is a lot more to it. I see. Sorry for not checking the docs better. Thanks guys! I'll get back if anything goes wrong that is not in the docs ;)
[Magisk] Nergal di Cuthah:
Yes with no problems on 25209
[Magisk] Nergal di Cuthah:
@m0han did you maybe lose the systenless hosts mod
[Magisk] ipdev:
Thanks for reminding me. 👍

I forgot about the impact the extra logging can have on (older) low resource devices. 🙃

Cheers. :cowboy:

PS.

I switched my snapshot builds back to release. ;)
[Magisk] ctcx:
Hello.

New to Magisk and here in this sub-forum.

I have two main "questions", but I'd like to post them in separate posts, as if "separate threads".

First, I'm on LOS 20.0. I already read that, with every LOS update -normally weekly-, boot image is overwritten, effectively uninstalling Magisk, or at least as if using Magisk "restore" option.

So every update I have to run again the Magisk patching process. The detail is, when patching, Magisk always keeps a backup of original boot image. So, with each LOS update, I'd be piling up lots of booting images over time.

How can I delete/clean them?

Also, with each LOS update, do I also lose all installed modules and I need to reinstall them?

Finally, what's the right way to update modules? Just downloading zip and installing with Magisk again?

Thanks.
[Magisk] ctcx:
Regarding the other doubt, I already read somewhere else that having root enabled full time is not necessarily bad or harmful. Yet I'd like to ask, isn't there really a way to "enable/disable" root without uninstalling Magisk, i.e., restoring original boot image?

Thanks again.
[Magisk] zgfg:
Eg, I use MiXPlorer, root file explorer. Go to /data and look for the folders named like:

magisk_backup_*

Properties, check their date.s Delete all except the latest

---

If ROM update does not include Factory reset, then all your modules will remain in /data/adb

Just patch and flash the new boot.img and continue using the previously installed modules, etc

---

Most of modules support notifications of updates. In Magisk app, modules tab, for those modules you will see, usually inactive, Update option

When update for the module is pushed, Update button will become active and you just press, chose Install, it downloads and installs, and you have to reboot

You can also use Fox Magisk Module's Manager (MMM), it will show you which modules are upgradeble and will give you the option to update them
[Magisk] pndwal:
Mostly covered above...

Nb. With LOS, you can often preserve Magisk through updates as it supports @osm0sis' addon.d survival script... This only works if you initially flashed Magisk from recovery as .zip however, may require recovery that can decrypt data and may not work with older devices using FDE type encryption...

Re. modules, it is generally quite safe to update or even downgrade simply by flashing from storage over current module... No need to disable etc... Generally, just take the internal update when notified (update indicator isn't grayed out) however...

🤠 PW
[Magisk] pndwal:
Many want root full time to allow Play Integrity solutions to work for GPay, bank apps etc... Some custom ROM integrate PI fixes however so root isn't needed for PI in these cases...

You can temp. boot an unrooted device with root using PC/fastboot where only part-time/occasional root is wanted. Use fastboot boot magisk_patched_boot.img

There isn't really a proper way to bypass magiskinit in a patched boot image, but if a user installs Magisk in recovery ramdisk (necessary for many A-only legacy SAR boot-type devices circa 2018, 2019) this can be done simply by booting normally as boot.img isn't patched...

To boot system w/ Magisk, user must use key combo to boot via recovery which works as magiskinit is patched to recovery ramdisk... Observe correct key-release timing to avoid (bypass) booting to recovery...

Not sure how this would benefit you, but you can try it if you're a maverick! 🙂 PW
[Magisk] dcarvil:
You can also use the EX Kernel Manager app to install the survival script by flashing Magisk.zip. This is a paid app, but worth it.

I suspect flashing Magisk.zip with LOS recovery would work, but have never tried it.
[Magisk] pndwal:
AFAIK, @huskydg hasn't merged new selinux/Magisk rule refactoring so his late builds may avoid unresolved issues...

Official 25206 also predates these changes... 25210 broke Magisk patch application to previously unpatched images and maybe caused other problems... Many reverted to 25209 and find this works ok although @canyie has confirmed some detection related issues still need fixing post 25206...

However, if you patched using .zip (incl as .apk) installer from recovery, you will probably have only partial root since 25206... To make selinux/Magisk rules work properly you now need to flash Magisk again (direct install) or patch an image for flashing while system is booted to allow a suitable directory for the rules to be utilised... PW
[Magisk] pndwal:
So a root app... For flashing.zip while booted to system?

With root such 3rd party app may not even be needed; Users should be able to flash Magisk.zip as a module from Magisk App to do the same... Please say if I'm wrong... PW
[Magisk] m0han:
AFAIK, no. I uninstalled Magisk from within the app and device rebooted on it's own. Installed 25206 and since I couldn't do direct install, I rebooted into recovery and flashed the renamed zip. I got root alright. I found that AdAway was not 'working'. I updated to 25209 but ads still appear. I am not able to open certain links because they go on to p*** sites and all. So I removed systemless module, rebooted, installed systemless module, rebooted and then installed AdAway, rebooted...., but I still have problems. I am running 25209 Delta now.
[Magisk] pndwal:
So guess you never did see "successfully installed"?...

Nb. 'Installing' in your screenshot just means 'installing Magisk patch to boot image'... You still need to install saved patched boot image to the device using fastboot or other... That's because Magisk App can't do that itself without root...

After rooting you will see extra Direct Install option so future updates can be applied using Magisk App...

All best installing root... PW
[Magisk] ctcx:
Thanks for all your advice.

The device I have is A/B "payload" partitioning (albeit seemingly without vbmeta partition), so boot.img would be permanently patched, at least until next OTA update or if restoring with Magisk.

Unless... could you be suggesting that I can somehow select which boot image to boot in case I certainly have more than one? (I asume I'd have two boot images in the partition, albeit only one would be in use of course)

If this were true, and I' not misunderstanding, could I boot one of the images directly from the device, without having to use a PC with fastboot?

Oh, and in another point, if I restore original image with Magisk to unroot, what happens with the currently patched image and the original image backup Magisk made?

And finally, is YASNAC a totally safe app?

Thanks very much again.
[Magisk] pndwal:
So did you also use .zip installer to update to 25209?... Please see my response to you above... (If so you'll need to patch or repatch image while system is booted for 25207+ builds...)

Where Direct install is not available you can patch in App then flash patched image with fastboot or from recovery... (for some Mediatek (and other?) devices that don't allow modification of boot.img after system boot as they are mounted read-only, Direc install simply doesn't work). PW
[Magisk] dcarvil:
Yes, you must be rooted for Ex Kernel Manager to flash the zip. You are probably right about the Magisk App doing the same. I have not tried it.
[Magisk] pndwal:
Ah yes... So using Magisk in recovery will generally be off the table for A/B devices as recovery partition is removed... Some A/B devides (eg OnePlus 8T) Do retain dual recovery partitions however, so Magisk could possibly be installed to recovery ramdosk...

You do have two, but generally can only boot to current slot... Magisk simply installs to current slot also...

I don't have A/B device, but unless you can change active slot on device somehow and have two complete (identical other than boot.img) systems installed I'm not sure swapping will be easy...

It's doubtful but I really don't know...

Perhaps you could explain your reasons for wanting unrooted + rooted partitions... I'd love to know what advantages you envisage...

Do you mean flashed image?... It vanishes as it's overwritten...

Guessing these should removed, but wouldn't be surprised if not...

Well Play Store version should be... But it's really obsolete as SafetyNet is depreciated for new Play Integrity API...

You should be checking with Play Integrity API Checker (if you trust it) or similar now...

Welcome... PW
[Magisk] manjaroid:
Is this an older device? Maybe installing the apk in addition to flashing the zip from recovery will make a difference. That's how I had to do it with a legacy phone running stock Oreo or custom Pie.
[Magisk] WoKoschekk:
That's not correct. The folder /data/adb does always exist on all Android distributions. But its content will be "erased" (or will not be mounted) without a Magisk patched boot.img. Booting a stock boot.img will result in a empty /data/adb folder.
[Magisk] m0han:
Yes. Direct Install installs 25210, which I don't want right now. So patched boot.img from the rom zip file. Can I install this patched img from recovery? See my screenshots.

My device is ARM64 Poco X3 Karna. I'd installed Manager using the apk file and then flashed the zip in recovery.
[Magisk] zgfg:
That's not correct (or you are messing with terms "erased", "not mounted" and so)

I've many times and on several devices (experimenting, upgrading ROM, etc), booted with the original, not-patched boot.img and then later booted again with the boot.img patched by Magisk, and /data was not erased, specially /data/adb was not erased

When I booted with the patched boot.img again, I continued using Magisk, magisk.db (database), modules folder, etc, everything was there as left before

I'm not talking about Uninstall Magisk (that would erase /data/adb).

I'm talking about going to Fastboot or TWRP and flashing the not-patched boot.img

That affects only Boot partition and does not erase /data - erasing /data (Factory reset) would erase all your User apps and their settings from Data

And System, when it boots with unpatched boot.img, them it does not care what's on /data/adb - hence it also does not erase, it just ignores

PS: But of course, when you boot with the not-patched boot.img, then Magisk does not initialize and therefore Magisk modules do not start (it's Magisk who must start the modules, not System itself)

Therefore, when you boot with the not-patched boot.img, /data (incl. /data/adb) is mounted but it's not processed

And it's not erased. It will stay there, until the next time you boot with the patched boot img - then Magisk will initialize, it will process /data/adb and will start your modules, etc