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

[zaxiby]

Yes, that is normal. To test if it worked, reboot recovery, select Advanced/File Management/sdcard and instead of a bunch folders with funny names, you should see just one folder named TWRP

Advanced/File Management/sdcard shows empty.

 

[lewmur]

Advanced/File Management/sdcard shows empty.

If you select /Backup and choose Internal Storage, how much available space does it show?

 

[zaxiby]

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]

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.

 

[cyb7]

When I did TWRP > Reboot > System, the device returned to TWRP. When I did TWRP > Power Off,
The unit would hang on "The tablet is not running Samsung's official software" nag screen, and not turn off.

Exactly the same behaviour I had. See: https://forum.xda-developers.com/t/gsi-12-unofficial-lineageos-19-sm-x200.4495865/post-87923811

 

[zaxiby]

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!

 

[openback]

I'm having the same issue as others where the touchscreen doesn't work in TWRP. I've flashed the 3 different versions with Odin and they've all been the same. Any ideas?

 

[Mackie Messer]

Is there any solution for the non-working touchscreen?

 

[hoody424]

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

 

[Magendanz]

Updated for the new Android 13 OEM release...

Downloads:

• twrp_3.7.0_12-1_X200XXU1CVL5.tar.md5
• twrp_3.7.0_12-1_X200XXU1CVL5.img

Change Log:
v3.7.0_12-1 (2023-01-22):

• Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).

 

[andr_SMOLKEYS]

Is there no build for the SM-X205?

 

[devasure]

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:

• twrp_3.7.0_12-1_X200XXU1CVL5.tar.md5
• twrp_3.7.0_12-1_X200XXU1CVL5.img

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):

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

v3.6.2_11-1 (2022-09-11):

• Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.

v3.6.2_11-0 (2022-09-04):

• Initial TWRP 3.6.2 release built from AOSP-11 branch.

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:

• android_device_samsung_gta8wifi

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

 

[SevastianXDA]

On latest version of your TWRP, stuck in touchscreen, SOS. ;(

 

[Magendanz]

On latest version of your TWRP, stuck in touchscreen, SOS. ;(

I'm guessing that you didn't update to the X200XXU1CVL5 (Android 13) OEM firmware before you installed. it.

 

[SevastianXDA]

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.

 

[Magendanz]

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]

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?

 

[SevastianXDA]

I'm guessing that you didn't update to the X200XXU1CVL5 (Android 13) OEM firmware before you installed. it.

Flashed latest firmware, still no touchscreen.
(Downloaded latest stock ROM from Frija, then flashed BL, AP and CSC (with HOME_CSC). No CP file since the tablet is Wifi only.)

 

[Magendanz]

Flashed latest firmware, still no touchscreen.
(Downloaded latest stock ROM from Frija, then flashed BL, AP and CSC (with HOME_CSC). No CP file since the tablet is Wifi only.)

Use the CSC, since you need to wipe the userdata partition.

 

[SevastianXDA]

Use the CSC, since you need to wipe the userdata partition.

I wiped it via the recovery and it boot me to system so not an issue, I bought a usb to type c adapter and my mouse works.