Не устанавливается gapps error 64

I found that if upon receiving this error, before booting into LineageOS I can

• Boot into the bootloader from TWRP,
  • Click on Reboot
  • Click on Bootloader
• Boot into a new TWRP from the bootloader
  • Run twrp boot ./twrp.*.img
• I can then install the gapps.

What cause this? Well my theory now is that the instructions on the Lineage OS suggest Wiping the System partition

• Now tap Wipe.
• Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
• Return to the previous menu and tap Advanced Wipe, then select the System partition and then Swipe to Wipe.

I was doing that and it was working for the purposes of installing LineageOS, but I believe after the Advanced Wipe on the System Partition something wasn’t working. It’s as if the wipe was complete and LineageOS could be installed, but mounting the partition after the install of LineageOS required rebooting into the recovery again. If you allow LineageOS to boot up before you flash GApps all bets are off. Worse this was the only way for it to work because if I rebooted into the recovery I would get the LineageOS recovery — LineageOS now replaces TWRP entirely. I may have been able to install GApps from the LineageOS recovery’s ADB Sideload option, but rebooting into TWPR recovery by proxy of the bootloader worked too.

answered Oct 17, 2019 at 17:22

There are numerous reasons of why this could happen.

• Have you mounted /system partition?
• Try an older version of TWRP
• Try SAR (System-as-root) version of recovery.

answered Oct 17, 2019 at 5:53

not the TWRP is the problem. I also had to search a long time. Although the processor is arm64 Architecture only the image Lineage OS is based on Android arm. Please try 11 arm Pico7 or Micro on Lineage OS 18.1 ???
or see this???

https://wiki.lineageos.org/gapps

cu SMorphin

answered Apr 26, 2022 at 19:33

I found that if upon receiving this error, before booting into LineageOS I can

• Boot into the bootloader from TWRP,
  • Click on Reboot
  • Click on Bootloader
• Boot into a new TWRP from the bootloader
  • Run twrp boot ./twrp.*.img
• I can then install the gapps.

What cause this? Well my theory now is that the instructions on the Lineage OS suggest Wiping the System partition

• Now tap Wipe.
• Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
• Return to the previous menu and tap Advanced Wipe, then select the System partition and then Swipe to Wipe.

I was doing that and it was working for the purposes of installing LineageOS, but I believe after the Advanced Wipe on the System Partition something wasn’t working. It’s as if the wipe was complete and LineageOS could be installed, but mounting the partition after the install of LineageOS required rebooting into the recovery again. If you allow LineageOS to boot up before you flash GApps all bets are off. Worse this was the only way for it to work because if I rebooted into the recovery I would get the LineageOS recovery — LineageOS now replaces TWRP entirely. I may have been able to install GApps from the LineageOS recovery’s ADB Sideload option, but rebooting into TWPR recovery by proxy of the bootloader worked too.

answered Oct 17, 2019 at 17:22

There are numerous reasons of why this could happen.

• Have you mounted /system partition?
• Try an older version of TWRP
• Try SAR (System-as-root) version of recovery.

answered Oct 17, 2019 at 5:53

not the TWRP is the problem. I also had to search a long time. Although the processor is arm64 Architecture only the image Lineage OS is based on Android arm. Please try 11 arm Pico7 or Micro on Lineage OS 18.1 ???
or see this???

https://wiki.lineageos.org/gapps

cu SMorphin

answered Apr 26, 2022 at 19:33

Sounds like you are trying to install the incorrect version of of Gapps for the Architecture of your device — You can always Google Search «twrp error 64» as well.

No installing wright GAPS ARM 64 FOR XIAOMI REDMI NOTE 4 AND DONE GOOGLE SEARCH ALSO FROM THERE ONLY I HAVE GOT THE TWRP THESE ASKING LINK IN GILTHUB TO ASK SO I HAVE POSTED HERE

Try using TWRP 3.0.2, that worked for me with Sony dogo. I’m unable to install using latest twrp version. I had the exact same error message as you — complaining about architecture. Something wrong happened since verseion 3.0.2, so stay with that if you want Gapps.
Git user @loa was also helped this way earlier today (also with dogo).

+1

I can confirm this. I tried installing open_gapps-arm-7.1-pico-20171215 with twrp 3.1.1-1 and 3.2.1-0 on my dogo (Sony Xperia ZR) device and got

ERROR 64: Wrong architecture to set-up Open GApps' pre-bundled busybox

When downgrading twrp to 3.0.2-0 installation of gapps worked.

