yashsingh1/xdaforums huggingface dataset:
[Magisk] Ayan Chakraborty:
Did u install the Bluetooth fix magisk module for Samsung?
[Magisk] rxk:
I am not aware of that one. Where can I download that fix?

I hope this solve my problem.
[Magisk] J.Michael:
How is there a patched image if Magisk fails to unpack?
[Magisk] Philnicolls89:
Just search the magisk modules for 'Samsung Bluetooth' and you should find a fix. Wether it actually works or not I don't know as I've never had issues with Bluetooth.
[Magisk] io2345:
Short version: The first step of the two-step-process worked, the second failed.

Long version:

I first tried to install Magisk 22.0 with a version of boot.img that I had used for some tests with Magisk before. Obviously there were changes to it (maybe Magisk already changed it in some way, or it just got damaged). Magisk couldn't use it for the initial process of patching boot.img (see Post 44760).

But I found an untouched boot.img in an older ROM, which Magisk then could successfully patch (see Post 44765).

I flashed this patched boot.img using TWRP. Now I have the option "Direct installation (recommended)" of Magisk in the App. If you select it the second process of actually installing Magisk starts, but ends with an error message that says, that the boot.img has unknown or unsupported format.
[Magisk] ineedroot69:
upload the untouch boot.img
[Magisk] io2345:
Here is the file (untouched boot.img):

The Magisk patched boot.img can be found here : Post 44770
[Magisk] ineedroot69:
this your phone https://www.gsmarena.com/lava_iris_x8-7023.php ?
[Magisk] pndwal:
You could try this:

From Installation with provided boot.img unaltered,

1) Run full cleanup (Unroot) options from SuperSU app.

2) Make a TWRP backup of (unrooted) boot.img.

3) Rename resulting boot.emmc.win file to boot.img and try patching / flashing that.

No guarantees, but may work. PW
[Magisk] io2345:
No, the phone is an Estar Takee1.

ROM is from here: Mikel Android 7 for Takee1

and is itself a port from this ROM: RidonOS for Micromaxx A311
[Magisk] Mik-el:
I'm the guy who made the Rom for the EStar Takee 1.

@io2345 is helping me cause I can't work on the Rom at the moment.

As @io2345 said, I ported the Estar Takee 1 Rom from the RidonOS Micromaxx A311 Rom.

At this point think that the Micromaxx developer ported his rom from an Iris Lava x8, that's why you got that name from the boot.img!

I don't know which traces of root were left in the boot.img by the 2 developers that preceded me.

I just know that these roms flash the SuperSu .zip file from the updater script, and I've already removed it from my Rom.

Now me, @io2345 and the other Rom users want to unroot the boot.img too.

So thank you for the help you're giving us, guys.
[Magisk] io2345:
Tried it with the oldest ROM I have. Ran unroot, it took two or three attempts to get it done. After that a TWRP backup of Boot.

The resulting boot.img can be patched, although first try didn't work (process error). Second try is ok with this message:

- Device platform: armeabi-v7a

- Installing: f152b4c2 (22005)

- Copying image to cache

- Unpacking boot image

- Checking ramdisk status

- Stock boot image detected

- Patching ramdisk

- Repacking boot image

*************************

Output file is written to

/storage/emulated/0/Download/magisk_patched_OMNUP.img

*************************

- All done!

Looks good so far.

I copy this file to the SD-Card and rename it to boot.img, install the file via TWRP -> install image -> "Boot".

After reboot I start Magisk App again. Now there is under "Magisk" -> "install" a new option in "method" called direct installation (recommended). I select that, the white terminal window opens and the messages are:

- Target image: /dev/BOOT

- Device platform: armeabi-v7a

- Installing: f152b4c2 (22005)

- Unpacking boot image

! Unsupported/Unknown image format

! Installation failed

Basically the same as before. At that point I already can use SU functionalities. If - for example - I start Total Commander, it asks for root rights and get's it granted. I can access root directory. But in Magisk-options I can not permanently activate "MagiskHide" (it's Android 7).
[Magisk] edici:
Just updated my phone (Mi 10 (UMI)) from v12.2.4 to v12.2.7 through official updater app.

As I updated, my root priviligies with magisk also got removed which was expected..., so I made myself prepared with the new boot.img file and a computer nearby to flash the patched boot.img I will make in magisk app.

