yashsingh1/xdaforums huggingface dataset:
[Magisk] troymz1:
I'm trying to uninstall by restoring images so I can take ota. Magisk says stock backup does not exist. Where do I need to put the stock boot.img
[Magisk] jcmm11:
Get the sha1 hash of the stock boot image. Rename the stock boot image:

stock_boot_<sha1 hash>.img

Now gzip the boot image. You can use a -9 compression level. You should end up with:

stock_boot_<sha1 hash>.img.gz

Place it in /data/

root:root

rw- r-- r-- 644
[Magisk] troymz1:
Wow. That gzip stuff is way over my head. I don't know Linux at all. Is there a way to do this all on my phone?

Edit: Could I just do a complete uninstall and a root again by patching the stock boot image hoping magisk will create that file for me?
[Magisk] ktmom:
A complete uninstall (using the Magisk uninstaller) requires the backed up boot.img. Which I think you said doesn't exist.

When rooting originally, either you flashed Magisk in recovery, which would have backed up the stock boot.img, or you used MM to patch the stock boot.img and flashed that manually. When manually patching then flagging the patched image, you should keep the original boot.img to be able to unroot.
[Magisk] troymz1:
Yes I patched the stock boot image with magisk manager. But apparently it didn't save the stock boot image. I have downloaded it on my phone now but don't know how to do what the previous guy said. Pixel 4XL..
[Magisk] ktmom:
Unless the 4 is substantially different than the 3, you should be able to just Fastboot flash the stock boot.img which will return you to being able to take the OTA. Of course at that point, since you're already in Fastboot, it's just easier to Fastboot flash the update, making sure to edit the flashall.bat to remove the -w. Before doing that, make a Magisk patched boot.img extracted from the Fastboot update so you can get root back.

If you really want to take the OTA, Google is your friend. Gzip/gunzip is just a program that archives like zip does. How to change permissions is easily found by Google.

Or, I'll bet all of this is discussed in your device forum. Probably with an easy to follow guide.
[Magisk] xringo:
How do I install this version of magisk?

https://github.com/solohsu/magisk_files

I am trying to get edxposed working https://github.com/Juxstin/EdXposed-SnapChat-Bypass but I believe I need to have the modifed magisk? But how do I flash this on android 10? Since twrp isn't supported. I'm on a pixel 2 xl. I already have the magisk installed via boot image.
[Magisk] martyfender:
Is there any forum for this build and you need help and backups, for sure, unless you have nothing to loose. You need the builds magisk manager installed, set to his custom channel, then you need to patch a stock boot.img with his magisk and then flash it in fastboot. That is about as much as I can gather from the info you provided. I do not have your device, or for that matter, so a thread on how to do this, is what I would look for. I don't believe this is newb territory, but what do I know?

Good luck.
[Magisk] gwenmillett:
Bootloops with miui 11.0.1 on redmi k20 pro. Please fix it
[Magisk] bluerush:
dear topjohnwu:

Hami app has been updated and it couldn't be hidden by magisk.

No matter reinstall Hami or downgrade Hami.

Thank you : )
[Magisk] jcmm11:
It did save it, just not in the location it needs to restore it. Since you can use MM to patch kernels for a different device storing the backup in the normal location could cause problems if you attempt to restore a kernel from a different device.

Look in /data/user_de/0/<package name>/install/ using a rooted file explorer, where <package name> is the name that Magisk Manager is installed under. Assuming you've hidden Magisk Manager you can get the current name from the home screen in MM. See image.

If you haven't hidden it just search on topjohn in /data/user_de/0/

It'll probably still be there. If not just repatch the stock kernel and it'll show up
[Magisk] Bluffer94:
In which location do I have to place the backup to restore it in MM?

Gesendet von meinem Pixel 4 mit Tapatalk
[Magisk] Utini:
Hello everyone, I am trying to update Magisk on my Nexus 6P but always get "There was an error parsing the package" after the downloaded of the update completed.

Any idea whats wrong? :o
[Magisk] martyfender:
Unhide your Magisk Manager and it will usually update then, after which you can rehide it.
[Magisk] clambert11:
I feel like an idiot. All I want to do is add a simple line to my build.prop since I can no longer use an editor. I've looked through the resetprop documentation and searched this thread.

All I want to add is:

net.tethering.noprovisioning=true

It seems like I just need to add the info to a script but I'm not entirely sure where to put it.

