yashsingh1/xdaforums huggingface dataset:
[Magisk] Giblet-dono:
My working order:

SuperSu

Reboot

Magisk

Suhide

Xposed

Reboot

(Xposed is optional)
[Magisk] teddy0209:
I just told you the steps... ?
[Magisk] ericotena:
That's what i did. Still fails to bypass safetynet.
[Magisk] teddy0209:
Check if su folder in root directory contains suhide... By the way, why are you trying to pass safetynet?
[Magisk] Elmarigo:
Shouldn't all that suhide related questions be asked in another thread?

I had some magisk related questions, but they won't get answered, just because of that kids game.
[Magisk] Giblet-dono:
Not sure what to tell you, but as far as I can see Secure Settings (pro) works for me with magisk 7

If you want me to test anyhting to be sure, just tell me what and how
[Magisk] Frostbiter:
Thanks, I got suhide to work with magisk but not with xposed but I'll ask about that in the xposed thread.
[Magisk] Giblet-dono:
as for Xposed, try version 86.6 first, it should work..

If it doesn't you should try 86.2

Those are the only versions that should work properly
[Magisk] Iceyogurt:
no dalvik-cache is generated when I was using SuperSU with Magisk v7.

flashing sequence:

SuperSU 2.78

suhide 0.54

Reboot

Magisk v7

Xposed. 86.6

After the process above, xposed, SuperSU, suhide worked well. Except no dalvik-cache was generated. Some app, like YouTube, crashed without corresponding dalvik-cache. This problem doesn't appear when I'm using phh's superuser with Magisk v7.

Device: OnePlus 3, Oxygen OS.
[Magisk] negroxxx:
I am very happy

I can play pogo.
[Magisk] Vinnom:
[MENTION=4470081]topjohnwu[/MENTION]

The device won't boot up. Moto X 2014, using brokenOS 5 (AOSP 7.0), SuperSU 2.78 SR1 (systemless update for working with magisk). Forgot to grab the log, but I can repro it and grab it if you need it. Below is the link to the backed up boot.img

I followed the instruction for using superSU systemless, which is download magisk manager and installing magisk from it. When I reboot, I can't boot up (stay at bootloader screen).

boot.img
[Magisk] andrew2432:
works amazingly

[MENTION=4456638]Äptiva[/MENTION]

Aptiva thanks this and your previous post got my lgg2 rooted and running pogo while root unmounted. Stock firm only, [MENTION=5031300]blastagator[/MENTION]s you mentioned.

ALSO installed paid version of fake GPS..actually bought it no idea if an apk exists, blue compass image for app, moved to system. Check expert mode, Set your location with mock location on, hit play in fakegps app. Disable mock locations, open pogo...GPS spoof once more...just my method. No xposed, no cf su, and they just released a 3 freaking dollar joystick for fake gps but I haven't tested. I'm trying to get pogo working on my galaxy s5 sprint smg900p with magisk method..installed v7 and then went back and pogo won't authenticate, if anyone has maybe tried to stock, magisk 6, manager 1.2, phh su, I would love to know if it worked.
[Magisk] dan60:
Congrats! This is the way we find solutions 👍🏻. Best luck for you 🍀
[Magisk] pndwal:
My understanding of this is that initrd and initramfs achieve much the same thing, but initramfs at an even earlier early stage, and also takes precedence over initrd.

https://www.linux.com/training-tutorials/kernel-newbie-corner-initrd-and-initramfs-whats/

Both require bootloader support, and even if support is missing from kernel / boot image, this can be restored thru custom modification, eg Magisk actually adds such basic initramfs support where missing.

The very real problem is custom modders generally cannot add such support to bootloader where missing; that's the whole reason for Magisk in Recovery on such devices.

The confusion comes because by design (for good reason) the ramdisk flag (in Magisk app) shows the FACTORY state of support for ramdisk in boot image, and will show 'no' (despite the presence of ramdisk in recovery, and) even after ramdisk is manually added to boot image, and in fact is working on some devices:

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

I like your 'issue' suggestions, but I won't be doing this as John is already annoyed with 'bug' reports that are not really bugs, he already addressed the confusion problem in the issue cited above in October, explaining why ramdisk says 'no' even if added, and it seems any changes to this will be a very low priority for him.

Clearly, that clarification from John explains the reason ramdisk = yes ONLY for FACTORY ramdisk (and we just need to understand that); ie, even with ramdisk manually added and ramdisk = yes to indicate this, it will still likely be unusable, whereas ramdisk in recovery will work.

