General [Tutorial] [Magisk] Enabling 32-bit Support For Apps

[Namelesswonder]

Just to clarify some things. I was on the Nov 5 update using Magisks 2.5.2-delta-5. I then removed all the Magisks delta modules and sideloaded the Dec 5 OTA. I then re-rooted using Magisks 2.5.2-delta-5 again. All is working in that setup. I never attempted or had the 32bit setup in the Nov 5 build.

I attempted to enable the 32bit in the Dec 5 build using the following method.
1. Removed all magisks modules, uninstalled magisks app.
2. Flash original init_boot.img from the Dec 5 build.
3. Rebooted into phone and installed your modified magisks delta.
4. Patched original init_boot.img from the Dec 5 build using your modified magisks delta.
5. Flashed 32bit modified init_boot.img.
6. Rebooted into boot_loop.

To get back up and running I then flashed original init_boot.img then re-rooted using the Magisks 2.5.2-delta-5 to patch original init_boot.img and reflash.

All is working using the above steps. Not sure what is going wrong.

RJR

Because you need to wipe in order to not have issues.
If you are sure that you have the patched Magisk init_boot installed on the phone then simply just run fastboot -w to wipe your storage.

Generally there is limited success with not wiping, some 32-bit apps won't work properly because some libraries aren't configured properly when Android doesn't get to freshly set things up with 32-bit support from the start.

 

[nomfway]

Can you clarify what (needed to wait for a while) means? Mine kept rebooting and after 5 minutes I stopped it.

Sorry to hear that! After flashing the image-xxx.zip and the patched init_boot.img, I ran fastboot reboot, and I saw the boot animation, but it was loading for relatively longer than usual time (more than 3 seconds) afterwards, so I thought perhaps it was having bootloop. Thankfully it booted up

 

[ghoster76]

Dumb questions:
- Does this support Pixel 7 Pro?
- Does this required to wipe after flashing patched init_boot.img with custom Magisk, I have rooted phone with default Magisk now?
- Are we able to enable Zygisk after flashing patched init_boot.img?

 

[wowkazmir]

Fixed, delete please.

 

[Namelesswonder]

Dumb questions:
- Does this support Pixel 7 Pro?

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.

- Does this required to wipe after flashing patched init_boot.img with custom Magisk, I have rooted phone with default Magisk now?

You do need to wipe the phone after flashing the custom Magisk image, just use fastboot -w as-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 previous init_boot if you don't want to wipe your data or use the above fastboot command to continue with using the custom Magisk.

- Are we able to enable Zygisk after flashing patched init_boot.img?

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 of earlymount.d tainting the persist partition, 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.

 

[wowkazmir]

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 use fastboot -w as-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 previous init_boot if 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 of earlymount.d tainting the persist partition, 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.

Thanks for posting such a transparent update. I can only embrace using stock magisk as the base, and as you mentioned the persist option has already served its purpose. I look forward to installing and testing the update.

 

[flyinglotus]

I forgot to backup my persist img before flashing my patched init_boot, I did it afterwards..
Is my persist.img useless?

 

[pdaddy]

I know there is a custom ROM with 32 bit enabled. But on the December stock, with enabling 32 bit, has anyone gotten V4A to work? Tried last night and I can get other 32 bit apps to work, but V4A seems to have issues with the driver not installing. Anyone seeing the same or have a workaround?

 

[Namelesswonder]

I forgot to backup my persist img before flashing my patched init_boot, I did it afterwards..
Is my persist.img useless?

It's not useless, it's better to have the modified one than to not have a backup at all. The biggest thing is having the calibration data backed up in case the partition gets clobbered on your device.
The only thing Magisk Delta does is create some empty folders on the persist partition to be used by modules making use of the early mount feature, so it hasn't made any bad changes to the partition, but it is no longer "untouched". This isn't problematic because I doubt Google is ever going to go far enough to verify device integrity by checking the persist partition because the partition is unique to each device.

If you want you can make a "cleaned" backup by just deleting the folder early-mount.d inside /mnt/vendor/persist and then running dd again to backup the partition. Magisk Delta will recreate the folder on next boot.

