yashsingh1/xdaforums huggingface dataset:
[Magisk] osm0sis:
It's a ChromeOS signed boot.img, which should work. The user should post the boot.img and logs from attempted image patch in a Magisk GitHub Issue.

Edit: Actually don't, there must be some sort of user error involved, since Magisk Manager patched it just fine here:

- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5MB) copied, 0.012871 seconds, 118.8MB/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0MB) copied, 0.009088 seconds, 112.4MB/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.zH.BcH.eP7kjgG2V/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [7551376]
RAMDISK_SZ [952106]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2019-11]
PAGESIZE [2048]
NAME []
CMDLINE [androidboot.selinux=permissive buildvariant=userdebug]
CHECKSUM [6fb78fcf264fe5708e66fe03cb13c7684862a637000000000000000000000000]
KERNEL_DTB [7551376]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- ChromeOS boot image detected
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [kernel_dtb]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.zH.BcH.eP7kjgG2V/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [7551376]
RAMDISK_SZ [952106]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2019-11]
PAGESIZE [2048]
NAME []
CMDLINE [androidboot.selinux=permissive buildvariant=userdebug]
CHECKSUM [6fb78fcf264fe5708e66fe03cb13c7684862a637000000000000000000000000]
KERNEL_DTB [7551376]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [7551376]
RAMDISK_SZ [1208570]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2019-11]
PAGESIZE [2048]
NAME []
CMDLINE [androidboot.selinux=permissive buildvariant=userdebug]
CHECKSUM [bc0d2cc6292e0b4733b9c2c04c80b8617d3ac698000000000000000000000000]
- Signing ChromeOS boot image

****************************
Output file is placed in
/storage/emulated/0/.Manager/magisk_patched.img
****************************
- All done!
[Magisk] ktmom:
Have you just patched the boot.img in Magisk manager? Not flash through recovery or install through Magisk manager, but just patch it?

If you can patch without trouble then Fastboot flash it to your tablet.
[Magisk] Markeee:
Patch? There is no option in Magisk manager to patch ?

How do you patch the boot.img in Magisk manager could you please explain ?
[Magisk] ktmom:
Install -> install -> patch a file

Magisk installation

Make sure you are using the correct Magisk manager for the version of Magisk you are using.
[Magisk] Markeee:
Thanks I patched it no problem I have the patched file saved as magisk_patched.img

Little rusty on my fastboot commands do I have to use fastboot can I rename it back to boot.img and just copy it over ?
[Magisk] Wolfcity:
Sry, I quoted another user ( [MENTION=7844570]Crowbro[/MENTION] ) and was answering his question.

I'm not so versed in Pixel stuff but I took a look into the latest stable 20.1 and the magisk manager APK is included. As far as I know this is the case in all magisk.zips.

Edit: Regarding your above question about flashing patched boot image:

https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
[Magisk] ktmom:
On the page I linked, the final bullet point in that section:

You can rename the patched image, or use the command (above) as is. I personally rename the patched image to reflect the Magisk version it's patched with.
[Magisk] Markeee:
I flashed the patched file in Twrp install > image and checked boot and its stuck at google google scream when I flash back to the stock boot its boots fine but still no root ?

Do you know why ?
[Magisk] ktmom:
I didn't look back, but I think you are on a custom ROM. I would do two things.

1st read https://www.didgeridoohan.com/magisk/MagiskHelp and get detailed logs.

2nd post in the ROM thread and see if anyone else is having trouble or offers advice

If you just want to get root and move on, you could try an older release
[Magisk] Crowbro:
I have zuk z1(ham). There's only latest uninstaller available for download. Can I download that and flash it to uninstall? Is there any way to uninstall it from within magisk manager?
[Magisk] Komapatient:
Hi, I am using crDroid 5.8 on Poco F1.

It is rooted and all saftey checks are passed after I worked through the tutorials.

But this app https://play.google.com/store/apps/details?id=de.tk.tkapp

MagiskHide is not working anymore since "TK app" was updated. It says I am rooted and won't start.
[Magisk] andrea0807:
UP!

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] ktmom:
There is no way for anyone to help you without comprehensive logs
[Magisk] Komapatient:
I am sorry, but nothing helped.

I have attached the logs.
[Magisk] ktmom:
"Nothing helped" is not very descriptive.