As I said earlier, there is now actually ramdisk in boot image; Magisk adds it! ... But this on its own DOES NOT mean it's usable... so Magisk simply reports if FACTORY ramdisk is present as this is the only one sure to work. (Factory ramdisk indicates compatible bootloader. Manually added ramdisk indicates nothing!) 👍 PW
[Magisk] ineedroot69:
So i was avail to install magisk 22.0 and im rooted but sadly my dm-verity is now triggered and i learn my lesson read the changelog
[Magisk] Didgeridoohan:
I can't quite remember currently, but I do believe that the adb command does not touch scripts in post-fs-data.d or service.d (I also currently can't remember if Safe Mode does, have to do some reading/testing later). Modules shouldn't be putting stuff there though, since that breaks encapsulation. Unfortunately a lot of modules do...

IMHBCO, since Magisk is such a powerful tool it is up to the module developers to make sure that it is possible for the user to recover if there are any issues. As an example, my MagiskHide Props Config module can be disabled or have it's settings reset by placing a specific file in the root of the device's internal storage. That way you can always recovery, even if the device can't boot with Magisk installed. Details (if anyone's interested):

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

Usually it is something along the lines of holding the power button until the OEM splash screen shows and then switching to holding volume down instead until your device boots into Safe Mode.
[Magisk] pndwal:
Well, it says "Sorry, test failed. This feature cannot run on your phone", and I agree this seems to be due to inability to see su now, although the same failure used to occur when installed on adopted storage or other external memory.

Seems the problem is:

https://www.didgeridoohan.com/magisk/MagiskRootIssues

You could try 'symlinking the su binary to the location where the app is looking' as suggested, or, using another File Manager from store (grant root access and enable r/w) COPY /sbin/su to /system/xbin.

You may need to make a module to do this systemlessly if mounting system rw isn't possible, or to take future OTA updates, but still may fail to pass SafetyNet any longer.

For these reasons (due to lack of current support), and because of serious security implications revealed w/ ES Explorer - mentioned by @curiousrom - , I've also moved to other less obtrusive Root Explorers...

I like Total Commander and Root Explorer. Here's a few more:

https://www.androidauthority.com/file-manager-explorer-apps-android-279800/ PW
[Magisk] ineedroot69:
I have question?? When installing magisk and your dm-verity is already trigger I need to uncheck "preserve avb 2.0/dm verity" is that correct??
[Magisk] DiamondJohn:
the vanced I am running uses a boot script, in post fs data. Its been a while since I checked, but I have a vague memory that each module can contain a script specific to itself. I need to go back and read and re-learn if a module have either or both a post-fs-data and service.d.

Although a good idea, with some of the cool featiures, its hard to resist trying a module that does not. There is one for my phone that I really wish to use (it has a few features found in Xposed Gravitybox!), and hence my interest in recovering if it triggers a boot-loop. I think I will suggest something along these lines to the dev on the thread. But, I think it will be quicker for me to make my own "boot three times and then uninstall" script. I already have a template that i previously used on another module.

I have only gone into safe mode on purpose once, to see what its about. And after all the config I lost, i have only accidentally done so since. But I have never accidentally done so using button combinations, and I have gone through all sorts of button combinations (accidentally). I just rebooted my current device, but backed out as i didn't want to loose my current config. I guess if I do get in a boot-loop, it will be worth a possible look. Maybe a question on my device specific thread/forum.

EDIT: someone just posted on that thread, how it caused their device to stall on boot...
[Magisk] Shady88:
Hi, have a question.

Since my phone probably wouldn't flash new magisk from recovery (i tried yesterday for lineageos 17.1 rom, from official twrp and lineageos' twrp they suggest), when i have the boot file extracted from the rom, i need to patch it from the rom i intend to use it with, or any rom would do, it won't make a difference?
[Magisk] Wolfcity:
I wanted to test Magisk 22 on my old Moto G 2014 running Aosp Extended (Android 7.1.2), unhid Magisk 20.4 and went to direct install. That didn´t work, nothing happened when pressing the button.

As I had no boot.img availabe at the moment I changed the ending of the apk to zip, booted into TWRP and tried to flash it.

I got an error message (sorry, I don´t remember the text) and now the device won´t boot anymore and the TWRP recovery seems to be gone too.

I only get to the Fastboot Flash Mode screen to select between

-Normal Powerup (goes back to Fastboot screen)

-Recovery (goes back to Fastboot screen)

-Factory

-Barcodes

-BP Tools

Underneath is the error message

Invalid boot image header

