General [Magisk] Magisk Zygote64_32: Enabling 32-bit Support For Apps

[t3chwizard]

I had no issues with 34.0.1 but I will probably use 33.0.3 to be safe

 

[huskydg]

I was referring to the OP's 32-bit patch for Delta which was deprecated last I checked. He recommends against it as it modifies the persist partition.

Official Magisk is also modifying persist partition

 

[freddienuxx]

Where did i say that?

preach and thank you for your forked magisk

 

[CodeOnDiscord]

Do you still have to wipe after patching the boot image?

 

[Bulletro]

Hey Namelesswonder, I was just wondering if you had implemented json support yet or if any progress has been made for easy updating and integration with pixel flasher etc. since I saw that you had mentioned it.

 

[wowkazmir]

Will you be working on patching the new official magisk release (v26) with 32-bit support?

 

[niphoet]

Will you be working on patching the new official magisk release (v26) with 32-bit support?

Yes, this would be awesome and very appreciated. I still have some old games that are 32-bit. Thanks!

 

[supermansaga]

I have this nasty Collect N Win app at http://nycollectnwin.com/android_install.html that doesn't work with 64 bit Pixel 7 Pro. Look forward to Namelesswonder's revised instructions on official Magisk 26001. Thx. I may still pass due to the data wipe requirement

 

[Namelesswonder]

Will you be working on patching the new official magisk release (v26) with 32-bit support?

Yes, this would be awesome and very appreciated. I still have some old games that are 32-bit. Thanks!

It's out now. It wasn't that much of an update since my fork had commits up to March 9th and had the bulk of changes, although stability with Zygisk was improved in later commits since the hooking was refined and has become less crash prone.

Hey Namelesswonder, I was just wondering if you had implemented json support yet or if any progress has been made for easy updating and integration with pixel flasher etc. since I saw that you had mentioned it.

The download repository now has canary and debug channels. Updating should be easier now.

Do you still have to wipe after patching the boot image?

I have this nasty Collect N Win app at http://nycollectnwin.com/android_install.html that doesn't work with 64 bit Pixel 7 Pro. Look forward to Namelesswonder's revised instructions on official Magisk 26001. Thx. I may still pass due to the data wipe requirement

I forgot to update the instructions for the wipeless installing, I'll get them put up in the original post later today. If you're already on the April update then it'll be too late to do wipeless unless Google releases another April build, if not then you'll have to wait until May.

Big Update - Magisk Zygote64_32​

In the making for a bit, haven't had the time lately to put aside for the project, but better late than never.

Magisk Zygote64_32 2ee5dc0f (26101)​

Name Change​

The project has been renamed to "Magisk Zygote64_32", since the previous name of "Magisk 32-bit" was ambiguous as to whether it was for 32-bit devices or if it added 32-bit support for multilib Zygote64 devices.​

​

Update Channels​

The download repository now has the channel JSON files, so updates can now be rolled out via the app.​

Currently it is untested whether the stub is capable of downloading the full app, and whether debug <-> canary channel swaps can be done.​

​

Because the previous releases forced the update channel to custom the app on preexisting installs will not get updates until you manually change the channel to canary or debug, and you will have to manually update to 2ee5dc0f to restore updating​

​

Currently only the canary and debug channels are active, stable and beta just redirect to canary​

​

Updated to v26.1 (26101)​

Magisk Zygote64_32 2ee5dc0f (26101) is based on 468f3efb​

​

Works on Android 14 Beta 1​

I've been testing it today and so far have not had any problems that would occasionally pop up on the previous release.​

​

I'll get around to making newer Magisk Delta build at some point, however I'm probably not going to be setting up an update channel for that, nor am I going to be doing much testing on it since I don't have a second device to do development with.

 

[Namelesswonder]

Wipeless instructions are up in the original post.

Currently if you are on March still then you can easily perform the wipeless upgrade.
If you are on April then you will either have to wait until the May update releases or you can try the downgrade instructions.
If you are on QPR3 or Android 14 then somewhat tough luck, you can try finding an older QPR3/Android 14 DP firmware image to perform the downgrade steps.
Be warned, downgrading can result in data loss, however because March and April are on the same QPR it shouldn't happen. Still, backup your data.

You're essentially flashing the older firmware and patched Magisk for that older firmware, booting, then flashing the newer firmware and patched Magisk for the newer firmware.

 

[badabing2003]

Thanks for the wonderful work and guide.
on user requests, I'm trying to automate this into PixelFlasher as much as possible (Me too don't actually use any 32 bit apps), I have some questions if you don't mind (and more might come as I get to implement it)

For Wipeless upgrade:

Upgrading Steps:​

Requisites: current firmware image and firmware image you are upgrading toNote: If you are unrooted and stock then skip to step 4