List every step that you tried but failed to hide root from the app. Following the steps in the linked page, then documenting the step and the result would be ideal. As started in the linked document, don't forget to clear the problem app's data and cache after each change.

And by the way, just gathering generic logs doesn't help, a specific logcat while trying to use the app and failing might.
[Magisk] Wolfcity:
This is the uninstaller for 17.1 :

https://drive.google.com/file/d/1Sc6Rn2XV2l7K3d7WUkvFl4TtU_qh3Bqw/view?usp=sharing

This will uninstall everything, so you have to start from scratch with magisk and it's modules.

Normally almost any magiskuninstaller will work for older builds but it's better to use the one fitting to the magisk version.

Run the uninstaller from TWRP and flash the magisk build you want right afterwards.

Download the magisk manager too and place it in your internal storage just in case it won't be installed after flashing the magisk.zip.

It should but sometimes it doesn't, than install the MM apk as usual.
[Magisk] Crowbro:
I don't have to wipe cache or dalvik during the process, right?

I'll flash uninstaller and then restart my phone to see if magisk has uninstalled and then flash the latest magisk via TWRP? These are correct steps, right?
[Magisk] Wolfcity:
I never wipe caches on newer devices, you can do it but I don't think it's needed.

You don't have to boot your system to check if magisk is uninstalled, it will be.

So there shouldn't be any problem to flash magisk zip right after the uninstaller.

It's up to you. If you prefer it boot to system, check everything and return to TWRP and flash magisk.
[Magisk] Crowbro:
Thanks a lot for helping me out.
[Magisk] watrill:
Is it possible to obtain the boot.img required for patching with Magisk Manager without TWRP?

I have a Sharp S5 (zeon_sprout) -- it's a fairly recent Android One device. There is no TWRP support, but the bootloader is unlocked (via fastboot). The manufacturer doesn't seem to provide factory images.
[Magisk] andrea0807:
I have a problem on my xiaomi mi 8.

Every time I update to the latest weekly release of the rom xiaomi.eu, I also flash magisk canary v20.2-11b7076a from recovery, but magisk does not install!

When I restart I don't have root access.

I always have to go back to recovery, uninstall magisk with the uninstaller and reinstall magisk version 19.5. Only this version is installed.

Then when I restart my smartphone I can update magisk via the magisk manager app. Why is this happening? It's very annoying, every time I lose all installed modules.

Inviato dal mio MI 8 utilizzando Tapatalk

View attachment 4906821
[Magisk] ktmom:
It looks like you are flashing the ROM update and then immediately flashing Magisk. Your device is an A/B slot device though right?

Have you flash the updated ROM, reboot (or switch slots in TWRP) then flash Magisk?
[Magisk] Zander_Sig:
File Explore apps are not getting superuser rights

Hey guys, I'm having a serious issue with the app "X-plore (v 4.18.12)". If I give it root access it kills my phone. All my system apps stop working one by one and I can't do anything until my phone finally restarts on its own.

It's very weird, I've contacted the developer for X-plore and he couldn't help me. He said I was using a weird form of root??

I'm using Magisk Manager version 7.4.0 (253) and the Magisk is at version 20.1 (20100).

Anyone else having this problem?

Well I've now switched to "ES File Explore (version 4.2.1.4)" and it's giving me problems with root also! Ughhh! I grant it root permission and I get two toasts saying that "ES File Explore was granted superuser rights" but after the two toasts disappears I then get another toast from ES File Explore saying "Root acces is not installed, functions not available right now"... WTH?

About 6 months ago I didn't have any problems with either file browser getting superuser right.

Help! /:
[Magisk] Techguy777:
Im curious what logs would I need to get to see why magisk fails. I have a fiio X5iii high res player its on android 5.1.1 we have TWRP 2.8.5 and superSu. I would really much prefer magisk and Ive tried flashing every version from 12-20.1 and none work. Version 19 will at least install without error on repacking boot in TWRP like all the others. Is it because of TWRP to old or what? The developer who made TWRP wont update it and he also built a kernel but its not good matter of fact hes very new. Im not sure what magisk does to the boot img or what the boot img would need to root it with magisk. SuperSu does work its into the system. I know magisk is meant for new version but I do know others have had it work on lollipop. If anyone knows what logs or how to go about resolving the problem id sure like help. Please dont respond with just use supersu or something not helpful. I have gone through the thread.