Can someone please point me in the right direction?
[Magisk] Didgeridoohan:
Put this in a file (name it whatever you want):

resetprop net.tethering.noprovisioning true

Place the file in /data/adb/service.d, give it execution permission, reboot and you're done. If that doesn't work, move the file to /data/adb/post-fs-data.d instead.

Edit: note that nothing will actually be added to build.prop. The new value will simply be loaded to memory and you can check if it works with the getprop command.
[Magisk] jcmm11:
Just place it in /data/
[Magisk] matif525:
My M7(U) is not dual sim version, and Magisk v6 works well in stock Android 5.0.2, Sense 6, firmware 7.18.
[Magisk] Cavaler:
I'm trying to install Magisk on Xiaomi Redmi Note 3 Pro with MIUI8. Unsuccessfully.

I won't describe all the debugging, but, long story short, the problem is that there is no make_ext4fs available in my ROM, so it is unable to create magisk.img

Can anyone provide me a link to ARM binaries of make_ext4fs and libext4_utils.so ?

And frankly speaking I thing magisk should include them in the package along with busybox and bootimg* tools.
[Magisk] IzaacJ:
The assumption about by-num is correct, by-name is not anywhere to be found. Been looking through /dev/block with the terminal in twpr and found mmcblk0boot0, which I think is the UBOOT (lk.bin) and mmcblk0boot1, which I think is the BOOTIMG, due to the UBOOT being the partition before the BOOTIMG partition in the scatterfile.

Agree on the possibility to chose a boot.img to patch if find_boot_image fails.
[Magisk] KaMyKaSii:
mmcblk0boot0 is preloader, you will see if open a backup of him with a hex editor. mmcblk0boot1 i think it's the low-level download partition if the preloader is corrupt (flash wrong file or something)

If you read my post below, you will see how to find the real name of by-num system. If it is available in recovery, [MENTION=4470081]topjohnwu[/MENTION] could also add a command to check the boot partition there

http://xdaforums.com/general/paid-software/flashfire-t3075433/post66143356
[Magisk] IzaacJ:
/proc/dumchar_info outputs this:

Part_Name Size StartAddr Type MapTo Region
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd BOOT_1
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 USER
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 USER
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 USER
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 USER
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 USER
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 USER
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 USER
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 USER
[B]bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0 USER[/B]
recovery 0x0000000001000000 0x0000000002d80000 2 /dev/block/mmcblk0 USER
sec_ro 0x0000000000600000 0x0000000003d80000 2 /dev/block/mmcblk0p4 USER
misc 0x0000000000080000 0x0000000004380000 2 /dev/block/mmcblk0 USER
logo 0x0000000000300000 0x0000000004400000 2 /dev/block/mmcblk0 USER
expdb 0x0000000000a00000 0x0000000004700000 2 /dev/block/mmcblk0 USER
tee1 0x0000000000500000 0x0000000005100000 2 /dev/block/mmcblk0 USER
tee2 0x0000000000500000 0x0000000005600000 2 /dev/block/mmcblk0 USER
kb 0x0000000000100000 0x0000000005b00000 2 /dev/block/mmcblk0 USER
dkb 0x0000000000100000 0x0000000005c00000 2 /dev/block/mmcblk0 USER
frp 0x0000000000100000 0x0000000005d00000 2 /dev/block/mmcblk0 USER
android 0x0000000076c00000 0x0000000005e00000 2 /dev/block/mmcblk0p5 USER
cache 0x0000000010000000 0x000000007ca00000 2 /dev/block/mmcblk0p6 USER
usrdata 0x0000000144100000 0x000000008ca00000 2 /dev/block/mmcblk0p7 USER
bmtpool 0x0000000001500000 0x00000000ffff0000 2 /dev/block/mmcblk0 USER
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
[Magisk] mathy007:
I checked my dev/block and I can only find by-num no by-name found is that why am getting error unable to detect boot image when trying to flash magisk? am using HTC one M7 dual sim running lollipop 5.0 2
[Magisk] IzaacJ:
That is probably the case. The script uses /dev/block/by-name/, /dev/block/platform/*/by-name/ and /dev/block/platform/*/*/by-name/ to find the boot image.

