Question The best way to root samsung tab a8 2021 pls

Search This thread

RootPsycho

Member
Mar 18, 2022
8
0
Android 11

I got fast as f boot loop solution below btw

An 4 gamers I got fps/ping boost solution below to
 
Last edited:

RootPsycho

Member
Mar 18, 2022
8
0
I've tried the odin method but it did not work.... Auth failed error and stuck in boot loader mode on my tab.... had to factory restore it
 

RootPsycho

Member
Mar 18, 2022
8
0
would very much appreciate root attempts..... [PC] boot loop fix: download FRP Hijacker by Hagard then plug in tab to PC then open Hijacker then select sm-x200 as your device model and select softbricker fixer option to fix bootloop then factory restore and keep trying to root 🙏
 
Last edited:

RootPsycho

Member
Mar 18, 2022
8
0
Performance boost: get ccleaner an use the stop all background process option and also get game booster 4x faster an select ur game an get ping booster if u got ms lag an get ethernet for mobile device adapter
 
Last edited:

MarcoGalaxySM-X205

New member
Mar 28, 2022
4
2
Hi at all I am stuck in bootloader loop too.
First of all I can not find my modell SM-X205 in FRP Hijacker. How is that possible that you guys find your SM-X200 and the last Device in my list in FRP Hijackers is SM-G3815?

I am currently in Bootloader mode (I am either there or in the loop). How can I factory reset everything?
Do I need original Firmeware I looked in Frija but I need CSC or TMB Description ( I do not know what that is) to search for something. Furthermore I have no clue how to use that with odin if I would be able to get the firmeware somehow.
 
  • Like
Reactions: IkeGolden

arutsuro

Member
Mar 25, 2011
31
9
Which version of Magisk did you use? Plus, are you sure that you used the correct firmware for patching?

After which step exactly did it bootloop?
Magisk 24.1 and downloaded the firmware from samloader and restored after bootloop with same. It get stuck in bootloop after flashing the tablet and get a green PASS with Odin.
 
  • Like
Reactions: IkeGolden

arutsuro

Member
Mar 25, 2011
31
9
1648488080038.png

I just noticed there are two newer versions. Maybe 24.3 is the good one to root A8.

https://topjohnwu.github.io/Magisk/changes.html
 
  • Like
Reactions: IkeGolden

arutsuro

Member
Mar 25, 2011
31
9
Yes, try it with the instructions in my guide.

Let me know how it goes.
It was the same, after bootloop I flashed original AP to restore the tablet.
I concerned about ! Installation failed and cp: can't preserve ownership of.... I hope someday we can root this tablet...

Code:
! Installation failed
- Device platform: arm64-v8a
- Installing: 24.3 (24300)
- Processing tar file
-- Copying: super.img
-- Extracting: boot.img
-- Copying: dtbo.img
-- Copying: socko.img
-- Copying: recovery.img
-- Copying: gnssmodem.bin
-- Copying: EXEC_KERNEL_IMAGE.bin
-- Copying: userdata.img
-- Copying: AGCP_DSP.bin
-- Patching: vbmeta.img
-- Writing: vbmeta.img
-- Copying: vbmeta_system.img
-- Copying: meta-data/
-- Copying: meta-data/fota.zip
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER      [2]
KERNEL_SZ       [21538832]
RAMDISK_SZ      [692567]
SECOND_SZ       [0]
RECOV_DTBO_SZ   [0]
DTB_SZ          [163175]
OS_VERSION      [11.0.0]
OS_PATCH_LEVEL  [2022-01]
PAGESIZE        [2048]
NAME            [SRPUI28B001]
CMDLINE         [console=ttyS1,115200n8]
CHECKSUM        [f5d63aceeeefd7a23c8835e8a8d7a2024ceb971c000000000000000000000000]
KERNEL_FMT      [raw]
RAMDISK_FMT     [gzip]
SAMSUNG_SEANDROID
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [dtb]
Patch @ 010DAB44 [736B69705F696E697472616D667300] -> [77616E745F696E697472616D667300]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER      [2]
KERNEL_SZ       [21538832]
RAMDISK_SZ      [692567]
SECOND_SZ       [0]
RECOV_DTBO_SZ   [0]
DTB_SZ          [163175]
OS_VERSION      [11.0.0]
OS_PATCH_LEVEL  [2022-01]
PAGESIZE        [2048]
NAME            [SRPUI28B001]
CMDLINE         [console=ttyS1,115200n8]
CHECKSUM        [f5d63aceeeefd7a23c8835e8a8d7a2024ceb971c000000000000000000000000]
KERNEL_FMT      [raw]
RAMDISK_FMT     [gzip]
SAMSUNG_SEANDROID
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER      [2]
KERNEL_SZ       [21538832]
RAMDISK_SZ      [1201584]
SECOND_SZ       [0]
RECOV_DTBO_SZ   [0]
DTB_SZ          [163175]
OS_VERSION      [11.0.0]
OS_PATCH_LEVEL  [2022-01]
PAGESIZE        [2048]
NAME            [SRPUI28B001]
CMDLINE         [console=ttyS1,115200n8]
CHECKSUM        [c133184558a8001015d996e4f233b112e5a0d05f000000000000000000000000]
-- Writing: boot.img

