Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S8 Series (Snapdragon)

Search This thread

afaneh92

Senior Member
Jul 31, 2012
3,448
4,953
I've already been reading the telegram thread and you did have a problem with data - July 22nd you fixed data backup issue and update kernel and modules. You didn't list that as a bug here
Its not twrp bug that cant backup data. Its samsung firmware bug so its not listed as twrp bug.
I have fixed it by excluding the fonts folder from data and still under testing.
 

afaneh92

Senior Member
Jul 31, 2012
3,448
4,953
Samsung fonts won't back up? Never heard that before
The data of fonts not the fonts, I cant explain more the mod will ban me if I do.
So if you got one of those devices come back and ask whatever you like
My twrp is 99.9% stable and if you are worried about the .01% its same for all samsung devices and dont buy samsung if you cant handle the loss of data encryption
 

Techguy777

Senior Member
The data of fonts not the fonts, I cant explain more the mod will ban me if I do.
So if you got one of those devices come back and ask whatever you like
My twrp is 99.9% stable and if you are worried about the .01% its same for all samsung devices and dont buy samsung if you cant handle the loss of data encryption
No are you kidding I hate encryption on my devices. Even with recovery on my poco f3 now able to read the encryption data. I still leave it unencrypted. I'm a lower security guy root, permissive kernel, unencrypted data, bootloader unlocked and no safety net. I think people get carried away with that stuff. I would rather my tablet be fully open for me to do whatever I want to.

Monthly security patches lol next month they'll tell you this months patch was crap again. I don't even care
 

afaneh92

Senior Member
Jul 31, 2012
3,448
4,953
No are you kidding I hate encryption on my devices. Even with recovery on my poco f3 now able to read the encryption data. I still leave it unencrypted. I'm a lower security guy root, permissive kernel, unencrypted data, bootloader unlocked and no safety net. I think people get carried away with that stuff. I would rather my tablet be fully open for me to do whatever I want to.

Monthly security patches lol next month they'll tell you this months patch was crap again. I don't even care
The only problem with newer 2022 devices is that you can't modify the ro f2fs partitions like system without making it rw and its not possible because I didn't release the script to do yet.
So in my opinion my twrp is stable, otherwise its users fault not following my instructions.
 

V0latyle

Forum Moderator
Staff member
I know this guy for long time, he never said thanks or appreciated people work.
Some people weren't raised with any semblance of manners.
I spent hundreds of hours to get this stable and usable. But people cant read. They want me to spoon-feed them every single moment.
Take a look at the Pixel 6 forums sometime and see how many people are bricking their phones because they can't follow explicit instructions.
Im supporting nearly 70 samsung device.
I have enough pressure at work and life.
I understand that it's frustrating and rather thankless. Just remember that you owe no one here anything. your time is your own, your work is voluntary, and you have no obligation to spend any more time on these projects than you absolutely want to.

For everyone using this project: You would do well to remember the same. Developers owe you nothing. Do not ask for updates or ETAs. Do not be rude. Be grateful that there are people who spend much of their own time developing work to share.
Thanks for your words, and sorry for being rude today.
I appreciate it.
 

deadedge7

Senior Member
Jan 13, 2018
83
10
The only problem with newer 2022 devices is that you can't modify the ro f2fs partitions like system without making it rw and its not possible because I didn't release the script to do yet.
So in my opinion my twrp is stable, otherwise its users fault not following my instructions.
Thanks support twrp and kernel permissive, partition sdcard very good.
SM-X800
/System ro script cool, glad to have you here!
 
  • Like
Reactions: afaneh92

Chaser42

Senior Member
Jun 11, 2015
105
82
Houston, TEXAS
I know this guy for long time, he never said thanks or appreciated people work.
I spent hundreds of hours to get this stable and usable. But people cant read. They want me to spoon-feed them every single moment.
Im supporting nearly 70 samsung device.
I have enough pressure at work and life.
Thanks for your words, and sorry for being rude today.

MOD EDIT: F WORD REMOVED | READ AND FOLLOW THE FORUM RULES

You. Are. Awesome.

I appreciate everything you do. We're very fortunate to have folks like you in the community who are able to be so altruistic just by doing something on the side as a hobby they enjoy.

Stay awesome, my friend. Many thanks for all that you do. :)

Chaser
 
Last edited by a moderator:

liuyc

New member
Nov 28, 2019
1
5
Hello @afaneh92 . I happen to own a Samsung Galaxy Tab S8 (Model X700, CSC: CHN) device. And, I forked your GitHub repository, applied some tweaks to the touch screen parameters, and tested the tweaks on my device. I believe that I have fixed the touch screen problem, at least for my device. My device's TWRP is fully working now. I used its touch screen to run the multidisabler, to flash the custom kernel, and to flash Magisk without any problems. Thank you for your brilliant works! And, I am happy to share with you and the community both the source code and binaries. I will attach the GitHub link of my release below. (Attachment 1/2) I will also attach the same binary here for the communities' convenience. (Attachment 2/2)

