yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Unless you're dealing with Manager issues, which has been the focus here the past few days.
[Magisk] zgfg:
True (e.g. for parsing error while updating Manager), but his Magisk hide issue may look like Manager issue (since UI control and empty list is in the Manager) but rather might be the issue with Hide db that is not covered by cleaning Data for Manager in Settings

Hence for users (not familiar how Magisk stores the data and how Manager accesses them for UI control) it is not always simple to judge what is Magisk issue or what is really only the Manager issue, i.e. what type of cleaning would help

And that leads e.g. for posts with wrong instructions
[Magisk] pndwal:
[MENTION=7786725]zgfg[/MENTION], [MENTION=4667597]Didgeridoohan[/MENTION]

But seems he's simply saying clearing manager data allowed him to load and flash new manager (without parse error), but clearing cache only, as he was advised, didn't. (Apparently didn't work for others thought.)

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83389825

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83393883

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83399247 ... PW
[Magisk] zgfg:
Maybe we have lost track of what was the last open issue here that was discussed.

Please correct me if wrong, but I think it was this user and it was no more about parsing error while updating Manager but his issue with blank Magisk hide list, and he tried things like cleaning cache, data, etc, with no success:

At least, I was referring in my today's discussion on that user and his blank Magisk hide list, no more to the old story about parsing error while updating Canary Manager, and related workaround to clear Manager's Cache
[Magisk] Didgeridoohan:
In my clarification post I was quoting a user that was involved in the parsing error discussion, so I was very much referring to that...

In regards to [MENTION=656056]vMAC[/MENTION]'s problems, since he has already tried both clearing data and reinstalling the Manager the next step would be to look at Magisk's internal files (deleting /data/adb/magisk.db might fix things if it's a database issue, but unhide the Manager first) and possibly reinstalling Magisk fully.
[Magisk] pndwal:
THE FUTURE'S LOOKING BRIGHTER for Mainstream Magisk Root!

With easy SU Hide for passing SafetyNet to boot! :)

From the Horses Mouth one may deduce that all is not yet lost -

Who knows what gains should Sorbet bring, or what could be the cost... :(

https://mobile.twitter.com/topjohnwu/status/1299903496028790785 PW
[Magisk] RebelLion_:
Another update, I tried the overlay method with no success. I also moved my script to an actual post-fs-data script before this to try and patch the rc file before it's triggered. Neither change seemed to make a difference. Idk if this is the correct thread for this since no one's replied but the module dev's help thread is pretty dead. Just looking for any advice, is there maybe a telegram for module devs? [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] vMAC:
Tried this and it still didn't work. I will uninstall Magisk and attempt a reinstall later this evening when I get home to access my computer with ADB.

Thank you [MENTION=4667597]Didgeridoohan[/MENTION] and [MENTION=7786725]zgfg[/MENTION]
[Magisk] jcmm11:
If I'm not mistaken the rc files are generated by the kernel. If you want to change an rc file you'll need to unpack the kernel, modify the rc files you'll find in the ramdisk, then repack the kernel. [MENTION=4544860]osm0sis[/MENTION] can correct me if I'm wrong.
[Magisk] RebelLion_:
Oof been a while since I've messed with ramdisk stuff like that, although I'll try to implement it that way. I didn't know where exactly i needed to do the work for it just had the general idea lol. Thanks
[Magisk] osm0sis:
Depends on the device, i.e., if it's SAR then they're in the system partition now (and you'd need to use overlay.d), and if it's also boot-as-recovery then the ones in the boot partition ramdisk are actually the recovery ones. Thank Google. :silly:

Also note that overlay.d is currently broken on Android 11, IIRC.
[Magisk] RebelLion_:
Nice. That was going to be my next question is with all the different layouts and such what would be the most universal method to detect the boot layout and find the file. I see that I'll need to do some digging and testing though. Any other tidbits I should know about I would appreciate it, I've been reading through Magisk's docs to try and find out what I could
[Magisk] vMAC:
Ok so I wanted to make sure to get everything reset. So I disabled all the modules in EdXposed, rebooted, Uninstalled EdXposed. I started to disable the modules in Magisk when I decided to check Magiskhide again. Voila it works. So I enabled each module back in Magisk, then started the same in EdXposed (rebooting after every install), and found out it was xPrivacyLUA that was the culprit. Nothing was checked for Magisk but it was still somehow blocking it. I toggled oon, off and restarted my phone Magiskhide was back.

tl;dr - xPrivacyLua was somehow blocking Magiskhide. Toggle On, Off reboot and Magiskhide UI is working again.

Thanks for everyone's suggestions.
[Magisk] RebelLion_:
For anyone who is following my posts, AnyKernel3 just pointed out my glaring ignorance (I'm a part-time kernel dev lol). That's the missing piece to my puzzle, made for kernel and ramdisk modifications. I'll have the zip ready shortly and make it available for devs/testers when I can
[Magisk] pndwal:
Well done!

I'm guessing "feeding apps fake data instead of real data" may be the problem for Magisk Manager.

https://xdaforums.com/xposed/modules/xprivacylua6-0-android-privacy-manager-t3730663

Just wondering, if one can "Manage any user or system app", perhaps Magisk Manager can/should be excluded within XPrivacyLua.

Sounds like you may have checked this ("Nothing was checked for Magisk but it was still somehow blocking it"), or may still be looking for compatibility solution. :)

I'm not an EdXposed/Xposed user, but please let us know it this (or similar) can allow this to work with MagiskSU/Manager for others. (I imagine others must have this working as module is still current.) :good: PW
[Magisk] hyborian:
My bank app has become smarter too. It is Magisk hidden, Magisk name is also hidden, both SafetyNet pass. The app only used to be able to detect if Developer Options was on, but with its latest update can now detect root.

Since all the usual tricks have failed now, my workaround when I want to use the app is to go to twrp, save the rooted boot img, restore the stock boot img, reboot back to system. Then restore back the rooted boot img after doing the banking transactions.

Will just buy another phone unrooted for banking later on :p
[Magisk] pndwal:
- Official (Stable) Android 11 [aka RVC / Red Velvet Cake] slated for this Tuesday (8 September)? (Maybe, maybe not: https://www.androidauthority.com/android-11-launch-date-1136129/ )

- Stable Magisk 21 before that?

(John wants to achieve this goal. - Last Stable was released 5 months ago. https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83350707 )

https://mobile.twitter.com/topjohnwu/status/1301011553819348992

Get ready! :)

Nb. Those with 2SI device checking logic problems running Android 11 (MagiskSU not working as /apex absent in ramdisk) will be especially interested to see if this is fixed so Magisk w/ Android 11 can work for affected SAR A-only devices also.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83293351

:good: PW
[Magisk] JudgeDread11:
Have you tried island?

Edit: nevermind.

If replacing the boot img solves it, I don't think island can help.
[Magisk] Tendor83:
I'm in the same boat as you. By any chance you are talking about ING RO?

After I updated to ver 4.1.5 the app will not work anymore on my rooted, magisk enabled and Hide device, also with SafetyNet pass. I also use a custom rom, but I don't think this was the culprit.

It is the only banking app that manages to detect the root or magisk component.

For banking transaction I just go the browser bank URL and login in there, with a PIN generated at every login, but this has become quite frustrating.
[Magisk] hyborian:
No, it's a different bank, and I use stock MIUI rom with custom kernel.

Thanks, why didn't I think of that ? ! Just go to the bank's website and do it from there, unless it has a check again if I'm using mobile phone and if rooted lol

I was looking at dual boot, but apparently no longer good for Pie, Android 10, 11 ...

---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------

No, it's a different bank.

However, thanks, why didn't I think of that ? ! Just go to the bank's website and do it from there, unless it has a check again if I'm using mobile phone and if rooted lol

I was looking at dual boot, but apparently no longer good for Pie, Android 10, 11 ...

* Edit : Darn, when I go to the bank's website and try to login, it redirects me to Play Store to download its app. I guess their programmers have it covered as well ...

.
[Magisk] Didgeridoohan:
Most browsers have a "Use desktop site" toggle you could try.
[Magisk] hyborian:
Thanks, I tried, but their systems analyst is smart, as they should be, being paid well by the bank ... they got it covered too, desktop or mobile site.
[Magisk] JudgeDread11:
Getting a little of topic here, but try to switch the user agent of your browser.

There are some browsers and tools available.

Google it.

It should make the browser identify itself as a desktop browser, rather then a Android browser requesting a desktop webpage layout.

I haven't tried this, but it might be worth a shot.

---------- Post added at 02:12 PM ---------- Previous post was at 02:07 PM ----------

There is a dual boot option available for Android 10 on OnePlus 7 making use of the a/b partitioning structure.

The dev mentioned at some point that it should be possible to port it to other devices it somebody has the device and the understanding of the innerworkings of the mod.

Also I'm not sure if it would be possible to have a stock boot image on one of the slots.

Thinking about it, if the only reason for dual boot is having a different boot image with same data just flashing your rom to both slots and only install Magisk on 1. You should be able to run your banking app when booting from slot a and be rooted when booting from slot b.

Not sure at all if this would work. Still need to unlock your boot loader and without Magisk you can't hide an unlocked boot loader. But if flashing stock but image, without removing your boot loader works it might be possible.
[Magisk] hyborian:
Ok, using a user-agent switcher for chrome, it works ! Webpage is fine, but only half of the login page can be seen in either portrait or landscape. It's like it is supposed to display on a huge wide screen, and the rest of it is out of the screen. It's the same on the Dolphin Browser, which can change user agent without a plugin.

Anyway, will try to figure it out, thanks.
[Magisk] zzz2002:
Just tried update, Magisk to 20421 on a SM-T813. Hung on reboot. Had to re-flash Magisk, only release I had avail was 20400.
[Magisk] beardymarrow:
Same for me on Oneplus 6t. I get the Qualcomm CrashDump Mode. Fortunately I can still get into TWRP. Installed 20420 from recovery and all fine. Tried again and get the same result.
[Magisk] :
Same problem for me, Magisk version 20241 freeze boot to G935W8 and N9935F.
[Magisk] mrbonine:
I took the Magisk update on my SM-970F this morning (latest Canary version pushed today) and I'm in bootloop. Not sure how to resolve, maybe flash previous version? Please advise.
[Magisk] zgfg:
Same on Xiaomi Mi 9T, MIUI 12, Android 10

Tried patching boot.img with Magisk 20421 from Manager 296 and 297, same bootloop.

I thought it's maybe due to the hidden (not controllable) patching options but log shows that it correctly used:

KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]

I always keep my old, working patched boot images, hence flashed back the one with Magisk 20420

And despite Changelogs claiming opposite (fixes in Hiding MM), Hiding MM is broken since the Manager 294.

MM 293 was the last version where Hiding MM worked (although with some limitations when setting the repackaged name but it worked), for 294, 295, 296 and now 297 it fails (Play Protect disabled)
[Magisk] Didgeridoohan:
I don't think I've seen anyone else report on this. Logs?
[Magisk] zgfg:
Just returned back from shopping (where I first tried on the go), repeated and collected logs:
[Magisk] Lukasyus:
My OnePlus 7 Pro doesn't boot up anymore since the last Magisk update a few hours ago. Pressing the power button doesn't do anything. When I hold power and volume up I see the "Bootloader unlocked" disclaimer screen for a few seconds, then the screen turns black again. Does anyone have a suggestion? Thanks in advance :)
[Magisk] palmbeach05:
Guys, the 20421 does have issues and there is a ticket open on github. revert back to 20420. no need to flood this thread.

https://github.com/topjohnwu/Magisk/issues/3128
[Magisk] zgfg:
You would have to have saved your boot/recovery (whatever applies to your device) image patched by 20420 (where it worked fine), now you would simply flash it back to return to the working Magisk 20420

If you don't have it, you would need now to flash your stock boot/recovery, and install or patch again but with Magisk 20420

Or ask somebody else with the sane device and firmware to share you the boot/recovery image patched by 20420
[Magisk] Lukasyus:
Thank you for the reply. How can I flash anything though if I can't even boot into recovery or fastboot? After the disclaimer message, the screen just goes black...
[Magisk] zgfg:
Sorry, didn't know that it got so bad for you.

In my case I just rebooted to TWRP and flashed my old patched boot image.

But did you try rebooting to Fastboot - don't know for your device but there is maybe a key combination to reboot directly to Fastboot (like keeping pressed Vol- while booting or so)
[Magisk] Lukasyus:
Somehow I managed to boot into fastboot. Could you please let me know step by step what I have to do now? I haven't used fastboot for a while and don't want any missteps at this point... FYI: I don't have a backup image. Thank you!!

Edit: I'm on a OnePlus 7 pro with A/B partitions, no custom ROM. TWRP recovery is technically installed, but I'm afraid to boot into it because when I tried it before the screen went black. Any way to get my phone working again by using fastboot (preferably without a full wipe)?
[Magisk] dobi3:
I had same problem on my OnePlus 7 Pro..

I just selected recovery from fastboot using volume +/- and then use power button and went to TWRP and then select previous version of Magisk zip and I am fine now.

I read where you said screen went black :(

I think went black from Qualcomm crash dump.. Was hard to read
[Magisk] zzz2002:
where can I find a copy of Magisk 20420.

I had to install the only copy Magisk I had on hand 20400, which is a little out of date|
[Magisk] palmbeach05:
https://github.com/topjohnwu/magisk...d9fab2017d57c723e28c18a0d996/magisk-debug.zip
[Magisk] Alxoom33:
Wow, did this thread explode! I had the same bootloop issue with 21 on my Pixel2XL. Manually booted to the bootloader, fastboot booted into TWRP and flashed Magisk canary v.20 easy peasy!
[Magisk] Lughnasadh:
John knows about the bootloops.

https://twitter.com/topjohnwu/status/1301702962104791040
[Magisk] Jakeroxs:
Oneplus 6t user here, had the same issue where the phone was bricked and booting to the Qualcomm Crash splash page. Didn't have twrp installed as a backup (just hadn't gotten around to getting it installed again) so I started there, booted into recovery first (couldn't get to fastboot through the volume + power for some reason) then used the "boot to fastboot" option. Installed adb+fastboot drivers (just google it and find the XDA link) and downloaded the option cmd.zip to easily access fastboot. From there I downloaded the latest TWRP recovery image from the official TWRP site and booted from that IMG via fastboot boot twrp.img (renamed to twrp.img for ease of typing) which got me into TWRP. I then downloaded the latest stable magisk-v20.4.zip and moved both it and the twrp.img file onto the phone. Through TWRP I installed the magisk-v20.4.zip and then went to Advanced > Install recovery ramdisk to flash the twrp.img so it'll be a bit easier to get to TWRP in the future.

Booted it back up and good to go! Hope that helps someone :)
[Magisk] pndwal:
You can try again now guys: :)

