Samsung Galaxy A02s - phhusson/treble_experimentations GitHub Wiki

Samsung Galaxy A02s

Components Status
Camera (FRONT/BACK) WORKING ✅/ One works but idk if the other 2 does.
Speaker/Mic (TOP/BOTTOM) WORKING ✅ / WORKING ✅
Bluetooth WORKING ✅
Wi-Fi WORKING ✅
SIM / Mobile Data / Voice Calls WORKING ✅ /  WORKING ✅ / Partially works ✳️
VoLTE Unknown ❔
Offline Charging WORKING ✅
Normal / Fast Charging WORKING ✅ / WORKING ✅
USB / USB OTG WORKING ✅ / WORKING ✅
Terms used:

Patched recovery - Stock recovery patched with the tool.

Custom recovery - TWRP, OFOX etc...

Custom recoveries/kernels/vendors

Important notes

Running GSIs

Any attempt in running a secure or secure-on-demand¹ GSIs that hasn't been updated at June 2023 or later will make the device hard reboot every 10-20 seconds after booting up. You might think that the GSI has booted properly but after some seconds, it will do it.

¹Only when you securize or you turn on Device Spoof Properties(On secure-on-demand GSIs)

Same applies for when you try to use any Magisk module to fix SafetyNet such as Universal SafetyNet Fix. Basically, any method used to fix SafetyNet will cause the above issue. Properties are always spoofed on Secure GSIs so that's why the above issue happens.

Phh has fixed the above issue by changing the way how Watchdog and Watchdogd is handled by GSIs. You can apply these fixes on old GSIs using appropriate tools to unpack and repack the GSI or by using root. However, I would recommend you to use a newer GSI or just wait for your developer to implement the fix on their GSI.

No need to and you shouldn't turn on any Alternate audio policy option or any audio-related options in phh Treble options. This will break the audio system. However, disabling sound effects in Qualcomm settings or disabling audio effect in Misc Settings won't break it.

Not sure how the above option works. -- @tangymc

How to GSI

Unlocking the bootloader.

  • To be able to install GSIs and a custom ROM, you should first unlock the bootloader. Do note that you can't unlock bootloader on some variants!

  • First, Enable the Developer's Settings in settings by tapping on the Build number several times in the About section (Basically how humans do it unless you're from Mars).

  • Then, go to the Developer's Settings (Last setting on the home page of Settings) and you should see OEM Unlocking and USB Debugging. If you don't see the OEM Unlocking option, it might be because it's a carrier-locked one or maybe a variant that doesn't allow the unlocking of the bootloader.

  • Enable both options and reboot to Download Mode by first, powering off your device, holding both Volume UP and DOWN button while plugging a USB cable to it that's connected to your PC. If you see a blue screen pop-up, it means that you've successfully booted into Download mode!

    If you see an option called Device Unlock Mode, this means that you can proceed further! Then, long press on the Volume UP and continue with the process!

    NOTE THAT THIS WILL ERASE YOUR DATA SO TAKE A BACKUP BEFORE DOING SO!(unless you don't care about your data or there's none). You can use the Smart Switch software on your PC to do it.

  • After rebooting, complete the setup process, connect to a network, check for updates, enable developer settings again and if you see the OEM Unlocking option greyed out, it means that you have successfully unlocked the bootloader!

Flashing a patched vbmeta/disabling vbmeta

The TWRP recovery mentioned above has a file that has been mentioned called vbmeta_disabler.tar. You should flash this before installing a custom recovery.

The above file should be also flashed after installing the patched recovery.

Choosing the right GSI and other stuff

A02s only supports a64/arm32_binder64 and A/B GSIs. So, make sure to only choose them.

If you're going to install Magisk, make sure to choose a GSI that doesn't contain phh SU.

SGSIs(Semi-GSIs) are not guaranteed to work perfectly on it. So, use them at your own risk!

Installing a GSI

Before installing a GSI, make sure you have a custom recovery or have installed a patched recovery(tool found above). The fastboot option that's found on the stock recovery (basically the one that says reboot to bootloader in recovery) is completely useless.

After installing any of them, you'll be able to flash a GSI by either:

  • Flashing it as a system image in a custom recovery using methods such as sideload or by having the image on an SD card that's on the phone. You can also plug a USB drive through OTG with the image on it.

    or

  • By flashing it through fastboot on a custom recovery or a patched recovery (Recommended) using the following commands:

    To flash a GSI:

    fastboot erase system # To erase the system partition

    fastboot flash system <your gsi img> # To flash your GSI

    To empty out the product partition (Optional):

    fastboot erase product # To erase the product partition

    fastboot flash product product_gsi.img # To flash an empty product image

    product_gsi.img - click to download Note that you should have ADB/Platform tools installed on your PC along with Samsung's or Google's USB Driver. Both works fine.

    However, if you're using another phone to do that (through OTG) then the above drivers won't be required.

    Then, reboot to the recovery by either pressing on reboot system if you use a custom recovery or just select the option to go back to the recovery if you're on a patched recovery.

    After that, clear data by going into the Wipe options in TWRP and pressing Advanced Wipe and selecting Data, Dalvik, Internal Storage and Cache.

    If you're on the patched recovery, you should use Wipe data and Wipe cache options to wipe the data and cache.