1. 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.
2. Reboot your phone into the bootloader.
3. Flash the stock init_boot.img for your currently running build version and then boot into Android.
4. Install the Magisk Zygote64_32 app from my repository.
5. Copy over the stock init_boot.img for the build version you want to upgrade to onto your phone and patch it in the Magisk app.
6. Copy the patched Magisk init_boot.img over to your computer
7. Reboot your phone into the bootloader.
8. Flash the newer build you want to update to with fastboot --skip-reboot update newer-image-xxx.zip
   • Do not use -w or you will wipe your device.
   • It may be necessary to also update the bootloader and radio beforehand.
9. Wait for it to finish, then flash the patched Magisk init_boot.img and boot into Android.
   • Flashing init_boot is possible from within fastbootd, so you don't need to reboot to the bootloader.
10. Install the Magisk Zygote64_32 app from my repository.
11. Open the Magisk app and finish setup for Magisk.

• Step 4 install Magisk Zygote64_32 app, and so does step 10, I don't see an uninstall in between, is a reinstall necessary?
• Step 1 can be performed after step 3 right? there is no absolute need to do it as the first step?
• Assuming that one has already done this with the previous firmware, and are already on Magisk Zygote64_32 (let's say April release), when it is time to upgrade (let's say to May release), it is not clear to me if a stock init_boot of April firmware needs to be flashed before doing step 5 and the following steps.
  Should the guide add a note that if you are already on Magisk Zygote64_32, skip to step 5?
• After doing steps 5 - 9 with the May release, and assuming that step 10 is not necessary (app already previously installed), is there still a need for step 11 ?

Thanks
BB

 

[Namelesswonder]

Thanks for the wonderful work and guide.
on user requests, I'm trying to automate this into PixelFlasher as much as possible (Me too don't actually use any 32 bit apps), I have some questions if you don't mind (and more might come as I get to implement it)

For Wipeless upgrade:

• Step 4 install Magisk Zygote64_32 app, and so does step 10, I don't see an uninstall in between, is a reinstall necessary?
• Step 1 can be performed after step 3 right? there is no absolute need to do it as the first step?
• Assuming that one has already done this with the previous firmware, and are already on Magisk Zygote64_32 (let's say April release), when it is time to upgrade (let's say to May release), it is not clear to me if a stock init_boot of April firmware needs to be flashed before doing step 5 and the following steps.
  Should the guide add a note that if you are already on Magisk Zygote64_32, skip to step 5?
• After doing steps 5 - 9 with the May release, and assuming that step 10 is not necessary (app already previously installed), is there still a need for step 11 ?

Thanks
BB

1. Forgot to take out step 10 when I was rewriting them from the wipe installation, it isn't necessary since the app will still be there.
2. Yes they can be swapped, all that matters is that the device isn't running stock Magisk as it will immediately uninstall the my version since I have signed it with my own keys. I probably should change the package name on mine so there isn't this conflict.
3. These steps are just installation steps, once installed then you only have to follow the system upgrade or Magisk upgrade steps that are further in the post which are the typical upgrading steps for rooted systems and Magisk. The installation steps are just to get Android to setup the 32-bit libraries, once they are setup they stay so, until a wipe or if the user boots into a different build version of Android without running my Magisk.
4. For a system that has never run my Magisk then yes step 11 is necessary since it ties the app to the kernel process. This isn't ever needed afterwards.

 

[badabing2003]

I probably should change the package name on mine so there isn't this conflict.

I was wondering about that, let me know the package name if you ever change it so that I make the necessary adjustments in PF.

These steps are just installation steps, once installed then you only have to follow the system upgrade or Magisk upgrade steps that are further in the post which are the typical upgrading steps for rooted systems and Magisk.

Yep, my bad, seeing Upgrading under Wipeless, I wrongly assumed that those were the upgrade steps for already installed Magisk zygot64_32, I see it now and it's super clear, and no different that normal Magisk.

One other question, is there an easy way to detect if multilib is supported, so that I could warn / block the user from attempting to install this version? Or should I leave it to your app to do that?

Thanks for the feedback.

 

[Namelesswonder]

I was wondering about that, let me know the package name if you ever change it so that I make the necessary adjustments in PF.



Yep, my bad, seeing Upgrading under Wipeless, I wrongly assumed that those were the upgrade steps for already installed Magisk zygot64_32, I see it now and it's super clear, and no different that normal Magisk.

One other question, is there an easy way to detect if multilib is supported, so that I could warn / block the user from attempting to install this version? Or should I leave it to your app to do that?

Thanks for the feedback.

There isn't an easy way to detect if the system is multilib or not, and worse there is no easy way to detect if a system is completely multilib with full coverage.
It would be entirely possible for a device to release with the Zygote process set to be 64-bit only and for it to have a limited amount of 32-bit libraries, meaning that 32-bit apps won't be able to run.

Right now there are testing firmwares for older Pixels that are truly 64-bit only and aren't multilib, but as outlined on the page the Pixel 7 is an outlier and is still multilib.

Really the easiest block to put in would just be to check if device or firmware is a Pixel 7, since as far as I know these are the only devices that have a 64-bit only Zygote and are fully multilib.

