yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
@rodken

Just out of curiosity, have you ever just downloaded (not install) and unpacked OTA zip file to see what it contains?

UW variation is the Verizon version?

If you restore it to a previous stock version with the msm tool and just unlock the bootloader.

With no other modification, can you update to the current stock version?

If the update works then it has nothing to do with unlocked bootloader.​

Something to do with another modification (like Magisk).​

If the update fails with just an unlocked bootloader.

There might be a proprietary file (or setting) in the update that would be removed or reset when you unlock the bootloader.

Widevine level, Camera HDR drivers (Sony 🤬) or something carrier related.

Something protected from booting if unlocked.

A while back I gave links to a few posts by osm0sis about updating via OTA.

Post 45,587 - Link

Not sure what you have all tried.

Not sure if you can but, it looks like you might be able to convert to Global OOS. 🤔

Quick search (Came back mostly for T-Mobile)​

[Guide] Convert to Global [WIP] - xdaThread - Link​

Cheers. :cowboy:
[Magisk] ipdev:
Now I will have a song stuck in my head for a few weeks. 🙃

🎵

And if you go.

Chasing rabbits.

And you know you're going to fall.

Tell them a hookah, smoking caterpillar has given you the call.

🎵

Actually it is not that difficult.

aOS 11 and 12 are a nice update from 10.

The changes in Magisk are a bit to get over but, (thanks to the xda family and the Android community as a whole) it is easy to get over the big change in Magisk.

Cheers. :cowboy:
[Magisk] Lughnasadh:
Love me some Gracie, The Great Society, and Jefferson Airplane, although I must say I have always been partial to Signe Toly Anderson before she quit, allowing Gracie to step in.

Funny how things happen. What if Signe didn't get pregnant and quit? What if they asked Janis instead of Gracie to step in?

But I digress and may be a wee bit off topic (see what you made me do 🙃 😅 )
[Magisk] HippoMan:
It's nice to go into (Jefferson) Airplane Mode! :)

From what I have been able to tell when trying to keep up with all of the discussions here and in the TWRP threads, I think that I will lose my ability to use TWRP for nandroid backups and restores if I upgrade to A11 and most likely A12.

Furthermore, I have doubts that OOS 11 or OOS 12 will fix the OOS 10 problem about missed push-notifications. If anything, I'm guessing that OnePlus will have made that even worse, because of their continuing efforts at battery-saving procedures which make it harder and harder for certain apps to function properly in real time.

Also, if I lose my ability to use TWRP, then I will have to go through an extremely painful process to restore my device back to A10, if the A11/A12 efforts don't work for me. In the old days, I could take a nandroid backup, upgrade the OS, and then revert back to the older OS simply by restoring that original nandroid backup. I'm pretty sure that those days are over.

I use my device for my work, in addition to all of my personal fooling around, and I can't afford to hose the device due to upgrade problems with OOS, Magisk, or TWRP, and then lose my ability use the device for an extended period of time while I go through the painful process of either (1) restoring it back to what I had before, or (2) jumping through hoops correcting those failures and then jumping through more hoops trying to get it working with a newer OS or a newer Magisk ... and then trying to get all my dodgy software back to the state where I can use all of it the way I like.

Some day, we might once again come to a place where nandroid backups (or some equivalent), rooting under Magisk (or whatever), and upgrading the OS are all as easy and straightforward as they used to be. If so, I will then try to upgrade.
[Magisk] pndwal:
I think there have been some links to backup apps in this thread supposed to be better than nandroid / better than ever!!

And before you chuck the modding towel into the bath of despondency or just give up in a melancholy hankering for the good ol' days of yesteryear that can no longer be had (I'm just joshin' with ya mate), you might:

Check if OOS major updates include anti-rollback bootloader version changes (unlikely) 'cos then you would really would have reason for caution / reticence.

Otherwise I imagine you could still take a TWRP Android 10 nandroid backup and use it later (in the event of severe depression brought on by regret that you listened to those XDA Magisk modding mugs) simply by saving current ROM & TWRP with it and clean flashing those before restoring backup... Am I missing something?

