yashsingh1/xdaforums huggingface dataset:
[Magisk] wallace108:
Actually when i enter that command it returns nothing (no error messages, just nothing).

I tried Canary Manager but the result is the same. This phone is driving me nuts!!
[Magisk] pndwal:
Don't worry about that as it appears you don't have system-as-root and can flash patched boot.img.

See my reply above. PW
[Magisk] wallace108:
Thanks for your help

Well, regarding TWRP I had read on hovatek's changelog that version 1.7 would support Android 10. See here https://forum.hovatek.com/thread-21839.html that's why I gave it a go. Anyway I'm back to square one: I restored stock recovery and flashed patched boot image with fastboot with the usual outcome.

Now about trying fastboot boot TWRP, this is new to me and don't know how to go.

Mike
[Magisk] pndwal:
Sad.

Just cleaning G play services cache worked for me.

You might want to try clearing data for Play Store, Framework, and Play Services also.

You don't have any other mods flashed either in TWRP or Magisk Manager? I'm guessing more may now trip basicIntegrity than I have on my list due to changes on Google's end (recent failing w/ EdXposed is a clue).

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

Without such mods, basicIntegrity should be passing with only native MagiskHide on. PW
[Magisk] pndwal:
Upgraded devices ONLY, not Shipped A10 (TWRP 3.4.0 does not yet bring support for dynamic/logical partitions)!

Patched boot image only this time? No vbmeta, changed dm-verity switch?

If so, I'd try changing channel in Magisk Manager and try patching with latest Canary Build; this is very close to (only days/hours away from) new Stable build, and includes MANY fixes.

To boot-only TWRP, run 'fastboot boot TWRP.img' with phone in fastboot mode and TWRP.img in PC fastboot folder. PW
[Magisk] zgfg:
If the phone is A/B, then ro.build.ab_update must be defined with the value: true

Hence, if the value is false or if it returns nothing (it means that prop is not even defined - e.g. firmwares released before A/B concept was even proposed), then it's not A/B device

Only if it returns: true, then it means it is indeed an A/B device
[Magisk] wallace108:
[/COLOR]

Yes patched boot image (with changed dm-verity switch) AND (empty) vbmeta.

I uninstalled the regular Magisk Manager and installed the Canary build as per your advice. I'll keep my fingers crossed.

Hell this phone is rugged on the outside AND on the inside!!!

I did try to boot-only TWRP but nothing really happened until the phone booted to system. Darn !!:mad:

Thanks man!

---------- Post added at 05:55 PM ---------- Previous post was at 05:50 PM ----------

Thanks. Good to know. There is always something new to learn. :good:
[Magisk] HippoMan:
Thank you very much.

I had cleared data as well as cache in Play Store, Framework, and Play Services, but I still have been getting the ctsProfile and basicIntegrity failures.

I don't have any TWRP-flashed mods, and I disabled all Magisk-flashed mods and rebooted, but that didn't change these SafetyNet failures, either.

Then, I restored a recent nandroid backup of my system in which I was using the non-Canary Magisk 20.4, and in which I had installed TaiChi instead of EdXposed. SafetyNet passes in Magisk now: both ctsProfile and basicIntegrity.

When I run a 3rd-party SafetyNet checker that uses Google-based checking, SafetyNet is also shown as fully passing.

The only Xposed mods that are installed via TaiChi are GravityBox, UnToaster Xposed, and AppContext ... nothing which purports to affect SafetyNet checking. Those are the only mods that I was previously running under EdXposed after I got rid of HiddenCore.

So, it might be that my previous OS had gotten corrupted in some way or another ... perhaps by HiddenCore itself. Some people claim that HiddenCore causes less-than-desirable side effects, even after uninstallation.

Anyway, I'm just going to stick with TaiChi and non-Canary Magisk 20.4 for the time being.

... and I'm still committed to moving to microg or something similar, and to getting as far away as possible from Google.

UPDATE: some clarifications, rewording, and elaborations in the text above.

.​
[Magisk] warrencoakley:
Yes had this issue as I was upgrading Vanced. Exposed and Riru Core were the issues. Removal all reminants of it and clear cache in Google services
[Magisk] pndwal:
Not sure why you couldn't restore pass... Likely something in OS got messed up, or some non-systemless changes were made/forgotten.

Great result w/ backup though... Aren't you glad you bothered!

Just remember cautions re TaiChi (Chinese, commercial, closed source). One take - see OP (but open for debate):