https://mobile.twitter.com/topjohnwu/status/1301702962104791040

Guess this demonstrates the importance of checking for typos! :D

(Thanks John Wu, and all you Mavericks pushing the envelope. You guys got The Right Stuff...) PW

Edit:

Many still have problems. See below.
[Magisk] dobi3:
Magisk-61599059(20422).zip working fine on

Oneplus 7 Pro :):D
[Magisk] pndwal:
20422 didn't work for you?

"Sorry, Goose, but it's time to buzz the tower." (Maverick)

Appears the bootup issues are not fully resolved by new build, and many are still in a '4g negative dive flying inverted'. See latest 'Issues' on GitHub. https://github.com/topjohnwu/Magisk/issues/3134

I'll stick to stable flight till you testers can land safely.

"This could be complicated. You know on the first one I crashed and burned!" (Maverick) PW
[Magisk] hanschke:
today build dont work on my pixel 4xl with android 11. so back to non root :(
[Magisk] zgfg:
Patching 20422 and working fine for me on Xiaomi Mi 9T, MIUI 12, Android 10

Still problem (broken in Magisk Manager till 294) with Hiding Manager, but no prio and time for that now
[Magisk] Lukasyus:
I finally managed to boot into TWRP, pushed the previous magisk version to the phone via adb, then installed it through TWRP and I'm up and running again. Thanks to everyone who helped!
[Magisk] 73sydney:
Do what i do, get to things after somethings happened and get the fixed canary update :)