FWIW, I think John / others are doing their level best to increase Android's potential for doing what we want... wasn't long ago my phone was not much more than a phone even rooted... now it seems an injustice to call it a phone... 😛 PW
[Magisk] vandyman:
That might explain why some peeps post crazy questions on this site.
[Magisk] HippoMan:
I think that some day, there's indeed a chance that John et al will get us to the point where we might be able to use Android similarly to how we used to be able to use it, and I will then be glad to go back into the modding world. I continue to mostly just lurk here these days, and that means that I'll be able to see when this would occur.

I missed the discussions about backup apps here, and I will go back and see if I can find what you are referring to.

I know I could roll back to OOS 10 if there are issues with upgrades. I just know from experience that this could be time consuming, and time is at a premium for me these days.

But maybe, some day, things will be better with Android again, and my hope for that springs eternal.
[Magisk] dcarvil:
My Pixel 3 did the same thing when A11 was released. I was unable to get monthly OTAs for A10, but got the constant nagging to upgrade to A11.
[Magisk] pndwal:
Here's a couple from simple search:

- https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85762351

- https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85961337

Can't vouch for them; I was just to lazy / time-strapped! 🤪

Just meant nandroid restore should be usable to roll back since you seemed concerned you'd 'lose ability to use nandroid backup' & would need to restore beloved A10 setup / mods piece by piece!...

Good thing we have such springs of hope... especially since time is such a limited / premium commodity these days! 😋 PW
[Magisk] rodken:
The conversion to Global is an idea that I have been debating on for the past few months - I just don't have the patience to be chasing anymore ghosts if I somehow 'bork' my device and have to rely on MSM to get myself out of a jam.

Restoring it to a previous stock version with the MSM tool and just unlocking the bootloader proved to be to no avail regarding taking OTA's.

The UW variation [IN2019] is the Verizon variant and I've been to hell and back tinkering with updates and OTA's when I first got the device. At one point in time, I've even taken the liberty of utilizing the SUA [Software Update Assistant] to update and ended up causing a corruption where the SIM card could not be read by the device which leads me to think that a proprietary file in the update has been changed.

The longer that I wait, the more the idea of converting to Global becomes enticing.

Nevertheless. there is also the issue of flashing a Custom ROM to mitigate the need to having the latest and greatest - but again, I find myself falling into the rabbit hole of not having a method of utilizing a Nandroid Restore due to the fact that the current beta versions of TWRP for my device doesn't have any clarification on whether or not performing a restore is 'clear cut and precise'.
[Magisk] unkwnuser01:
Hi I need some help. I recently was able to get magisk working on a samsung galaxy a52s 5g (building from source) which works just fine except for the fact that I can't view and download available magisk modules in the modules tab. I don't have any firewalls on anything so it's not a network issue. Does anyone know what may be causing this? please and thank you!
[Magisk] J.Michael:
You will need to search this thread to find whether your version of Magisk supports a module repository.
[Magisk] zgfg:
Removed from new Magisk app. Mentioned several times here, search for Fox Mmm
[Magisk] Homeboy76:
GitHub - Fox2Code/FoxMagiskModuleManager: A new module manager for Magisk when the official app drop support for it

Fox Magisk Module Manager Releases

Happy Holidays!
[Magisk] HippoMan:
Doing this search is exactly what I meant when I said that I was going to go back and check for those backup apps, and I have already done so. Thank you for also doing so and then posting those links. Time permitting, I'll check out those backup apps.

Yes. I know I can restore my device to a pristine state via MSM, and then install the TWRP that still works under OOS 10, and then restore my nandroid backup. But I am even losing patience with that ... and anyway, it would only be necessary after having previously spent time unsuccessfully trying to upgrade OOS, Magisk, and TWRP, and based on what I see here, I'm sure there is a good chance that this upgrade procedure will also involve lots of headaches, and there's a very good chance that I will hit roadblocks along the way which take even more time to deal with. So, I don't even want to take the first step down that road, for the time being.

I'm just waiting for things to stabilize again (I hope!) with Android, Magisk, and TWRP (or some alternative way to do backups and restores), so that modding stops being so onerous. It used to be fun and interesting for me.
[Magisk] HippoMan:
I'm in the same place these days.
[Magisk] HippoMan:
PS: I have now checked out those links, and both refer to software which does not do the same things as nandroid backup/restore.

Those utilities just deal with installed apps and don't backup/restore the Boot, System, Vendor, and Data partitions like TWRP's nandroid does, and therefore, they can't be used to restore an entire OS from a backup.

