Magisk General Support / Discussion

zuelber

Member
Dec 9, 2010
5
0
21
São Paulo
Hi guys. Some guidance needed here. My phone (Mi9 Lite) have received an OTA update, I tried to install and the installation failed. Totally forgot about root/magisk.
Then I´ve followed some instructions to uninstall Magisk restoring images option, tried to apply the OTA and the phone rebooted and after that I am stuck on fastboot. Not sure what to do now.

Please help.
 

J.Michael

Senior Member
Jan 20, 2018
373
137
43
I have a SM-G960F/FD with Android 9 G960FXXS7CTA1. I unlocked the bootloader installed TWRP and the no encript and rmm patches. I installed Magisk manager 8.03 and extracted the boot.img.lz4 from the AP file and renamed it to boot.img copied it to the phone SD card. I ran magisk and tried the the install patch img. Not sure if the Preserve AVB 2.0/dm-verify needs checking or not but did not check the box. Picked select and patch. picked the boot.img file. Then i get a failed message. I am attaching the log file.
I don't think you should rename boot.img.lz4 -- if that's what's in the AP.tar, just point Magisk at that to patch image.

I think Magisk can handle lz4. I don't know if it keys off the filename, or can recognize lz4 by the content.

I have a Samsung tablet. I made a new .tar file containing boot.img, recovery.img, and vbmeta.img. I let Magisk patch the mini-AP.tar file to install Magisk in recovery. I don't have TWRP.
 
  • Like
Reactions: pndwal

Harlock1978

Senior Member
Jun 8, 2013
117
19
38
Hello I updated my P8lite to the latest version of Magisk ap and installer, but now most of my apps start and exit and everytime I turn the phone on I'm asked to install Magisk manager even if it is installed.

What can I do?
 

pndwal

Senior Member
Jun 23, 2016
1,713
847
113
Sydney
Hi guys. Some guidance needed here. My phone (Mi9 Lite) have received an OTA update, I tried to install and the installation failed. Totally forgot about root/magisk.
Then I´ve followed some instructions to uninstall Magisk restoring images option, tried to apply the OTA and the phone rebooted and after that I am stuck on fastboot. Not sure what to do now.

Please help.
If you have TWRP you could 'fastboot boot recovery_img' from PC, then run Magisk-uninstaller zip from here:
and reboot to see if full uninstall fixes issues (corrupt ramdisk, etc)

Otherwise, try selecting latest Fastboot MI 9 Lite ROM from here:
and flash using MI Flash Tool w/ 'save user data' selected. PW
 

zuelber

Member
Dec 9, 2010
5
0
21
São Paulo
If you have TWRP you could 'fastboot boot recovery_img' from PC, then run Magisk-uninstaller zip from here:
and reboot to see if full uninstall fixes issues (corrupt ramdisk, etc)

Otherwise, try selecting latest Fastboot MI 9 Lite ROM from here:
and flash using MI Flash Tool w/ 'save user data' selected. PW
Tried several methods and the only one that actually worked was MiTools V2. (using device bricked option)
Fastboot was returning this message: \$fastboot -s .* lock
Not sure what happened
 

theGeekyLad

Senior Member
May 27, 2013
222
252
93
Thane
thegeekylad.firebaseapp.com
Actually, Google recently enabled it (look like just for little testing for now).
OK, here we go again!

Google announced new iteration (after "March boom" testing) of hardware attestation with new API back in 5 May here: https://groups.google.com/d/msg/safetynet-api-clients/lpDXBNeV7Fg/Ov2H6ZvhBQAJ
And now, they start turning it on.

How to check it?
1.
Install normal SafetyNet testing app. In this case best: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
2. Start LogCat recording (as you prefer). You can use this app or ADB: https://play.google.com/store/apps/details?id=com.dp.logcatapp
3. Open SafetyNet testing app and run attest check.
4. Look into LogCat and find SafetyNet response in RAW format. You can find it by mask "evaluationtype". If hardware attestation enabled - the value be "BASIC,HARDWARE_BACKED", if not - just "BASIC".

Check via ADB (no ROOT needed)
https://forum.xda-developers.com/showthread.php?p=82964687#post82964687
Thankfully my Pixel 2 shows an evaluationType as BASIC only. I'm on it's last EOL security patch with an unlocked bootloader and no root. I stumbled upon a post by someone here who penned that the evaluationType on their Redmi unexpectedly turned from BASIC to HARDWARE_BACKED.