The patching of boot.img file goes without any error and so does the flashing of the patched boot.img file (or atleast fastboot tells me it went ok) so I continue with a reboot of the phone and it boots up to my lockscreen. Now my problem happens...:

-If I do not do anything (Not trying to unlock or start camera from lockscreen) it looks like my phone soft-reboots (goes back to bootanimation and then tries to load interface and everything again)

-If I do enter my password to get the launcher showing desktop, it will do the soft-rebooting before any icons load on the launcher.

-If I enter Camera, I can make pictures and look at the ones I did make (I tried making several) and my phone will NOT soft-reboot until I am back at the launcher/lockscreen.

To fix this temporarily I did enter fastboot again and flashed my unmodified boot.img file. and then my device will boot normally and I can use it.

I have also tried booting twrp and installing magisk that way, but the result has become the same...

I have tried both stable and canary versions of magisk.

I did try to pull the boot.img from my phone and patch, and from the downloaded zip. Same result.

I have tried with my "old" patched boot.img also (the one I made for my last firmware version) but phone behaves the same, soft-rebooting after I enter password.

Anyone has any ideas of what I can try?

I am trying two more things right now, one is gonna be install of older magisk.zip from twrp, and the other one will be a disabled lockscreen before flashing the patched boot.img file... Updating as soon as I finished testing.
[Magisk] Mik-el:
Do you know if the tool to unpack/repack the boot.img during the Rom porting process could have done something that now generates problems when we try to patch it?

Should we try to unpack/repack the bootimg with a different tool?
[Magisk] loony_tuna:
Sup folks! Has anyone tried pushing modified boot.img through adb to gain root? Redmi Note 9 Pro, MIUI 12 Global rom. I can see someone already did it, but I'm interested about this particular model and rom.
[Magisk] loony_tuna:
You must be trying to flash the old boot.img from 12.2.4 while having a new 12.2.7 on your phone. Am I correct?
[Magisk] edici:
Sadly not. I have doublechecked it 20 twenty times, and even tried to flash the old patched file also, with same results :/

I will try to remove my lockscreen now before flashing boot.img again and then if it doesnt work I will try to install older version of magisk from twrp... after this I am out of ideas...
[Magisk] loony_tuna:
I mean, you need to flash boot.img extracted from new 12.2.7 rom, not 12.2.4.
[Magisk] edici:
Sorry for not making myself understood..., I have done that.

After when it did not work, then I tried old.
[Magisk] Didgeridoohan:
@edici Have you made sure it isn't one of your modules that is causing issues?
[Magisk] edici:
Yes I am sure. I also booted it normally and uninstalled everything + ran uninstall.zip from twrp after.

BUT I JUST MANAGED TO GET IT TO WORK!!!!

Using unmodified boot.img file (to have phone working as intended) then just fastboot boot twrp.img, and while in twrp I flashed magisk 21.4.

Phone boots up normally, I went into magisk and chose to update with "direct install" and now I am on latest version with phone booting up!

Thank you guys for the time and effort!

Edit: I take it back, not working (phone is working, magisk is not), my "old" apps have full root access without being able to control it (magisk says no apps have that kind of access)

Uninstalling while I hoping next update will help with my issue.
[Magisk] J.Michael:
@edici have you checked your apps drawer to find and remove all instances of Magisk Manager?
[Magisk] J.Michael:
If you have removed the install of SuperSU from the updater script, why does the boot.img need to be "unrooted"? Isn't the install of SuperSU the reason you end up rooted?
[Magisk] Mik-el:
The updater script contained these lines that installed superSU:

package_extract_dir("supersu", "/tmp/install/bin/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/install/bin/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/install/bin/supersu");
run_program("/sbin/busybox", "sh", "/tmp/install/bin/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/install/bin/supersu/supersu.zip");

I've correctly removed them, and I added a little script like that flashes magisk instead.

The problem is that the phone still appears rooted so we can't use banking apps.

Also there is nothing in the following paths usually used by superSU ( "system/bin/busybox" , "system/bin/su", "system/xbin/busybox" and "system/xbin/su").

So we ended up looking at the boot.img
[Magisk] edici:
Yes I have, and now phone works as intended (non-rooted). Probably doing a backup of everything and full wipe tomorrow to see if it might help anything.