And in any case, I currently have these installed and have been using both of them for a while for my app backups and restores.
[Magisk] DiamondJohn:
A LOT of config is stored in the settings. For example:

settings put global "window_animation_scale" "0.5";

Because I use to build ROMs from source and therefore clean flash my devices a lot, I built a method to extract and reinstate all my config, to be used selectively and in combination with normal back-up apps, to reinstate my device as close to its previous state without manually hunting and seeking all the settings, after a clean flash.

I automated this task as a method within the app TeMeFI and can be found under Current State>Settings>Generate Set All
[Magisk] HippoMan:
Thank you. Yes, I have seen and used that from TeMeFI.

This is probably as close as I can get to restoring my OS without nandroid backup/restore, and it certainly is helpful.
[Magisk] Lord Sithek:
Oh thats interesting! How exactly does it work to restore settings using this app?
[Magisk] rah2501:
I'm in the same situation, I have the last official LineageOS build (14.1) installed on a Nexus 5. @proza 's question didn't seem to be answered. When I try to install Magisk, I have this option:

The official documentation doesn't even mention this option.

Looking through @Didgeridoohan 's guide, it says "there are those devices that need it to still be enabled or they won't boot". How can someone determine whether their device needs this checked in order to boot? This is pretty critical information! I don't want to brick my device so how can I determine whether this should be checked?
[Magisk] pndwal:
Yup, needed on some non SAR devices.

The rule is Don't touch such Magisk settings unless you need / understand them; if you can boot to Magisk as it is preset, don't touch it...

This and a number of other settings appear only for 'legacy' devices; here's why you see it / newer devices don't show it:

www.twitter.com/topjohnwu/status/1297833910320021504?t=4K-QHRPBwLsin12s35Hf2w&s=19

Here's an answer re. it's use to restore ability to write to (modify) protected partitions lost in recent Android versions + advice:

www.twitter.com/topjohnwu/status/1038842557290213376?t=EZvPHejxdUswgs6wm8OcYg&s=19

👀 PW
[Magisk] rah2501:
What do you mean? Are you saying I should check it?

Which non SAR devices? What is a non SAR device?

How do I determine whether my device is a non SAR device and if it is, how do I determine whether it's one of the non SAR devices that needs this option checked?

This is the first time I've installed Magisk. I don't know whether I can boot to Magisk. That's what I'm trying to determine, before I try it and brick my device.

I don't understand any of this thread.

I don't understand any of this thread either.
[Magisk] pndwal:
No, I said 'Yup, needed on some non SAR devices' as you stated @Didgeridoohan's wiki indicated. Then I said 'The rule is Don't touch such Magisk settings unless you need / understand them; if you can boot to Magisk as it is preset, don't touch it'. So try WITHOUT changing whatever John preset for your device!...

If you get bootloop etc, recover by flashing uninstall.zip from TWRP, of flash stock boot.image from TWRP or Fastboot and then try with altered settings...

Alternatively, check forums for your device to know if you can or should change the setting...

Doesn't your 23.0 Magisk app home screen mention SAR? It means uses System As Root for booting.

Yours should say 'SAR - no' (indicating Legacy ramdisk type) as the dm verity option shouldn't show on SAR devices; it has become"complicated" / breaks boot for many of these as John said.

'Legacy ramdisk' generally includes devices launched with Android 8.1 (API 27) or less with the exception of some Pixel / OnePlus etc devices that booted with 'Legacy SAR' on Android as early as 7.1 (API 25).

Here is information on SAR and the major Android architecture changes since the 'good old days' of Legacy ramdisk:

https://topjohnwu.github.io/Magisk/boot.html

You'll note here that if you (can) upgrade your OS to Android 10+ (API 29+), you device becomes '2SI ramdisk SAR' for Magisk's purposes although Google still considers it (Legacy?) ramdisk boot type.*

*Nb. I believe this may be relavent to why John has removed SAR indication in main Magisk branch (as built in Canary already); his definition of SAR at odds with official Google documents can cause confusion... I wouldn't be surprised to see this document updated with John's SAR definition etc harmonised with Google's once new public Beta or Stable is released. 😜

Both questions covered above...

All the best! (Suggestions above also.)

He's explaining that settings like this may be "confusing/useless installation options" particularly dangerous for SAR devices with logical partitions scheme etc, but that "In the spirit of backwards compatibility, these options are still there on supported legacy devices" to confuse their users. 😛

