ChangeLog:
v4.1.8
App Update:
Google Play Store 28.3.18
Google Play services 21.48.15
Happy New Year From GMT+8
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
v4.1.8
App Update:
Google Play Store 28.3.18
Google Play services 21.48.15
Happy New Year From GMT+8
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
👍17🤩5🔥4❤2
Reaction is enabled~
👍102🔥32❤20💩17😱12🎉7😁6🤩6👎3😢3🤮3
WeebGApps-arm-arm64-12.0-5.0.0.zip
93.7 MB
🥰10👍7❤2🔥1🎉1
WeebGApps-arm-arm64-11.0-5.0.0.zip
93.5 MB
👍8❤4🥰2😁1🤩1
V5.0.0 Changelog
The development of WeebGApps v5 (code with copy and paste ) has come to an end, and it is expected to be released before the start date (the seventh day of the lunar new year).
General function:
- One installation package comes with three modes (referred to as one for three): system installation mode (flash in TWRP/OFRP/Lineage Recovery, no need to modify the file name), system removal mode (experimental function, after adding the file name
- Increase the space size of the detection system partition before flashing to prevent mindless flashing
- Add a fool-proof mechanism: the device can only have one of system installation and module installation. If you want to switch, you must first remove it
News
- Added support for Android 12
- (Experimental) Added remove GApps mode
Fixes and improvements
- Improve compatibility of A/B system architecture installation
- Update Busybox to v1.34.1-osm0sis (sync with Magisk v24.1)
- Update Google Play Store to 29.1.10
- Update Google Play Services to 22.02.20
Known issues:
- (System installation) The function of Addon.d may not work properly (repair slowly, or leave it unrepaired)
- (Magisk module) Metaphysical problems generated under Magisk (for example: MagiskHide or Zygisk will cause Google Play services to be forced to stop. Since I can't find a solution, and no one has provided an improvement plan, it will not give relevant Support. If you have a better improvement plan, welcome to submit)
- (Magisk module) CTS failed to become successful, the reason is unclear (the mitigation plan has been rudely handled in service.sh. If there is a better improvement plan, welcome to propose)
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
The development of WeebGApps v5 (code with copy and paste ) has come to an end, and it is expected to be released before the start date (the seventh day of the lunar new year).
General function:
- One installation package comes with three modes (referred to as one for three): system installation mode (flash in TWRP/OFRP/Lineage Recovery, no need to modify the file name), system removal mode (experimental function, after adding the file name
uninstall Flash in TWRP/OFRP/Lineage Recovery) and Magisk Module Installation (Flash in Magisk Manager App, no need to modify file name) (this function is synchronized with the current Magisk installation mode)- Increase the space size of the detection system partition before flashing to prevent mindless flashing
- Add a fool-proof mechanism: the device can only have one of system installation and module installation. If you want to switch, you must first remove it
News
- Added support for Android 12
- (Experimental) Added remove GApps mode
Fixes and improvements
- Improve compatibility of A/B system architecture installation
- Update Busybox to v1.34.1-osm0sis (sync with Magisk v24.1)
- Update Google Play Store to 29.1.10
- Update Google Play Services to 22.02.20
Known issues:
- (System installation) The function of Addon.d may not work properly (repair slowly, or leave it unrepaired)
- (Magisk module) Metaphysical problems generated under Magisk (for example: MagiskHide or Zygisk will cause Google Play services to be forced to stop. Since I can't find a solution, and no one has provided an improvement plan, it will not give relevant Support. If you have a better improvement plan, welcome to submit)
- (Magisk module) CTS failed to become successful, the reason is unclear (the mitigation plan has been rudely handled in service.sh. If there is a better improvement plan, welcome to propose)
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
👍26❤11👏1😁1
V5.0.1 Changelog
Fixes and improvements
- Try improve compatibility of A/B system architecture installation(This is for Android 12 devices which with Product Partition, I don't have that devices so I may try more and more nya...)
- Fallback the and fix Magisk Module with
- Update Google Play Store to 29.4.13
- Update Google Play Services to 22.06.15
Known issues:
- (System installation) The function of Addon.d may not work properly (repair slowly, or leave it unrepaired)
- (Magisk module) The file name can't be detect in Magisk App Hide mode,Maybe is Magisk App bug. Bypass that,restore the Magisk App to normal mode to flash with magisk module
- (Magisk module) Metaphysical problems generated under Magisk (for example: MagiskHide or Zygisk will cause Google Play services to be forced to stop. Since I can't find a solution, and no one has provided an improvement plan, it will not give relevant Support. If you have a better improvement plan, welcome to submit)
- (Magisk module) CTS failed to become successful, the reason is unclear (the mitigation plan has been rudely handled in service.sh. If there is a better improvement plan, welcome to propose)
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
Fixes and improvements
- Try improve compatibility of A/B system architecture installation(This is for Android 12 devices which with Product Partition, I don't have that devices so I may try more and more nya...)
- Fallback the and fix Magisk Module with
service.sh- Update Google Play Store to 29.4.13
- Update Google Play Services to 22.06.15
Known issues:
- (System installation) The function of Addon.d may not work properly (repair slowly, or leave it unrepaired)
- (Magisk module) The file name can't be detect in Magisk App Hide mode,Maybe is Magisk App bug. Bypass that,restore the Magisk App to normal mode to flash with magisk module
- (Magisk module) Metaphysical problems generated under Magisk (for example: MagiskHide or Zygisk will cause Google Play services to be forced to stop. Since I can't find a solution, and no one has provided an improvement plan, it will not give relevant Support. If you have a better improvement plan, welcome to submit)
- (Magisk module) CTS failed to become successful, the reason is unclear (the mitigation plan has been rudely handled in service.sh. If there is a better improvement plan, welcome to propose)
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
👍23❤5
V5.0.2 Changelog
Add
- Support Android 12L theoretically(Not test on my device yet nya)
Fixes and improvements
- Try improve compatibility of A/B system architecture installation
- Improve bypass method for Magisk Module with service.sh
- Update Google Play Store to 30.1.19
- Update Google Play Services to 22.13.12
Known issues:
- (System installation) The function of Addon.d may not work properly (repair slowly, or leave it unrepaired)
- (Magisk module) The file name can't be detect in Magisk App Hide mode,Maybe is Magisk App bug. Bypass that,restore the Magisk App to normal mode to flash with magisk module
- (Magisk module) Metaphysical problems generated under Magisk (for example: MagiskHide or Zygisk will cause Google Play services to be forced to stop. Since I can't find a solution, and no one has provided an improvement plan, it will not give relevant Support. If you have a better improvement plan, welcome to submit)
- (Magisk module) CTS failed to become successful, the reason is unclear (the mitigation plan has been rudely handled in service.sh. If there is a better improvement plan, welcome to propose)
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
Add
- Support Android 12L theoretically(Not test on my device yet nya)
Fixes and improvements
- Try improve compatibility of A/B system architecture installation
- Improve bypass method for Magisk Module with service.sh
- Update Google Play Store to 30.1.19
- Update Google Play Services to 22.13.12
Known issues:
- (System installation) The function of Addon.d may not work properly (repair slowly, or leave it unrepaired)
- (Magisk module) The file name can't be detect in Magisk App Hide mode,Maybe is Magisk App bug. Bypass that,restore the Magisk App to normal mode to flash with magisk module
- (Magisk module) Metaphysical problems generated under Magisk (for example: MagiskHide or Zygisk will cause Google Play services to be forced to stop. Since I can't find a solution, and no one has provided an improvement plan, it will not give relevant Support. If you have a better improvement plan, welcome to submit)
- (Magisk module) CTS failed to become successful, the reason is unclear (the mitigation plan has been rudely handled in service.sh. If there is a better improvement plan, welcome to propose)
Team Group : @WeebGappsGroup
Team Channel : @WeebGappsChannel
👍34🎉3👎1