Framework caused the soft-reboot I had after patching boot.img.
[Magisk] edici:
Unable to use banking apps even if you hide root in magisk?
[Magisk] io2345:
Well, that's the Problem: It is an Android 7 rom, and Magisk Hide can not be set permanently, unless Magisk is correctly installed.

What is the reason for the message "! Unsupported/Unknown image format" in the second step of the process? I guess only the Magisk developers can tell us that.
[Magisk] gil80:
Hi. Can’t I hide magisk. Please help. How can I install the latest update?
[Magisk] rxk:
I found the magisk module but unfortunately did not resolve the problem.

I hope this will be fix in the next magisk update.

So sad, I am using my watch as standalone until fix arrive.
[Magisk] pndwal:
Yes, @edici, looks likely that you have a conflicting (hidden) manager/app instance as mentioned.

re. earlier problems, did you try disabling password/pattern when booted w/ unpatched image, before trying patched image again?... Sorry if I'm stating the obvious. PW
[Magisk] pndwal:
Looks like this may have actually worked perfectly!

You booted w/ latest Magisk 22005 installed.

I'm not sure why you tried to install the same again (later versions will say Update instead of just Install) using direct method, but it normally should work anyway.

Also, I'm not sure why Direct Install is failing (assuming you use 22005 Magisk app) and it may mean you need to use successful patch method (keep the renamed unpatched TWRP backup boot image) for future Magisk updates... I'd wait till you see Update to 22006 etc, and try direct update with that to confirm however.

Re. Magisk app problems, it may well be that you (too) have a conflicting (hidden) manager/app instance from previous Installation(s). Have you tried searching for and removing ALL Magisk app/manager instances before reinstalling latest? (This would likely account for your Direct Install problems also). PW
[Magisk] pndwal:
If you are using Universal SafetyNet Fix module, you could try latest test module (Shim the keystore service instead of replacing it).

Fixes for S20, S20+ & S21 Exynos are confirmed (Biometrics etc, not sure re Bluetooth issues etc) incl. on A12 Snow Cone DP.

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635 PW
[Magisk] pndwal:
This may help:

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

While Patch File only, then flash w/ fastboot or TWRP works, Direct Install failure may be due to hidden Magisk app instances, or other.

May be obvious, but I'll state it anyway; boot.img pre. Magisk may still be clean.

Many bank apps etc. Report 'Root' when there is none. User should read 'Modified Insecure Environment' detected. (These Devs often use 'root' VERY loosely.)

So rather than root in the real sense, apps are likely detecting unlocked bootloader, TWRP, Magisk app/manager, sundry root-capable apps on a blacklist, or other 'mods' using their own means (as SafetyNet API is patently unreliable), declaring 'root' / 'Jailbreak', and restricting use.

Therefore, MagiskHide may well be working as intended when Magisk is Installed, but additional solutions will be needed for some (many) security-centric apps. Much information on that here:

https://www.didgeridoohan.com/magisk/MagiskHide 🤠 PW
[Magisk] Didgeridoohan:
I saw this statement earlier and I'm wondering where you got this information from? Magisk's hiding capabilities are fully compatible with Android 7+...

From what we've seen, you have Magisk correctly installed (by patching the boot image manually) and it's only the direct install option that seems to be faulty somehow. As has already been mentioned, it might very well be that some incompatibility means that you just have to use the "patch file" option on that device whenever you need to update.

If you've got MagiskHide issues I really think you're looking in the wrong direction for the problem...

Tagging in @Mik-el, since you seem to be involved in this one too.
[Magisk] io2345:
Thank you very much @pndwal @Didgeridoohan and all the others who helped to clear things up. I think I misunderstood the procedure - you install Magisk either via patching boot.img OR via direct installation, you don't have to do both, right? Silly me...

That leaves us only with the riddle, why MagiskHide doesn't stay activated. You can switch it to "on" in settings. But if you return to settings, it is set to "off" again. I thought it has to do with the fact, that it's a pre-Android9 system (think I read that somewhere, that this functionality is working from "Pie" on upwards. Might have been true for Magisk below 22.0 version).

Upon first activation of Hide, Magisk tells you that it will reboot to perform additional action, but the on/off behavior of MagiskHide remains the same.
[Magisk] Didgeridoohan:
Correct.