Clearly users of these devices need to know what they're doing but are not denied the old options if intrepid!

User wanted to alter vendor partition; example of an intrepid user. 😝

John said you could use verity switch for that but that there's a better way to achieve desired result...

Hope this helps get 2022 off to a good start!

🤠 PW
[Magisk] Bright.Light:
I tried searching in this thread, but the xda app is really impossible.

What has happened with the directory of modules? I have to search over the complete internet just to find some modules, but most are out of date.

Can please anyone recreate module directory? (and don't tell me they're is a thread here because that's impossible to read)
[Magisk] zgfg:
You were answered here, for the app you need to Google for (or search about in this this thred):

Also (if you didn't follow posts in this thread where changes were discussed several times), please at least read ChangeLog when installing new Magisk to be up-to-date with what you are going to use 😍

More older posts about the same:
[Magisk] zgfg:
Duplicate
[Magisk] Bright.Light:
I did read the log, that 's why I question the possibility of using any search. Seems the modules are all gone, over and out. For that xposed library was much better.

If possible to request : please (re) create a usable pickle library
[Magisk] zgfg:
Please before asking over and over, did you search to find the Github for Fox Msgisk Module Manager I pointed you?!

Did you read there what the guys did - they created new Modules Repo?
[Magisk] Bright.Light:
Thank you for this. I still wonder why the library was dropped. Or better, I don't understand why. This way others will make their own libraries and so we might get a lot of different ones, making only more fragmentation in the sources.

But for this thanks!
[Magisk] zgfg:
It was discussed here long ago, when TJW announced on the Twitter. In short, he mentioned that he didn't want to maintain the Repo anymore (taking time and energy, not interested about and not being part of developping/maintaining the Magisk itself)
[Magisk] ipdev:
I would recommend switching to the (un)official hammerhead builds.

[ROM][unOFFICIAL] LineageOS 14.1 for Nexus 5 (hammerhead) - xdaThread - Link

When Lineage stopped building 14.1, razorloves switched over to running unOfficial builds.

He does this for a few devices that he could not bring up to a newer Lineage version. ;)​

I did a clean flash on my hammerhead a few weeks ago testing something and never got around to rooting it.

I just rooted it again. ;)​

When I patched the boot image with Magisk, I did not adjust any setting in the patching.

It took awhile to patch. :rolleyes:

Then I rebooted to bootloader and tested it by temporarily booting the patched image.

Magisk was active so I used the Direct Install option to patch the installed boot image.

Again this took awhile (Almost three minutes).

Rebooted and all good.

Cheers. :cowboy:
[Magisk] DiamondJohn:
ummm.. It is all done by running shell scripts. And an example of "how" it sets/restores an individual item is explicitly shown in the post that you quoted.

In a nutshell it loops through ALL the settings, and writes out a matching "set" statement (as in the quote) to restore that specific item.

The "exactly" is provided/detailed in the app by retrieving the source code of the script (ie open source), which is viewable & save-able from the app itself, ie TeMeFI see the first few post, in that thread, on how to get the source. Also long clicking the menu item gives the option to view the source.
[Magisk] dergrey:
i also meet this problem, could you tell me how to solve it?

thx
[Magisk] pndwal:
A recap of John's known changes / intentions re. module repo + recent developments:

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

Subsequent Magisk builds have already dropped repo access.

Update functionality is now broken even in previous builds as per John's tweet:

www.twitter.com/topjohnwu/status/1474101935611408389

and announcement update in TG Magisk Alpha group:

https://t.me/magiskalpha/397

Seems John has completely repurposed Magiskbot just a few days a ago:

Readme.md is updated from:

to:

https://github.com/topjohnwu/magiskbot/commit/43e39211708251bb7900799e0e7705e9672d9264

I note heaps of code deleted along with all these files:

+0 −9 .babelrc

+0 −173 lib/Github/Gist.js

+0 −231 lib/Github/Issue.js

+0 −38 lib/Github/Markdown.js

+0 −113 lib/Github/Organization.js

+0 −209 lib/Github/Project.js

+0 −3 lib/Github/README.md

+0 −34 lib/Github/RateLimit.js

+0 −859 lib/Github/Repository.js

+0 −245 lib/Github/Requestable.js

+0 −97 lib/Github/Search.js

+0 −150 lib/Github/Team.js