https://xdaforums.com/xposed/warning-taichi-t4012681 PW
[Magisk] HippoMan:
Thank you very much.

As for backups, yes, I always take a full nandroid backup before making OS or module changes.

I'm aware of the TaiChi cautions. I'm takling a deliberate, calculated risk in using it.

However, I have had no problems with TaiChi during the time that I've used it over the past year or so. On the other hand, I have had lots of headaches as a result of the way that Google deals with Xposed, EdXposed, and other root-related issues, especially in recent times.

I understand why Google has implemented its SafetyNet procedures, and I also understand why many developers are glad that these procedures are available. I'm just not one of the users who has benefitted from SafetyNet, given that I do not use my device in the way that millions of others use theirs. They and Google are free to continue with the SafetyNet status quo, but I am looking for an alternative to Google now.

Long ago, I went with Android because it was a reasonably open platform, and I could write and install software for it which allows me to configure and use my device in the ways that I prefer. Those days are rapidly ending, now that Google is getting more and more like Apple with regard to locking down the OS.

My linux laptop computer is "rooted" just like almost every other linux, Windows, and MacOS machine. It has a root account and a working su executable, as well as tools like sudo which make root even easier to manage. Few software packages are written to cease to work on my linux machine, simply because root is available.

I carry my laptop with me to public places, and there is just as much risk of it being stolen and then hacked as there is for my mobile device. I use that machine for accessing the internet, making purchases, etc. much more frequently than I use my mobile device for those purposes, and therefore, the machine is a more visible target on the internet to would-be attackers than my android phone is. I use anti-virus software and other protections on my laptop in order to secure it.

I wish that hardware/software vendors such as Google and Apple would take the same attitude towards "rooting" on their mobile devices that laptop and desktop hardware and software providers take, instead of trying to lock down those mobile devices. But I know that this wish of mine is little more than a pipe dream.

.​
[Magisk] pndwal:
In other news...

... Way to go John!

* Release candidate!

Magisk (20427)

- Remove compressed ramdisk support

- Update magiskboot to always pad images to original size with zeros

- Add new install-module command to magisk to install modules without Magisk Manager

Magisk Manager (301)

- Support patching modern Samsung AP.tar (devices launched in 2020)

- Fix inconsistent Internet status monitoring

- Various minor improvements

... Wow!

... John's clearly loving his shiny rooted (in 20 min) Samsung Z Fold2 5G!... Is Samsung suddenly the new Pixel?... May be now for modders who don't care about Knox fuse... he's celebrating blowing his within hours of unboxing! (I don't imagine Samsung lovers here will miss Knox Security layer / Enterprise Management (much) either... :D ) PW
[Magisk] wallace108:
Thanks for the heads up pndwal. Unfortunately no good news for me ..... yet :(
[Magisk] pndwal:
In the HIGHLY likely event that something has been messed up (by use of incompatible TWRP, flashing vbmeta, changes to dm-verity or other), I'd be SERIOUSLY considering restoring FULL STOCK using official package before trying OFFICIAL Magisk root method for non A/B & non System-as-root devices, retaining STOCK Recovery (as your device shipped with Android 10 so TWRP is incompatible)!

Ie. simply install latest Magisk Manager, select and patch Stock boot.img file, copy patched boot.img to PC and flash boot partition using ADB fastboot with NO OTHER CHANGES (no switch changes, no vbmeta etc), and see how it goes. :good: :cowboy: PW
[Magisk] Stomey:
I need help on how to fix my magisk ctsProfile false on galaxy A51

I have rooted like 10 to 15 times but my ctsfrofile is getting false each time how to fix it
[Magisk] wallace108:
Thanks pndwal. Been there done that :) This very day Oukitel posted the wp5-pro full rom (until today I had to resort to a memory dump). So I immediately flashed the device and restored it to its factory settings. And then I flashed the newly patched boot (with the latest Canary build).

Meh ... I wish it were that simple .... ;)

Mike
[Magisk] dougandthepixel:
Troubles installing Magisk on Pixel 2XL w/Android 11