Timezones for the win... :)
[Magisk] Ryuuske01:
Confirming

Just to confirm:

Runs on the Lava IRIS 88s ( MT6739).

Had to patch the boot.img and then either flash with fastboot( OEM bootloader unlocked) or with the SP Flash Tool.

Works perfectly :)

Thanks for the great work!
[Magisk] :
Version 20422 canary same problem bootloop with G935W8 and N935F android 9.0. reverts to 20420.
[Magisk] pndwal:
Despite ongoing problems, John is clearly working on 2SI device checking logic problems for those running Android 11 on affected SAR A-only devices (MagiskSU not working as /apex absent in ramdisk).

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83414511

Seems this proper fix he wanted to preceed the imminent Android 11 Official Launch may be largely achieved in today's earlier release:

"Magisk (20421)

- Properly detect 2SI init, should fix Android 11 support on many devices."

BUT this was overshadowed by the bootup issues experienced, and another fix was needed:

"Magisk (20422)

- Fix bootloops on 2SI legacy SAR devices."

(Including Commit to "Fix typo for SAR first stage init")

We are still awaiting a fix for a very similar but new issue:

"Canary 20422 patched kernel boots to Fastboot #3134"

John Wu is aware of this, and added "bug" label 5 hours ago.

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

+++++++++++++++++++