Does it mean that SafetyNet in my Pixel 2 "already" sends keystore certificates but it's just the SafetyNet servers that don't pay heed to it yet hence BASIC type? Or is it that whenever Google intends to bring HARDWARE_BACKED into my Pixel, they'd roll out a covert Play Services update (which would then send the keystore certfs.) that would screw my happiness?
 

MECH_TECH

Member
Dec 6, 2014
48
2
38
If you have a working TWRP installed then you do not need to patch AP. Unless something has changed? You should just be able to boot to TWRP and Flash Magisk zip when you have TWRP.
Oh I was looking on his github site installation instructions. I downloaded the zip file and installed it through TWRP and it worked. Thanks
 
  • Like
Reactions: pndwal

pndwal

Senior Member
Jun 23, 2016
1,713
847
113
Sydney
Tried several methods and the only one that actually worked was MiTools V2. (using device bricked option)
Fastboot was returning this message: \$fastboot -s .* lock
Not sure what happened
Apparently error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done is normal w/ MI Flash Tool if 'clean all and lock' (bootloader) option is not selected, but ROM is still actually flashed fine according to users.

You seem to be up and running again in any case. 👍 PW
 
Last edited:

pndwal

Senior Member
Jun 23, 2016
1,713
847
113
Sydney
Thankfully my Pixel 2 shows an evaluationType as BASIC only. I'm on it's last EOL security patch with an unlocked bootloader and no root. I stumbled upon a post by someone here who penned that the evaluationType on their Redmi unexpectedly turned from BASIC to HARDWARE_BACKED.

Does it mean that SafetyNet in my Pixel 2 "already" sends keystore certificates but it's just the SafetyNet servers that don't pay heed to it yet hence BASIC type? Or is it that whenever Google intends to bring HARDWARE_BACKED into my Pixel, they'd roll out a covert Play Services update (which would then send the keystore certfs.) that would screw my happiness?
Yes, seems Google frequently play with triggers for their selected devices for Hardware Key Attestation, and some are even exempted after bootloader unlock that were HARDWARE before!
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-83977547

Seems Google selection does not rely on any Play Services build; it is REALLY Hardware Key Attestation, and once implemented across the board we don't expect to be able to subvert it - presently it is easy as a simple model prop mismatch causes fallback to basic on any device.

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-82999891

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-82941997

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-82296901

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-82242343

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-82198257

So Fun's not (quite) over yet... But no knowing how long reprieve will last... PW
 
Last edited:

pndwal

Senior Member
Jun 23, 2016
1,713
847
113
Sydney
Oh I was looking on his github site installation instructions. I downloaded the zip file and installed it through TWRP and it worked. Thanks
Good show... But John does state there:
Samsung (System-as-root)
If your device is NOT launched with Android 9.0 or higher, you are reading the wrong section.
... didn't Galaxy S9 launch w/ 8.0 Oreo? 😉

Must admit, best option choices are not particularly clear there. PW
 
Last edited:

GuyInDogSuit

Senior Member
Jan 4, 2009
5,490
1,200
253
38
Sacramento, CA
I've tried to root my OnePlus 7T on Android 11 multiple times now, with no success, and I'm at my wit's end here.
The process can either be done through TWRP or through manually patching the boot.img. Neither has worked for me so far.
On Pixel Experience, it straight up crashdumped no matter how I did it.
On YAAP, it booted the patched boot.img, and I was able to flash the Magisk zip successfully. However, once I rebooted, root was gone. Every time afterwards it wouldn't even root at all, regardless of what version of Magisk or TWRP I tried (Magisk 21.1 beta, canary, Chinese TWRP, etc).
Someone suggested trying a different kernel. Got the crashdump there, as well.
I have no clue what to do at this point. While others have run into a similar issue, they have all resolved it somehow, while mine just... fails every time.

UPDATE: Decided to wipe and try again, finally rooted, again, and I hope it sticks after a reboot this time. But currently waiting on the "hiding Magisk Manager," sitting there with a spinning circle, doing nothing, for ten minutes now. Did this the first time I flashed YAAP and rooted it, and I stopped MM, tried again, and it failed, so I rebooted, which led to..... the above, regarding YAAP, all over again. I'm guessing it's not gonna happen this attempt, either.
Someone please tell me what I'm doing wrong....

UPDATE 2: So, like before, I waited, and waited, and waited.... and Magisk Manager never succeeded in hiding itself. I ended up closing the app, and any attempt to launch it or even uninstall it, failed. So I rebooted... and lo and behold, no root, again. So once again, gonna start all over, and fail, again, and again, and again, because I have clearly lost my mind and I don't know any other alternative than to just keep trying.