I've been running Android 10 on a Pixel 2XL with Magisk (just simple stuff to avoid ads and allow root access for things like Tasker and Titanium Backup). I followed the standard method of uninstalling before doing the OTA for Android 11, however I neglected to update Manager to the Canary build. So Android 11 refused to boot (slot a), and Android 10 (slot b) was left without Magisk installed. Switching back to slot b I re-did the OTA and booted Android 11 stock which runs with no apparent issues. I updated to Canary, downloaded the Android 11 package from Google, and patched the boot image. Flashed it (fastboot flash boot) but am stuck in the boot animation screen (which eventually reboots). Re-flashing the unpatched boot image gets me back to stock A11 so the boot image I'm using appears to be the right one. I've done this with the last 3 Canary builds (299, 300, and 301) hoping that the boot image size would be fixed (which it has, went from 40MB unpatched to 26MB patched, and with 301 it is now 40MB patched), but it hasn't resolved the problem. As the latest Canary is labeled as the next stable release candidate I thought I'd post now. Magisk install log attached.

Any help is much appreciated!

Doug
[Magisk] HippoMan:
In case anyone is interested, I discovered that there is now a Lineage 17.1 (Android 10) microG build for guacamole (OnePlus 7Pro). I'm going to be trying it soon. This could be a good first step towards getting away from Google.

Lineage microG works with Magisk 20.4 (at least when I tried it on my paleolithic S5 device), and it also comes with a way to turn SafetyNet checking on and off for the entire OS.

Unless there are objections, I'm glad to report my findings here.

.​
[Magisk] Alxoom33:
Flashing latest Canary 4027 worked fine with my Taimen running A11.

However, on Pixel C running Lineage 17.1 flashing Canary 4027 fails. Insufficient partition space. However, Canary 4026 is running fine.
[Magisk] zgfg:
To avoid confusion what are these numbers, you are referring to 20427 or shortly 427 ?
[Magisk] dnsmo:
anyone tried the systemless host yet? Is it working now with 427? This is on Pixel 3 XL with A11.
[Magisk] zgfg:
You probably mean on Pixeks with A11

On other devices, it works as usual (at least for me)
[Magisk] cojocar.andrei:
Hi, I'm having problems with magisk hide on android 10 and Resurrection remix rom. Whenever I enable magisk hide on magisk 20.4 or even canary applications start to not being able to launch (camera, setting, even magisk manager)... Anybody encountered a similar situation on a custom rom? Thanks.
[Magisk] pndwal:
Likely you need MagiskHide Props Config Magisk module, configured.

Other than that, we need more information. :D PW

---------- Post added at 09:42 PM ---------- Previous post was at 09:35 PM ----------

Why not? This is Magisk General Support / Discussion! :good: PW

---------- Post added at 09:51 PM ---------- Previous post was at 09:42 PM ----------

If you patch boot.img, is it not now exactly the same bit size as unpatched? PW
[Magisk] topjohnwu:
Are you using TWRP? If not, I will have to do something about this...
[Magisk] pndwal:
Welcome back to the slugfest! ;) ...And many thanks! PW
[Magisk] zgfg:
Yeah, that's an interesting point from the last Changelog:

>> ...always pad images to original size with zeroes

Tested myself with Canary Manager 301 and Magisk 40427:

a) Patching my magisk_patched.img (that was patched by a previous Canary version) of 16 MB, got the newly patched image again of only 16 MB

b) Patching my stock boot.img of 128 MB, obtained 128 MB. Hex editor proves that last 112 MB are padding zeroes

(Re-patching a previously patched inage first removes the previous patch, then applies the new one)

Both work fine. Since I like to store the old patched boot images for a month or two (just in case, if it shows that newer Canary versions brought some bugs) I will have to pay attention to patch like in case (a), to avoid storing now hundreds of megabytes of padded zeroes ?

Edit: For the record (and if somebody wants to cut off his zeroes): By disk-dumping, magisk_patched.img from (b) can be cut-off to the same size as obtained by (a) - just tested, the files have then the same checksum and that cut-off magisk_patched.img from (b) can be successfuly used for flashing

P=/sdcard/Download
ls -l $P/b.img
dd if=$P/b.img bs=1 count=16519168 >$P/a.img
ls -l $P/a.img

One needs to adjust to his file size (count= in bytes), e.g. by inspecting by Hex editor where the zeroes start
[Magisk] Alxoom33:
On Pixel C which is not an A/B device I do have TWRP as my recovery running LOS17.1 (ANDROID 10). It works fine with Canary 20426. However, when I tried a direct installation of 20427 I got an error message "! Insufficient partition size"

! Installation failed"

---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------

I am already rooted, so I use the MM direct installation method. No need to patch.

[SIZE=1]---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------[/SIZE]

[/COLOR][QUOTE="zgfg, post: 83599639, member: 7786725"]To avoid confusion what are these numbers, you are referring to 20427 or shortly 427 [emoji851][/QUOTE]Yes, I mean to type 20427. Thank you.
[Magisk] pndwal:
Probably to do with new 0 padding.