Fastboot Reason: Fall-through fron mot-charger boot mode

USB conncted

Usb is conncted as I tried to flash or boot into TWRP by fastboot, results in the following error:

C:\Mini ADB and Fastboot>fastboot flash recovery twrp-3.4.0-0-titan.img

(bootloader) has-slot:recovery: not found

(bootloader) is-logical:recovery: not found

Sending 'recovery' (8192 KB) OKAY [ 0.290s]

Writing 'recovery' OKAY [ 0.400s]

Finished. Total time: 0.743s

I´m a bit rusty regarding those errors so any help is appreciated .

As this is my testing device every way would be ok for me, restoring a backup or anything else but as long as I can´t boot or flash into TWRP it seems I´m stuck at the moment.

Edit: Extrcted a boot.img from the AEX firmware I´m running and tried to boot into it, error message:

C:\Mini ADB and Fastboot>fastboot flash boot boot.img

(bootloader) has-slot:boot: not found

(bootloader) is-logical:boot: not found

Sending 'boot' (8592 KB) OKAY [ 0.310s]

Writing 'boot' OKAY [ 0.418s]

Finished. Total time: 0.801s

and see attached screenshot.
[Magisk] pndwal:
Some details -

Bootlooping Pixels due to Google changes:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md PW
[Magisk] pndwal:
This has happened to a number of us w/ this update. Corruption of boot image occurs when no activity occurs when doing direct update or patching image. Fixed easily by fastboot flashing working boot image (I used a previously used Magisk patched one).

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

Later, I tried patching and direct update from 22001 again, and this time it worked fine... Still a bit baffled by that.

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

Not sure why your TWRP seems corrupted, but looks like boot.img flashing may fail only due to some corruption (from screenshot)...

Keep trying! PW

Edit: See you succeeded w/ boot image. Great...

You haven't got a previously patched / working boot image to flash from same ROM? - easy way to get root back!

Otherwise, try patching image only. If no freeze now direct update should work also, but you may want to patch / flash manually to avoid a repeat. PW

PW
[Magisk] Wolfcity:
Just booted into OS and am going to flash the boot.img.

Than I will check the TWRP status.

EDIT: TWRP is back too.

Thx for your help.(y)
[Magisk] pndwal:
Working fine for me on 22001 (identical to public 22.0). Redmi Note 8T, stock ROM.

Have you selected app in MagiskHide list also? And check Google Play Services is selected too.

Also check that Playstore Settings Play Protect says Device is certified. If not, clear PlayStore Data.

Next, Toggle MagiskHide off and on again in Magisk app Settings (sometimes helps). Reboot. Check if root is detected now. If still detected, clear App data and check again.

If still detected, many more tips here:

https://www.didgeridoohan.com/magisk/MagiskHide PW
[Magisk] Wolfcity:
Was able to patch a boot.img with Magisk 22.0 (22000)(18) stable and flash it by fastboot.

Still no root (installed (n/a).....

No older patched img available, was the first time I used this method on that device.

Should I try the procedure with 22001 ?

I could downgrade to 21.4 but I´m curious now.......

C:\Mini ADB and Fastboot>fastboot flash boot magisk_patched_v2LUN.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (9072 KB) OKAY [ 0.317s]
Writing 'boot' OKAY [ 0.333s]
Finished. Total time: 0.695s
[Magisk] vittorekaos:
Where can I find the latest version of Magisk to download?
[Magisk] Wolfcity:
As ever on GitHub :

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] pndwal:
Did you have hidden Magisk app when upgrading? See release Notes:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84543421 PW
[Magisk] Caffeinadict:
Hey all, I recently flashed LineageOS 17.1 to my Galaxy S5, (SM-G900W8) and am now attempting to root with Magisk using TWRP (v3.5.0). Upon installing the Magisk manager app I noticed that it now says SAR: yes, whereas when I had rooted previously (Android 6.0.1) it said SAR: no. The official installation page has special instructions for rooting Samsung devices with SAR, so just wondering if I should follow a different procedure than usual or if it doesn't matter since I'm using a custom recovery to flash the root/running Lineage. Thanks!

Update: Decided to just go for it and flash the root since the instructions for Samsung devices with SAR didn't seem to apply to devices with custom ROMs. All went well!
[Magisk] Wolfcity:
Yes, I unhid it before. I'm the kind of guy who's looking for changelogs everywhere...;)

Patched the boot.img several times with stable and canary but without success, device stayed unrooted.