You'll probably have to wait for either a by-num or a manual patch solution, just like me.
[Magisk] mathy007:
Is it something I can do? or we have to wait for [MENTION=4470081]topjohnwu[/MENTION] to fix it
[Magisk] IzaacJ:
We will have to wait for him. Unless someone comes up with a way to mod the current version of Magisk to do it. I'm too unfamiliar with these kind of scripts to do anything myself.
[Magisk] mathy007:
Thanks for your response really appreciate it
[Magisk] QWEnter:
Read this post http://xdaforums.com/showpost.php?p=68884579&postcount=3543

Thanx to toshi127k, there is a solution to install Magisk v6 on Z1 Compact with the latest stock firmware (14.6.A.1.236).
[Magisk] KaMyKaSii:
bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0 USER

Partition name: boot (obviously)

Block device: /dev/block/mmcblk0 (your entire emmc device)

Start of partition: 0x1d80000 or 30932992 bytes (29,5MB)

Size: 0x1000000 or 16777216 bytes (16MB)

After discovering all these informations with some command (Maybe grep?) the Magisk Installer should do the backup wich in your case would be:

dd if=/dev/block/mmcblk0 of=/cache/boot.img bs=1024 count=16384 skip=30208

Do the patch and install the modified image

dd if=/cache/boot.img of=/dev/block/mmcblk0 bs=1024 count=16384 skip=30208

As my device has explicitly separate partitions each other, I never had to use these additional parameters in dd (actually always used "cat inputpartition > outputfile" what you really should not do because will corrupt your memory). That said, and as I am not a developer and not very knowledgeable of the subject, it would be good if you to test the first backup command in a terminal with super user permission and see if the backup works perfectly. The generated file seen by a hex editor should get more or less like the picture (in your case I think is mtk header instead of ANDROID!)
[Magisk] ggfdbbv:
Is it working on Redmi 3S?
[Magisk] -leo-:
"Moto devices generally: I suspect it is something to do with dtb image not unpackable"

I happened to boot with all 3 current mods enabled, but magisk manager cant toggle lol

I'm on AICP custom rom (seems CM13 based), and with latest xposed/phh/viper flashed till 29-Sept

[MENTION=4470081]topjohnwu[/MENTION] Is it possible to get a workaround? And thanks for the supernatural project

Will help debuging if needed (do not know any android knowledge except flashing zips and a good brain, XD)

EDIT: Using XPOSED 86.5+phh cant unmount and SuperSU+ xposed 86.2+suhide does prompted unmounted

but in material xposed it says active, so does SuperSU (Still prompts su calls), because no Pokemon GO latest, haha

Thanks
[Magisk] misteurz:
No, it is officially unlocked by lg

Envoyé de mon LG-H850 en utilisant Tapatalk
[Magisk] droid_1989:
So I have this installed, and i'm using AdAway by f-droid, if I apply the adblock, and turn root off, will it still block ads?
[Magisk] Rayman96:
Unfortunately, no.

But I have few tips:

Install drivers for your device

Download "Minimal ADB and Fastboot"

Then open CMD Line and enter commands when your phone is connected.

Paste output somewhere and link it here.
[Magisk] Devilix:
Does exist a good soul with CM13 that has remove completely native su binary?

I have try everything! I'm not figured out what i'm wrong or if i missing something...
[Magisk] Azuritko:
I am confused. #3302 said to first flash magisk, then flash boot.img

#3543 said to first flasth boot.img then magisk. And also I do not know what to do before and after theesee two steps.
[Magisk] Utini:
Nope that didn't fix it. Also tried rebooting after unhide.

Edit:

Seems like Bitdefender prevented the unhide and also the hiding (renaming of the package). Without bitdefender it updated just fine.

Edit2:

Hiding (renaming) the manager still fails even without bitdefender installed.
[Magisk] chisnz:
Feature request (Magisk Manager): Ability to "Select All" to hide.

To hide from all apps I don't know or want to expose to root, I'd like use Magisk Hide as a white list - hiding every app except those I turn off.
[Magisk] RandomPooka:
It's repeatedly been explained why this is a bad idea.
[Magisk] ashyx:
Why? Most apps don't even request nor are aware of root, so it's a pointless thing to do and has the likely hood of destabilising the system.

Cue the raft of posts blaming Magisk for problems.
[Magisk] martyfender:
That is insane.
[Magisk] Lownita:
There's a bug with Magisk manager 7.4.0 (253) (3), as it opens the manager app as soon as an app asks for root access. This happens one time until another reboot. Happens on Android 9 and 10.
[Magisk] Hateware:
Same here, glad I'm not the only one.

