yashsingh1/xdaforums huggingface dataset:
[Magisk] Davion86:
Hi

I have a problem since yesterday after a ota update of lineageos 17.1.

My leeco lepro3 elite (x722) doesn't boot into the system, is stuck at the lineage boot animation and then turns off.

Magisk worked perfectly until then, i installed it some time ago via twrp.

After a system wipe and installing Los again i was able to boot again.

I discovered that the recommended way to install magisk is to patch the boot image which i then did.

But the problem stayed the same, i can't boot into the system.

Thanks for some help :)
[Magisk] JudgeDread11:
Possibly a module you have installed. Disable it remove your modules before you install Magisk again.
[Magisk] tarlabasi:
Hi friends,

I uninstalled the magisk because I had a problem with bank applications. But I always see a cts profile match fail error. How can I get rid of this problem without resetting the device to factory settings?

I use Mi 6 Global. Android Version is 9.
[Magisk] zgfg:
Please search for: CTS (Profile failing due to) Hardware (attest and for) Magisk Hide Props Config (aka) MHPC (its Github docs and its XDA thread)

It's been really answered countless many times here in this thread - just use the search icon top-right?

By MHPC module, Force Basic attest you shall fix the CTS Profile failing (if it really fails due to Hardware attest and if Basic Integrity is passing).

Then, if you would still have problems with a particular banking app, read the Magisk Wiki pages on Github - chapter devoted to that topic (with hints, etc)
[Magisk] tarlabasi:
Edit :double comment.
[Magisk] tarlabasi:
Thank you for your support but I guess I could not explain it completely. Sorry about that. I don't want to use magisk anymore. I uninstalled it but cts profile problem is continuous. I changed the fingerprint settings on magiskhide.props. How can I fix again?
[Magisk] noodlenoggan:
Thank you for explaining the difference as I thought both magisk and magisk manager were one of the same. During the repackage process, I didn't realize that it created an entirely different app name and installed it in the apps drawer. I thought it had simply renamed itself. Also it used a generic android icon so when I was quickly browsing through the drawer, I completely missed it. Only after closely reading the app names did I notice that.

Uninstalling the repackaged version brought the original magisk manager working again.

Thanks again for everyone's help and suggestions!
[Magisk] zgfg:
You can uninstall Magisk without reformatting (by flashing Magisk uninstall zip through TWRP or by flashing the stock boot img - to properly clean up, uninstall Magisk modules and reboot before you go for uninstalling Magisk)

But CTS Profile will continue to fail since your Bootloader is unlocked. However, re-locking Bootloader requires Factory reset

Shortly, you have two options:

- keep using Magisk (and possibly also MHPC) to hide that Bootloader is unlocked

- uninstall Magisk, then relock Bootloader but relocking will trigger Factory reset
[Magisk] J.Michael:
What did you uninstall? How did you uninstall it?

If you really uninstalled Magisk, then you will no longer have changes made by way of Magisk. In particular, you will no longer have magiskhide.props. You should be able to verify the current values of props from a command line in a terminal emulator.

If you used Android to uninstall the app Magisk Manager, you still have Magisk running. Re-read [MENTION=7786725]zgfg[/MENTION]'s response.
[Magisk] tarlabasi:
Thank you for your support again. Factory reset is problem for me now. and I don't want to unlocked the bootloader.

I think I should keep using it and hide the problematic application in the magisk hide.

---------- Post added at 09:20 PM ---------- Previous post was at 09:11 PM ----------

I guess I can't explain the problem.

I uninstalled magisk but safetynet test is missed. So i don't found some applications in the play store.

That's why I asked for help. He explained it nicely in his last comment.
[Magisk] Davion86:
True and worked, thanks. I kind of thought after the system wipe that the modules are deleted.
[Magisk] zgfg:
Magisk stores its modules, db, etc to /data

Few cents from my side

1) CTS Profile Hardware or Basic:

Goes on and off, I mentioned here and in MHPC thread several times, sometimes I need to fake ro.product.model (to force Basic and to pass SafetyNet), sometimes not