Does anybody have an idea what change causes the issue between the versions?

I can confirm this too .

I tried installing open_gapps-arm-7.1-nano-20180212 with 3.2.1-0 onSony Xperia Z and got same error.

ERROR 64: Wrong architecture to set-up Open GApps’ pre-bundled busybox
Lenovo vibe x2 twrp bopo ohuk

Mount /system first. The updater-binary use unzip command which is on /system.

Mount /system first. The updater-binary use unzip command which is on /system.

what is updater-binary use unzip command? where do we see this option?
If that simply means Mount-> check system and try to install->gapps.zip, I did it and it still returns same error message

@ngoquang2708 you mean unzip gapp.zip file and find updater-binary file in the unzip but what should we do with that? can you please help here?

@EmilAlipiev Before install gapp.zip, mount /system partition first if it is not mounted yet.

@ngoquang2708 i did it already but unfortunately it didnt work. after long time searching, I found 3.0.2 version and installing it solved my problem as it is said. it is such a pity that latest version has such problem and causes to waste a lot of time. For sony xperia z3 hard to find 3.0.2 version while there is one officially for xperia z3 compact but is not compatible for z3 version.

@EmilAlipiev Check your rom if there is /system/bin/unzip or /system/xbin/unzip or whatever, then copy it to /system/bin. Maybe your rom is missing unzip binary. I guess.

For anyone it may help, unzip having not been installed was the issue in my case working through all beta builds of Emteria, which currently have TWRP 3.1.1 bundled with it. Going back to the last stable build of the OS (currently, v0.5.21) corrected this error as it seems to have unzip installed. There could be better error handling for this, since the cause wasn’t an architecture incompatibility, but that’s not on TWRP either — it’s on the GApps installer script.

@CtxShaun This is actually a TWRP issue. Unzip should be included in a TWRP build in /sbin by default, but if TW_USE_TOOLBOX was used, it’s possible that it didn’t get copied over, due to this patch being missing: https://gerrit.omnirom.org/c/android_bootable_recovery/+/32815

This has been remedied since the merging of this patch: omnirom/android_bootable_recovery@9338282 however there hasn’t been an official build since that was merged, so it’ll still be an issue on most devices. A new TWRP build should have no issue, though.

The OpenGApps zip doesn’t depend on system’s unzip binary — it expects the custom recovery to have one available. Mounting system as a workaround works if the installed system includes this binary, but that isn’t the intended source.

I am sorry but i dont understand the actual solution here. All i understood is that newest twrp version should fix the problem but my phone is sony xperia z3 and there is no official version for it only xda forums has some versions by other users non-official. So how can I solve this problem? I have 2 problems.

1. using 3.2.1-2 version i can install carbon rom but i cant install or update using 3.0.2
2. using 3.0.2 twrp I can install gapps but not latest carbon rom.

Thats why as workaround i first installed carbon rom with 3.2, downgraded to 3.0.2, installed gapps and upgarded back to 3.2 in order to be able to install future updates of carbon rom

@EmilAlipiev May I ask, where did you find TWRP 3.0.2 for Xperia Z3? I’m having the exact same issue and can’t find anything that looks to be compatible.

@Ivorforce i cant remember but probably somewhere on xda forums. check over there see if you can find it. if not, 6 hours later i can attach here because it is on my personal PC and i need to do it after work. give me a reminder here in case you dont find and i forget to attach

Thanks, I actually found it!

Here are the versions that work, for Xperia Z3:

• fastboot flash TWRP 3.2.1-2 (twrp_z3_2018-03-28.img) to recovery
• Install OmniROM 8.1 (omni-8.1.0-20180101-z3-nailyk.zip) from TWRP 3.2.1
• fastboot flash TWRP 3.0.2 (recovery-z3dual-20160907.img) to recovery
• Install GApps ARM 8.1 Nano from TRWP 3.0.2
• fastboot flash TWRP 3.2.1 again, to keep it installed permanently

This is a lot more complicated than I had hoped for, but eh. At least it works now.

adb sideload worked on xiaomi note 6 pro tulip

@deepaklodha if you have A/B slot device after install the OS switch to B slot and then install GAPPS (if architecture is correct). I had the same problem and I did this and works for me.

@deepaklodha if you have A/B slot device after install the OS switch to B slot and then install GAPPS (if architecture is correct). I had the same problem and I did this and works for me.

Me too. My moto z2 force was was failing GApps install for los 16 with error code 64, incorrect architecture. Booted into recovery (flashboot boot «same as flashed version of TWRP.img») and installed GApps.

