yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
@ctcx You can test yourself:

Patch the padded and not-padded boot img and then temporarily (one time) boot to one and another by:

fastboot boot <patched-boot-img>

If it boots correctly and Magisk app shows that Magisk is installed, then the corresponding IMG file is ok.

And you can then do Direct install or flash it permanently:

fastboot flash boot <patched-boot-img>

Otherwise, just reboot to the previously flashed and working boot img

That way you will know if for your device padded/not-padded images are ok
[Magisk] zgfg:
Here we go.

Let boot img be saved to Internal memory, Download folder

Execute the commands:

su

od -A d -t d /sdcard/Download/boot.img | tail -4

It will take some time (it must dump the boot img till the end).

The result will be eg:

22304240 1147097165 4281409 0 0

22304256 0 0 0 0

*

33554432

That means that the last not-padded 'line' starts with the byte number 22304240

and.that padded 'lines' begin by byte number 22304256, till the end 33554432 , ie till the end of the 32 MB file

Hence the padded img file could be cut off by:

dd bs=1 count=22304256 if=/sdcard/Download/boot.img of=/sdcard/Download/cut-boot.img

And the resulting cut-boot img contains the not-padded part of boot img

Indeed, the last 'line' of cut-boot.img:

od -A d -t d /sdcard/Download/cut-boot.img | tail -2

equals to the last not-padded 'line' of boot.img:

22304240 1147097165 4281409 0 0

22304256
[Magisk] m0han:
That was what I first tried after uninstalling magisk completely (and rebooting) and installing 25206.

I had 6.0.3, but I tried 6.0.0 (and 5.1.2 before that) to see whether things would change.
[Magisk] m0han:
I didn't swap forks; I was on Delta all along, and I did 'Uninstall Magisk'. See screenshots from my post, marked now.
[Magisk] pndwal:
Still configuration can become corrupted sometimes... And you haven't said which option for Uninstall Magisk you took... Only "Complete Uninstall" will remove configuration files...

Interesting!... That's not expected Magisk behaviour...

Could possibly be flashing binaries from an online repo, but I doubt this... TJW Magisk hasn't done that since 22.0 as I mentioned...

I suspect @huskydg simply hasn't set up Install information properly; seems it may simply be reading his online Update/Latest build JSON and giving the same info as App Update does...

My guess is that both Patch file and Direct install options will still probably patch with your 25209 currently installed package binaries (unless Delta installation works entirely differently)... @zgfg may confirm or deny... 🤪

I currently have Alpha fork 25209 installed (simply because I wanted to test latest Shamiko v0.6 (141) which requires Alpha ATM) so haven't been able to double check TJW Magisk, but I can confirm that while 25210 is the latest Alpha, the Magisk Install screen correctly shows changelog for my installed 25209 Alpha...

😝 PW
[Magisk] m0han:
I tapped the marked button and did 'Complete Uninstall'. I did not 'Restore Images'.
[Magisk] zgfg:
Cannot test/confirm since Im already on that latest Delta 25210

But I believe it's just in displaying the one and single changelog.md for the latest version

Anyway, his other screen shows his actual version 25209 and I asked him, he tested and posted the screenshot with the result of

magisk -c

and that was also 25209

Anyway, he is IMO on Delta 25209 as he wanted

But @m0han has some problem with AdAway - I asked him what to check (how 1 up-to-date + 0 out-of-date hosts sources could make 3 hosts sources his hosts file is merged from) and to address further questions about AdAway to its thread

I can no more help
[Magisk] pndwal:
Yes, he knows what version he's on...

He's just worried that if he takes Direct Install with that (in order to patch while system is loaded to repair possibly bad 25209 .zip installation) he'll end up with 25210...

I said I doubt this can happen unless @huskydg still allows installation from online repo... TJW Magisk hasn't done that since 22.0... 😉 PW
[Magisk] AnnetkoO:
Good afternoon. Recommend the module the most relevant module to disable the navigation bar on Android 13 (miui 14) (I plan to use Nova launcher). Regards.
[Magisk] jons99:
Releases · Magisk-Modules-Alt-Repo/HideNavBar

Fullscreen/Immersive Gesture Tweaks for Android 10-14 - Magisk-Modules-Alt-Repo/HideNavBar

github.com
[Magisk] AnnetkoO:
Thanks so much!
[Magisk] zgfg:
MRepo update to v1.2.2:

Release v2.4.10 · MRepoApp/MRepo

What's Changed Bump protobuf from 4.26.1 to 4.27.0 by @dependabot in #230 Full Changelog: v2.4.9...v2.4.10

github.com

Changelog:

Support in-app check for updates
[Magisk] m0han:
How is that done?
[Magisk] zgfg:
Don't know. Will see when v1 2.3 cones
[Magisk] m0han:
Hope the dev squares up to something like this
[Magisk] martyfender:
It looks like one has to jump through hoops to add more than the default, small repository. Also on both of my Onn 8, Android 9, ARM 8-A devices, it constantly crashes.
[Magisk] zgfg:
They have a copy of Alt repo, you can add

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

I use the app since then (three weeks), on two phones, no crashes for me
[Magisk] xzenx1234x:
Hi Please Help Me.

I have Device LG G4 H815.

I have an unmodified Android 7 Nougat operating System here. Needs to know how to generate a new img Magisk Mask file / image from Magisk Mask application developer.

I know there is a Magisk Mask released by Magisk 981ccabb beta which is downloadable on APK mirror.​

Magisk 981ccabb beta APK Download by topjohnwu - APKMirror

Magisk 981ccabb beta APK Download by topjohnwu - APKMirror Free and safe Android APK downloads

www.apkmirror.com

Kindly ask for information on what to do to generate an img image file in the latest version. The stable version generates an img Magisk Mask Image File in a version that does not load my rooting.