Seems that we are now in the moon year when G relaxed and (I'm lazy to search did I post it a month or more ago) I pass CTS on my Xiaomi Mi 9T without MHPC and the stuff

2) Flashing boot img:

When I got my Mi 9T I was searching for the guides how to root. Frankly, on most places about Xiaomi it was only about flashing Magisk from TWRP (or OrangeFox - essentially the same thing) but I was interested in patching the image from Manager and flashing (my previous phone was Huawei P9 with Oreo, TWRP there did not support storage encryption hence flashing Magisk from TWRP was not an option [without reformatting and decrypting the storage] and I was accustomed to patching and flashing the patched image method)

I stuided Magisk Github instructions at that time, it did have specific instructions for Huawei (ramdisk.img) and Samsung but not for Xiaomi

By following the general instructions I tested:

getprop ro.build.system_root_image
true

getprop ro.build.ab_update
<blank=false>

and by following the Magisk Github general instructions (at that time) Ihad to patch recovery.img (not boot.img)

(According to your post, Magisk installation instructions would be updated for Xiaomi now, I'll have to check)

I was not sure about and I asked here (it was beginning of 2020) but obtained no response, comment, no feedback

Fortunately, I found two guides clearly claiming that for MIUI 11/A9 (at that time), Magisk can be installed by parching the boot.img

Since then I always install/update Magisk that way to Mi 9T (for the various versions of stock and Xiaomi.eu A9 and A10 firmwares) and never had a problem.

(It's good because recovery can be still used for TWRP)

Anyway, patching Magisk to boot.img for MIUI was also mentioned here few and more times over the months - good that it also works for you
[Magisk] zgfg:
What the hell is that Aug 2016 (I didn't participate here at that time) ?

But XDA server has its issues this night again and you can't open the attached screenshot from XDA app showing as the last post here was mine, but dating to 4+ years ago?!
[Magisk] dev444:
Hi guys, I received today Oneplus 8t, android 11.

I tried to flash magisk as I always do:

1) unpack payload.bin from full rom

2) extract boot.img

3) patch boot.img from magisk manager

4) fastboot flash boot patched.img

5) fastboot reboot

But, once I open magisk manager again, it is still without root :( what is happening? Some blocks with Android 11?

Thanks for help guys
[Magisk] zgfg:
For A11 you must use Magisk v21.1, not v20 4 (hence not the Stable channel) - did you follow that
[Magisk] dev444:
Ohhh nice! It worked finally :)

didn't know that.

So by doing this, if I would like to go back in the stable channel in the future, any issue?

Thanks
[Magisk] pndwal:
Yes, but I've had RN8T locked since Feb, and MM has consistently shown Hardware since then, also since MIUI 12 / A10 firmware update, and I did check fairly frequently.

The strange thing is that it has consistently shown Basic from the moment I unlocked bootloader, last week.

I'll be sure to post if this changes. I expect it likely will, but seems Google's 'fluctuations' may somehow target some devices only when unlocked, as when Locked my RN8T used Hardware key exclusively for some 10 months.

Well, the actual Installation Instructions are not updated for Xiaomi, but the fact that working ramdisk can be added 'manually' to boot.img 'on some type III devices, incl some Xiaomi / excluding Samsung S10 / Note 10', is covered right at the end of https://topjohnwu.github.io/Magisk/boot.html documentation (Android Booting Shenanigans, 'for developers') as I indicated.

A link to this is provided from Installation Instruction page (end of 'Getting Started') with the statement:

... Pretty obscure, and partly why I posted this information...

Some indication of the possibility of patching boot.img even on type III booting (no ramdisk) in Installation Instructions would clearly be helpful.

Well now we at least have official confirmation / acknowledgement... Don't know how long it's been there, but I'm learning that reading official documentation, (just like OPs here ;) ) can save much time / dispel misinformation. :mad:

Yes, I'd seen these references incl. yours, thanks.

Just wanted to get more official info. in case of problems, and I'm happy to have found it / wanted to share / have profited from checking official documentation once again :)... no matter how obscure / deeply burried it is! :D