Now I think you're mixing things up again. Up until Magisk v22.0 you needed to be on Android 9+ to be able to fully hide the app, but MagiskHide would work fine. From v22.0 Magisk's full arsenal is available from Android 7+.

Hiding the app (by giving it a random package name) and MagiskHide are two separate things.

From the sound of it, MagiskHide isn't working properly for you and that's what you need to figure out. Or? You might want to detail that further... Having the Magisk log from when you've tried this stuff, while having the Canary release installed (to get better logs) might shed some light on things.
[Magisk] pndwal:
Right, but you do need two complementary components, Magisk (root) in a boot image (boot or recovery), and App (aka manager), installed.

Not sure you should be getting the additional setup... I believe it's for special setup on some devices (LG, Samsung?) but I'm fuzzy on that, and IIRC I've only ever seen it in my (Xiaomi) device when things weren't working properly... may be a clue re. your issues too.

Have you EVER enabled 'Hide the Magisk app' in settings? If so, you likely still have conflicting instances of Magisk app/manager. And the hidden legacy versions are not removed by 'uninstall Magisk' in app, or uninstall.zip... PW
[Magisk] io2345:
Both components are true: Patched boot.img is installed (wouldn't get Root-authentication pop-up for apps else) and Magisk-App (couldn't toogle MagiskHide-switch if it wouldn't be there).

Don't worry for settings done before. I almost always do a fresh install of the ROM after making changes to it - last time this morning. It is set up now to install with untouched boot.img and without any root solution. I flash canary-patched boot.img in TWRP afterwards and install canary.apk after boot-up.

@Didgeridoohan : Here is a log. Yes, I'm talking about "MagiskHide" (hiding MagiskApp works fine). I threw the MagiskHide-Switch to "on" at 13:23 (as close as I could), left settings page and re-entered a few seconds later. Switch was "off" again.

EDIT: For some reason I don't know I cannot attach the log file. Will show the content in a follow-up thread.
[Magisk] io2345:
The log:

Spoiler content hidden.

The Emoji shown in the text stands for ": o"
[Magisk] unibombz:
Has anyone ever came across this instance which can or would allow magisk to be installed on a MDM work profile?

Thanks,
[Magisk] Didgeridoohan:
@io2345 Could you try starting MagiskHide manually:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Starting_MagiskHide_manually

That might show a message that tells us why it isn't enabled when you flick the switch.
[Magisk] io2345:
Absolutely! The message upon "magiskhide enable" is

Your kernel doesn't support mount namespace

Now we know what's missing. Thank you for your patience!

So we'll have to wait, until @Mik-el get's his own kernel done
[Magisk] Didgeridoohan:
Figured it'd be something like that. If details on that is necessary, there are a couple of links to resources in my guide:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Requirements
[Magisk] alroger:
No no no no. Downloads doesn't install all apks. Don't know about the technicalities but it doesn't. For me it opens ROM Toolbox thinking it's a flashable zip. I use Root Browser to find, click and install apks.
[Magisk] KaMonsieur:
With magisk installed, do I have to do something before installing Android OTA? Or I can just install OTA in the system notification? Thanks.:)
[Magisk] Artim_96:
That's just a very old bug that it doesn't recognize the file format anyways properly, but as I said about 99% of the time it detects it correctly and opens the package installer... At least for me
[Magisk] hamonmaru:
Waiting Magisk update without suhide installed to bypass safety net.

I cant install suhide because my redmi note 2 that still miui android 5.0.

Dont know why xiaomi doesnt give update to android 6.0 for reno2 :(

Dont tell me to buy a new phone with android 6.0 system... :)
[Magisk] Iceyogurt:
Thx. Maybe I get a solution for my problem from the systemless xposed thread. I'll have a try tonight. http://xdaforums.com/showpost.php?p=68991765&postcount=2734
[Magisk] Ninoh-FOX:
If you install magisk v7+ supersu + xposed 86.6 + suhide you has a bootloop, the problem is suhide, install only magisk v7 + supersu systemless + supersu for magisk + xposed 86,6 for a well boot kernel, the only problem is that the bypass work fine, but not work the autetication of the google verification api.