Still could be useful to try Magisk patched boot.img to see if it handles this better than Magisk's direct install script. (May help John know if it's a problem w/ direct install only, or both direct and Manager patching.)

Could still flash from recovery (or from fastboot) if size is identical to original boot.img.

Could even flash MagiskSU zip to check if Magisk recovery zip script works or not also. Should handle flashing over older Magisk build if it's ok. Or try after unroot. :good: PW
[Magisk] scooter1979:
Pixel 3 with A11 here - 20427 still freezes just after boot when applying the systemless host module. I'm getting tired of dodging ads. Makes me realize how spoiled I was when it did work. Certainly makes me more appreciative of John & all of his work.
[Magisk] Alxoom33:
Ok, I'll try patching 427 and flash in MM.
[Magisk] pndwal:
Great, but how do you flash patched boot image in Magisk Manager? Official method is fastboot flash. PW
[Magisk] guest4711:
Use DNS66, Blockada or AdAway in VPN mode. They filter DNS using a local VPN (from localhost to localhost) without needing root.
[Magisk] Alxoom33:
That's only if you're not rooted yet. I am. Also can use TWRP to flash img file.

Or fastboot flash... so boring:)
[Magisk] zgfg:
Patch in Magisk Manager but then flash in Fastboot (or TWRP if available/applicable)
[Magisk] Aaagogo:
who and what kind of info can i extract from my device to send to magisk devs for this weird issue that I have/had.

ROOTED android 10 on MIUI 11; magisk hide works on every app that detects root other than 1 app. tried every method out there to hide; riru edxposed, taichi... etc... and nothing works.

found this "new" method by just deleting magisk manager app and the app no longer detects root.

is there some info from my device that i can send to the magisk dev so that can look into this app detecting magisk manager even after it has been hidden.

thanks.

---------- Post added at 16:07 ---------- Previous post was at 16:07 ----------

who and what kind of info can i extract from my device to send to magisk devs for this weird issue that I have/had.

ROOTED android 10 on MIUI 11; magisk hide works on every app that detects root other than 1 app. tried every method out there to hide; riru edxposed, taichi... etc... and nothing works.

found this "new" method by just deleting magisk manager app and the app no longer detects root.

is there some info from my device that i can send to the magisk dev so that can look into this app detecting magisk manager even after it has been hidden.

thanks.
[Magisk] Canaan:
Instead of uninstalling magisk manager, maybe try renaming it in magiskhide? The app in question may be looking for the name "Magisk".
[Magisk] pndwal:
Magisk Manager hidden? By 'repackaging with random package and app names'?.... Or did you hide it some other way?

As mentioned, you want to 'Hide Magisk Manager' from apps. If you didn't do that, option is in Magisk Manager settings, reading here:

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot# :good: PW

---------- Post added at 12:31 PM ---------- Previous post was at 12:09 PM ----------

Well I'll take your word for it... Does the option to flash patched image in Magisk Manager show after patching? - cos I haven't seen it. PW
[Magisk] dougandthepixel:
Thanks for that information--gives me some hope. Had you installed A11 on Taimen via OTA or flashing the factory image manually?
[Magisk] pogo-airsupport:
You only need magisk manager installed, not magisk itself.

You can't install via twrp after android 10 due to encryption.
[Magisk] ACHILLES R32:
Has anyone experience any of the following issues with the pixel 3a xl and Android 11 after rooting.

Blacks screen when trying to wake up the device.

Random freezes when using apps ex: google news, amazon.

Once the phone freezes, commands to restart the phone via the power menu are unresponsive

The only work around I have found is to force restart the phone by long pressing the power button.

I don't know if the issues are root related or module related . But the response I got from the pixel 3a xl thread seem to indicate a that this might be root related.

I'm on the latest canary build and have the following modules installed.

Sent from my Pixel 3a XL
[Magisk] catdoggy:
Hello, Samsung A70, Android 9, with new MAGISK 20427 its possible to patch TWRP img, but not to install it. Failure "size too big".

Last version: patched.recovery.img size is 26,8 M, with new version 78,9M..??? Whats wrong?
[Magisk] supachris:
This is caused by systemless hosts. See my issue opened at github. Disable systemless hosts will work. Of course without hosts adblock.
[Magisk] Alxoom33:
Right, you can flash a module.zip. But, there is no reason to flash a patched boot image when you are already rooted!

---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------

I flashed the full factory OTA.zip in fastboot booted-up TWRP.