I must say, Android Booting Shenanigans document has really enhanced my understanding of Terminologies, (SAR, 2SI...), Boot Methods (A, B, C), History, chronological device types (I, II, III, IV; for purposes of Magisk root) etc.

Other Magisk docs, incl. sections for developers, also give fairly concise appraisals of vital Magisk root aspects:

https://topjohnwu.github.io/Magisk/ PW
[Magisk] zgfg:
For going back to Stable on your A11 phone, you'll have to wait till Stable be updated to v21(Beta was but Stable is still on v20.4 - even more confusing, Stable's Manager was updated to 31x, causing some people to wrongly believe that Stable has also new Magisk but it's v20.4 is 5 months or more old, older than A11)
[Magisk] zgfg:
I wanted to explore more about CTS Profile, Basic and I (re)tested the following on my Xiaomi Mi 9T with the Bootloader unlocked, Magisk 21006/Manager 315, no props faking (particularly ro.product.model is on the original value: Mi 9T)

1) Magisk Hide enabled and SafetyNet is passing showing that CTS Profile takes Basic attest

Retested SafetyNet with two other apps, also passing

2) I disabled Magisk Hide and rebooted.

Both Basic Integrity and CTS Profile are failing now (CTS Prifile still showing Basic attest)

IMO, this is expected since the phone is rooted but Magisk is no more hiding

3) I flashed the stock boot.img hence Magisk Manager displays now that Magisk is not installed

But SafetyNet is passing again, and showing that CTS Profile is taking Basic attest

I must confess that I was litte confused with this result (3) - I expected that Magisk would be needed to hide to CTS Profile (although taking the Basic attest mode) that Bootloader is still unlocked

I.e., it means that I can have SafetyNet passing without Magisk installed, although my Bootloader is still unlocked

Maybe you could test the same - just temporarily reflash your stock boot.img and check the SafetyNet status in Magisk Manager (Manager allows now testing SN without having the Magisk installled)
[Magisk] pndwal:
Good test. Yes, 1 & 2 are as expected. 3 is surprising... Not sure what it means, but evidently unlocked bootloader is not being detected for Mi 9T.

... Is Google PlayStore still showing Device is certified?

I did check SN in MM after unlocking RN8T and before rooting as I reported, and didn't get this result:

The surprising thing for me was evalTypes change to BASIC on unlocking bootloader... but this would take a clean stock install to check if unlocking was just coincidental to Google un-slating RN8T for Hardware key Attestation...

I'm fairly certain that the anomaly causing fallback to Basic Key Attestation is in fact somehow caused by bootloader unlock. PW
[Magisk] zgfg:
Frankly, I didn't check but from the past I know that it takes time (an hour or more) to change the Certified/not Certified state - giving me confidence that I can do tests like (2), not worrying that rebooting and staying just a minute or two with SafetyNet failing would un-certify my phone from the Playstore's perspective
[Magisk] arik100:
why magisk doesn't sort modules by popularity-subject?

it would be much easier to find stuff this way
[Magisk] mayur.3.92:
Resurfacing this to get some guidance
[Magisk] zgfg:
Guys, I have now a serious problem with Magisk Manager (TG, not with Magisk itself).

Apparently after the test (3) I mentioned earlier today - after temporarily flashing the stock boot and testing SafetyNet without root.

Btw, I did similar things with earlier Magisk versions (flashing stock boot.img, then upgrading firmware), but never had a problem

Info:

- Magisk Canary 21106, Manager 315

- Did not change modules for a week, never repackaging/hiding Manager since my last formatting Data a month ago

- Everything worked perfectly (still does, except for Magisk Manager)

- I flashed stock boot.img to check how SafetyNet would behave without Magisk (it surprisingly passed although Bootloader was unlocked)

- Then I flashed back my previous Magisk_patched.img and rebooted

- root works (checked by Root Checker, Reboot app, MiXPlorer, su command in Terminal)

- Magisk hide works (checked from Rootbeer fresh app, magiskhide command in Terminal)

- modules work (AdAway filling hosts file, BusyBox, most perky module V4A running ok)

