Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]

Search This thread

zaxiby

Member
Oct 4, 2017
10
1
If you select /Backup and choose Internal Storage, how much available space does is show?

I found out what I was doing stupid. I wasn't doing "Swipe to Factory Reset first". TWRP now shows up in sdcard.
I did do that first, days ago, but I didn't know about encrypted data. More than one thread advised this >
Wipe/Advanced Wipe/Select Data/Repair or Change file System/Change File System. Then do the EXT4 trick.
I'm rebooting into fastboot, and going to try flash.
Many thanks for your time, regardless what happens.
 

lewmur

Senior Member
Apr 30, 2011
2,403
517
I found out what I was doing stupid. I wasn't doing "Swipe to Factory Reset first". TWRP now shows up in sdcard.
I did do that first, days ago, but I didn't know about encrypted data. More than one thread advised this >
Wipe/Advanced Wipe/Select Data/Repair or Change file System/Change File System. Then do the EXT4 trick.
I'm rebooting into fastboot, and going to try flash.
Many thanks for your time, regardless what happens.
Yes, I have seen that advice before for other tablets. I've NEVER used it. It's always seemed redundant.
 

zaxiby

Member
Oct 4, 2017
10
1
Yes, I have seen that advice before for other tablets. I've NEVER used it. It's always seemed redundant.
I think I tried the proper way first, but got those errors. That's when I discovered the "Trick" which gave no errors.
After no flashing success, I carefully read all steps, but my brain replaced the correct way with the "Trick".
Said I was stupid. Anyway , the flash went flawlessly., and thanks a ton!
 

hoody424

New member
Apr 22, 2021
1
0
Same here. Touchscreen without function.
Hope u'll get this fixed soon^^

adb.exe shell
recovery --wipe_data
recovery --wipe_cache
also lead to a boot loop after flashing
 

devasure

Senior Member
May 18, 2015
85
15
twrp-featured.jpg

Notes:
  • What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
  • This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.

Not working:
  • Support for metadata encryption (which causes mounting errors in log)
Downloads:
Change Log:
v3.7.0_12-1 (2023-01-22):
  • Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
  • Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
  • Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
  • Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
  • Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
v3.6.2_11-1 (2022-09-11):
v3.6.2_11-0 (2022-09-04):

Instructions:
From OEM stock firmware:
  • Unlock bootloader
  • Hold Vol Up & Vol Down buttons during restart to enter Download mode
  • Install TWRP to AP with Odin
  • Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
  • Hold Power & Vol Up during restart to enter TWRP recovery
  • Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
  • Reboot to Recovery

What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.

Source:

Donations:
  • Your support is always appreciated! Just click here.