My pc made the post 4 times sorry I hope this edits it.

---------- Post added at 12:29 AM ---------- Previous post was at 12:26 AM ----------

I dont know whats going on my computer keeps messing it up and it wont edit and delete sorry guys.

---------- Post added at 12:29 AM ---------- Previous post was at 12:29 AM ----------

I dont know whats going on my computer keeps messing it up and it wont edit and delete sorry guys.
[Magisk] ktmom:
They all sounds like malware. You could get a logcat while these issues are happening - I'd do it through ADB on a PC so you can monitor it and save to a file. I would be inclined to do a clean install and be very careful about what apps you reinstall. I also would not restore from a recent backup.

If SuperSu is installed, it needs to be fully removed before attempting to install Magisk.

This document is full of useful information, including how to remove previous root, how to get logs and more.
[Magisk] jcmm11:
I agree with [MENTION=6617276]ktmom[/MENTION]. I would start with a clean install. You can try restoring from backups but be ready to go with another clean install if that gives you issues as well.

I won't say it's definitely malware but something is not right with your system (and malware is one possibility).

X-plore is working fine here.
[Magisk] JazonX:
Patching the Recovery_Ramdisk partition worked to get root access during EMUI 9.1 Days, However since EMUI 10 this is not working.

Stock and Magisk Patched image both are Uploaded here.

Stock Firmware Link - EMUI 10 / Mate 30 Pro

Would anyone be able to have a look what's wrong or missing?
[Magisk] Goncalo29:
Any suggestion? I have tried uninstalling and installing again, but nothing changed.
[Magisk] zputnyq:
It's better if you provide logs & your device's details (magisk's version, android version, rom, kernel, device brand & model etc) if you post.

So far what I can only suggest is this, check it on superuser section of magisk manager. There will be list of apps, if they're swithed off then you can switch them on, I hope this could help.
[Magisk] zgfg:
Can you please share how did you patch magisk_patched.img from RECOVERY_RAMDIS.img, if not by MM, using Install Magisk, Patch (boot) image file with Recovery mode checked in
[Magisk] JazonX:
I used the attached option below in Magisk - Select and Patch File
[Magisk] jcmm11:
Superuser section of the menu. See image.
[Magisk] zgfg:
Ok, as expected.

(That way it worked since Oreo, and even Nougat but using Boot.img)

Nevermind, seems I missunderstood your original post (making me curious if something else is needed for EMUI 10) :)
[Magisk] Goncalo29:
I have it named "root", not "superuser", but it only shows one app, the only one that I got a notification to allow root, I don't know why.
[Magisk] realista87:
hello i would ask u an advice, i have an old phone(lenovo k3 note) with custom rom 7.1 (resurection remix), with magisk 15.3 is it ok to install the LATEST magisk version on a nougat phone? or.. is it useless? i would just understand if the benefits are useful even on an old androidrelease nougat, or it's THE SAME to use an old version of magisk, but time compatible with the release timeof the rom.
[Magisk] Wolfcity:
My advice would be never change a winning team.

As long everything you need is working (modules, hide) you can stay on that version.

15.3 is really old but if it's working for you?

I don't know what features where actual at that time but if you don't miss anything it should be ok.

I'm using the latest stable (20.1) on a 7.1.2 device but also magisk 18.1 on another one running 8.1.

It's up to you.
[Magisk] ktmom:
Try the canary build. Some devices have had trouble with the broadcasts. Fixes were made in the development release.
[Magisk] bark1234:
Anyone able to use magisk on emui 10 yet? i tried to patch recovery_ramdis, it says unable to repack boot image.

"- Device platform: arm64-v8a

- Copying image to cache

1566+0 records in

1566+0 records out

1603584 bytes (1.5 M) copied, 0.005257 s, 291 M/s

1045+1 records in

1045+1 records out

1070668 bytes (1.0 M) copied, 0.004257 s, 240 M/s

Segmentation fault

Segmentation fault

- Unpacking boot image

Segmentation fault

- Checking ramdisk status

- Stock boot image detected

- Backing up stock boot image

Segmentation fault

Segmentation fault

- Patching ramdisk