UPDATE 3: SUCCESS!!!
WOW! I am so glad I thought of this. So, on a whim, before I tried wiping and starting fresh again, I decided to uninstall MM from adb, with the command
Code:
adb uninstall com.topjohnwu.magisk
The command returned "success" so I checked my app drawer, and "Manager" was now there, but had an android icon. I launched it, and it asked to install the "full version" as it does when flashing it. It then asked me to manually relaunch the app, and voila! It was not only "hidden" but still had root active and up to date (canary, anyway). I rebooted it, tested SafetyNet, and success!!
Whew. That was an ordeal. And the best part is, this ROM I've been using (YAAP), has not had any crashdumps since I flashed the full thing (it did once or twice when I flashed the extracted YAAP boot.img I patched with MM, though).

Anyway, sorry for the long rant. Hope this helps out anyone else who might have run into this wall.
 
Last edited:

MECH_TECH

Member
Dec 6, 2014
48
2
38
Good show... But John does state there:
Samsung (System-as-root)
If your device is NOT launched with Android 9.0 or higher, you are reading the wrong section.
... didn't Galaxy S9 launch w/ 8.0 Oreo? 😉

Must admit, best option choices are not particularly clear there. PW
Yes this phone came with 8.0. Guess i missed that section.

More problems, I put my google account in so I could get all my apps on it but it will not allow me to add my Samsung account i keep getting failed error. I tried both with the email I'd I have and with google option but both fail. Is there something I'm missing? Is this related to Magisk or something else and do i need to post in a different forum?
 

zgfg

Senior Member
Oct 10, 2016
4,554
1,955
233
Updated to the to-be Canary Manager 316 (31x number is now omitted, hence 4766 or 15) and Magisk 21103, all ok (Xiaomi Mi 9T, Xiaomi.eu beta A11)
Screenshot_2020-12-28-16-04-09-432_com.topjohnwu.magisk.jpg
 
Last edited:

J.Michael

Senior Member
Jan 20, 2018
373
137
43
Yes this phone came with 8.0. Guess i missed that section.

More problems, I put my google account in so I could get all my apps on it but it will not allow me to add my Samsung account i keep getting failed error. I tried both with the email I'd I have and with google option but both fail. Is there something I'm missing? Is this related to Magisk or something else and do i need to post in a different forum?
Is there web access to a Samsung account? Maybe from a browser you can check access, reset password, get a hint about which e-mail address you used.
 

pndwal

Senior Member
Jun 23, 2016
1,713
847
113
Sydney
Latest Canary Changelogs:

Magisk (b51b884f) (21103)
  • Unblock signals before executing commands
  • Fix module installation in recovery
Magisk Manager (b51b884f) (4766)
  • More minor changes
John Wu, Dec 27

Sorry, but I don't drink Mountain Dew, don't eat Doritos, and I hate anything RGB, but I will hunt down anyone using light theme
PW
 
Last edited:

tazcan

Member
Nov 27, 2013
6
1
21
hello, when trying to hide magisk manager it just hangs it creates an app but if i try t start it just says app is constantly stopping what can ı do to hide magisk manager succesfully, btw i am trying on a MIUI and usb install is enabled, play protect disabled

edit: after i uninstall it via adb and try again it worked
 
Last edited:
  • Like
Reactions: pndwal

tramp20

Senior Member
Jan 15, 2012
685
124
63
I currently do not have anything useful to add towards getting you up and running with Magisk. That error is interesting though and I'll be in the lookout...
My problems are gone since the last Magisk canary before v21.2 (release notes: Fix module installation in recovery )..

Thank you for your interest :)
 
  • Like
Reactions: pndwal

Val81

Senior Member
Jan 14, 2016
80
8
28
Hello,
I'm using magisk since 2016 without problems, but now it's installed but have lost root permissions...
Tried to install it again on twrp but no success 🙁.
I need your help to solve my problem!
Thanks
 

abhinitagrawal

Senior Member
Oct 5, 2007
217
4
48
Jaipur
1. You cannot restore Knox. Knox isn't software - It is hardware. Once you trip Knox you blow a fuse, it's literally broken components - s it's irreversible.

2. Samsung Pass will not work without Knox. So that is gone forever.
Samsung Secure Folder is recoverable - You'll need SmaliPatcher.
S-Health I'm not sure of - You used to be able to get it working again but you'll need research it.

3. SafetyNet is failing because it is detecting root - Likely based on Hardware. You can fix that by using MHPC to spoof a different device. I'd suggest a Galaxy S10+

4. Not sure on that one.

5. Like #2 SmaliPatcher would also allow you to spoof location. Just select that option when you create the patch.
Did all steps 4-5 times and with extreme focus but still can't pass SafetyNet