How To Guide [GUIDE][ROOT][MAGISK v22.0+] Samsung Galaxy A02s SM-A025G

Search This thread

Maverynthia

Member
Jun 9, 2012
12
0
So has anyone that actually HAS the Boost US version NON-International SM-A025U1/DS with Android 11 phone rooted it. When in Download Mode the computer no longer recognizes it on the USB so I can't flash anything. I've installed all the Samsung USB stuff and the Google USB stuff and the only thing I see is "Android Device" with a ⚠️ in devices and no recognization.
 
So has anyone that actually HAS the Boost US version NON-International SM-A025U1/DS with Android 11 phone rooted it. When in Download Mode the computer no longer recognizes it on the USB so I can't flash anything. I've installed all the Samsung USB stuff and the Google USB stuff and the only thing I see is "Android Device" with a ⚠️ in devices and no recognization.
I don't think anyone has you & I are in the same boat here all I can say is did you go into developer mode & turn on oem unlock?
 

EJ Deveaux

Member
Feb 7, 2022
5
0
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Im trying to do the same.
Maybe ADB oem unlocking will help.
 

Wish39

Senior Member
Jan 13, 2015
215
63
XAA as I said before us the Boost Mobile version and I do have the OEM unlock option. I am trying to root this and am looking to know if this would work with mine since it's not written for my model.
XAA is the CSC code for unlocked/unbranded US phones. If you really had the Boost model the CSC would be BST. Also SM-A025U1/DS is the factory unlocked A02s, the Boost/Metro model would be SM-A025U.
 
XAA is the CSC code for unlocked/unbranded US phones. If you really had the Boost model the CSC would be BST. Also SM-A025U1/DS is the factory unlocked A02s, the Boost/Metro model would be SM-A025U.
That's what was on the box when Boost Mobile shipped it to me & I ordered it from their website. I had no issue turning on OEM Unlock.

Screenshot_20220516-063610_Settings.jpg Screenshot_20220516-063547_One UI Home.jpg Screenshot_20220516-063632_Settings.jpg Screenshot_20220516-063810_Settings.jpg
 
Last edited by a moderator:

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    This guide was made prior to there being a working custom recovery for this device. I highly recommend installing @afaneh92 TWRP in this thread and then simply flash magisk from recovery.




    I purchased this phone a few days ago for around £120 - Bargain.
    I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk

    Full data wipes are required during the process (please backup first)
    Knox will trip but safetynet passes and google pay working once magisk hide enabled

    Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.

    I have uploaded all of the tools and files used to my personal onedrive folder -

    Make sure your device is on the latest firmware and download the zip
    - I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
    • Install Magisk apk on your device.
    • Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
    • Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
    • Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
    Unlocking bootloader on modern Samsung devices have some caveats:

    Allow bootloader unlocking in Developer optionsOEM unlocking
    Reboot to download mode: power off your device and press the download mode key combo for your device
    Long press volume up to unlock the bootloader.
    This will wipe your data and automatically reboot.

    If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.

    Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
    Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
    Your bootloader now accepts unofficial images in download mode

    This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
    • Extract the boot.img from magisk patched AP
    • Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
    • 7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
    • Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
    The next part is essential and doing it wrong will again, result in no root....
    I mistakenly pressed power up and it loaded fastboot... booting direct to recovery from fastboot again, results in no root.

    • Hold volume down and power to reboot...
    • As soon as the screen turns black indicating it is rebooting let go of volume down and hold power and volume up
    • Release power button when you see the android logo but continue to hold volume up
    • Release volume up when the unlocked bootloader warning appears
    • Tap the power button once to skip that warning
    • Stock recovery should now appear
    • Select wipe data / factory reset
    • Reboot system
    • Setup as usual and install the magisk apk
    • Screenshot_20210306-134846_Settings.png. Screenshot_20210306-134957.png. Screenshot_20210306-135010.png

    Update 10April2021: Since doing this quite a few times, I've actually had most success with Magisk 22.0 (I initially went with Canary - but stock is less hit and miss and if you do it exactly like the steps above you will get root.
    1
    Update:
    Have just updated to magisk 22003 directly within magisk app - no issues to report so far
    1
    thank you so much for the guide, i found nothing from google
    can i unroot after modify this device with magisk canary ??
    1
    thank you so much for the guide, i found nothing from google
    can i unroot after modify this device with magisk canary ??

    No problem at all, It was the same position I was in so had to post as it was painful process - needed it documented for myself to follow in future too lol

    yes - it's very easy to unroot directly in the magisk app

    I successfully upgraded to the latest version 22004 from within the magisk app. No issues to report. :)
    1
    How did u root it I have the metro version
    I first flashed a firmware file i found online : sm-a025u_tmk_a025usqu1auc6_(mobileguru4.com) with odin. that flashed with no problems. i then followed the tutorial for rooting sm-a025m or whatever. followed it to a tee. I am now rooted and with twrp installed. i have magisk manager and some edxposed modules running. its still locked to boost though. if i knew what files to look for in the root directory to retrieve my mck i could unlock it i know i could. so PLEASE ANYBODY know what file holds my MCK CODE?
    Screenshot_20210729-213851_Root Checker Basic.jpg
    Screenshot_20210729-213851_Root Checker Basic.jpg