+0 −159 lib/Github/User.js

+0 −143 lib/Github/index.js

+0 −138 lib/MagiskRepo.js

+0 −88 lib/Module.js

+0 −23 lib/Shared.js

+0 −88 lib/Submission.js

+0 −127 lib/count.js

+0 −39 lib/errno.js

+0 −5 lib/index.js

+0 −70 lib/server.js

in the commit Rewrite with TypeScript

So far Magiskbot is reassigned Moderate issues to follow template and Auto close spam issues/Pull Requests among other things. This coincides with the following commit (to remove old issues Bot) in Magisk master:

Remove issues action …

'Handled by external MagiskBot'

... Time will tell if John does 'transfer administration and maintenance of GitHub (module) organization to trusted community members & who candidates will be and / or 'eventually enables users to set their own online Magisk module sources which the Magisk app can handle', but it now seems we will likely get a "per-module update URL that the Magisk app can use to download and upgrade on a per-module basis" before we ever get "another centralized "store-like" module repository"... Yay! 😛

https://github.com/topjohnwu/Magisk/issues/4908

👀 PW
[Magisk] pndwal:
A number of fixes coming (already merged downstream) in imminent Magisk build:

Skip loading Magisk when detecting DSU …

GSI compatibility fix

Add an old cgroup path ...

Fix for PineNote device

* If dt fstab contains error, fallback to default fstab …

Fix for a number of Samsung device issues:

https://github.com/topjohnwu/Magisk/pull/5139

Fixes in pipeline with working test builds:

Sony Xperia

https://github.com/topjohnwu/Magisk/pull/5146

Samsung Note 4 and other armeabi-v7a devices running stock Android 6, 7

https://github.com/topjohnwu/Magisk/issues/4174

Great recent progress in longstanding issue!

OnePlus 7

https://github.com/topjohnwu/Magisk/pull/5070

Support Android 12L for largescreen devices

https://github.com/topjohnwu/Magisk/pull/5048

* This may well fix your issue.

Also, John's comment on Sammy's handling of 'broken stuff in device tree.' 🤪 (MA rating):

www.twitter.com/topjohnwu/status/1475985579036667904

🤠 PW
[Magisk] dergrey:
thx！
[Magisk] optionalmgrr.la:
i can no longer use icbc app after the app was updated to latest version, help!!! thx!!!!!
[Magisk] pndwal:
RN8T, latest Magisk Alpha w/ USNF 2.2.1 + Shamiko + Hide the Magisk app set only:

PW
[Magisk] zgfg:
Did anybody play with SUI ("Modern SuperUser Interface"):

https://github.com/RikkaApps/Sui

I installed Zygisk flavor (Magisk module), enabled sui.app, created /data/adb/sui/enable_adb_root

but when I try to copy and use rish shell per /data/adb/sui/post-install.example.sh, there is no rish.dex, etc

---

Unrelated:

Just updated Zygisk LSposed to the latest v165 (6298) and everything is ok except that it complains that I have to update - and when I accept updating from the app it fails complaining there is no Riru?!
[Magisk] IamTheBRAVE:
Hey guys, i would like to report something i noticed...

I have magisk 23.016 with root working ok but system partition is inaccessible to root file managers because of the EXT4_RO issue ( i read about it and i know there's nothing that can be done other than use modules to flash files)

Today i was doing just that. Flashed a couple overlays to product. The files weren't flashed correctly, so instead i tried copying the files again and all my root file managers were able to rename, copy, and delete files from the overlay folder.

Does that mean if we flash files to a specific partition it becomes switched to rw ? Or am i missing something?
[Magisk] shoey63:
Same behaviour here
[Magisk] pndwal:
Just added this:

www.twitter.com/topjohnwu/status/1474101935611408389

To this:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86184789

Somehow I'd missed official announcement. 🤪

Seems we will likely get a "per-module update URL that the Magisk app can use to download and upgrade on a per-module basis" before we ever get "another centralized "store-like" module repository"... Yay! 😛

https://github.com/topjohnwu/Magisk/issues/4908

😝 PW
[Magisk] Qnorsten:
The app always seem to try and install the official riru lsposed version regardless of which one you have installed. So you need to download the zygisk zip manually and install it. It sound like you already did that though. No idea why the app still complain for you, my app is fine. Perhaps try to wipe cache or reboot?