I am uploading screenshots from Iinstallation Root-A through Magisk Mask - a. Although version Magisk 981 CCABB (25210) loads correctly through the installer Magisk-a. but the img image file is still generated in version 25200. Informs that the image file version 25200 does not root my device LG G4 H815 with Android 7.0 Nugat. Is there an img image file version 25210 or higher to boot LG G4 H815 with Android 7 Nougat ? At this moment I am not able to access TWRP Recovery After Installing Android 7 Nugat via the TWRP Recovery Menu - it removed TWRP from my Recovery partition from my Smartphone. kindly ask for a hint on how to generate the img Magisk Mask file in version 25210 or later.
[Magisk] xzenx1234x:
Every time it generates an img file-it loads the same version, i.e. 25200. What to do in this situation ?
[Magisk] pndwal:
All official latest Downloads here (DON'T download from other sources):

https://github.com/topjohnwu/Magisk

Follow Installation Instruction from here also...

Scroll to bottom for earlier stable releases...

Yours appears to be the latest stable...

25210 is latest Canary (bleeding edge) Magisk but, since major selinux/module rule and overlay mount point refactoring (ie. a brand new magic mount backend added that should properly support overlayfs systems) a few things are broken ATM... You could try it, but I'd recommend being very familiar with current issues discussed here recently... Also, were expecting many fixes in next Canary, 25211, any tick-of-the-clock...

With an old device like LG G4, 25.2 (stable) should work fine anyway...

I'm rather confused about your install process...

Are you following official instructions?... As you don't have TWRP, did you flash the patched boot.img you successfully generated (in your downloads directory) using ADB fastboot from a PC? What errors did that give?... or did it flash successfully?

😃 PW
[Magisk] xzenx1234x:
Hello, can you help me with this step by step?

Yes I try to flash the patched file - but it doesn't help. I am following the instructions.
[Magisk] xzenx1234x:
Could you download and paste in the files for me the latest Magisk Mask? Version 25200 doesn't seem to work at the moment.

Version 25.2 doesn't work either. I need to get the latest version of the test release.

I tried Flashing via Kingroot but it doesn't help.
[Magisk] xzenx1234x:
Connecting to a device on Microsoft Windows in Power Shell Console I have.

Can you help me ?

I have such a message.

I have the correct drivers on my Huawei laptop with Microsoft Windows 10.

I don't have any yellow exclamation mark warnings in device manager. The drivers for Android devices are working.

Any idea how to enter TWRP Recovery via Command?
[Magisk] pndwal:
You need to be clear... Why didn't flashing patched image help?... This is plumb necessary... Image left in downloads folder will do nothing whatever Magisk version you use! 😬

Did something not work when flashing the patched file?... Did you use ADB fastboot? ... Can you see connected device from ADB command prompt / PowerShell?... What are you typing in CLI? ... What errors show?.... PW
[Magisk] pndwal:
Nothing in the message 😦...

And keep well away from kingroot... You may now need to clean flash ROM!... Or dirty flash at least... PW
[Magisk] CrazyCypher:
Yaay :) Then we can only hope phh's future hidesu versions could implement something to hide Xposed..I guess we'll see
[Magisk] Ashtrix:
Tried the SELinux changer, Showed me the Permissive but Alas ! Still no Processing :(
[Magisk] RodMY:
I didn't believe at all that changing to a custom kernel would make SafetyNet to pass in my case but that's exactly what happened. Flashed ElementalX and all green. Thanks!
[Magisk] requiiiem:
:rolleyes:
[Magisk] TamalePie:
Not working

I went through all the steps methodically, however I'm not getting the toggles to turn root on and off when I open the app. It just shows me that I have the latest versions installed. I'll attempt to attach a screenshot.

I'm using a Samsung Galaxy S4 with android version 5.0.1. Any suggestions are appreciated.

p.s. How do I attach an image? :p
[Magisk] andrew2432:
Settings within the magisk manager has magisk hide. Root toggles were last seen in v6
[Magisk] dimm0k:
any idea why I can't attach attachments from my device in the Gmail app when I have Magisk v8 active? as soon as I freeze it, I can attach files with no problem.
[Magisk] Thot Ctrl:
I installed the Viper driver from Magisk Manager and then installed the apk from official thread but the app keeps prompting me to install drivers for which I select no every time. Anyone have an idea what the problem might be?
[Magisk] adomm420:
EDIT: fixed the issue myself.
[Magisk] schwarzerfleck:
I'm not fooling, but did you enable V4A? Like, the master power toggle?
[Magisk] ziotom2:
Driver and application are same version?

Inviato dal mio SM-G935F utilizzando Tapatalk
[Magisk] Thot Ctrl:
The Viper drivers are the ones from Magisk Manager download section which says Viper4Android FX v2.5.0.5 and the apk version is 2.4.0.1 which seems to be the latest version
[Magisk] ziotom2:
Search in google v4A version 2.5.0.5. there is the new apk to download.

Inviato dal mio SM-G935F utilizzando Tapatalk
[Magisk] Thot Ctrl:
I searched in the thread found a couple so I am not sure which is the official one.

But I downloaded this one http://xdaforums.com/showthread.php?t=2191223&p=69308482

Is that the right one?
[Magisk] ziotom2:
Don't remember. Just try it. Kepp in mind that the new version has a completely renewed UI.

Inviato dal mio SM-G935F utilizzando Tapatalk
[Magisk] poulopoulosa:
Heya, I been tinkering around Magisk and the xSetprop but it seems that I cant pass safety net (CTS Profile match: False). Did google cover the "setProp" hole again or not?

Also, It seems that OnePlus one doesnt need to verify the bootlock?

Cuz xsetprop logs says that:

verifiedbootstate prop does not exist

flash.locked prop does not exist

veritymode prop does not exist

shoulda put the "xsetprop ro.boot.flash.locked 1" to the beginning of the post-fs-data.sh or end?
[Magisk] mobileman88:
Magisk is being detected by safety net
[Magisk] poulopoulosa:
Even with the hide setting?
[Magisk] mobileman88:
Yes.
[Magisk] CrazyCypher:
Someone should make RootSwitch for Magisk :D
[Magisk] xzenx1234x:
I do not load TWRP Recovery from the img file.

I am following this guide

Jak zainstalować TWRP Recovery w LG G4 (L815)

Nie wiesz, jak zainstalować TWRP Recovery w LG G4? Zobacz nasz poradnik krok po kroku, w którym pokazujemy cały proces instalacji TWRP w LG G4 (L815).

www.download.net.pl
[Magisk] pndwal:
Forget TWRP... (You said you lost it anyway)... Forget those instructions...

Follow official instructions I linked.... Your screenshots show messing with TWRP etc; they don't show you've tried flashing patched boot.img AT ALL per John Wu's instructions... HAVE YOU?...

Please do as suggested above... I have to go out now... Others may help you further... PW
[Magisk] xzenx1234x:
Hello can you help me still?
[Magisk] xzenx1234x:
Hello, I am logged into GitHub.

Can you tell me how to successfully find and download an img image?

I know where the search engine is on GitHub, but after entering the word img, it does not find an image file in img format. How does it work - ie... on GitHub file search?

Ok, I downloaded Android Studio. According to this it is stated on GitHub.

Building and Development​

Magisk builds on any OS Android Studio supports. Install Android Studio and do the initial setups.​

Run the first step with Android Studio pre-configuration.

I kindly ask you to lead.

How should I configure the second point?

Trying to do android studio setups. Should I configure for Android 7 Nougat?

I have Main Menu. What next steps?

Ok, I choose a new Project. What next steps?
[Magisk] pndwal:
No... Going out! 🙃

... You already made the patched image... It should work if from your current ROM!... You just need to follow official instructions to flash it!!!... Then report results. 😉 PW
[Magisk] J.Michael:
Stop asking for the latest Magisk. The latest Magisk has problems.

Read the last five pages of this thread. I think every question you have asked has been covered (again) recently.

If you were able to reinstall the Android system, then you know how to flash a ROM. If you would take the trouble to tell us how you flashed a ROM, we might be able to say how to flash a single partition.

You had TWRP before you lost it. You must have installed TWRP once. You can install it again. (Also covered recently, someone gave his procedure for installing a system update. He specifically said he loses TWRP every time he flashes a new ROM, because a ROM includes a recovery, and the recovery it includes is not TWRP. So he reinstalls TWRP. Not a big deal, not a problem that needs to be solved.)

If you would specifically answer @pndwal's question "How did you install the patched boot image?", then we could stop wondering whether you just missed this vital step.

Which still leaves the fact that there are problems with the latest Magisk. It is harder to explain what is wrong with the latest Magisk, and how you might get around the problems, than it is to tell you "Do not try to use the latest Magisk."

Download Magisk 25209 from github. If you do not understand these words, ask again.

And please read what you have written before you hit "Post reply". If you can catch the places where you have scattered fragments of words, and delete them, it will make it much easier fo understand your questions.
[Magisk] xzenx1234x:
Thank you for your reply. According to your post you sent to me. So I answer. I chose these steps. I downloaded the Android 7 Nougat zip package - this is the full version of Nougat because it also contains the Bootloader released for Android Nougat. So I paste the link from where I downloaded Android 7 Nougat. I chose the option that I downloaded the zip package from the XDA Forum. I am pasting the link here

https://xdaforums.com/t/h815-nougat-stock-v29a-int-variant-official.3659860/

So I chose the option that I downloaded the zip package from Nougat and copied it to the MicroSD Card in my smartphone.

Then I selected the advanced wipe options from the TWRP Menu. I cleared everything but the last two options.

Moving on. I answer the next question on how I got Recovery TWRP. Describes the Steps.

Having Android version MarshMallow 6.0 for LG G4 H815 on unlocked Bootlader - successfully booted TWRP from img file - using Console in Microsoft Windows.

It states that when I have Android OS version MarshMallow 6.0 on my G4 H815 device - then the device will successfully boot into Bootlader and then go to Recovery TWRP.

After updating the Android System to LineageOS 18.1 - that is, to Android 11 - I just couldn't deal with the performance configuration in this device.

I am asking for help and steps.

The simplest way of explaining this is Recovery TWRP, which I got only with the cooperation of Android MarshMallow 6.0.

Can I ask for support?
[Magisk] J.Michael:
I'm not sure what you mean by "img image" -- that's what I meant when I accused you of scattering word fragments.

You will not be downloading what we call an image file from github. An image file is a file specifying a partition on your device. As @pndwal said, you should be extracting the boot image from the bigger file you use to install a ROM, then using Magisk manager app to patch that boot image, then flashing the patched boot image.

You have my sympathy. I have found what needs to be downloaded from github. Other times I have been a

unable to find it. Start at John Wu's github page. Look for something called release files. Better, search this thread for "github" -- somebody (I'm looking at you, @pndwal) described how to find the files well enough for me to do it once. It was not necessarily recent, you may have to go back a few years.

