i'm on the latest delta. i see no option to disable 'enforce denylist'. well, i 'removed' dlu and shamiko, rebooted, installed shamiko 0.5.1 afresh. now momo 4.3.1 does not find zygisk. but, init.rc is modified.
I have one of my devices on the delta. I believe there is no option to disable enforce denylist because the delta includes magiskhide and with it the denylist must be enabled. I asked @huskydg this twice to clarify, but he never responded, if I recall he responded with something else.
Turning Magisk hide off acts like disabling enforce.I have one of my devices on the delta. I believe there is no option to disable enforce denylist because the delta includes magiskhide and with it the denylist must be enabled. I asked @huskydg this twice to clarify, but he never responded, if I recall he responded with something else.
I disabled magiskhide in the delta, installed the new shamiko and rebooted and shamiko now shows as working. Onn 8 first gen, Android 9 tablet. The latest momo only reports init.rc modified.
Now reading all these recent posts about Delta, everything is pretty logical
True, but for that one must be somewhat familiar with GitHub, while newbies usually are not, and then they ask how this/how that/where is what, what to click, etc
Just to clarify:
For me (recently I learnt it's 2SI device - whatever it means - ok, 2 Stage Init), nothing changed
Haha ... Suitably cryptic comment about fish prices...
I answered and detailed the hallmarks of each Android boot-type (Legacy Ramdisk, Legacy SAR & 2SI "SAR"):Sorry, I didn't decipher
It's Xiaomi Mi 11 Lite 5G NE, launched with MIUI 12.5, Android 11 - I didn't upgrade to A12, and running stock firmware (only Magisk and custom Recovery)
It's A/B device, with Recovery integrated to Boot, Magisk recognizes as Ramdisk Yes
2SI or not?
Too late to be of help this time, butI am not sure where I am supposed to post this. I have a google pixel 6 pro rooted on android 13.3. I accidentally hit 'reboot to recovery' in magisk and I am stuck in a bootloop. I am able to get into fastboot mode but adb does not recognize my device. Device manager recognizes it as lemobile android device>android bootloader interface. I searched on here, the pixel 6 forum and just google but am not too sure what I should do. I don't know if I have a rogue module but I do not know how to uninstall it since I cannot find a twrp for the pixel 6 pro.
edit: I didn't realize it was 'fastboot devices' instead of 'adb devices'. I downloaded the android 13.3 factory image and am now installing via the 'flash-all' script. Hoping I don't run into any more problems.
Bro, I formatted my data and everything and flashed disable dm verity force encrypt. After patching this file, I wasn't able to patch magisk.zip (I got the same error that I talked about in this thread."Unsupported boot image extra"). So I re-formatted my phone again and flashed magisk.zip only in twrp and it worked. But I want to disable force encryption in my device because I'm not able to access internal storage in twrp. Please I need helpPlease see my last post for further explanation...
so since you seem to have this issue, you still need to do this...
Known issue, but not a regression, so no further fixes will come... (Edit: Except this one: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87068697 )
Basically, Direct install breaks due to previous Magisk injection method for 2SI being incompatible with new Magisk... It's more complicated in configurations where disabling verity/verification to boot is still required, but for most 2SI device users the solution is simply to do initial Patch and fasttboot flash original boot image again, thereby replacing the incompatible fstab-patched image...
Search the threads again. I think, after installing TWRP, you use TWRP to wipe data. And somewhere in there you say "do not encrypt".Bro, I formatted my data and everything and flashed disable dm verity force encrypt. After patching this file, I wasn't able to patch magisk.zip (I got the same error that I talked about in this thread."Unsupported boot image extra"). So I re-formatted my phone again and flashed magisk.zip only in twrp and it worked. But I want to disable force encryption in my device because I'm not able to access internal storage in twrp. Please I need help
I wouldn't source. The script is supposed to be called as an executableHow does PixelFlasher invoke boot_patch.sh?
Does it invoke it as an "executable", creating a new process? Or does it "source" it, so changes to the environment will survive?
Does PixelFlasher create an environment variable named "SHA1"?
My copy of boot_patch.sh has a compound statement that tests whether SHA1 has a non-zero length value before setting it to the sha1 of the boot image. If the environment variable is already set, it will not be overwritten. I don't know why.
#!/system/bin/sh # Boot partition AB=$(getprop ro.boot.slot_suffix) BOOT_PART=/dev/block/bootdevice/by-name/boot"$AB" # Boot and patched boot images DOWNLOAD=/sdcard/Download/ BOOT_IMG="$DOWNLOAD"boot.img PATCHED_BOOT_IMG="$DOWNLOAD"patched-boot.img # Magisk path MAGISK_PATH=/data/adb/magisk/ # Disk-dump boot image to Download folder dd if="$BOOT_PART" of="$BOOT_IMG" # Patch the boot image and move to Download folder "$MAGISK_PATH"boot_patch.sh "$BOOT_IMG" mv "$MAGISK_PATH"new-boot.img "$PATCHED_BOOT_IMG" # Flash the patched boot image dd if="$PATCHED_BOOT_IMG" of="$BOOT_PART" # Reboot reboot
Okay folks, thought I'd post up the procedure:
adb pull /sdcard/Download/magisk_patched_[random_strings].imgworks just fine;
$ heimdall detect Device detected $ heimdall print-pit --no-reboot > print-pit.txt
$ heimdall detect Device detected $
fastboot flash boot /path/to/magisk_patched.imgat the 7th bullet point here
$ heimdall flash --BOOT magisk_patched-25200_UjUVt.img Heimdall v1.4.2 Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au/ This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... Protocol initialisation successful. Beginning session... Some devices may take up to 2 minutes to respond. Please be patient! Session begun. Downloading device's PIT file... PIT file download successful. Uploading BOOT 100% BOOT upload successful Ending session... Rebooting device... Releasing device interface... $
You can do some cleaning like this:I'm using the systemless debloater module to degoogle and debloat a device (and several other magisk modules to assist in that endeavor). I'd really like to be able to do a factory reset to clear the device of any data/artifacts from the debloated apps, but of course a factory reset wipes out magisk modules, so I'm in a catch 22.