But I cannot open Magisk Manager:

- regular Manager's icon was still on the home screen

- tapping just opens the splash screen (big logo as on the screenshot), staying forever

I spent over an hour, experimenting with:

- clean Data and Cache for Manager app from Settings/Apps

- wipe Dalwik and Cache from TWRP

- uninstall Manager, install again 315 or even the older 311

- give Storage and Install from unknown source permissions to the newly 'installed' Manager

- go to Airplne mode (thinking if MM was blocked by trying to connect back)

- put "disable" file to each /data/adb/modules subfolder and reboot

Btw, I have also Install via USB enabled in Developer options (needed for repackaging but now I'm not doing that)

Always the same: Magisk fully functional, Manager's regular icon present (there is no duplicate Manager or similar app in the Settings/Apps), but when opening the Manager it stays forever in the splash screen

I checked logcat, among the various magisk and com.topjohnwu.magisk (package name for MM) logs, I can only see a potentially suspicious one:

11-25 10:59:26.007 E/Layer (889): [Surface(name=AppWindowToken{9d417f2 token=Token{9023efd ActivityRecord{501bf54 u0 com.topjohnwu.magisk/a.c t1027}}})/@0xa44f5ee - animation-leash#0] No local sync point found

Please help if you have any useful idea.

Since everything else works (incl. Magisk modules and root apps), I definitely don't want/need to:

- uninstall modules (e.g. by putting "remove" files to their folders and reboot)

- flash magisk-uninstaller.zip from TWRP

- format or Factory reset

It's also not urgent since for the moment all root reuests are granted, modules installed, etc, hence I can shortly survive without the MM app while trying to fix it without intrusive actions
[Magisk] pndwal:
Sorry to hear that.

Can't think of much, except that magisk-uninstaller.zip may fix since when run "the stock boot image will be restored and all Magisk related files will be removed from your device", 'may' being the operative word, but I appreciate you don't want to do this. Edit: searching this thread (stuck, splash screen, manager) shows this worked for many.

My guess is that something may have gotten messed up when booting unrooted by flashing standard boot.img only, since some unexpected/incompatible Magisk files/settings will remain if Magisk is not uninstalled using proper cleanup scripts. Again, operative words being 'may,' and 'my guess'... :mad:

Edit: Manager issues / freezes can occur if installed to external/adopted memory (reinstall to internal), or as System App (de-systemise).

Also, I'd try simply reflashing Magisk 21106 (dirty) from TWRP to see if things are normalised (or if any errors are reported)... Can't hurt.

Nb. This is not supposed to work on our type III devices (no ramdisk), but should work for us just as patching method does due to bootloader retaining ramdisk compatibility, and Magisk being made to "simply just create an empty ramdisk with magiskinit added as init" since Feb 2019.

Nb2. I don't use TWRP with Android 10. My understanding is that it can work fine with A10 as RV (running version) unless LV (launch version) is 10 or later, but Fastboot Booting TWRP from PC may still be a safer bet.

Hope something works... PW
[Magisk] ipdev:
[MENTION=7786725]zgfg[/MENTION]

Had a similar issue a while back with a rom update flash.

The rom updated but, TWRP went derp with the backup scripts for some reason.

The magisk script ran along with the others but, they all gave errors.

On reboot, Magisk was still active, SN passed, the fingerprint I last tested on it was still active, root was still granted to everything I had granted it to.

Manager would hang on the splash screen and/or force close.

I ended up deleting /data/adb/magisk.db and rebooted to let Magisk regenerate database.

I do not remember if everything was still set or not.

Cheers. :cowboy:
[Magisk] pndwal:
... Just out of interest, which Android version was updated? PW
[Magisk] ipdev:
[MENTION=7550078]pndwal[/MENTION]

Android 10.

Since I could not reproduce the error, I wrote it off as a one-time gremlin and forgot about it. ;)

Cheers. :cowboy:
[Magisk] zgfg:
Wouldn't flashing magisk-uninstaller.zip do the same - to delete /data/adb?

Since I still have root and TWRP, I have full access to /data and I just want to make sure that next time when I reflash magisk_patched img and install MM again, it does not find any remnants that would block the MM app again on splash screen

I already made my mind and started (taking the opportunity to experiment few things when I reduce the number of my audio Magisk modules) the following:

- uninstall modules (by use of "remove" files)

- then I would flash magisk-uninstaller.zip

- then I would double-check and delete from TWRP /data/adb folder and com.topjohnwu.magisk*== subfolders from /data/app and /data/data

What are the other folders on /data where Magisk or Magisk Manager could leave something, to double-check and delete them from TWRP?

I know there were folders (but forgot the paths now) where Magisk keeps stub for the Magisk Manager app, cache, logs, boot images from last Magisk updates, etc (some of them are benign but I rather want to spend few more minutes for manual cleaning to make sure nothing would remain from Magisk or Manager since wiping Data or factory resetting are absolutely out of the option)
[Magisk] Didgeridoohan:
[MENTION=7786725]zgfg[/MENTION] Start by only deleting the database file, /data/adb/magisk.db. It's quite possible that your issue is a faulty db and that would fix it.
[Magisk] pndwal:
Yeah, thats what I wondered. TWRP freshly made compatible with devices upgraded to A10 only. (I'm assuming it was flashed on device, and Launch Version was 9 or earlier).

Base A10-compatible TWRP was never updated, so I suspect it may have had bugs extant even on devices without dynamic/logical partitions using A10.

Seems such bugs are likely responsible for you MM freeze as you flashed updates. Can't quite see how these could cause [MENTION=7786725]zgfg[/MENTION]'s issue, but I still suspect it may be TWRP related. PW
[Magisk] OzKenny83:
After reading topjohnwu's initial tweet about the underlying issue, I (like others in the resulting replies) am wondering why he felt the need to remove this option for all devices, rather than just the Pixel devices that are affected. Or does the issue actually affect all Android devices?

If only Pixels are affected, then perhaps it was/is too difficult to determine a user's actual device from within Magisk Manager...although I doubt this is the case. Please correct me if I'm wrong.

In any case, I'm also wondering whether I could downgrade Magisk/Magisk Manager to get the "install to inactive slot" option back. Others seem to have been able to use that option in September, so I don't see why it wouldn't work for me now. I will go through the manual boot image patching process this time, since I have nothing better to do while I wait for a reply, but it'd be nice to be able to get the November update for my Mi A3 in a much easier fashion.

MTIA for any advice you experts can provide! :D

P.S. I just realised that I don't even have Magisk 21 yet; I'm still on 20.4 and Magisk Manager 7.5.1. So why don't I see the inactive slot option?!
[Magisk] zgfg:
I cannot blame TWRP for my case, I didn't have any OTA or Magisk or Manager update this time, it was simply reflashing the previously patched boot.img - it had nothing with Boot, System, OTA updates, etc - only with Data

I just reflashed that same magisk_patched.img to Boot that I previously used and with no issues.

And I still don't have issues with Magisk (root, hide, modules), only with Manager app - hence something got wrong with its data on Data partition (strange that deleting data for MM or even uninstalling MM cannot fix it)

Problem might be as reported in logcat by Manager: No local sync point found.

Hence I'm afraid that Manager cached/wrote something, when I temporarily booted with stock boot.img/without Magisk (cannot blame Magisk either bcs Magisk was not active then, and later when I flashed back the old, patched Boot, Magisk continued to work with no problems)

We saw other issues that people had when updating Manager (e.g. on Stable, Magisk is still the same and old v20.4 and people only Manager got updates), resulting that Manager hangs up or cannot find what are the latest available versions, thinks it has no connection when the connection is available, etc

Frankly, I update to each and every mew Canary version (always by patching Boot from Manager and flashing by TWRP and NEVER had any problem with TWRP).

But I'm not afraid to update Magisk (knowing also that I can always flash my older patched Boot img - I rename and keep them on Mega, just in case), I'm more worried about the possible new bugs coming with the new Manager builds (this time I didn't update Manager either, but Im writing about the overall stability and maturity of MM)