---- Attachments ----
- Attachment 1/2: Release GitHub link
Link: https://github.com/liu-yucheng/TWRP-GalaxyTabS8/releases/tag/v3.6.2_12-2-3

- Attachment 2/2: Released TWRP binary
File name: twrp-3.6.2_12-2-3_afaneh92-gts8-yliu-patch.tar
File MD5: EC2D4D1E839C6EA1319C65E1CAD63546
 

Attachments

  • twrp-3.6.2_12-2-3_afaneh92-gts8-yliu-patch.tar
    52.9 MB · Views: 36

Chaser42

Senior Member
Jun 11, 2015
105
82
Houston, TEXAS
Thanks
Hello @afaneh92 . I happen to own a Samsung Galaxy Tab S8 (Model X700, CSC: CHN) device. And, I forked your GitHub repository, applied some tweaks to the touch screen parameters, and tested the tweaks on my device. I believe that I have fixed the touch screen problem, at least for my device. My device's TWRP is fully working now. I used its touch screen to run the multidisabler, to flash the custom kernel, and to flash Magisk without any problems. Thank you for your brilliant works! And, I am happy to share with you and the community both the source code and binaries. I will attach the GitHub link of my release below. (Attachment 1/2) I will also attach the same binary here for the communities' convenience. (Attachment 2/2)

---- Attachments ----
- Attachment 1/2: Release GitHub link
Link: https://github.com/liu-yucheng/TWRP-GalaxyTabS8/releases/tag/v3.6.2_12-2-3

- Attachment 2/2: Released TWRP binary
File name: twrp-3.6.2_12-2-3_afaneh92-gts8-yliu-patch.tar
File MD5: EC2D4D1E839C6EA1319C65E1CAD63546

Thanks @liuyc! So far everything is running smoothly.

Ch42er
 

Chaser42

Senior Member
Jun 11, 2015
105
82
Houston, TEXAS
So I have a question about the kernal patch. I was looking at the notes and it looks like it was made specifically for the kernal in build AVF5. However, I am running the latest update which is build AVG9. Is it normal for this to work? It has been about a day so far everything has been working properly. Maybe I was just lucky? :)

Ch42er
 
  • Like
Reactions: roirraW "edor" ehT

afaneh92

Senior Member
Jul 31, 2012
3,448
4,953
So I have a question about the kernal patch. I was looking at the notes and it looks like it was made specifically for the kernal in build AVF5. However, I am running the latest update which is build AVG9. Is it normal for this to work? It has been about a day so far everything has been working properly. Maybe I was just lucky? :)

