Yes I did, but I'll give the one you uploaded a try. I'm also going to try disabling zygisk before updating and maybe that will help but idk, I'm fine with staying on the November build tbh if I have to, it works great
General [Tutorial] [Magisk] Enabling 32-bit Support For Apps
- Thread starter Namelesswonder
- Start date
Mind you, the patched boot file I shared is for the January build. I do recommend updating to either December or January for the memory optimization improvements Google made.
November has been the best yet. Battery life was amazing. December and January are good. November was amazing.
I didn't see this spelled out explicitly anywhere but this lets you buy and download 32-bit apps from the Play Store as well where Google allows that (so for 32-bit apps you already bought in the past, and for ones that are compiled with APIs old enough that they didn't get removed from Play Store visibility on 64-bit devices in July of last year for being 32-bit only). I think this means you should actually be able to buy 32-bit apps on the Playstoire using an AVD image as long as you're using one of the 32-bit only Play API images and then download them on a Pixel 7 Pro.
ETA - Which is pretty handy because the AVD compatibility is still meh.
ETA - Which is pretty handy because the AVD compatibility is still meh.
I seem to be experiencing issues with Play Services and Play Store crashing when I try and use Shamiko / Universal Safety Net fix with this (using your patched Magisk Delta). Are either or both of these incompatible with Magisk Delta and if not I guess I'm configuring them wrong ? Could you let me know how to set them up correctly.
Edit - It's Shamiko that's causing the Google Play Services / Store crash
Edit - It's Shamiko that's causing the Google Play Services / Store crash
Last edited:
I used the Custom Magisk Delta by OP, so I followed the updating steps for Custom Magisk Delta build
I did the same thing and kept getting crashes so I will just stay on the November build
I don't know then, I suppose you have installed and set up the Custom Magisk Delta correctly?
I'm not restoring stock init_boot because then I'll lose the ability to use 32bit apps. I'm just going to stay on November it works fine for me
I'm trying to backup my persist.img, but running the script leads to this:
cheetah:/ # sh backup-persist.sh
sh: backup-persist.sh: No such file or directory
Any help?
Edit: Nevermind found a fix roaming some subreddits, ran the command:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
and it got me the persist.img.
cheetah:/ # sh backup-persist.sh
sh: backup-persist.sh: No such file or directory
Any help?
Edit: Nevermind found a fix roaming some subreddits, ran the command:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
and it got me the persist.img.
Last edited:
Namelesswonder are you going to continue using Magisk Delta as the base or are you still moving to regular Magisk. Also is there any way to self update to the new canary 25206, Base Magisk Delta has been updated to it so I'm just wondering if or when you will update, or if there is a way we can do it our selves.
Same question although he did upload the diff to GitHub so all we really need is someone with the knowledge to edit and update it for future builds
Last edited:
The procedure for Namelesswonder's Magisk Delta custom patch in the OP worked for me ~3 weeks ago. I have a 32 bit app for an auto-sync'ing distributed file system I put together in 2015 that I'm not ready to upgrade.
- I was on the Nov. update with minimal setup since getting my P7P
- I did not have any problems backing up the persist partition
- I paused between steps 8 & 9 and installed the Jan. full factory image
- Once complete, I flashed modules safetynet-fix-v2.3.1-MOD_2.1 by kdrag0n/Displax & MagiskHidePropsConf-v6.1.2 by Didgeridoohan
- I'm passing SafetyNet and "Device is certified."
- My 32 bit app installed fine. I see I unknowingly side-loaded another 32 bit app too.
I was unable to update to December from November with the 32bit magisk delta patch for some reason. Did you differ from the steps to upgrade at all?
I keep a diary for efforts like this to save time when I need to repeat one. Reviewing, I really didn't do anything different from the OP procedure. However, there was one. I doubt it made a difference. Where I paused between steps 8 & 9 to install the Jan. image, I kept data by editing out "-w" in the script. That logically shouldn't make any difference.
The state my P7P was in: New from Fi in late Nov. Initially updated to the Nov. full image, factory kernel, Magisk stable 25.2 and minimal setup.
My diary: (I referred to HomeBoy76's Guide)
- Downloaded the Jan full factory image and extracted the zips accordingly
- Copied init_boot.img, Magisk Delta custom modified APK & backup-persist.sh files to the phone
- Installed the modified Magisk Delta APK.
- Patched init_boot.img in modified Magisk Delta (edit: be careful not to use stock Magisk)
- Copied the patched boot image file to the Platform Tools folder on PC
- Installed a terminal emulator (Termux for me)
- Opened a SU prompt & ran the backup-persist.sh script (edit: script @ /storage/emulated/0 if you copied to "Home" above so, "cd /storage/emulated/0" then "sh backup-persist.sh" since trouble reported here before)
- Copied resulting presist.img off the phone for safekeeping.
- At this point I flashed the Jan update using HomeBoy76's Guide keeping data
- I rebooted the phone and let the Jan update complete
- Once updated, I shutdown & booted into the bootloader
- On the PC, I reflashed & wiped data: "fastboot --skip-reboot -w update image-cheetah-????.xxxx.xx.zip"
- When finished, I rebooted the bootloader: "fastboot reboot bootloader"
- Then I flashed the Magisk patched boot image: "fastboot flash init_boot magisk_patched-xxxxx_xxxxxx.img"
- Rebooted the phone and allowed the install to complete
- Installed the custom Magisk Delta APK
- I setup Magisk
- Flashed Magisk modules safetynet-fix-v2.3.1-MOD_2.1 by kdrag0n/Displax & MagiskHidePropsConf-v6.1.2 by Didgeridoohan (it took ~12 hrs for "device certified" to appear)
Now I also can see accidentally patching the boot image in stock Magisk could be a tripping point. I have reloaded all my apps and fully setup my P7P. Setup from scratch BTW. Two 32 bit apps too. No problems for ~3 weeks but, it's not my primary phone yet. I can make it my primary in another week, or so, and I'll report if anything changes.
You shouldn't have to wipe between updates, as it would become very tedious to set everything back up every month.
The directions should work, and November to December is what I did test with my custom Magisk Delta.
I assume something was done incorrectly on your end.
And you won't lose the ability to use 32-bit apps if you remove the custom Magisk. I did it several times while testing and it would still function after restoring it. The thing that is important is Android needs to setup the libraries, but it can only setup the 32bit libraries on first boot so a wipe is required. Once they are setup they are fine, you can boot the stock kernel and the libraries will still be there. I didn't perform any testing on custom Magisk -> update, don't run custom Magisk, boot stock -> later install custom Magisk; but it is possible it is fine, however I don't endorse doing that.
So just to clarify you're saying that I won't lose the ability to run the custom 32bit magisk even if I installed stock magisk (after updating) as long as I had run the custom 32bit magisk beforehand on a previous update? I don't want to mess up and have to wipe the device and start over so I apologize for all the questions
I haven't tested performing installing an update and booting stock (as if someone forgot to flash the patched init_boot), but it may work. I would recommend holding off on it as I'm doing some testing right now and I will be testing that scenario soon, as I am currently testing a newer version of Magisk Delta with the patch along with Magisk with the patch and I am still on the December update and need to move to the January update soon.
Top Liked Posts
-
There are no posts matching your filters.
-
2
Update News
Magisk 32-bit b27e4930-32bit (25210)
An hour after I pushed out the last update the navigational issues in the app were resolved. This version is based off of fe6b658c.
There's no changes outside of the app, so updating the Magisk in the init_boot is not necessary, although because of the version change the app will give the option to.
Magisk 32-bit b8989a16-32bit (25210)
New version is up that is based off of 1a164679.
It aligns with canary 25210, however includes the latest commits that have fixed Magisk on Android 14 Developer Preview 2.
I tested it and it works on A14 DP2, however that was with a dirty flash update from DP1. I don't know if it is functional after a clean flash.
Known issue is that the patching/flashing log window can't be backed out of in the app, just close and reopen it if you need to do something else in Magisk before rebooting.2
Great news, I was able to get a replacement (not from google but the 3rd party I bought it from since I am in an unsupported country) after almost 6+ hours on phone arguing over it. I was able to get the GE2AE Model too so I get mmwave + sub 6ghz so everything is great, it should arrive tomorrow.
From what I know if anyone else bricks their phone through the bug of r34.0.0 it should be fully under warranty, since most 3rd party's are providing support and so is first party google. Funny part is that after I warranty'd they updated their policies to add if "You have used a computer to flash, update, or modify the software on the phone it voids the warranty"1
It depends on what you mean by bricked.
It means has different meaning to different people.
If you can get into bootloader mode, then it's not bricked and should be recoverable by flashing stock image with proper Android platform tools.
A true bricked is when the phone does not respond to anything, it can't get into bootloader or recovery mode.
Bootloop is not a brick.11
Technically yes, since there will be another process running, but in practice it should be negligible. For the most part less than 0.1% of the battery usage in a 100% to 0% run on battery could be attributed to the 32-bit zygote process. The 32-bit zygote process does nothing, and simply holds a small amount of memory to be used for starting 32-bit apps. Really it uses less battery than the 64-bit zygote process, since that has every single app on the phone that is 64-bit being forked off of it (the only non-64-bit apps on your phone are going to be 32-bit apps you sideload), and it has to keep a larger JVM on standby.
My phone has had an uptime of 8 days and the total CPU time used by the processes are 28 seconds for zygote64 and 12 seconds for zygote.
You can check how much CPU time and other things are being used by the zygote processes with this command as root.
ps -p $(pgrep -f '^zygote') -o 'PID,NAME,BIT,%CPU,TIME+,SHR,RES,%MEM'
However, CPU time is fundamentally flawed because the frequency could be anything while the task is being executed, so the following command as root will print the time the process spent at that frequency for that node of CPUs in 10-millisecond units.
for PID in $(pgrep -f '^zygote'); do echo "$(cat /proc/$PID/cmdline):"; cat /proc/$PID/time_in_state; echo; done
For me on my phone after 8 days, and using the longest time spent at a frequency that isn't a low power frequency, zygote64 has held the A55s at 1.8GHz for 4 seconds, the A78s at 2.3GHz for 2.2 seconds, and the X1s at 2.85GHz for 0.78 seconds. For the 32-bit zygote process it has held the A55s at 1.2GHz for 1.1 seconds, the A78s at 1.5GHz for 0.2 seconds, and the X1s at 2.85GHz for 0.8 seconds
That cumulative amount of time spanning over 8 days is practically nothing, when in comparison the screen will burn more energy when at high brightness in one second.
The only concern is going to be installing old 32-bit apps that could act up and consume resources in the background.
It could be a problem with RiceDroid and my Delta fork being somewhat outdated now, but I can't point to anything without logs.
I would recommend just running my regular Magisk fork.
At some point this weekend I might look into building a newer version of Delta, somewhat inconveniently Delta switched to doing only source archive releases. -
26
The 32-bit apps are back!
Synopsis
The Pixel 7 line is Google's first "64-bit only" phones, along with being the highest profile release of a 64-bit only device so far. The device uses the Tensor G2 (GS201), which is a close descendant of the Tensor (GS101) from the Pixel 6 line. So close, that the only major change was swapping out the ARM Cortex-A76 cores for ARM Cortex-A78 cores. The SoC still has full 32-bit support.
This was seemingly done at the last minute to get the ball rolling on switching Android to becoming 64-bit only at some point in the future. That future might be soon for other currently supported Pixel phones as the Android 13 QPR1 Beta includes optional firmware images that are 64-bit only. Given that it is currently optional on QPR1, there is a chance that at the earliest Android 14 will be 64-bit only across all supported Pixels, with a slimmer chance that it will be 64-bit only for AOSP also.
The three items that are of importance are AArch32, what Zygote services are set to start, and whether the build supports multilib.
AArch32Is a mode starting with ARMv8 that provides support for the 32-bit ARM ABIs: armeabi and armeabi-v7a. An ABI is what defines how software is to be built and ran for specific instruction sets.AArch32 is not required to be supported with ARMv9-A architectures, which would be processors starting with ARM Cortex-X2/X3/A715. These processors support AArch64 only.The ARM Cortex-A510 is currently the only ARMv9-A processor that supports AArch32. This combination of processors (X2/X3/A715 with A510) results in asymmetric 32-bit support. This is the likely reason for Google expediting these changes. It is speculated that the Cortex-A520 will not support AArch32, which would put a stop to native 32-bit support completely for future devices.Tensor G2 cores are still on ARMv8-A and thus still support AArch32.ZygoteIs a service that handles creating VMs for starting applications, and is responsible for allowing resources to be shared to reduce memory bloat from duplication. There are two Zygote services, Zygote64 and Zygote (colloquially referred to as Zygote32). Each handle a "warm" VM that is preloaded with libraries, which gets cloned for starting an application. This is done via copy-on-write, which means a copy is only made and occupies memory when attempting to modify a resource. The untouched copies all point back to the original, saving memory.Without Zygote32, 32-bit applications can't be started. Without Zygote64, 64-bit applications can't be started.Having multiple Zygote processes is referred to as "Zygote64_32"MultilibIs a scheme that allows for 32-bit and 64-bit libraries to reside on the same device. This is required to support running 32-bit applications on 64-bit devices. Android has it's own implementation that differs from most Linux distributions, which may also differ between each other.Obviously, without 32-bit libraries (or inversely without 64-bit libraries), a build does not support multilib.Somewhat important to note is that the 64-bit only QPR1 Beta images for the Pixel 4a to 6 are true 64-bit only, they do not support multilib. However, as noted here by Google, the Pixel 7 is 64-bit only but does support multilib.
The support matrix is as follows:
Phone + SoC, BuildSoC AArch32 SupportZygote PropertyMultilib32-bit Support?Pixel 6 with TensorYesZygote64_32YesNativePixel 6 with Tensor, 64-bit Only BuildYesZygote64NoNot Possible*Pixel 7 with Tensor G2YesZygote64YesWith ModificationPixel 7 with Tensor G2, 64-bit Only Build**YesZygote64NoNot Possible*Phone with AArch64-only ARMv9-ANoZygote64NoNot Possible**** If no multilib build is also available. It may be possible with extensive work to use Treble to bring 32-bit libraries forward, assuming Android 14+ doesn't remove AArch32 and Zygote32. Emulation could be a possibility but has not been done yet.** Build does not exist yet. It may be realized with Android 13 QPR2/3 or it may be done with Android 14 instead.*** Emulation could be a possibility but has not been done yet. Currently just the Pixel 6 and 7 have KVM built-in, but the Pixel 7 is the only one with it on by default. There is no graphics layer yet.
This means that with the right changes 32-bit support can be enabled and used if 32-bit libraries are on the device and the SoC supports AArch32.
Modifications
The changes required are as follows:
ro.zygote=zygote64_32ro.vendor.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabiro.vendor.product.cpu.abilist32=armeabi-v7a,armeabiGenuinely that simple, property changes. Because the libraries are already in the firmware images it is just the need to instruct Android to use them.
Zygote64_32 refers to starting Zygote64 as the primary process, then starting Zygote32 as the secondary process. With this in place 32-bit applications can be installed and ran as 32-bit libraries are now able to be loaded.
The changes that need to be done are to either be applied to/vendor/build.prop, or done withinit.rcmodifications, or applied in some way beforeinit.rcis read.
The last point is the critical issue that has halted this: there has not been any easy way to set properties very early in the boot process outside of simply just modifying the file on the partition.
This can't be done easily due to dynamic partitions requiring a custom super partition, and with the larger issue being AVB.
However two solutions have been brought forward:
The first solution is thanks to ThomasKing2014, he has created Pixel 7 32-bit helper which is a modified Magisk that changes
The patch he has created has been the start for this. The patch gets applied to Magisk and modifiesmagiskinitto modify/vendor/build.propearly in bootmagiskinitso that during boot Magisk will modify/vendor/build.propwith the values for the properties needed.magiskinitcontinues with initialization, hands off to the stockinitwhich then readsro.zygoteto determine what Zygote rc file to load.
Then Zygote64 and Zygote32 are started.
The second solution is thanks to @huskydg for Magisk Delta which is a Magisk fork that implements many additional features
Currently I have repositories set up with rebased patches and modified versions of Magisk and Magisk Delta using the patch.
Forewarning
Currently, a wipe is required to get the modification to work fully.
I do not know exactly why, but when a device is first booted with only Zygote64 it can't be switched over to use Zygote64_32. For some reason the 32-bit libraries inside APEXs are not discovered and loaded by Zygote32.
It's a strange thing. If first boot is with Zygote64, then immediately rebooting to use Zygote64_32 will appear to work, but things are subtly broken in the background as only a few libraries don't have their 32-bit counterparts loaded. This gets exacerbated with preexisting systems, where lots of libraries have been used and their 32-bit counterparts are never discovered when switching to Zygote64_32. Ends up resulting in things like boot hangs or even the boot process aborting very early.
Magisk Delta uses
Thepersiston the Pixel 7 and allows modules to write to itpersistpartition is used by Magisk Delta to hold the early-mount.d directory for it's early-mount feature.
Modifyingpersisthas an inherent dangerous aspect due to the fact it is unique to each device. Corruption or modification of the calibration data in the partition can result in causing functions of your device to fail.
Magisk Delta is not doing this inherently on all devices, this is actually because the Pixel 7'spersistis the only partition that is not encrypted, is not checked by AVB, and is available early in the boot process. This is actually an extension of the functionality from stock Magisk, as stock Magisk is trying to do the same thing to store SELinux policy rules.
Thus I recommend using my Magisk 32-bit fork instead. However if you need Magisk Delta for it's features then it is best practice before installing Magisk Delta to make a backup of yourpersist. There will be steps on how to do that before installing Magisk Delta.
Support for custom ROMs is not guaranteed
It may or may not work. As a matter of fact, doing this modification isn't necessary as custom ROMs could implement this change themselves.
It is known that the modification does work on LineageOS.
I have not tested all 32-bit applications
I don't actually use any 32-bit apps. I have done testing with a few 32-bit apps I've gotten from APKMirror. So no, I don't know if your Instagram mod is working. I don't see any reason why it wouldn't.
This modification is not 'install and forget'
Like with using custom kernels requiring you to keep on making sure verity and verification are off, this modification requires that you keep a finger on the pulse for any news or updates. You're essentially on the bleeding edge now. The hammer could drop next month and the update is true 64-bit without multilib. Performing an update and forgetting to flash the patched Magisk could require you to wipe your device.
Download Links
All files are hosted at my download repository
Magisk 32-bit:
Recommended:If you are having troubles and need to produce logs:Magisk Delta 32-bit:
For Advanced Users:
If you are having troubles and need to produce logs:
Installation Instructions
General Prerequisites:
A working platform-tools environment
platform-tools 33.0.3 is required with the Pixel 7The version you are running can be checked withadb --versionandfastboot --versionIf you need assistance then read this thread by @roirraW "edor" ehT.Tools like PixelFlasher can be used, just read into how to use it.The factory image for the firmware version you are running or plan to run
Part of the steps are going to be doing a flashing wipe on your device, to guarantee that you start with a reproducible blank slate.Copyinit_boot.imgout from image-xxx.zip
Backup your data
At the moment a wipe is required, so perform two backups: with Google Backup or your favorite backup app and a manual backup of any files.With my Magisk 32-bit fork (Recommended)
Magisk 32-bit with the rebased patch by me.
Direct download link for my Magisk 32-bit APK
Steps:
Note: If you are unrooted and stock then skip to step 4- On your phone uninstall the stock Magisk app. Do not use the uninstall Magisk button from within the app, simply just uninstall the app itself.
- Reboot your phone into the bootloader.
- Flash the stock
init_boot.imgfor your version and then boot into Android. - Install the Magisk 32-bit app from my repository.
- Copy over the stock
init_boot.imgto your phone and patch it in the Magisk app. - Copy the patched Magisk init_boot.img over to your computer
- Reboot your phone into the bootloader.
- Flash and wipe via
fastboot --skip-reboot -w update image-xxx.zip - Wait for it to finish, then reboot back into the bootloader either on the device or with
fastboot reboot bootloader - Flash the patched Magisk
init_boot.imgand boot into Android. - Complete the setup wizard as normal
- Do not open the Magisk stub (the default Android icon), install the Magisk 32-bit app from my repository.
- Open the Magisk app and finish setup for Magisk.
init_boot.imgand that you flashed it to your phone. You will have to perform the steps including the wipe over again.
With my Magisk Delta 32-bit fork (Not Recommended For General Use, Advanced Users Only)
Magisk Delta 32-bit with the rebased patch by me.
Direct download link for my Magisk Delta 32-bit APK
Warning:
Magisk Delta will mount thepersistpartition for it's early-mount feature, meaning that modules using early-mount could inadvertently fill up the partition, leading to possible corruption.The steps will take you through creating a backup of the partition to restore if you ever need to.
Prerequisites:
You need to already have root with Magisk so you can backup thepersistpartition
Steps:
Note: If you already have backed up your persist partition then you can skip steps 4 to 7.- Install my Magisk Delta 32-bit app, it may be installed alongside stock Magisk without issue as it has a different package name.
- Copy over the stock
init_boot.imgto your phone and patch it in the Magisk Delta 32-bit app. - Copy it back over to your computer
- Enter a root shell via either method
- adb
adb shellsu- You will need to approve the attempt on your phone
- Terminal emulator
su
- adb
- Run the following command:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
- Copy
persist.imgover to your computer, keep it safe, keep it in multiple places.- This is not the Google Pixel 7 persist image, this is uniquely your phone's persist image.
- Reboot phone to bootloader
- Flash and wipe via
fastboot --skip-reboot -w update image-xxx.zip - Wait for it to finish, then reboot back into the bootloader either on the device or with
fastboot reboot bootloader - Flash the patched Magisk
init_boot.imgand boot into Android. - Complete the setup wizard as normal
- Install my Magisk Delta 32-bit app.
- Open the Magisk app and finish setup for Magisk.
init_boot.imgand that you flashed it to your phone. You will have to perform the steps including the wipe over again.
System Upgrade Instructions
Either of my Magisk 32-bit forks
- Extract the
init_bootfrom image-xxx.zip of the firmware you want to upgrade to - Patch it in the Magisk app that you are using
- Copy the patched Magisk image back over to your computer
- Reboot your phone into fastboot
- Update the bootloader and radio if necessary
fastboot --skip-reboot update image-xxx.zip- No
-w! That flag will wipe your userdata partition.
- No
- Wait until it is finished
- Don't boot the phone into Android!
- Flash the patched Magisk
init_boot.img- This can be done from inside
fastbootd
- This can be done from inside
Magisk Upgrade Instructions
Either of my Magisk 32-bit forks
- Unhide the Magisk app if you are currently hiding it
- Download and install the latest APK for the 'flavor' you are using from my repository
- It may be required that you uninstall the app if Android won't let you upgrade it
- Perform a direct install from the install menu
- Reboot
Changing Between My Magisk Forks
- Download and install the app you want to switch to from my repository
- Uninstalling the previous Magisk app is not necessary
- Copy the stock
init_boot.imgfor your system version over to your phone - Patch it in the Magisk app you want to switch to
- Copy the patched Magisk image back over to your computer
- Reboot your phone into fastboot
- Flash the patched Magisk
init_boot.img- If moving from Magisk Delta 32-bit to Magisk 32-bit then at the same time you can flash your backed up persist
fastboot flash persist persist.img
- If moving from Magisk Delta 32-bit to Magisk 32-bit then at the same time you can flash your backed up persist
- Remove the other Magisk app
- Finish setup in the remaining Magisk app.
Uninstallation Instructions
My Magisk 32-bit fork
Flash the stockinit_boot.img
My Magisk Delta 32-bit fork
- Flash the stock
init_boot.img fastboot flash persist persist.img
Manual method on phone if without original persist image- Uninstall all Magisk modules, they will clean up any files they put into
early-mount.d - Enter a root shell via either method
- adb (heavily preferred)
adb shellsu- You will need to approve the attempt on your phone
- Terminal Emulator
- adb (heavily preferred)
- Navigate to the persist mount
cd $(magisk --path)/.magisk/mirror/persist/
- Remove the directory
early-mount.drm -ir early-mount.d- You will be prompted for each removal and descending into directories, respond with
yto approve the action
- You will be prompted for each removal and descending into directories, respond with
- Can now reboot and flash stock
init_boot
Troubleshooting
Stuck at boot animation or bootlooping
Restore stockinit_boot.Grab a logcat with adb to determine what the problem may be.You might not have wiped your device.
Booted after installing new Android update but forgot to flash Magisk
Usually there is a "carrier specific" firmware that can be downloaded each month. These are not truly "carrier specific", they can be ran just fine, download whatever is available for the monthly update you are running.Follow the system update instructions using the new firmware you downloaded.After performing the steps and booting you can then repeat the steps but this time use the firmware you originally wanted to run.
Unable to install 32-bit apps
Rungetprop ro.zygote; getprop ro.vendor.product.cpu.abilist; getprop ro.vendor.product.cpu.abilist32If the values do not match these then the modification was not applied.zygote64_32arm64-v8a,armeabi-v7a,armeabiarmeabi-v7a,armeabi32-bit apps force close
This only happened in my testing when I did a first boot with Zygote64 and then installed the modification to use Zygote64_32. Wipe your device.It is possible the app may just have issues, or will not work because of missing libraries.Clobbered the persist partition
Follow the uninstall steps for Magisk Delta, easiest to use the fastboot steps.If you didn't backup your persist partition, then RIP.
Questions
Will I have to wipe on every system update?
I'm glad to say no.I've tested with my Magisk Delta 32-bit, going from October -> November, while keeping Zygisk/MagiskHide enabled along with the Magisk app being hidden.I also tested December -> January with my Magisk 32-bit and even swapping to my Magisk Delta 32-bit in the process without issue.Can I take OTAs instead of flashing factory images?
I would heavily recommend against doing so.
I booted with the patch, but then accidentally flashed over
init_boot, what do I do?Simply just flash the patched Magisk image back over. I've tested it, 32-bit applications are still kept, and I haven't encountered any issues once I flashed the patched Magisk image back onto it.If this was because of an update then try the troubleshooting method above.that uses a different build of the update.
Will my persist partition be destroyed?
You shouldn't have to worry about that, a backup persist image will be able to completely restore it.
Thanks To
Thomas King for Pixel 7 32-bit Helper5ec1cff for maru@nickelnine for bringing attention to Pixel 7 32-bit Helper4
Well the thread is in the Pixel 7 Pro forum, the post is completely full of direct references to the Pixel 7 Pro, the intro video was recorded on a Pixel 7 Pro, and the download page makes reference to that it enables 32-bit support on the Pixel 7. So I'd say yes.
You do need to wipe the phone after flashing the custom Magisk image, just usefastboot -was-is.
You can try without a wipe but the majority of the time it will just bootloop. You will have to either flash back to the stock or your previousinit_bootif you don't want to wipe your data or use the above fastboot command to continue with using the custom Magisk.
If you need Zygisk, which you will need for Universal SafetyNet Fix, then yes.
Some short news on the custom Magisk Delta fork.
Upstream Magisk Delta just removed maru, which isn't that great for us.
For now my fork still works and will continue to have maru so we can continue to use Zygisk, however I do have a solution going forward:
I'm just going to be creating a stock Magisk fork with the maru patches going forward.
This solves the issue ofearlymount.dtainting thepersistpartition, however for the people that do use that feature I'm sorry but you are going to have to limited support. For now the custom Magisk Delta fork can still be used until it no longer works or Magisk gets a large enough update to necessitate moving. Keeping up with rebasing the maru patches onto Magisk Delta is going to get more difficult as time moves on, so it will just be easier to just use stock Magisk with the maru patches and my patch.
This does mean that stock Magisk Delta will pose issues with Zygisk as it doesn't have maru, so I can't recommend using it going forward.
My time frame for getting the new custom Magisk fork out will be sometime next week or the week after. Right now there isn't any pressing matters to get it out the door quickly as everything is still fine, but it's something I'm going to have to do sooner rather than later.3