Segmentation fault

- Repacking boot image

Segmentation fault

! Unable to repack boot image!

! Installation failed"
[Magisk] andrea0807:
The problem occurs equally magisk is not installed.

Then I went into recovery, flashed the ROM xiaomi.eu weekly, then restarted in recovery.

Back in recovery again I flashed magisk v20.2-11b7076a then I restarted the system but magisk is not installed on the smartphone. To install magisk I always have to enter recovery uninstall magisk with the uninstaller and then install version 19.5, only that version is installed and then I have to update from magisk manager.

How can I solve it?View attachment Log.zip

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] Goncalo29:
Did not help, but thank you.
[Magisk] phelite2015:
anyone from Philippines who manage to solve the issue in banking apps? Several banking apps are not working even with Magisk Hide like BDO, RCBC and Citibank... the rest like PNB, BPI, HSBC, etc even there is a prompt that your phone is rooted atleast they are working with Magisk Hide...the other 3 banks mention above is not working, after the prompt it will only force close the app...

Im currently using the latest stable version 20.1 of magisk manager
[Magisk] JazonX:
From EMUI 9 - All Root articles mention using the recovery image instead of boot image.

This is actually a nightmare in one way, because if the recovery gets corrupted - There is no way to get back to the Bootloader mode.

There is no physical volume key on the Mate 30 Pro, so it goes to the bootloader through the recovery mode.
[Magisk] ktmom:
Instead of booting to recovery, boot to system before returning to recovery to flash Magisk. This is one way that will help ensure you are on the active slot before attempting to flash root. Make sure to flash the canary release and save those logs.

---------- Post added at 07:38 ---------- Previous post was at 07:35 ----------

This entire page covers hiding apps and the many ways a simple Magisk hide may be insufficient.
[Magisk] andrea0807:
I finally did it Thanks.

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] phelite2015:
to answer your post my bad i only included in my post the magisk hide.

yes i done it all, magisk hide, hide magisk manager, cts profile and basic integrity both pass(safetynet pass), use magisk prop modules,

now i am trying to use the canary version just to solve this issue...

just what i have said all other banking apps are working except those 3....
[Magisk] ktmom:
And those apps are on internal storage as described in that page? You have disabled all modules as described in that page? You have removed all apps that require root (e.g. Root explorers, TiBu, ect), as described in that page? And whatever else I'm not taking the time to list.
[Magisk] phelite2015:
i dont have sd card since k20 pro premium is already 512gb rom so yes its already in the internal storage...

anyway i will re-read and try to understand again all the list in that page...
[Magisk] Severus_:
after upgrading lineageos's dogo, I cannot see Download and Hide Manager section on magisk manager
[Magisk] jcmm11:
Make sure you have an internet connection
[Magisk] Minkshaman:
Hi,

The Teacher's Mutual Bank app, TMBank, appears to be detecting root after it's latest update.

I've followed the troubleshooting in Magisk Documentation except for uninstalling Magisk.

It gives the error message:

redi2pay

For security reasons this application cannot be run on this device.

---------- Post added at 02:38 AM ---------- Previous post was at 02:38 AM ----------

Hi,

The Teacher's Mutual Bank app, TMBank, appears to be detecting root after it's latest update.

I've followed the troubleshooting in Magisk Documentation except for uninstalling Magisk.

It gives the error message:

redi2pay

For security reasons this application cannot be run on this device.

---------- Post added at 02:40 AM ---------- Previous post was at 02:38 AM ----------

Hi,

The Teacher's Mutual Bank app, TMBank, appears to be detecting root after it's latest update.

I've followed the troubleshooting in Magisk Documentation except for uninstalling Magisk.

It gives the error message:

redi2pay

For security reasons this application cannot be run on this device.
[Magisk] Didgeridoohan:
No issues when testing the app on my device. In other words Magisk can hide itself from that app, but there might be something about your setup that is preventing proper hiding.

Tested on a OnePlus 3T, Android Pie, Magisk Canary debug release 20109 with the accompanying, hidden Manager build 262. All I did was to add the app to the Hide list and it started without the mentioned error message.

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] absinth4:
Hi guys. After i flashed the latest oxygenOs version, my device was unrooted ( as expected) . i then flashed twrp and then magisk (as usual) but during the boot, i am getting a "power off" message and my device goes off. if i get into the twrp again and reflash the 9.0.9 zip the device boots normally but the thing is i cant root my device.. any ideas what is causing it and what can i do about it? any help would be much appreciated!thanks