Incidentally, Magisk Manager received the following fixes on 31 August:

"Magisk Manager (297)

- Fix several bugs in manager upgrade logic. It should now successfully upgrade under all circumstances after this build. If you ran into "cannot parse package" error, clear the app cache and try again.

- Allow arbitrary package name and app label length for repackaging." PW
[Magisk] Iustin_Theft-07:
Hello! Is there any way to switch from magisk 20.4 to supersu on a device running android 4.4.4 (touchwiz) that doesn't have a custom recovery ? Magisk causes extreme overheating on this phone (CPU temp > 80°)
[Magisk] pndwal:
...And here's the next fix!

Wanna try again you gluttons for punishment? :laugh:

"Magisk (20423)

- Fix bootloop on legacy rootfs based devices

- Fix incorrect 2SI detection that always report incorrect results (that will also fix tons of bootloops)

- Update SELinux rules, fixing several issues"

(Including Commit to "Fix typo causing rootfs device bootloops")

Three builds in a day! ... Got to be a record.

Pretty impressive I'd say, for this solo flying engineer! Kudos John! :good: :good: :good:

(Still, problems are being logged with this build as we speak. - SELinux implementation, etc... Stay tuned.)

"You’re everyone’s problem. That’s because every time you go up in the air you’re unsafe." (Iceman)