OnePlus 7, OOS 10 Beta 4.
[Magisk] :
+1 the same for me

OnePlus 3 with LineageOS 16 (Android 9)
[Magisk] swieder711:
I am on a Pixel 3 XL with the November image. Got stuck on the "G logo" screen when trying to install EdXposed without the patched Magisk. Was able to get back up by reflashing the original boot.img file, but now I lost root.

I tried "adb wait-for-device shell magisk --remove-modules" which didnt seem to work, but maybe I did not wait long enough. How long does this command take to complete?

Are there other ways to uninstall Magisk on Android 10 without TWRP and Root?
[Magisk] ktmom:
You could boot in Magisk core only mode
[Magisk] RuKaDa:
Hello Magiskers,

I wonder if someone could give me a little help. I have an installed app that "requires" non rooted device, so with the help of Magisk hide i was able to use that app until Magisk v19.2, since this build, despite i have selected to hide root the app doesn´t work anymore. I didn´t mess with any other Magisk settings, just installed 19.2, hide root for that app and voilá.

With 19.3 and all the above Magisk versions it seems that the app can find that i have root, am i doing something wrong? There´s any other Magisk option that I should mess with to get it work again.

Thanks for your help.
[Magisk] ktmom:
From just a couple pages back:
[Magisk] RuKaDa:
Thanks for your help, really appreciate it. It´s working now, I guess I missed the Magisk Hide Toogle under general settings, after turn it off and on a few times the app is now working.

Sorry I missed that option but like I´ve said before, with 19.2 Magisk Hide is working right after install it, with newer versions I have to re-enable it through the general settings, checked in the Magisk logs and it show the apps and the service starting.

Thank you. :highfive:
[Magisk] Johnn78:
From the new version (Magisk 20.1), I can't unistall system apps via System app remover Pro (although I give root privileges to the app) while if I return to 19.3 then I could. Why ?
[Magisk] Didgeridoohan:
That's intended behaviour. Details:

https://didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
[Magisk] hackermssharma:
Everything was going smooth but today i Updated to the lattest magisk as well as manager and then i get to know that basic intigrity as well as cts profile both are not passing so now i am not able to use gpay app. I have edexposed miui 11 .eu rom.
[Magisk] danielqf45:
Help pplz

So I'm using oneplus 7 pro android 10 previously with magisk and twrp. I installed a bad module on it and the phone failed to boot so I flashed stock boot image, it got back fine and then I flashed the magisk patched boot image of the same

version of magisk I used before, and the boot loop came back. the rooting process of this phone requires me to flash a patched boot image because of there isn't official twrp support.

I know this boot loop happens because magisk backs up the modified boot image and when you reinstall boot images from stock to magisk patched it uses the backed up image, a corrupted image.

so I need to get rid of that image without root permission. if anyone has any ideas please I would appreciate your help

I can still use my phone as stock but I need to get it back to root.
[Magisk] Didgeridoohan:
The reason why the bootloop returns when you flash a Magisk patched boot image again is that the "bad" module is still installed. Modules are in /data/adb/modules and won't be touched by just flashing a stock boot image.

Take a look here for some solutions:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
[Magisk] Didgeridoohan:
How about the good old "have you tried turning it off and on again"? MagiskHide that is...
[Magisk] bmg1001:
Same thing just started happening to me today, both CTS and basicIntegrity failing. Gonna poke around and see if anything fixes it. I'm on a OP7 Pro with OOS though.
[Magisk] hackermssharma:
I caught the culprit by disabling ed exposed ( riru core and riru exposed) in magisk and then turning off and on the magisk hide cts and basic integrity both get passed. But i wander how suddenly the ed exposed starts braking the sarty net ???
[Magisk] bmg1001:
Yep, seems like EdExposed is now tripping SafetyNet for me too. Oh well.
[Magisk] hackermssharma:
I also tried the older versions of riru core but it also does not work i think googel updated something and catching that ed exposed is hooking into the system. ☹️
[Magisk] euclanville:
I can confirm the edxposed module is trip the safety net.

Leaving the riru module enabled and the edxposed disabled will pass safety net.

Do we have a separate for edxposed xda forum?

Edit:

The edxposed and riru module on magisk will be fine passing the safety net. But once you enabled any module on the Xposed manager that's the safety net begin to failed. Means Xposed no use at all.
[Magisk] kitsune_snake:
to add to the masses,

Edxposed is also tripping safety net on my end, Worked fine at about 2 am local and no longer the case as of this morning.

Redmi k20 Pro, miui 11 EU, magisk 20.1
[Magisk] Johnn78:
All this is NOT happening due to Pie but due to Migisk 20.1 ? They decided to release some new version which will be wors than previous because is not explained to release some new version with limitations in system files when with previous version you could.
[Magisk] Didgeridoohan:
It's a combination of Pie and Magisk v20+ (@topjohnwu is just implementing the same thing that Google does). You should still be able to edit /system on Pie, you'll just have to mount / rw rather than /system. And it's up to the app developers to update their apps to work with Android Pie+ SAR.

Edit: And what do you mean "not explained"? It's clearly explained in the Magisk v20.0 release notes.
[Magisk] Johnn78:
How to mount my system as rw ? I tried some commands from terminal like "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system", "mount -o rw,remount /system/" & "busybox mount -o rw,remount system" but all commands have the same error : "can't find /system in /proc/mounts".
[Magisk] clambert11:
Worked like a charm. I pretty much did understand everything right except for setting the permissions, which somehow I missed in the other posts I read. Thanks for the help. ??
[Magisk] ahmadpower:
Hello,

I need urgent help,

Now whenever I install a new app which needs superuser and root, the Magisk manager automatically denies the super user rights...

I Certainly made the option to Prompt, but no prompts appears at all, and even when I made it to automatically grant superuser rights, it also automatically denies the superuser rights....

Sometimes some apps grant the super user rights after some time, but other apps Never grant superuser access whatever I do...

Any fast help please
[Magisk] ktmom:
Did you read the post and link that was provided to you?

Either mount /

Or use an older Magisk

---------- Post added at 17:49 ---------- Previous post was at 17:39 ----------

From the last several days:
[Magisk] hfam:
[MENTION=4667597]Didgeridoohan[/MENTION] (or anyone who knows the answer),

About a week ago you'd answered a question for someone wanting to host their own json and files for the custom link. You replied to them indicating "why make it so hard" because the json links were still on tjw's GitHub, and you even provided a link to 19.3 there.

I tried to go to the Magisk github to get to those files and I feel like a fool, I absolutely cannot figure out how you got there, or got to installable json files for the various previous versions of Magisk.

My motivation is, right now 20 seems to work fine for my needs. 20.1 seems to have some issues, and my MM is indicating an update to 20.1 is available. I want to apply the Nov sec patch (I do this via adb and full system image, -w), and then reinstall v20 without going to 20.1. I'd like to make a custom link for v20 that I can use to tell my current installation it's "up to date" instead of needing an update, and then proceed to patch boot.img with v20.

Can you, or someone, please explain how to get to these json files on tjw's GitHub so I can use them as a safety precaution and install a previous version of Magisk and MM?

Sorry, I feel stupid but I just couldn't figure it out and would be grateful for an assist.
[Magisk] Didgeridoohan:
[MENTION=2843606]hfam[/MENTION] Don't worry about it. Even though it isn't very hard to get the file history, it isn't that intuitive...

You go to the file you want the history for (in this case stable.json in the magisk_files repository). Click the "History" button and pick the commit that corresponds to the version you want. Open the commit, find the part corresponding to the file you want and open it (by just clicking it's name). Lastly open it in raw format (the "Raw" button) and you have the link you want.
[Magisk] pedro1977:
20.1

- [General] Move acct to prevent daemon being killed

Is this a fix for the not installed error that would occur after a few days usage and resolve itself after a reboot??
[Magisk] mrbonine:
Thank You

Excellent advice, did so with no change to the volume until I disabled the last one, I think Libsecure_storage companion, so it may have been BusyBox for Android NDK. At the last reboot I got flashing "Android Starting...." which looked like a bootloop. I did force off again reboot and after a bit of panic booted into recovery an had an August 2019 backup. I restored that, then had to update Magisk, and figure out delta from current but backup saved the day.

I was surprised that I was able to get to that state so easily, but no harm done. I've tried to test the "ear speaker" and think it's likely blown/failed hardware. Having caused another hardware failure (nice impact crack midscreen right edge) I'll look into repair pricing.

Thank you, again!