Confirmed, My Mi6 (sagit) have the same problem. I try to change the install.sh, line 1379, to
# Check to make certain that user device matches the architecture device_architecture="arm64"

It can pass the verify but after boot no app installed (Although the log output show all installed) (Solved, just avoid install opengapps and magisk together. I don’t know why but install each in twice boot will work.)

It works for me, but I have found a «new» solution. After you flashed the ROM you want, just reboot to TWRP recovery (by Power off device, fastboot boot twrp…img) and then flash gapps.

It works for me, but I have found a «new» solution. After you flashed the ROM you want, just reboot to TWRP recovery (by Power off device, fastboot boot twrp…img) and then flash gapps.

That not a solution for me, I still will get the error 64. I only can modify the install.sh to pass the varify.
Another interesting thing is I have to avoid install opengapps and magisk together. Or won’t boot into the system normally.

I had the same issue with Xiaomi Redmi 7 (onc/onclite), twrp-3.3.1-1-onclite couldn’t install open_gapps-arm64-9.0-pico-20191127, failed with error 64.
Changing install.sh with device_architecture="arm64" hardcoded didn’t actually help: TWRP installed gapps without complaining, but gapps were not present after restarting the phone.

What helped was using recovery TWRP-Redmi7-LRTeam, which installed normal gapps successfully 🎉

Works 100% so if I tried different versions TWRP too but that was not the problem.
The problem was exactly what it showed.
It was wrong version of Gapps and non compatible architecture.
so I tried ARM 10.0.0 pico instead of ARM 64 10.0.0, and it worked.
Be sure of your architecture. Many are confused with ARM 64 it seems.

Sounds like you are trying to install the incorrect version of of Gapps for the Architecture of your device — You can always Google Search «twrp error 64» as well.

No installing wright GAPS ARM 64 FOR XIAOMI REDMI NOTE 4 AND DONE GOOGLE SEARCH ALSO FROM THERE ONLY I HAVE GOT THE TWRP THESE ASKING LINK IN GILTHUB TO ASK SO I HAVE POSTED HERE

Try using TWRP 3.0.2, that worked for me with Sony dogo. I’m unable to install using latest twrp version. I had the exact same error message as you — complaining about architecture. Something wrong happened since verseion 3.0.2, so stay with that if you want Gapps.
Git user @loa was also helped this way earlier today (also with dogo).

+1

I can confirm this. I tried installing open_gapps-arm-7.1-pico-20171215 with twrp 3.1.1-1 and 3.2.1-0 on my dogo (Sony Xperia ZR) device and got

ERROR 64: Wrong architecture to set-up Open GApps' pre-bundled busybox

When downgrading twrp to 3.0.2-0 installation of gapps worked.

Does anybody have an idea what change causes the issue between the versions?

I can confirm this too .

I tried installing open_gapps-arm-7.1-nano-20180212 with 3.2.1-0 onSony Xperia Z and got same error.

ERROR 64: Wrong architecture to set-up Open GApps’ pre-bundled busybox
Lenovo vibe x2 twrp bopo ohuk

Mount /system first. The updater-binary use unzip command which is on /system.

Mount /system first. The updater-binary use unzip command which is on /system.

what is updater-binary use unzip command? where do we see this option?
If that simply means Mount-> check system and try to install->gapps.zip, I did it and it still returns same error message

@ngoquang2708 you mean unzip gapp.zip file and find updater-binary file in the unzip but what should we do with that? can you please help here?

@EmilAlipiev Before install gapp.zip, mount /system partition first if it is not mounted yet.

@ngoquang2708 i did it already but unfortunately it didnt work. after long time searching, I found 3.0.2 version and installing it solved my problem as it is said. it is such a pity that latest version has such problem and causes to waste a lot of time. For sony xperia z3 hard to find 3.0.2 version while there is one officially for xperia z3 compact but is not compatible for z3 version.

@EmilAlipiev Check your rom if there is /system/bin/unzip or /system/xbin/unzip or whatever, then copy it to /system/bin. Maybe your rom is missing unzip binary. I guess.

For anyone it may help, unzip having not been installed was the issue in my case working through all beta builds of Emteria, which currently have TWRP 3.1.1 bundled with it. Going back to the last stable build of the OS (currently, v0.5.21) corrected this error as it seems to have unzip installed. There could be better error handling for this, since the cause wasn’t an architecture incompatibility, but that’s not on TWRP either — it’s on the GApps installer script.