Pm me if you need help.
[Magisk] ACHILLES R32:
Found the github link thank you, good to know that I'm not the only one with the issue lol

Sent from my Pixel 3a XL
[Magisk] 7wells:
Oops, I missed that important change. Thank you so much!
[Magisk] pndwal:
Unless your aim is to see if alternative method to update works when direct flash over existing SU fails. (Even if it's boring!) PW
[Magisk] Alxoom33:
No probs my friend! I will flash and let this thread know.

---------- Post added at 07:24 PM ---------- Previous post was at 06:31 PM ----------

FYI, same insufficient partition size error report in flashing the Canary 027 zip installer in TWRP.

Looking for the los boot.img...

OK, extracted los, saved boot.img to downloads and patched boot.img with MM. Flashed patched boot.img in TWRP.

This worked!

Conclusion: The 027.zip installer is too big for flashing in twrp or for self install in Magisk Manager. However patching the boot.img with 027 in MM and flashing the patched 027-boot.img works (in TWRP) and presumptively by fastoboot flashing. Although this woks it is an unnecessary PIA, as 026 can be self installed in MM. I reccomend that John put 027 on a diet, slim it down and make a slimmer and better v. 028. Again [MENTION=4470081]topjohnwu[/MENTION] you are amazing. Thank you!!!
[Magisk] pndwal:
There seem to be problems with new zero padding feature. What is size of boot.img extracted from ROM?... Is that what you are patching? PW
[Magisk] zgfg:
Instead of patching a stock image (78,9 MB), patch with 20427 the image that was previously patched by 20426 (26,8 MB) - then the newly patched size should be again 26.8 MB and then try flashing with that image.

See (post about my similar experimenting with the sizes)

https://xdaforums.com/showpost.php?p=83600499&postcount=41668
[Magisk] pndwal:
Not sure encryptions any problem. Some TWRPs decrypt, some don't, but even those without encryption support can flash ROMs fine, eg from SD card / USB.

Compatibility problem on 10 and 11 is unsupported dynamic/logical partitions. Seems it can still work fine on older devices w/ 10 (upgraded, not shipped), but on 11 it causes bootloops if flashed w/ Magisk.

https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/

TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10. There have been no further versions.

Nb. Many are still using TWRP to flash MagiskSU (boot.img or Magisk zip) even on 11 if booted from ADB fastboot only. Other however, have issues with it too. PW

---------- Post added at 08:42 AM ---------- Previous post was at 08:38 AM ----------

Any idea why some are getting 'insufficient space' problem when patched image size = original ROM image size? PW
[Magisk] catdoggy:
I always flash patched recovery. img as boot, not boot.img

---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------

ok, you mean i should patch the aready (old) patched recovery.img with new magisk versiom, not thr original recovery.img?
[Magisk] JudgeDread11:
If xda gives an error posting it's mostly false alarm. Just refresh and your post will show up.

Could you please edit your post to take the dozen duplicates out?

Thank you.
[Magisk] zgfg:
Yes, I meant that - you didn't need to ask twelve times (please edit your post to remove duplicates)?

I used to do it previously when patching (sometimes I grabbed the stock, sometimes previosly patched image), and never had a problem. Btw, it should work like when updating Magisk by Direct method (then it patches directly to the partition containing the previous patch)

You can also disk-dump your big magisk_patched.img to cut it to the smaller short_patched.img (Terminal with root):

>> DIR=/sdcard/Download

>> LEN=<lenght_in_bytes_like_your_old_patched_images>

>> dd if=$DIR/magisk_patched.img bs=1 count=$LEN of=$DIR/short_patched.img

Alternatively, for LEN, open the fat patched image by hex editor and take the offset where padding zeroes start

---------- Post added at 12:18 PM ---------- Previous post was at 12:01 PM ----------

I was wondering why that change was introduced now, maybe there was an Issue on GiTHub reporting a problem when flashing the shrunk patched images (maybe related to the new A11)
[Magisk] catdoggy:
Yeah, sorry, XDA gives multple errors while posting.. I deleted it and try your tip after work. Thanks a lot :)
[Magisk] pndwal:
Yeah, it was suggested for Moto g7 back in October.

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

Just got implemented as an 'enhancement'.

Interesting [MENTION=4544860]osm0sis[/MENTION] commented on 1 Nov 2019:

Implementation seems to be flawed presently, as some are facing the 'insufficient space' issues with zero padded image, and suggested checkbox to make this optional may have been overlooked. PW