This turorial worked for my A8(x200XXU1AUL5).Android 11.
The method I followed is given below:
*Unlocked device bootloader
*In odin,loaded BL,TWRP.tarmd5(in AP,and CSC.
(I don't remember if the TWRP.tar.md5 was this one
twrp_3.7.0_12-1_X200XXU1CVL5.tar.md5
or this one
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5)
*Flashed the files,and when Odin showed PASS and phone screen started to black ,pressed Power+Vol up keys together and got the device into TWRP
*Once in TWRP,I flashed majisk.zip that I had kept on my ext.sd card.(just rename your majisk manager app to majisk manager.zip or majisk.zip to make the zip for flashing)
*After flashing magisk manager.zip,I did not do any data wipe or cashe wipe.I just rebooted into system.That is all.
NB.twrp.img file did not work in my case.
Dont do any any data wipe.It caused bootloop on my first attempt.Just flash majisk.zip and reboot to system
 

Attachments

  • IMG-20230201-WA0000.jpg
    IMG-20230201-WA0000.jpg
    77.1 KB · Views: 29
  • IMG-20230201-WA0003.jpg
    IMG-20230201-WA0003.jpg
    68.8 KB · Views: 31
  • IMG-20230201-WA0002.jpg
    IMG-20230201-WA0002.jpg
    42.5 KB · Views: 31
  • IMG-20230201-WA0001.jpg
    IMG-20230201-WA0001.jpg
    48.9 KB · Views: 32
  • Like
Reactions: macallik

SevastianXDA

Member
Dec 3, 2020
33
5
I'm guessing that you didn't update to the X200XXU1CVL5 (Android 13) OEM firmware before you installed. it.
Not sure, I'd guess so (I think it might've been on Android 13, although I'm not sure, but definitely not latest), but I recommend you add a very visible note about this to the main post and also explain the fix for this, which is that you'll need a USB Type A to Type C adapter and a mouse to connect to the tablet and use TWRP that way.
Since well, I assume there's no way for me to flash the latest firmware (via Odin?) nor will it let me to boot into the system anymore, always brings me to recovery.
If the possible fixes I talked about being impossible to do is false or u know of any other fix, please tell me how, if not, I'll be going to the store tomorrow to buy an adapter.
Ultimately, I want to end up using the LineageOS GSI or if it's too bad/unstable at least root the stock ROM and debloat it of it's crap.
 
Last edited:
  • Like
Reactions: macallik

Magendanz

Senior Member
Mar 25, 2008
954
994
Issaquah, WA
www.Vote4Chad.com
Not sure, I'd guess so (I think it might've been on Android 13, although I'm not sure, but definitely not latest), but I recommend you add a very visible note about this to the main post and also explain the fix for this, which is that you'll need a USB Type A to Type C adapter and a mouse to connect to the tablet and use TWRP that way.
Since well, I assume there's no way for me to flash the latest firmware (via Odin?) nor will it let me to boot into the system anymore, always brings me to recovery.
If the possible fixes I talked about being impossible to do is false or u know of any other fix, please tell me how, if not, I'll be going to the store tomorrow to buy an adapter.
Ultimately, I want to end up using the LineageOS GSI or if it's too bad/unstable at least root the stock ROM and debloat it of it's crap.
You might be confusing me with a custom service rep. I build TWRP for my own use and share those builds with the XDA community in the hope that others can benefit and start building their own custom ROMs. After all, my OP starts with a note that says, "This is unofficial and unsupported." As much of a hassle as it was for you to discover that the OEM bootloader isn't compatible with all versions of the kernel, I'm guessing that it's still easier than if you'd started from scratch like I did.

Rather than complain that an unofficial and unsupported build of a custom recovery needs fixes, I suggest you embrace the fact that you're taking some risks by following this path and that some more advanced knowledge of how the boot sequence works may be required. You should also easily be able to enter Download mode and flash the latest OEM firmware without needing a USB adaptor.
 

SevastianXDA

Member
Dec 3, 2020
33
5
You might be confusing me with a custom service rep. I build TWRP for my own use and share those builds with the XDA community in the hope that others can benefit and start building their own custom ROMs. After all, my OP starts with a note that says, "This is unofficial and unsupported." As much of a hassle as it was for you to discover that the OEM bootloader isn't compatible with all versions of the kernel, I'm guessing that it's still easier than if you'd started from scratch like I did.

Rather than complain that an unofficial and unsupported build of a custom recovery needs fixes, I suggest you embrace the fact that you're taking some risks by following this path and that some more advanced knowledge of how the boot sequence works may be required. You should also easily be able to enter Download mode and flash the latest OEM firmware without needing a USB adaptor.
Oh, via Odin? That's great then! Do you know where exactly I'd need to flash it? Like, AP, BL, CSC, CP?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    New build posted...

    Downloads:
    Change Log:
    v3.7.0_12-2 (2023-02-28):
    • Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
    1
    Can you elaborate on the steps you took to resolve your flash?

    I ran into TWRP being unresponsive, used Frija to try forcing the latest stock image, and then used the USB-C to USB-A converter to use my wireless mouse to select options in TWRP.

    Now, I am using these instructions to flash this image (system-squeak-arm64-ab-gapps.img.xz) but it doesn't take at the end even tho the process doesn't show any errors. When I manually reboot the tablet after the installation, the tablet just restarts back in TWRP
    View attachment 5861999
    It looks like you never renamed the image to "system". For the SM-X200 you need to do that to get compatible GSIs to work
    1
    Thanks! So I'm assuming I just reformat & wipe in TWRP and give it another shot?

    Yes do all the same steps as before except to rename to system.img

    Let me know how it goes, I was able to install that GSI but wasn't able to get Magisk working
    1
    Thanks! So I'm assuming I just reformat & wipe in TWRP and give it another shot?
    fastboot -w must be done BEFORE you flash system NOT AFTER!!!!
    1
    Use a USB-C -> USB Adapter to plug your mouse into your tablet. Navigate TWRP via your mouse and otherwise proceed w/ the regular steps. Sevastian has 1-2 posts earlier in this thread on the issue. (I experienced the issue myself as well)
    Ok i read his post but i thought already anyone ha a fix :)
    Anyways, now i have installed LOS. Thank you for your work and help :)
  • 15
    twrp-featured.jpg

    Notes:
    • What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
    • This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.

    Not working:
    • Support for metadata encryption (which causes mounting errors in log)
    Downloads:
    Change Log:
    v3.7.0_12-2 (2023-02-28):
    • Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
    v3.7.0_12-1 (2023-01-22):
    • Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
    v3.7.0_12-0 (2023-01-01):
    • Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
    • Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
    • Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
    v3.7.0_11-1 (2022-10-24):
    • Adjusted dynamic partition size and removed redundant backup image.
    v3.7.0_11-0 (2022-10-09):
    v3.6.2_11-1 (2022-09-11):
    v3.6.2_11-0 (2022-09-04):

    Instructions:
    From OEM stock firmware:
    • Unlock bootloader
    • Hold Vol Up & Vol Down buttons during restart to enter Download mode
    • Install TWRP to AP with Odin
    • Hold Power & Vol Up buttons during restart to enter TWRP recovery
    From existing TWRP install: (No need for data wipe.)
    • Hold Power & Vol Up during restart to enter TWRP recovery
    • Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
    • Reboot to Recovery

    What about rooting with Magisk?
    These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.

    Source:

    Donations:
    • Your support is always appreciated! Just click here.
    4
    New release for Android 12 is posted. Note that the OEM's stock recovery auto-restoration "feature" has been removed in X200XXU1BVI6, so TWRP installs should survive rebooting to system now.

    Downloads:

    Change Log:
    v3.7.0_11-0 (2022-10-09):

    • Updated to TWRP 3.7.0 release built from AOSP-11 branch.
    • Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
    4
    New release is posted...

    Downloads:

    Change Log:
    v3.6.2_11-1 (2022-09-11):
    4
    New build posted...

    Downloads:
    Change Log:
    v3.7.0_12-2 (2023-02-28):
    • Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
    4
    Updated for the new Android 13 OEM release...

    Downloads:
    Change Log:
    v3.7.0_12-1 (2023-01-22):
    • Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).