@CtxShaun This is actually a TWRP issue. Unzip should be included in a TWRP build in /sbin by default, but if TW_USE_TOOLBOX was used, it’s possible that it didn’t get copied over, due to this patch being missing: https://gerrit.omnirom.org/c/android_bootable_recovery/+/32815

This has been remedied since the merging of this patch: omnirom/android_bootable_recovery@9338282 however there hasn’t been an official build since that was merged, so it’ll still be an issue on most devices. A new TWRP build should have no issue, though.

The OpenGApps zip doesn’t depend on system’s unzip binary — it expects the custom recovery to have one available. Mounting system as a workaround works if the installed system includes this binary, but that isn’t the intended source.

I am sorry but i dont understand the actual solution here. All i understood is that newest twrp version should fix the problem but my phone is sony xperia z3 and there is no official version for it only xda forums has some versions by other users non-official. So how can I solve this problem? I have 2 problems.

1. using 3.2.1-2 version i can install carbon rom but i cant install or update using 3.0.2
2. using 3.0.2 twrp I can install gapps but not latest carbon rom.

Thats why as workaround i first installed carbon rom with 3.2, downgraded to 3.0.2, installed gapps and upgarded back to 3.2 in order to be able to install future updates of carbon rom

@EmilAlipiev May I ask, where did you find TWRP 3.0.2 for Xperia Z3? I’m having the exact same issue and can’t find anything that looks to be compatible.

@Ivorforce i cant remember but probably somewhere on xda forums. check over there see if you can find it. if not, 6 hours later i can attach here because it is on my personal PC and i need to do it after work. give me a reminder here in case you dont find and i forget to attach

Thanks, I actually found it!

Here are the versions that work, for Xperia Z3:

• fastboot flash TWRP 3.2.1-2 (twrp_z3_2018-03-28.img) to recovery
• Install OmniROM 8.1 (omni-8.1.0-20180101-z3-nailyk.zip) from TWRP 3.2.1
• fastboot flash TWRP 3.0.2 (recovery-z3dual-20160907.img) to recovery
• Install GApps ARM 8.1 Nano from TRWP 3.0.2
• fastboot flash TWRP 3.2.1 again, to keep it installed permanently

This is a lot more complicated than I had hoped for, but eh. At least it works now.

adb sideload worked on xiaomi note 6 pro tulip

@deepaklodha if you have A/B slot device after install the OS switch to B slot and then install GAPPS (if architecture is correct). I had the same problem and I did this and works for me.

@deepaklodha if you have A/B slot device after install the OS switch to B slot and then install GAPPS (if architecture is correct). I had the same problem and I did this and works for me.

Me too. My moto z2 force was was failing GApps install for los 16 with error code 64, incorrect architecture. Booted into recovery (flashboot boot «same as flashed version of TWRP.img») and installed GApps.

Confirmed, My Mi6 (sagit) have the same problem. I try to change the install.sh, line 1379, to
# Check to make certain that user device matches the architecture device_architecture="arm64"

It can pass the verify but after boot no app installed (Although the log output show all installed) (Solved, just avoid install opengapps and magisk together. I don’t know why but install each in twice boot will work.)

It works for me, but I have found a «new» solution. After you flashed the ROM you want, just reboot to TWRP recovery (by Power off device, fastboot boot twrp…img) and then flash gapps.

It works for me, but I have found a «new» solution. After you flashed the ROM you want, just reboot to TWRP recovery (by Power off device, fastboot boot twrp…img) and then flash gapps.

That not a solution for me, I still will get the error 64. I only can modify the install.sh to pass the varify.
Another interesting thing is I have to avoid install opengapps and magisk together. Or won’t boot into the system normally.

I had the same issue with Xiaomi Redmi 7 (onc/onclite), twrp-3.3.1-1-onclite couldn’t install open_gapps-arm64-9.0-pico-20191127, failed with error 64.
Changing install.sh with device_architecture="arm64" hardcoded didn’t actually help: TWRP installed gapps without complaining, but gapps were not present after restarting the phone.

What helped was using recovery TWRP-Redmi7-LRTeam, which installed normal gapps successfully 🎉

Works 100% so if I tried different versions TWRP too but that was not the problem.
The problem was exactly what it showed.
It was wrong version of Gapps and non compatible architecture.
so I tried ARM 10.0.0 pico instead of ARM 64 10.0.0, and it worked.
Be sure of your architecture. Many are confused with ARM 64 it seems.