What you are supposed to be downloading from github is an Android apk file. It is much more than a normal apk file, but it looks like an apk file.

Start here.
[Magisk] xzenx1234x:
Dear J.Michael

Can we continue here on Android 7 Nougat? Let's try through the commands available for the Power Shell Console - get the entry options in the TWRP Recovery Menu. Ie... booting into Recovery from the img file.
[Magisk] J.Michael:
Explain "successfully booted TWRP from img file - using Console in Microsoft Windows."
[Magisk] xzenx1234x:
So I need the apk file right now?
[Magisk] xzenx1234x:
If you could show me, i.e. send me a hint, how to download the apk file from GitHub correctly - I will be very grateful to you.

Describing the word - img file, I mean the file format.

describing in a word

img file - I mean TWRP Recovery image file.
[Magisk] J.Michael:
You are mashing words and concepts together in a way that does not make sense to me.

I don't care what version of Android you are using. If you installed it and it runs, by all means stick with it.

Understand that 7 is old, and further supports @pndwal's caution that you might be better off with an old version of Magisk. Only experimenting will tell.

"commands" typed in a Power Shell window are not always "Power Shell" commands. I don't use Power Shell. I'm sure it has many commands not available in the creaky old Command Prompt window I use. But what you used to "boot into recovery" was probably a program you installed on your computer. I am deliberately refraining from suggesting the first things that come to mind -- I want *you* to tell me what you did.
[Magisk] J.Michael:
The apk file is one of the first things you need, but it will be useless if you do not know how to flash a partition.
[Magisk] J.Michael:
If you can use TWRP at all, you will not get it from John Wu. You have a TWRP. The first thing I would try is installing the TWRP that worked with Android 6 on a system running Android 7. I don't know all the things that can go wrong, but it might work.