****************************
 Output file is written to
 /storage/emulated/0/Download/magisk_patched-24300_oslvJ.tar
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!

Code:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> skip file list for home binary
<ID:0/009> userdata.img
<ID:0/009> Home Binary Download
<ID:0/009> Total Binary size: 5492 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> u-boot-spl-16k-sign.bin
<ID:0/009> teecfg-sign.bin
<ID:0/009> sml-sign.bin
<ID:0/009> tos-sign.bin
<ID:0/009> lk-sign.bin
<ID:0/009> sharkl5pro_cm4.bin
<ID:0/009> grd_fw.img
<ID:0/009> super.img
<ID:0/009> dtbo.img
<ID:0/009> socko.img
<ID:0/009> recovery.img
<ID:0/009> gnssmodem.bin
<ID:0/009> EXEC_KERNEL_IMAGE.bin
<ID:0/009> AGCP_DSP.bin
<ID:0/009> vbmeta.img
<ID:0/009> vbmeta_system.img
<ID:0/009> boot.img
<ID:0/009> cache.img
<ID:0/009> optics.img
<ID:0/009> prism.img
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Removed!!
<ID:0/009> Remain Port ....  0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Added!!
 
  • Like
Reactions: IkeGolden

keksas3

Member
Feb 14, 2022
8
5
extract boot image from original AP then put it on your A8 tab and patch it with magisk newest version.compress it to .tar format and flash it with odin and that should be it.worked for me.

used X200XXU1AVC1 version of firmware.
 

arutsuro

Member
Mar 25, 2011
31
9
extract boot image from original AP then put it on your A8 tab and patch it with magisk newest version.compress it to .tar format and flash it with odin and that should be it.worked for me.

used X200XXU1AVC1 version of firmware.
Thank you @keksas3 and @DJBhardwaj, patching boot.img instead AP.md5 with new magisk was the answer. Now I can confirm A8 is rootable without bootloop issues.

Code:
- Device platform: arm64-v8a
- Installing: 24.3 (24300)
! Installation failed
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER      [2]
KERNEL_SZ       [21538832]
RAMDISK_SZ      [692567]
SECOND_SZ       [0]
RECOV_DTBO_SZ   [0]
DTB_SZ          [163175]
OS_VERSION      [11.0.0]
OS_PATCH_LEVEL  [2022-01]
PAGESIZE        [2048]
NAME            [SRPUI28B001]
CMDLINE         [console=ttyS1,115200n8]
CHECKSUM        [f5d63aceeeefd7a23c8835e8a8d7a2024ceb971c000000000000000000000000]
KERNEL_FMT      [raw]
RAMDISK_FMT     [gzip]
SAMSUNG_SEANDROID
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [dtb]
Patch @ 010DAB44 [736B69705F696E697472616D667300] -> [77616E745F696E697472616D667300]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER      [2]
KERNEL_SZ       [21538832]
RAMDISK_SZ      [692567]
SECOND_SZ       [0]
RECOV_DTBO_SZ   [0]
DTB_SZ          [163175]
OS_VERSION      [11.0.0]
OS_PATCH_LEVEL  [2022-01]
PAGESIZE        [2048]
NAME            [SRPUI28B001]
CMDLINE         [console=ttyS1,115200n8]
CHECKSUM        [f5d63aceeeefd7a23c8835e8a8d7a2024ceb971c000000000000000000000000]
KERNEL_FMT      [raw]
RAMDISK_FMT     [gzip]
SAMSUNG_SEANDROID
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER      [2]
KERNEL_SZ       [21538832]
RAMDISK_SZ      [1201584]
SECOND_SZ       [0]
RECOV_DTBO_SZ   [0]
DTB_SZ          [163175]
OS_VERSION      [11.0.0]
OS_PATCH_LEVEL  [2022-01]
PAGESIZE        [2048]
NAME            [SRPUI28B001]
CMDLINE         [console=ttyS1,115200n8]
CHECKSUM        [c133184558a8001015d996e4f233b112e5a0d05f000000000000000000000000]

****************************
 Output file is written to
 /storage/emulated/0/Download/magisk_patched-24300_6D1Cj.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!