"That's right, Iceman. I am dangerous." (Maverick)

..."You can be my wingman any time!" (Iceman)

Go John! :cowboy: PW
[Magisk] zzz2002:
Installed 20421, 20422 & 20423 on gts210vewifi and hero2lte

Same problem all of them on SM-T813, hangs or loops on boot. Reverting to 20240.

hero2lte (S7 Edge) Boot loop 421 (known problem), worked 20422 & 20423.
[Magisk] palmbeach05:
Yes there is, but are you absolutely sure its magisk that is causing the overheating?
[Magisk] zzz2002:
Where is the boot log to be found on a SM-T813?
[Magisk] pndwal:
Think your version numbers are muddled... Unless you're going WAY back... Guess typos are only human! :) PW
[Magisk] dope77:
i have j610f running stock 9.0,

21&22 are causing bootloops,

i flashed 23 and device booted but magisk manager wont open,it just hangs on magisk logo and its denying su requests for all apps that were previously granted su.

guess i'll revert back to 20
[Magisk] :
Okay version 20423 work fine. No bootloop to N935F android 9.0
[Magisk] Iustin_Theft-07:
Yes. Had supersu on it before. It didn't overheat at all. Switched to magisk for the modules but now I want to revert. So, what's the method? ))
[Magisk] hanschke:
20423 tried and no luck. How to flash 20420 with the manager because I have no backup of android 11 boot.img patched
[Magisk] palmbeach05:
20421 is a bad revision, its all over here, tg, github. Everyone knows to stay far away from it.
[Magisk] 73sydney:
Just updated twice to day from 20421 to 20422 and then to 20423 just now

No drama here, must only be affecting certain devices

Pixel 2 XL here
[Magisk] zzz2002:
ooops! tht should read 421,422, 423, will edit original post
[Magisk] KaMyKaSii:
If you don't have TWRP to flash 20420 directly:

1. Go to fastboot, flash stock boot.img/ramdisk.img and reboot to Android

2. Open Magisk Manager settings and set the below custom channel, it's just a edit pointing to 20420 files https://github.com/KaMyKaSii/Unlock-SSH-on-Xiaomi-and-Redmi-WiFi-6-routers/raw/master/debug.json

3. Patch your stock boot.img/ramdisk.img and flash it using fastboot again
[Magisk] Thaiban:
I use magisk manager v 7.5.1 can i update to canary manager ? If yes how? please.
[Magisk] palmbeach05:
Well there's the culprit. The modules. Some of them may be causing it.

Flash unpatched boot.img, then unstall supersu per device guides. But keep in mind chainfire's project is very outdated, and is not systemless as this is.

I have an s3, att variant, stock 4.4.2, magisk patched and all, no issues.
[Magisk] farvehar09:
Hello

xinternalsd and obb on sd and etc

Not working with riru core and edxposed magisk modules on android 9 and 10

I want programs to be able to save their data on sd
[Magisk] andrea0807:
An update of magisk canary has been released, is the latest version compatible with the eu weekly Android 11 rom?

Spoiler content hidden.

Inviato dal mio POCO F2 Pro utilizzando Tapatalk
[Magisk] palmbeach05:
Nah, never. Magisk is never compatible with poco f2 pro. Smh, just flash the thing and get magiskized, or fall back to an earlier revision.

---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------

And how is this magisk's issue? Thats a riru/edxposed issue. Take it up with them, not us
[Magisk] J.Michael:
Have you tried disabling all modules? Does it still run hot?
[Magisk] andrea0807:
[emoji24][emoji24][emoji24][emoji24]

Inviato dal mio POCO F2 Pro utilizzando Tapatalk