The latest version is not compatible with one ui 5.1 kernel, or so it appears, as my touch screen is not working in twrp, are you working on a new version?
Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]
- Thread starter Magendanz
- Start date
MrFluffyOven
Senior Member
kevinco1
Senior Member
I'm now on X200XXS2CWD2....wondering if anyone has built a new version of TWRP as well but doesn't look like it
MrFluffyOven
Senior Member
Due to the delay in updating this I'm looking into how to port the update myself if I manage I'll post
Hello, is this version of TWRP even compatible with the A8 revision 2022 (SM-X205NZAEEUE)? Or is tested only for the old 2021 (SM-x200) model?
Thank you.
I can get the 2022 version for a cheap price but of course i won't get it if is not compatible with the actual tools (twrp, lineageos, etc...) compared to the pervious version. Anyone who own the last version tried it?
Thank you.
I can get the 2022 version for a cheap price but of course i won't get it if is not compatible with the actual tools (twrp, lineageos, etc...) compared to the pervious version. Anyone who own the last version tried it?
I have this very problem. I cannot get my tablet to disable avb. If I modify system partition at all, or install a gsi it bootloops with a kernel panic. I have been able to use magisk modules to fake an engineer build and "disable-verity" from an elevated terminal but then it stalls on boot stuck on a Samsung Galaxy splash screen indefinitely, and can't even boot to recovery. The only way to fix from there is to use Odin to flash stock vbmeta.
What am I missing? How can I disable avb and install a gsi?
jonpjingleheimler
Senior Member
I have had no touch response in twrp also but it was a certain version. Double check your version. or It may be a hassle but you should be able to use an otg and run a mouse.
Hello. I'm trying to install twrp on my Galaxy Tab A8 SM-X200, but I'm getting fail message.
I enabled Developer options and inside it enabled OEM unlocking, I had to signin Google for OEM onlocking option to appear.
I'm using Odin 3.10.7 downloaded from https://samsungodin.org/#google_vignette on a Win10 PC.
I enter download mode by holding up and down volume then connecting USB plug. Odin detects it with message `<ID:0/005> Added!!`.
Then I click AP and select twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5, Odin reports:
On options tab I verify that only Auto Reboot and F. Reset Time are checked. Then I press Start. The tablet shows no change, here's full Odin log.
I enabled Developer options and inside it enabled OEM unlocking, I had to signin Google for OEM onlocking option to appear.
I'm using Odin 3.10.7 downloaded from https://samsungodin.org/#google_vignette on a Win10 PC.
I enter download mode by holding up and down volume then connecting USB plug. Odin detects it with message `<ID:0/005> Added!!`.
Then I click AP and select twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5, Odin reports:
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..On options tab I verify that only Auto Reboot and F. Reset Time are checked. Then I press Start. The tablet shows no change, here's full Odin log.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img.lz4
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!What version of stock ROM are you running? Have you unlocked the bootloader?
Stock TPA1A.220624.014.X200XXS1CWA3. I rechecked and OEM unlock is checked.
I found Odin 3.14.1, it instructs to remove Google account. I did it and gonna try again.
On tablet log it says "OEM lock: ON (U)", does that mean OEM unlock isn't working?
Indeed, I noticed now that after trying to install, tablet log adds "Final Ver 5 3 Custom Binary Blocked By OEM Lock : Recovery".
So what am I missing?
You didn't answer the question. Have you unlocked the bootloader? Has nothing to do with OEM or Dev mode.
Indeed, I missed the bootloader unlock. I followed https://androidcatch.com/unlock-boo...a8-10-5-2021/#Step_3_Unlocking_the_Bootloader and it worked, green PASS!
But I'm now unable to enter twrp. I hold Vol Up and Power, some lines of white letters show up very quicly, and it seems to reboot. I had tried releasing the buttons and keep holding them and twrp never shows up.
Edit, it didn't work, I'm entering Android recovery mode, with a list of commands: reboot system now, reboot to system load, etc.
Code:
<ID:0/006> Added!!
<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/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 64 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)But I'm now unable to enter twrp. I hold Vol Up and Power, some lines of white letters show up very quicly, and it seems to reboot. I had tried releasing the buttons and keep holding them and twrp never shows up.
Edit, it didn't work, I'm entering Android recovery mode, with a list of commands: reboot system now, reboot to system load, etc.
Flashing TWRP is tricky. If you allow it to reboot by itself, it will reboot to system instead of TWRP and overwrite what you flashed with stock recovery. Before flashing TWRP click the option button in Odin and uncheck auto-reboot. When it finishes flashing, leave the cable attached, hold vol down and power for about 7 seconds. As soon as the screen blanks, switch your finger for vol dn to vol up while still holding down power. Keep holding both button until red message appears. Release power but continue hold vol up till screen blanks. It should now enter TWRP. Also, after unlocking the bootloader did you let it boot to system and enable Dev mode again?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Thanks for posting this howto - it worked perfectly on my Tab A8. I use Arch as my linux distro and never had any issues with my PC recognizing the tablet - it just worked. I knew there were linux apps for this kind of stuff - but there were so little "real world" examples - until you posted this - that I just used a windows VM in VirturalBox to run Odin... -
18
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)
Change Log:
v3.7.0_12-2 (2023-02-28):
- Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
- Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
- 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).
- Adjusted dynamic partition size and removed redundant backup image.
- Updated to TWRP 3.7.0 release built from AOSP-11 branch.
- Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
- Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
- 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
- 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.
4New 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.
4New release is posted...
Downloads:
Change Log:
v3.6.2_11-1 (2022-09-11):
- Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
4Updated 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).
4I successfully installed TWRP (and Magisk, and a phh GSI Lineage) on the A8. Pretty simple if you know the caveats.
- Enable developper settings and unlock botloader ("OEM unlock"). For me this option did only appear in the developper settings with a working internet connection (so at least Wifi had to be set up).
- I was not able to install TWRP without a rooted boot.img despite running the most current official firmware. The original recovery seemed to re-appear after a reboot. So first I had to patch boot.img with the Magisk app. Can be done with any device where Magisk is installed, not necessarily the A8. boot.img is hidden somewhere deep inside the nested archive of the official firmware.
- The download mode of the A8 for me had the annoying habit of allowing only exactly one operation, afterwards the tablet had to be rebooted again to download mode in order to be recognized again by the connected computer?!
- For Linux users: You don't need Odin, Heimdall works.
- So: Reboot to download mode (Vol+/-) for the first time, flash the patched boot.img (heimdall flash --boot magisk_patched_file.img --no-reboot; I added --no-reboot, because I wanted to have control over the reboot process and avoid booting to system in between)
- Reboot to download for the second time and flash TWRP (heimdall flash --recovery twrp-name.img --no-reboot)
- ...and then flash the GSI image according to the instructions in this forum. I tried to avoid booting the system whenever possible until the GSI was flashed, but I don't know if this is necessary.
Getting rid of the Samsung cruft was like a liberation for the tablet. Thanks for all involved devs!