Ch42er
If kernel is the same version 5.10.81 or 43 the old one it will work depending on what is yours
 
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I don't know if I understand your directions.

    Might need to reflash stock firmware to decrease vendor size if you are coming from twrp build 3 or older
    Flash this tool on fresh firmware before runnung multidisabler to resize vendor (Build 3 or older)
    then run multidisabler and format data
    reboot to recovery and flash the tool again to resize system
    on Build 4 (from androidfilehost) after running multidisabler, format reboot to twrp then flash zip

    Heres what I think your saying
    I would need to flash stock firmware again
    before then flash twrp after setting up google acount
    flash rw zip
    then do
    - Go to Advanced > Terminal, type: multidisabler.
    If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.
    - Type: multidisabler again. will see - Finished. when done.
    - Go back to Wipe > Format Data > type yes.
    - Reboot to recovery.
    7. Flash custom kernel and magisk apk in twrp.
    8. Reboot to system, Enjoy.

    If thats right I dont understand why running multidisabler before flashing rw makes system to big and how it works if flashing before multidisabler makes system size doable.

    Just a yes or no if im correct is all I need

    Also after flashing twrp I turn off auto reboot and hold volume down and power, when screen goes black I switch to volume up. The instructions don't say to do that. Do you not have to anymore?

    can I just hold power and volume up plugged in?

    feel free to comment anyone any input is welcome
    As I said it need new twrp with size fix, just wait
    2
    I got an error like the guy on telegram did.

    How do I fix it? Wont it make it the same size again if I flash stock firmware?

    You seem very knowledgeable when one ui 5.0 drops for WIFI is twrp, kernel, and root the same or do you have to update it?

    I figure the vb meta file is the same

    Thanks for the help
    Im working on new twrp build, will fix the size and make it work without custom kernel. Need some time for debugging.
    1
    Thanks for that video now im all caught up. I didn't know you could do just the boot.img on samsung. Its nice to have a video to follow along with. I always ask and no one ever says anything. They act like same way its always been but then come to find out its not the same way. I still prefer TWRP, Kernel, and flash magisk. That way you have a recovery to stop boot loops.
    I agree it is a big mess when different information comes from different places. What's a poor boy supposed to do ?

    Is it because different instructions are tied to the older Exynos chip . . . then the newest Snapdragon chip ( like in the ultra ) have a totally different way of doing things ? Does this mangle up @afaneh92 and his work ?

    The twrp mothership keeps loudly beating the mantra, 'must disable dm-verity in the fstab' or you're guaranteed a boot looping brick... . . . . Huh ?

    So Magisk ( thankfully ! ! ! ) gives us root. Magisk comes first and not last like the old way. Then we're still missing a step or two to make twrp happy ? ? ?

    Like in the newer pixel phones, they have to 'fastboot flash vbmeta vbmeta.img --disable-verity' to have custom kernels. What about recovery there ? The pixels have 'NO' recovery. Waa waa waa . . .

    Update Saturday night:
    Received a 'data-only' sim from google fi. My hope was that the internal tablet radios would give me 5G speed data ! Nope. Got LTE 4G, band 41. Carried the plastic slab out to the quiet street and turned 'on' the cell tester app. It said I had -94 dbM of signal strength. That is not a great level and then also not a bad level.
    1
    Heres a question everyone is there a place in the US where you can get the S8 plus tablet with 5G without a carrier?

    Im not finding anything but sometimes you guys know people in Hong Kong that sells them to US.
    Please refrain from attempts to highjack this development thread with posts not related to the development of THIS TWRP. I'm convinced you'll find suitable threads to discuss your generic topics unless you like to create an own one. Please contact me privately in case of further questions but do NOT reply to my post. Thanks for your cooperation.

    I've removed all posts that were triggered by your post. Additionally, I'v subscribed to this thread.

    Regards
    Oswald Boelcke
    Senior Moderator
    1
    Hello!It doesn't work on TabS8 5g, yes?
  • 9
    home.png
    backupname.png

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Code:
     * Your warranty is now void.
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or your getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.

    Supported Models:
    Galaxy Tab S8 X906B, X906C, X906N, X900, X806B, X806C, X806N, X800

    Download & Guide:
    1. Unlock your bootloader.
    2. Downloads for Tab S8: gts8u twrp, gts8p twrp , gts8 twrp and kernel
    3. Reboot to download mode
    4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
    5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
    6. Disable encryption:
    - Go to Advanced > Terminal, type: multidisabler.​
    If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​
    - Type: multidisabler again. will see - Finished. when done.​
    - Go back to Wipe > Format Data > type yes.​
    - Reboot to recovery.​
    7. Flash custom kernel and magisk apk in twrp.
    8. Reboot to system, Enjoy.

    Support:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.

    Telegram group

    Bugs:
    - Encryption not fully working.

    Thanks:
    TWRP team
    @ianmacd for multidisabler
    @Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
    Donators

    Sources:
    Kernel tree
    Device tree: gts8u, gts8p
    8
    Changelog:
    01.09.2022 - Fix touchscreen not working on regular TabS8 thanks to @liuyc
    - Exclude fonts data from backup
    25.06.2022 - Remove unused vm-bootsys mount point.
    - Add micro-sd support.
    - Add touch/keyboard firmware for TabS8 and TabS8+
    09.06.2022 - Initial Release.
    5
    Note1: You need a custom permissive kernel to boot with R/W vendor.
    Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section
    5
    Hello @afaneh92 . I happen to own a Samsung Galaxy Tab S8 (Model X700, CSC: CHN) device. And, I forked your GitHub repository, applied some tweaks to the touch screen parameters, and tested the tweaks on my device. I believe that I have fixed the touch screen problem, at least for my device. My device's TWRP is fully working now. I used its touch screen to run the multidisabler, to flash the custom kernel, and to flash Magisk without any problems. Thank you for your brilliant works! And, I am happy to share with you and the community both the source code and binaries. I will attach the GitHub link of my release below. (Attachment 1/2) I will also attach the same binary here for the communities' convenience. (Attachment 2/2)

    ---- Attachments ----
    - Attachment 1/2: Release GitHub link
    Link: https://github.com/liu-yucheng/TWRP-GalaxyTabS8/releases/tag/v3.6.2_12-2-3

    - Attachment 2/2: Released TWRP binary
    File name: twrp-3.6.2_12-2-3_afaneh92-gts8-yliu-patch.tar
    File MD5: EC2D4D1E839C6EA1319C65E1CAD63546
    4
    ***Moderator Announcement***
    Keep it civil, folks. While you're welcome to differ in opinion, you must treat one another with respect and civility. Flaming and disrespect will not be tolerated.