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

[eldenmisty]

works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.

He.lo. did you only flash the img? Trying to do what you did

 

[AllexBast]

1

 

[theclev]

i have a sm-x200 on firmware X200XXS1BVJ1 will this work or do i need to downgrade?

 

[theclev]

got it installed, but cant boot past twrp and touch screen isnt working inside twrp. Any suggestions?

 

[withwaves86]

Touchscreen in TWRP 3.7.0 doesn't work. How can I fix it?

 

[lewmur]

Touchscreen in TWRP 3.7.0 doesn't work. How can I fix it?

I have LOS 19.1 with TWRP 3.7.0_11-2 and touchscreen work in it.

 

[Magendanz]

New build has just been posted...

Downloads:

• twrp_3.7.0_12-0_X200XXS1BVJ1.tar.md5
• twrp_3.7.0_12-0_X200XXS1BVJ1.img

Change Log:
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).

 

[kenishi720]

Greetings all,

I've been trying to install a GSI for a couple of days now (from BVJ1), no dice. When I go to wipe things in TWRP (12-0) I get a "Can't Mount ________" message. I've "fixed" that by formatting the filesystem to EXT2 and then back to EXT4 as recommended by another forum post elsewhere.

When I boot into fastboot, I get through the flashing. But when I get to fastboot -w, I get a file system type raw not supported and it doesn't boot. Am I missing something?

 

[Magendanz]

I've been trying to install a GSI for a couple of days now (from BVJ1), no dice. When I go to wipe things in TWRP (12-0) I get a "Can't Mount ________" message. I've "fixed" that by formatting the filesystem to EXT2 and then back to EXT4 as recommended by another forum post elsewhere.

When I boot into fastboot, I get through the flashing. But when I get to fastboot -w, I get a file system type raw not supported and it doesn't boot. Am I missing something?

I finally got a GSI running on Monday, thanks to a hint from @lewmur. My issue was that I was using vndklite variants of LineageOS 19, but I also noticed that I needed to format userdata....not wipe it. Consequently, using fastboot -w caused a bootloop, but all was fine after I did a Wipe > Format Data in TWRP.

Note: When I tried to do a fastboot format:ext4 userdata from Fastboot mode, that also caused a bootloop. I had to format it in TWRP.

 

[kenishi720]

I finally got a GSI running on Monday, thanks to a hint from @lewmur. My issue was that I was using vndklite variants of LineageOS 19, but I also noticed that I needed to format userdata....not wipe it. Consequently, using fastboot -w caused a bootloop, but all was fine after I did a Wipe > Format Data in TWRP.

Note: When I tried to do a fastboot format:ext4 userdata from Fastboot mode, that also caused a bootloop. I had to format it in TWRP.

That did it! Thanks so much!

 

[KeinName_exe]

Tried flashing TWRP 3.7 on X-205 (LTE)
Touch in recovery dont work so i cant use custom firmware...

 

[zaxiby]

What am I doing incredibly stupid. I can't flash a custom ROM to this to save my life.
I have a Tab A8 SM-X200 A 12. I Downloaded the latest firmware with Frija.
Rooted it with a Magisk patched boot.img. Installed TWRP through Odin. I could
boot either into TWRP or the rooted, but otherwise stock firmware. Before flashing
a ROM, I would format the data folder to ext4, wipe everything, enter fastboot mode from TWRP and do the
fastboot flash command with no errors. See screenshot. Fastboot reboot would take me back to TWRP.
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.
I have tried 2 different ROMs, lineage-19.1-20220814-UNOFFICIAL-arm64_bgS.img and
lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img. My stock tars for ODIN are AP_X200XXS1BVJ1, BL_X200XXS1BVJ1, and
CSC_XAR_X200XAR1BVI6. Could it be that the CSC_ file is BV16, and AP_ and BL_ are BVJ1 are a problem?
Using TWRP_3.7.0_12-0_X200XXS1BVJ1.tar.md5, Magisk-v25.2, and Platform Tools 33.0.3.
Treble Info: no seamless upgrades, system-arm64-ab.img.xz, Treble and VNDK, System as root A/B, Dynamic partitions.
For laughs and giggles I tried flashing the img files from TWRP and it went into a bootloop.
Remember the good old days of zip files? I don't need encryption for this tablet. It's a Lazy Boy companion.
Attached: Screenshot of the fastboot process, the fstab file, the TWRP recovery log, and twrpflags.txt.

 

[lewmur]

The only thing I see different is that you formatted the data to ext4 instead of just using TWRP /Wipe and selecting Format Data option.

 

[zaxiby]

The only thing I see different is that you formatted the data to ext4 instead of just using TWRP /Wipe and selecting Format Data option.

Thanks for the reply. I did use > TWRP /Wipe and selecting the Format Data option, to format data.
To expand, with TWRP I formatted data to EXT2 first, then EXT4. You can't go straight to EXT4.
Thanks to whoever discovered that trick.

 

[lewmur]

Thanks for the reply. I did use > TWRP /Wipe and selecting the Format Data option, to format data.
To expand, with TWRP I formatted data to EXT2 first, then EXT4. You can't go straight to EXT4.
Thanks to whoever discovered that trick.

I don't understand the "To expand" part. Just choosing the "Format Data" option under /Wipe, is all that's needed.

edit: "That trick" may be what's causing your problem. As to the CSC and AP versions not being the same, shouldn't matter if the stock ROM booted OK. The CSC is being erased when you format the data partition.

 

[zaxiby]

I don't understand the "To expand" part. Just choosing the "Format Data" option under /Wipe, is all that's needed.

edit: "That trick" may be what's causing your problem. As to the CSC and AP versions not being the same, shouldn't matter if the stock ROM booted OK. The CSC is being erased when you format the data partition.

Again, thanks. On the initial wipe, TWRP can't read the data folder because it's encrypted.
Should I just ignore that?

 

[lewmur]

Again, thanks. On the initial wipe, TWRP can't read the data folder because it's encrypted.
Should I just ignore that?

No. The whole purpose of formatting the data partition is to get rid of the encryption long enough to flash the new ROM. But it doesn't require formatting to ext2 and then ext4. You just choose the Format Data option under Wipe and TWRP will do it.

 

[zaxiby]

No. The whole purpose of formatting the data partition is to get rid of the encryption long enough to flash the new ROM. But it doesn't require formatting to ext2 and then ext4. You just choose the Format Data option under Wipe and TWRP will do it.

In the "Wipe/Format Data screen, I typed yes, then enter, got the following.

Unable to mount storage
Simulating actions...
Updating partition details...
Failed to mount 'data' (invalid argument)

Is this normal?

 

[lewmur]

Again, thanks. On the initial wipe, TWRP can't read the data folder because it's encrypted.
Should I just ignore that?

This is the option to choose. Do this before factory reset.

 

[lewmur]

In the "Wipe/Format Data screen, I typed yes, then enter, got the following.

Unable to mount storage
Simulating actions...
Updating partition details...
Failed to mount 'data' (invalid argument)

Is this normal?

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