Code:
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> skip file list for home binary
<ID:0/009> userdata.img
<ID:0/009> Home Binary Download
<ID:0/009> Total Binary size: 5492 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> u-boot-spl-16k-sign.bin
<ID:0/009> teecfg-sign.bin
<ID:0/009> sml-sign.bin
<ID:0/009> tos-sign.bin
<ID:0/009> lk-sign.bin
<ID:0/009> sharkl5pro_cm4.bin
<ID:0/009> grd_fw.img
<ID:0/009> AGCP_DSP.bin
<ID:0/009> boot.img
<ID:0/009> dtbo.img
<ID:0/009> EXEC_KERNEL_IMAGE.bin
<ID:0/009> gnssmodem.bin
<ID:0/009> recovery.img
<ID:0/009> socko.img
<ID:0/009> super.img
<ID:0/009> vbmeta.img
<ID:0/009> vbmeta_system.img
<ID:0/009> cache.img
<ID:0/009> optics.img
<ID:0/009> prism.img
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Removed!!
<ID:0/009> Remain Port ....  0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/020> Added!!
 
  • Like
Reactions: IkeGolden

arutsuro

Member
Mar 25, 2011
31
9
I have a question @DJBhardwaj, when I'll want to update the firmware I just need to flash all updated and patched files, using HOME_CSC instead the normal one to avoid format user data? Always gives me laziness to reconfigure and reinstall all my staff on my devices... Thanks again!
 
  • Like
Reactions: IkeGolden

MarcoGalaxySM-X205

New member
Mar 28, 2022
4
2
can you please tell me if I need to rename the patched file to boot.img and then compress it with all the other extracted files from AP_Xxxxx.tar to a new AP_Xxxxx.tar?

EDIT: I tried it, for everybody who is in doubt this is the way to go ;)
 
Last edited:
  • Like
Reactions: IkeGolden

thicc_pp

Member
Jan 26, 2022
5
5
Hey y'all, glad to see that there's been a way to make it work!

I've been doing the following but still can't seem to get out of bootloop, can anyone help out? (@arutsuro @MarcoGalaxySM-X205 @keksas3 @DJBhardwaj )

1. Grab the firmware package "X200XXU1AVC1" and unzip
2. Unzip the AP tar file
3. Extract boot.img, send to device, and patch with magisk 24.3
4. Replace boot.img with the newly patched one (renamed to boot)
5. Create a tar file from the AP folder using
Bash:
tar -C AP_folder -cvf AP_patched.tar .
6. Get tab to download mode, open Odin v3.14 and add BL, HOME_CSC, and the AP_patched.tar
7. Flash via Odin, exit download mode, enter stock recovery, factory reset

After step 7 is where I get stuck in bootloop, anything seem off to you? My plan now is to repatch boot.img after flashing the stock AP again and retry.

EDIT:
So this is pretty weird, I went to test if it's because of the way I'm creating the tar file, so I extracted the stock AP and made a new tar file from the extract. In Odin, I see the following when I try to flash with the tar I created (no patch applied):

<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> ./
<ID:0/007> ./AGCP_DSP.bin
<ID:0/007> ./boot.img
<ID:0/007> ./dtbo.img
<ID:0/007> ./EXEC_KERNEL_IMAGE.bin
<ID:0/007> ./gnssmodem.bin
<ID:0/007> ./recovery.img
<ID:0/007> ./socko.img
<ID:0/007> ./super.img
<ID:0/007> ./userdata.img
<ID:0/007> ./vbmeta.img
<ID:0/007> ./vbmeta_system.img
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 397 M

All of these skipped files are the ones present in the AP tar, which is why I think I keep getting stuck in the loop. If I use the stock AP file, these parts aren't skipped. Does anyone have some advice on how to properly generate this tar file?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    When I rooted my Samsung Galaxy Tab A8 10.5 I extracted the boot image and patched with magisk 24.3 but instead of putting the file back in AP I create a tar with the boot image using 7zip then using Odin I flash the boot image tar to device. This always works for me I have rooted all my tablets this way even a generic tablet from Amazon the flash tool for the other tablet was different depending on model but the patching of boot image is the same process!
    2
    Looks like that was the issue, 7-zip did the trick. Thanks a ton @MarcoGalaxySM-X205 @arutsuro !
    2
    extract boot image from original AP then put it on your A8 tab and patch it with magisk newest version.compress it to .tar format and flash it with odin and that should be it.worked for me.

    used X200XXU1AVC1 version of firmware.
    1
    Hi at all I am stuck in bootloader loop too.
    First of all I can not find my modell SM-X205 in FRP Hijacker. How is that possible that you guys find your SM-X200 and the last Device in my list in FRP Hijackers is SM-G3815?

    I am currently in Bootloader mode (I am either there or in the loop). How can I factory reset everything?
    Do I need original Firmeware I looked in Frija but I need CSC or TMB Description ( I do not know what that is) to search for something. Furthermore I have no clue how to use that with odin if I would be able to get the firmeware somehow.
    1
    Yes, I have come across that thread as well. I'm not sure where to find the file boot.img that was mentioned (on the device itself?).
    Look in message #7 in that thread. Get the factory firmware. UNzip it, untar it, there is the boot.img.