Try that.
[Magisk] martyfender:
https://github.com/topjohnwu/Magisk
[Magisk] pndwal:
@xzenx1234x, @J.Michael

Yup, things are getting more convoluted (complicated) by the minute...

If you look at the first posts in this saga, @xzenx1234x has patched boot.img successful with 25.2 Magisk but says "The stable version generates an img Magisk Mask Image File in a version that does not load my rooting"... And shows Magisk Installed = N/A...

@xzenx1234x then asks for latest Canary etc, but there was no indication 25.2 patched image was ever flashed ... Best answer we got was "it didn't help"... All screenshots offered show is attempts to flash TWRP and other stuff so I believe 25.2 patched image was never actually tried...

So until user reads proper instructions, not the 3rd party 'instructions' proffered, and stops being fixated on getting Canary builds, getting some imaginary image file or extra apk from GitHub, building Magisk with Android Studio, installing TWRP, understands that 25.2 is correct to patch with 25200 binaries (as these are the same build), using kingroot, fixing TWRP failure to boot from fastboot (it probably doesn't work for N as built w/ M or earlier base and bootloader has apparently updated device from arm23 to arm64 V8 what's more...), etc etc, were getting nowhere...

The fact is with such an old device any stable Magisk build should just work; 25.2 is fine, member already has it and has patched a proper N ROM boot.img successfully with it from what we see in screenshots...

Why break things by using broken Canary?!

@xzenx1234x apparently still needs to do what I suggested:

What's so hard fastboot flashing patched boot image???... Fastboot is working!... Member needs to read, understand the simple thing being missed and report any issues. Period...

If kingroot etc has messed up the installation we can help later... 😬 PW
[Magisk] pndwal:
FYI (only), if you mean older TJW Stable, Beta and Canary Builds, S&B are found easily by clicking Releases at bottom of Magisk main page on GitHub...

Older Canary builds are in

https://github.com/topjohnwu/magisk-files repo.

To download Canary --> change branch from master to canary --> click history (clock) symbol --> select a build by date --> Browse files --> View code --> select app-release.apk (Nb. app-debug.apk is corresponding Debug build) --> Download from 3 dot menu...

Even Older Canary builds are archived in

https://github.com/topjohnwu/magisk_files repo. (Look carefully to spot the difference.)

Same as above to download Canary builds here...

🤠 PW
[Magisk] ctcx:
Thanks very much for the explanation sir.

I also found that, at least in the case of LOS downloads, either the boot image direct download and the extracted one from the ROM zip are actually both zero-padded. So by following the Magisk official instructions we'd be always flashing a padded image.

Then, now just final doubts:

You say one can temporarily boot the patched image with fastboot for testing with the corresponding command previously mentioned. So the device will reboot indeed. But what do I do with adb currently running in the PC? Should I keep it running until device is done rebooting into system, then close adb? If so, it will lose connection while in the process of rebooting anyways...

It was mentioned here that, theoretically, zero-padded images should not affect the final results at all. Is there a reason you in particular un-pad the images you use?

Finally, just as comment, I found other equivalent commands to od which output the basically same results:

hexdump -C boot.img | tail
od -A x -t x1 boot.img | tail
xxd -a boot.img | tail

Again thanks for all your help.