I haven't modified the Magisk installer to block other devices, so it actually would have no qualms about running on another device. The modification will have no effect on 64-bit devices that support 32-bit, since they already have the properties set to do so, in fact I'm running my version on my Pixel XL without issue. However on a truly 64-bit only device my Magisk will cause the system to not boot.

The problem that is going to crop up will be later Pixel devices. Potentially even as early as the Pixel 7a or Tablet, Google could decide that they've had enough testing and ship out the firmwares for them with only 64-bit libraries. For the Pixel 8 there will be no way around this anyway since Tensor G3 isn't even going to be able to execute 32-bit instructions.

 

[badabing2003]

Thank you again.

Really the easiest block to put in would just be to check if device or firmware is a Pixel 7, since as far as I know these are the only devices that have a 64-bit only Zygote and are fully multilib.

I'll do that, check for P7 or P7P and otherwise warn.

 

[wowkazmir]

Thanks for the large update! Trying to avoid a wipe or downgrade, I first attempted to update the app and then use the install directly option. While this probably works just fine I then went ahead and patched the April init_boot file with your latest modifications. I believe flashing it through fastboot could end up being more stable in the long run. Either way, I am able to run 32-bit apps still and just wanted to share this!

 

[Superguy]

Thanks for the wonderful work and guide.
on user requests, I'm trying to automate this into PixelFlasher as much as possible (Me too don't actually use any 32 bit apps), I have some questions if you don't mind (and more might come as I get to implement it)

For Wipeless upgrade:

• Step 4 install Magisk Zygote64_32 app, and so does step 10, I don't see an uninstall in between, is a reinstall necessary?
• Step 1 can be performed after step 3 right? there is no absolute need to do it as the first step?
• Assuming that one has already done this with the previous firmware, and are already on Magisk Zygote64_32 (let's say April release), when it is time to upgrade (let's say to May release), it is not clear to me if a stock init_boot of April firmware needs to be flashed before doing step 5 and the following steps.
  Should the guide add a note that if you are already on Magisk Zygote64_32, skip to step 5?
• After doing steps 5 - 9 with the May release, and assuming that step 10 is not necessary (app already previously installed), is there still a need for step 11 ?

Thanks
BB

Thanks for this. I hope you can get it to work!

I really want to use Swype (32 bit only) but I find the current methods too complicated. Would be nice if there'd be a way to recompile apps for 64 bit too.

 

[badabing2003]

Thanks for this. I hope you can get it to work!

I really want to use Swype (32 bit only) but I find the current methods too complicated. Would be nice if there'd be a way to recompile apps for 64 bit too.

App recompilation would have to be made to the specific app developers, as of PixelFlasher, the next version will support installing Magisk zygote64_32, creating a patch with it and flashing.

Please keep in mind that PixelFlasher is primarily for Pixel phone, although most of its features would work for other phones, they remain untested.

 

[thatrunks]

@Namelesswonder

Thank you so much for this!
I'm using the LineageOS 20 MicroG build (lineage-20.0-20230409-microG-cheetah) from April 9th.
And used the init_boot.img from this version: 13.0.0 (TQ2A.230305.008.C1, Mar 2023) (cheetah-tq2a.230305.008.c1-factory-cefc4e56)

I followed these instructions;

Steps:​

Note: If you already have backed up your persist partition then you can skip steps 4 to 7.

1. Install my Magisk Delta 32-bit app, it may be installed alongside stock Magisk without issue as it has a different package name.
2. Copy over the stock init_boot.img to your phone and patch it in the Magisk Delta 32-bit app.
3. Copy it back over to your computer
4. Enter a root shell via either method
   • adb
     • adb shell
     • su
       • You will need to approve the attempt on your phone
   • Terminal emulator
     • su
5. Run the following command:
   • dd if=/dev/block/by-name/persist of=/sdcard/persist.img
6. Copy persist.img over 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.
7. Reboot phone to bootloader
   
   SKIPPED STEP 8 AND 9
8. Flash and wipe via fastboot --skip-reboot -w update image-xxx.zip.
9. Wait for it to finish, then reboot back into the bootloader either on the device or with fastboot reboot bootloader
   SKIPPED STEP 8 AND 9
   
10. Flash the patched Magisk init_boot.img and boot into Android.
11. Complete the setup wizard as normal
12. Install my Magisk Delta 32-bit app.
13. Open the Magisk app and finish setup for Magisk.

Every 32 bits app are installing and working, especially the older ones I used and couldn't install. Even Flappy Bird. Was looking for a donate button to support you for this great fix.

 

[Superguy]

App recompilation would have to be made to the specific app developers, as of PixelFlasher, the next version will support installing Magisk zygote64_32, creating a patch with it and flashing.

Please keep in mind that PixelFlasher is primarily for Pixel phone, although most of its features would work for other phones, they remain untested.

Oh I'm on a pixel. My thoughts were actually 2 separate thoughts.

I didn't expect PF to be able to recompile anything, just that it would be cool if apps could be recompiled so such hacks wouldn't be necessary.