For now everything is back to normal (on 21.4 again) but I'm not through with 22.
[Magisk] ineedroot69:
previously I can install this banking app directly to play store while magisk 21.4 is installed but now it say "your device is not compatible with this version" on magisk 22.0 I don't want to download apk from 3rd party software since it's a banking apps 🙃🙃
[Magisk] pndwal:
Do you have 'device is certified' in PlayStore (Play protect) Settings? PW
[Magisk] ineedroot69:
Well **** me it look like not certified anymore how do I put it back 😭😭😭
[Magisk] frazelle09:
Wow, you guys are great! i really appreciate your detailed reply. i was afraid that it was due to what pndwal mentioned (not finding su where it was looking).

i also really appreciate the other reply about ES-FileExplorer. i was really used to it and really liked it and, etc., etc. but if it's not really passing the security tests anymore, perhaps it's time to ... sigh ... move on - lol. i'll have to try the others - about the only other thing i liked about ES was that i could set up various FTP addresses. Very interesting.

Anyway, again thanks a lot for such complete posts, stay safe and have a great Saturday afternoon! :)
[Magisk] ineedroot69:
I apply for Google Play Certification i submitted my "Google Services Framework Android ID" let's just hope they approve it i don't want to go full 1337 style and install modded Google Playstore
[Magisk] banannerz:
Just here for some general support on installing Magisk. I downloaded the apk from here (https://github.com/topjohnwu/Magisk/releases/download/v22.0/Magisk-v22.0.apk) straight to my phone and installed the app. On the app I'm trying to install Magisk but it wants me to "select and patch a file". Not sure what it wants me to select. The instructions on github say "If your device has boot ramdisk, you need a copy of the boot.img. You should be able to extract the file you need from official firmware packages or your custom ROM zip (if using one)."

What file is this referring to? I'm using LineageOS on Xperia XZ2 comapct.

Edit: is it referring to the .img file found here? https://download.lineageos.org/xz2c. But ramdisk for me is yes, and this appears to be the recovery.img. I'm not sure what the boot.img is
[Magisk] Fil76:
Like a monkey a made a disaster

Easy Happy on my oneplus 6t with magisk 21.4 and 8.07 manager

I had the good idea to upgrade to 22

Updated manager ok

Tried to update magisk all yes (ramdisk..sar)

Give me error...argh (Sorry i didn't note the error)

Rebooted phone and only fastboot mode available (Lost twrp) and sideload doesn't install twrp permanently

So i Lost anything ..(photo doc...etc...my fault )

Lucky Mauronofrio tool unbrick my phone erasing and reinstalling os

Can someone explain me how to update ?

Thank you

Edit; ok i see that other user got same problema

Could someone

Link to 21.4 download

Link.to a guide for boot.img backup procedure ?
[Magisk] ineedroot69:
If your device has Ramdisk result is Yes, you need a copy of the boot.img

If your device Ramdisk result is No, you need a copy of the recovery.img

also the img file it's referring is from the current rom you are running so If you are running lineage os that's "provably" the img file.. pretty straightforward If you ask me. ( take note of the " " I'm not responsible if you bootloop your device )
[Magisk] Zoki88:
Okay, so, after literally whole day spending to wipe out whole phone, put again stock rom, twrp, magisk, all apps again setting up etc etc, when apps finally worked without recognising root, it again started recognising when i put busybox from backup, and even if i clicked to uninstall in app and deleted app itself, and restarted phone, nothing helpped, now again apps recognising root, so again need to spend whole day tomorrow to go whole process again of wiping and restoring just because of some hiden busybox files maybe... Guessing there isn't any easier way to remove that thing from busybox that causing apps to not work recognising root? (magiskhide can't help on that one, i tried, neither magisk manager hidden doesn't help and passing safetynet)
[Magisk] peter1miller2:
How do i install magisk in Revovery Mode without loosing Orange Fox Custom Recovery? Since patching it with Magisk App former Magisk Manager does not work it destroyes it. Can i have both Magisk and Orange Fox in recovery partition or not?
[Magisk] banannerz:
Sure, straightforward enough, but I don't know what "boot.img" is supposed to be in regards to LineageOS
[Magisk] ineedroot69:
busybox is "must have" application if you are rooted .. like for instance

Titanium Backup would not work without it

also the most infamous game hacking apps for android Lucky Patcher would not work correctly aswell without it ...

i recommend this https://play.google.com/store/apps/details?id=stericson.busybox it's free and does the job

also if i remember correctly there's a busybox magisk modules never tried it thou
[Magisk] pndwal:
Interesting... keep on it! 😬 PW
[Magisk] HippoMan:
The busybox magisk module (which is installable via magisk under the name "Busybox for Android NDK") is generally recommended over any others, when you are using Magisk.

Any other Busybox installations might not play well in today's Magisk world.
[Magisk] pndwal:
You need to extract it (open zip file) from rom package (xxxLineageosforyourdecicexxx.zip) you currently use. 👍 PW
[Magisk] pndwal:
Don't do that unless you have uncertified phone from STOCK! Chinese, etc.

Assuming you fully pass SafetyNet check, just clear PlayStore Data and Google Play Services cache, check your app is selected app in MagiskHide list, clear the App's data, toggle MagiskHide off and on again in Magisk app Settings (re-adds Google Play Services to MagiskHide list), and reboot.

Check if root is detected now. If still detected, many more tips here:

https://www.didgeridoohan.com/magisk/MagiskHide PW
[Magisk] banannerz:
Hi, I did that, but I don't see anything useful.

Here's the file that I flashed (lineage-17.1-20210219-nightly-xz2c-signed.zip, acquired from this page https://download.lineageos.org/xz2c) and here are literally all the files within that were extracted:

payload_properties.txt

payload.bin

care_map.pb

compatibility.zip (extracted and pulled out these files: system_manifest.xml, system_matrix.xml, vendor_manifest.xml, vendor_matrix.xml)

META-INF (folder) > com (folder) > android (folder) > metadata, otacert

Edit: I found a boot.img file here (https://androidfilehost.com/?w=files&flid=309552) which is *probably* the right one. I'm going to confirm in the XZ2c Lineage thread, but if anyone here has input on this, feel free to let me know. 🙏
[Magisk] DiamondJohn:
RE busybox. In todays world of non writable system partitions, then as far as I know, a magisk installation is your only choice.
[Magisk] ipdev:
There is no boot.img in the zip because it uses a payload.bin file.

You need to unpack the payload.bin to get the image files.

Personally, I switched to using Lineage's unpack for payload.bin files.

LineageOS wiki website - Link

I use Linux (fedora) and MacOS.

Did a quick cleanup of the script I use and added a few comments.

Normally I just copy the update-payload-extractor from my build directory. ;)

#!/bin/bash

# Extract and dump payload.bin file

### Switch to using LineageOS scripts.
# sudo apt-get install python-protobuf
# sudo dnf install python-protobuf
# git clone https://github.com/LineageOS/scripts

# Use git and clone the LinegeOS scripts to the same directory
# as this script and the OTA zip file.

TDIR=$(pwd)
EXTRACT=$TDIR/scripts/update-payload-extractor/extract.py

for zip in *.zip; do
{
unzip "$zip" "payload.bin";
NAME=$(printf "$zip" | sed 's/.zip//g');
python3 $EXTRACT payload.bin;
mv output $NAME;
rm payload.bin;
}
done;

#

echo "Done"
exit 0;

Cheers all. :cowboy:

Edit:

PS.

I use the LineageOS script to unpack factory and other custom rom payload.bin files also.

Edit 2:

Did a quick download and unpacked the payload.bin file.

Attached is the boot image from lineage-17.1-20210226-nightly-xz2c-signed.
[Magisk] banannerz:
Wow thanks for going the extra mile.
[Magisk] pndwal:
Better click his 'like' button! 😆 PW
[Magisk] ipdev:
No fun if you give away the secret. 🙃
[Magisk] pndwal:
Keep giving away the important ones...

That one's sure to help me (and others) in future. (My last LOS had boot.img in root of zip IIRC.)

Edit: Found this tutorial for PC also (Uses Payload Dumper Tool and Python to extract firmware files including boot.img):

How to Extract payload.bin and get stock boot image file

To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.

www.droidwin.com

And here's one to extract using phone!:

https://xdaforums.com/t/tutorial-android-ota-payload-dumper-on-android.4061799/

Don't know why LOS doesn't host the image files for root users; perhaps they make it difficult intentionally as Magisk makes prop spoofing etc easy and the have strict anti-spoofing policies etc... or perhaps some other reason, I don't know. PW
[Magisk] jenslody:
If you have a working TWRP you should be able to backup the boot-partition and patch the image-file from backup with Magisk.
[Magisk] Fil76:
But boot.img for magisk update must be original from stock image or a arleady boot IMG patched by Magisk ?

Can some One explain how to update from 21.4 to 22 cause disaster i made Yesterday ?

Thank you
[Magisk] banannerz:
Excellent, my question was somehow useful to others