I know there is a custom ROM with 32 bit enabled. But on the December stock, with enabling 32 bit, has anyone gotten V4A to work? Tried last night and I can get other 32 bit apps to work, but V4A seems to have issues with the driver not installing. Anyone seeing the same or have a workaround?

I haven't used V4A since getting it working on the Nexus 6P, but I believe it does not work on stock anymore and is required to be baked into the ROM now.

 

[Iven321]

I have encountered a very strange problem, a 64-bit application can run for the first time on the pixel 7 pro, and it will crash when it is opened for the second time, but after enabling the 32-bit support (other conditions remain unchanged), the 64-bit programs can run normally, how is this going on?

 

[lunacies]

Man, I am really kicking myself for buying this stupid Verizon version of the phone because of the deal they had going on at the time. I wish I had known prior that it would never be possible for me to unlock or root my phone if I bought this, otherwise I would have gone with another option as I was not in a huge rush to get a new phone anyway. It just kills me because I have had verizon for so long and never had an issue doing this on my older phones when I cared more about doing it (Moto Droids up to the Pixel 1) and then never needed to again or followed it to realize how locked down their phones are now. No 32 bit apps is one of my main gripes with this phone (again, did not realize this phone was 64 bit only prior to purchasing it, or what apps of mine were only 32 bit previously) and it kills me that I will never be able to have a way to install them on my phone. Ugh, F Verizon, I guess I learned the hard way and now I know for future phones but still, it is infuriating.

 

[TheAnomalyy]

Absolutely phenomenal write up. I did everything as written and the results are fantastic. I am able to run 64-bit and 32-bit apps without issue. All apps open up normally each time and there are no problems seen so far. Thanks for this, much appreciated. Now to put back all my main applications and bask in the glory of the Pixel 7 Pro with 32-bit support.

 

[Samuel Holland]

Sorry to have to ask, but I'm failing cts profile. I tried universal safyeynetfix_mod and reg. I tried using fingerprint module. I enabled zygosk. Did I miss something? Any ideas? I started with a fresh wipe and wiped after installing delta. I disabled verity and verification and wiped again, do y'all think that could have caused my issue. Thanks sincerely for sharing this. I tried installing an 32 bit app with success. just thought I'd ask, I might try again with another fresh install tomorrow if I can find the time. Thx

 

[wowkazmir]

Sorry to have to ask, but I'm failing cts profile. I tried universal safyeynetfix_mod and reg. I tried using fingerprint module. I enabled zygosk. Did I miss something? Any ideas? I started with a fresh wipe and wiped after installing delta. I disabled verity and verification and wiped again, do y'all think that could have caused my issue. Thanks sincerely for sharing this. I tried installing an 32 bit app with success. just thought I'd ask, I might try again with another fresh install tomorrow if I can find the time. Thx

Try using this:

Releases · Displax/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix

github.com

 

[Samuel Holland]

Try using this:

Releases · Displax/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix

github.com

Thank you so so very much for quick reply and this worked. Yes, awesome!

 

[antonio_d25]

this method should work with the latest Dec. update or any future updates?

 

[Samuel Holland]

this method should work with the latest Dec. update or any future updates?

I'm on Dec, and I seen reports of it being okay from Nov-Dec.

 

[huskydg]

Some short news on the custom Magisk Delta fork.​

Upstream Magisk Delta just removed maru, which isn't that great for us.

I didn't remove maru :v

 

[Namelesswonder]

I didn't remove maru :v

The commit is no longer showing up in the repository though.

this method should work with the latest Dec. update or any future updates?

Yes it'll work. It should continue to work until Google stops building the 32-bit libraries.

I have encountered a very strange problem, a 64-bit application can run for the first time on the pixel 7 pro, and it will crash when it is opened for the second time, but after enabling the 32-bit support (other conditions remain unchanged), the 64-bit programs can run normally, how is this going on?

I don't know how it would help. There might be some other issue with the app that get resolved somehow with any of the steps, I don't entirely know. A logcat of the app failing to open would be helpful, because there must be some strange things going on for that happen.

 

[huskydg]

The commit is no longer showing up in the repository though.

GitHub - HuskyDG/Magisk at delta

The Magic Mask for Android. Contribute to HuskyDG/Magisk development by creating an account on GitHub.

github.com