minor update: i went back to verrsion 17 of magisk (and the supported magisk manager) and everything works fine, but the problem persist withi the newest versions of both.
[Magisk] ktmom:
Did you try the canary build? These types of problems can only be addressed if good logs are provided.
[Magisk] aresbv2000:
Anyone having problems using the inbuilt SuperSU? Sometimes, the root file explorers doesn't ask for root rights, and even if they ask, all root operations fail. I'm using Solid Explorer and Xiaomi MI 9 SE. The only root file manager that works is Root Explorer. I'm on latest Xiaomi.eu ROM(Miui 11, Android Q).
[Magisk] Never_Sm1le:
I have a question. Just bought an old HTC one M8 and installed a rom. When I flash magisk, it fails with "error: boot image already modified by other program" which I read on this forum is caused by SuperSU, so I extract the original boot image but encounter the same result. Looks like the developer pre-patched the boot image with SuperSU as well. Is there any way to use Magisk on this rom?
[Magisk] zgfg:
Not sure if that would work for a boot image with pre-patched supersu, but you can try.

Find (if existing), full unroot option.

Or search for and flash by twrp, unsu.zip
[Magisk] absinth4:
Hi and thanks for the quick reply my friend. No i havent tried it yet. what exactly is the difference of the canary build because im not sure i understand it
[Magisk] Never_Sm1le:
I already tried but all the unsu.zip does is remove supersu. The boot image is still intact and the error persist.
[Magisk] lartomar2002:
How to backdown to 17.1

DELETED: I figured it out.
[Magisk] washwash:
what's the solution if some magisk module brick my phone and i doesn't have a working recovery because doesn't exist at the moment? (the data partition is encrypted i think and don't know what else but it's just useless)

every solution i found need a recovery, any other solution that doesn't involve reset and reflash the entire firmware?
[Magisk] welder73:
Try with Adb command:

adb wait-for-device shell magisk --remove-modules

Turn the phone off

Connect it to laptop/computer

Open cmd

Type the command

Turn the phone on and wait
[Magisk] jcmm11:
What OS version is the ROM? (What ROM?) You might be able to use a boot image from a different ROM (the key word being might)
[Magisk] Never_Sm1le:
S-Rom SL 2.0.1 HTC One M8. And I think I can't do that, because the author stated in Aroma that he did some modification to the boot.img for some sound mod in the rom to work.
[Magisk] ktmom:
Canary is the pre-release, development version that has fixes that don't yet exist in the stable version. It is also a debug version that provides better logs to troubleshoot problems.
[Magisk] J.Michael:
magisk recovery menu obscured

...at least, I think it's the Magisk Recovery menu.

Galaxy Tab A 8" (2019) Android Pie SM-T290

I can get to a menu that is *not* the normal recovery menu, so I assume it's Magisk.

Options menu:

Press volume key to select, and press power key to select

Power off

Restart

Recovery

Fastboot

Back to <illegible>

The last option is obscured by a line of the warning that my bootloader is unlocked.

Is this the Magisk Recovery mode/menu?

What does that "Back to..." line say?

Is there a way from here to boot via Magisk without having to dance on the buttons? (It's hit or miss whether I make it to this menu. I'm not convinced I've ever gotten to Android by way of Magisk: every time I check Magisk Manager, it says Magisk is not installed.)

Is this the right place to suggest that the screen be erased before writing that menu?

And to suggest that "Press volume key to select, and press power key to select" is confusing? (One of those should not say "select".)
[Magisk] ktmom:
It sounds like your device requires installing root into the recovery partition (I.e. System as root, A-only)

I don't think that Magisk actually has a "recovery menu".

From the installation guide, magisk in recovery

In other words, the way to boot to system with Magisk is to use the hardware keys to boot to recovery then release the keys.

To get to recovery, you have to keep holding the volume up button.

It would be important to know what the key combo is for your device to get to recovery. Your device forum should be helpful for this.

In case you haven't seen this, here's the link to the installation instructions for Magisk that applies to system as root, A-only Samsung devices.