Enviado desde mi E5603 mediante Tapatalk
[Magisk] teddy0209:
Using these steps, you need to disable suhide prior to flashing of xposed for it to properly optimize. Move the suhide file in su.d to somewhere else. Or you could try switching to phh magisk in the manager, disable supersu helper, install xposed then reboot, switch back to supersu after the optimization and you're good to go...
[Magisk] Sillik:
Gonna try that tomorrow. Thanks!
[Magisk] ChokingHazard91:
Both methods did not work on my Note 4. I moved the file to my sdcard, and installing Xposed went fine. After the reboot I placed the file back, changed the permissions to 0700 (as I read elsewhere) and rebooted. But unfortunately I got a bootloop. So I tried it via phh (without and with moving the suhide file) but after I enable Supersu Helper and reboot, I get the same bootloop..
[Magisk] Guitos30:
Can I do this procedure in a custom rom that is pre rooted?
[Magisk] snoprosledneck88:
So I have phh magisk version along with magisk v7. I can't get snapchat to work or android pay. i could really care less about AP but would like to get snapchat working. How do i do this and why doesnt it work. I'm on Pure Nexus 7.0
[Magisk] Rhoban:
You need a special version of phh. It's called phh 266 hidesu

---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------

What procedure?

What exactly are you aiming for?
[Magisk] Guitos30:
I am running Alexis rom in my s6.

Does magisk + suhide work? The rom is pre rooted, so how can I pass safety net and play pkm go?
[Magisk] Rhoban:
Magisk is optional.

But yes, it should work. But you have to completely unroot first.
[Magisk] Guitos30:
Can you tell me how to do it? I dont need xposed and magisk, just to hide root and play the game.

Thanks man
[Magisk] tabp0le:
Root: SuperSU 2.78-SR1-systemless

Magisk: Magisk v7

Hidesu v 0.54

SafetyNet: Pass
[Magisk] Captain_Throwback:
Why would you quote this now? We all know suhide has been updated to circumvent SafetyNet. I even posted as much soon after the last time I posted that (a third time). Now you're just going to confuse people...:rolleyes:
[Magisk] Rhoban:
I told you, you have to unroot first.

Then flash SuperSU in systemless mode and suhide.
[Magisk] tabp0le:
Sorry, I didn't see where you said magisk would work. My bad. :(
[Magisk] Guitos30:
If I do the unroot via SuperSU is that enough?
[Magisk] io2345:
Thank you for pointing to that. Let's wait what Mi-kel thinks about it.

One more question: Installing the 22.0 APK as ZIP (just renamed) from recovery during the ROM installation process probably isn't officially supported I guess? Because this is one more riddle I can't solve: No matter if I do that with untouched or magisk-patched boot.img, it always ends up with "Unsupported/Unknown image format" and doesn't get installed.
[Magisk] Didgeridoohan:
Having the zip installing as a part of the ROM is exactly the same as just flashing the zip by itself in recovery, so it's supported.

The issue you're having on that device is that the installer scripts can't recognise the boot image properly. That could probably use some investigating, probably checking /proc/mounts and stuff like that. Since the boot image can be patched, we know that's not the issue. You need someone like @osm0sis to figure out why the install scripts don't work...
[Magisk] osm0sis:
Log? boot.img dump?
[Magisk] Didgeridoohan:
That was quick... Didn't even have to whisper your name three times in the mirror.

Boot image is here:

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

And this is supposedly the install log:

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

And for good measure there's a Magisk log as well:

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

And some device info:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84689305
[Magisk] Mik-el:
Thank you guys! @Didgeridoohan @edici @pndwal

Yes, actually the Rom is an Android 7 Rom but it runs on an older kernel, 3.4.67 (so KitKat).

The guy who made this kernel before me doesn't want to publish the code for some reason, so I should make a new kernel and apply patches / add backports, that could make "magisk hide" totally working.

I don't have experience in making custom kernels for mediatek devices (it's a mt6592t) so it won't be easy for me.

Anyway we faced a strange "out of space" problem when trying to install apks on some releases of this Rom. Could this bug be connected to the fact that Android 7 tries to install apks in a way that an old kernel that doesn't support the mount namespace?

Anyway this "out of space" bug seems to disapper if I don't patch core-o.jar and services.jar in system/framework (I patched them because I customized the framework-res.apk).