yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] zigonneux:
it should be written 3.0.2-1 the buggy TWRP with black screen which hasn't been fixed yet. I'm fighting with the black screen while i type this. Trying to get to TWRP. Don't be surprised if you get a black screen when trying to boot to TWRP , it look like a normal thing on these days. For the T800 anyway.

This prevent me from testing various ROMs as I'm very tired to fight with TWR and that blackscreen. But there are no alternatives.
[Galaxy Tab S Android Development] meduza:
...?? What about 2.8.7.2 ? I just used it ... . Don't have any problems with 3.0.2-1 as well.

m.
[Galaxy Tab S Android Development] zigonneux:
I might revert to 2.8.7.2, the bug is there only when we try to reboot to TWRP directly from the Rom. With the buttons when the tab is OFF it work ok.
[Galaxy Tab S Android Development] DBCAB:
I use the 3.0.2-0 , and have had no issues I did see on the twrp page here a second download where black screen is fixed if i remember correctly.
[Galaxy Tab S Android Development] meduza:
... to 99% I boot from the ROM...

Seems to be kind of strange issue like the Wi-Fi drops... .

m.
[Galaxy Tab S Android Development] zigonneux:
I'll reflash again to see if it will fix the problem.. TWRP is the most useful program out there, so I'll work on it.

this time, reflashing seemed to fix the issue. Rebooted from Rom went straight to TWRP. Strange , because I"ve already flashed again after the fix..anyway, it's working now. Good !
[Galaxy Tab S Android Development] meduza:
Glad to hear! Step by step we getting cured from our issues :)

m.
[Galaxy Tab S Android Development] zigonneux:
yes indeed ! I'm thinking that because TWRP used to work fine for a while when rebooting from Rom and then just stop working after a restore, it look like when we restore too much we can break the "reboot to recovery" . This is from the asps rom most of the time. So the trick is if it stop working well, flash it again.... easy !
[Galaxy Tab S Android Development] meduza:
Yep, similar like with ROM issues sometimes :)

m.
[Galaxy Tab S Android Development] ¿GotJazz?:
I'm having a problem with my SM-T800 and TWRP 3.0.2-1

My SM-T800 had TWRP 3.0.2-0 installed, and I was rebooting my tablet this morning. The tablet went into a Recovery Mode bootloop with TWRP 3.0.2-0 where it never entered into Recovery Mode.

So, I downloaded and installed TWRP 3.0.2-1 through Odin.

I saw the same problem occurring with TWRP 3.0.2-1 - A Recovery Mode bootloop.

When nothing worked, I decided I would try reflashing TWRP 3.0.2-0, and now I was able to boot back to Normal Mode (whew! :)). However, when I attempted to create a backup, the tablet rebooted.

So, I reflashed TWRP 3.0.2-1. Again, the tablet went into a Recovery Mode bootloop.

I reinstalled TWRP 3.0.2-0 for now. I can at least get back to Normal Mode to use the tablet again with that Recovery Mode installed.
[Galaxy Tab S Android Development] Tilagoon:
Try to flash TWRP 2.8.7.0 !! :)
[Galaxy Tab S Android Development] ¿GotJazz?:
Thanks, [MENTION=4449541]Tilagoon[/MENTION] for the suggestion on TWRP 2.8.7.0

I have been able to get TWRP 3.0.2-1 booting stable (for now, anyways). Not sure what changed, but I'm OK with it as long as it works.

Well... about that "as long as it works" part ... Recovery Mode doesn't restore from my previous images. I can't seem to restore any of my recent backups that have a Data partition, even though they pass all the MD5 checks. I have Encryption turned "Off", and Compression turned "On".

Each recovery image I try to restore with a Data partition results in a extractTarFork() process ended with ERROR: 255 error message. :(

I'd really hate to have to rebuild from scratch, especially when I have to explain it to my wife. :eek:

P.S.: Not sure if it matters, but my Data partition was formatted as a f2fs patition.
[Galaxy Tab S Android Development] imp3r10:
I installed the latest version and when I try to create a backup it hangs up when creating the md5 for the data. Anyone know why it does this and how to fix it?
[Galaxy Tab S Android Development] zigonneux:
one thing you could fix is to buy your wife a tablet so that you don't have to explain anything :D

The same thing happened to me once, since then all my restores work fine. Did you do your backup with the same version of TWRP ? f2fs should not be a problem for DATA. With MM6 it's rather easy to reinstall everything .
[Galaxy Tab S Android Development] ChewVodka:
Wow, I'm glad this thread exists and it's not just me. I'm having a heck of a time here, and I thought it was my noobness because I've just now for the first time jumped into the "deep end of the pool" as it were with rooting. I've never done it, don't know what I'm doing, and thought I broke it. I've been having this issue where TWRP won't load. All I get is a black screen. I had it working once, and even have a few backups. But then I installed CyanogenMod and it stopped working when I tried to use TWRP Manager to make another backup. Strange thing is, sometimes if I tap the screen, the vibrator buzzes, so something is there, the screen is just black. I've tried reflashing TWRP once, but not multiple times as suggested by some people here. What I have ended up doing is going through the whole process from square one, reinstalling the stock firmware, rooting it, then try to reflash TWRP again, to no such luck. It's driving me bonkers because I've not done ANYTHING different than what I had been doing. I'm going to try multiple flashes (rebooting into Recovery first each time to see if it works). I just don't know what to do.
[Galaxy Tab S Android Development] zigonneux:
I've flashed it multiple time and it's still unstable, often fighting my way to TWRP still. It's better to power off, then boot TWRP the old fashion way,

Power off your device completely.

Press and hold Volume Up, Home and Power buttons simultaneously.

Release the buttons when the phone's screen flickers or the Stock / TWRP Recovery logo appears.
[Galaxy Tab S Android Development] ¿GotJazz?:
Hi, [MENTION=7000441]zigonneux[/MENTION] - Best suggestion I've heard all day! :)

Yes, I did all my backups with the same version of TWRP. In fact, I created a new one yesterday using my current (TWRP 3.0.2-1), and it failed again on the Data restore with the extractTarFork() process ended with ERROR: 255 error. The Boot and System restores worked fine.

I found what appears to be a workable solution. I reset the F2FS Cache and Data partitions back to ext4, and reinstalled TWRP 2.8.7.0

I created a new backup, and restored everything fine.

Maybe not the "latest and greatest", but "old and reliable".
[Galaxy Tab S Android Development] zigonneux:
anyway, if you plan to test the new N7, F2FS is not supported and twrp 3.0.2-1 is very hard to reboot to.....
[Galaxy Tab S Android Development] nirh216:
Did exactly as you said,

Uncheck Auto reeboot, use the POWER + VOL DOWN + HOME when the screen goes black, change to the VOL UP and keep other buttons, black screen, when I touch the screen it vibrates but can't see anything (even after 30 sec)

I have android 6.0.1 Germany ROM

sammobile.com/firmwares/download/89326/T805XXU1CPH5_T805OXA1CPH6_DBT

I have Galaxy Tab S 10.5 LTE

What can I do?

Thanks
[Galaxy Tab S Android Development] ashyx:
You have to wait for screen time out, this will kick start the display driver.

Timeout is usually 60 secs as default then press home or power.

Workaround is to set the timeout to minimum.
[Galaxy Tab S Android Development] nirh216:
The timeout is something that I can choose there?
[Galaxy Tab S Android Development] ashyx:
It's in twrp settings.
[Galaxy Tab S Android Development] zigonneux:
ho i was wondering where was that setting, so it should improve my experience with twrp quite a lot. Blank screen right now and TWRP never kick in after 1 minutes if i press any buttons, i've been waiting for 2 minutes after the first attempt a coming out of the black screen, so I'll try to get TWRP back on track and find that setting.

I never mentioned it before but i've tried the "wait a minute"solution many times and it never worked for me anyway.

Cheers !

and thanks for TWRP ,ashyx, it might be buggy but it so useful

EDIT : The screen timeout option was OFF by default, so this is why it never kicked in, now it's a 30.... I never used screen time out because i dislike the fact that I have to do everything very quickly before i get a blank screen while using TWRP..but it's easy to come back to it.
[Galaxy Tab S Android Development] ChewVodka:
I don't know if it's been mentioned, but I found a possible fix to the BLACK SCREEN OF DEATH... It's been bugging me ever since I installed my root, but it seems to be working so far. I still want to play with it a bit more but I think the whole black screen issue is fixed with this method:

Start from Stock

Root via ChainFire autoroot with TWRP (http://xdaforums.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488)

Boot into TWRP before booting into OS to make sure TWRP is working....

Boot into OS and download the TWRP 3.0.2.0 IMAGE (not tar) (https://dl.twrp.me/chagallwifi/)

Reboot into Recovery

Install, change to Install Image

Select the 3.0.2.0 TWRP

It'll give you the option to select the partition, just install the RECOVERY one...

It's flashes...

Boot into Recovery to make sure it takes...

Power Off, On, boot to Recovery via TWRP Manager, etc.. all works after 24 hours of checking...

Problem solved? I think the problem is that the boot partition of the image isn't programmed right. I don't know anything about any of this really. I'm a tinker'er and I play with stuff till I got it working. This seems to have worked for me. It'll probably break something else in the long run, but for now... you success may differ, but I thought I'd at least pass it along. :) You probably don' t need to start from Scratch like I did. If you can get the older TWRP to install with the older BOOT, the solution should be then to use that and then just flash over the new recovery partition only.

-----------------

EDIT - This doesn't work with the latest (May) nightly of CyanogenMod. I had hoped this would fix the problem. I even re-rooted as per instructions (to get the older TWRP installed) after installing CM. The older TWRP works great, but once you try to put the new version on (without flashing the BOOT partition) the screen starts going black again.. back to the drawing board I guess... :(
[Galaxy Tab S Android Development] UBorba:
My SM-T800 was OTA updated to Android Marshmallow 6.0.2.

It this method compatible with this latest Stock firmware?
[Galaxy Tab S Android Development] mickrick:
I just flashed this twrp on my T800 and now I'm getting a red notice in the top left corner when booting into recovery "recovery is not seandroid enforcing". What's happening?
[Galaxy Tab S Android Development] ashyx:
Don't worry about it, it means nothing.
[Galaxy Tab S Android Development] mickrick:
Its the first time I've seen it and I've had my T800 unlocked, twrp'd and rooted for well over a year. I even redid it after installing 6.0.1. Maybe its the latest version of twrp doing it?
[Galaxy Tab S Android Development] ashyx:
It's because of the MM bootloader. Previous bootloaders didn't flag it.
[Galaxy Tab S Android Development] Tinderbox (UK):
Hi.

I am trying to install twrp on my T800 with odin in download mode, over the stock UK OTA version of MM, odin says the flash was ok, but when i boot into recovery it`s just the standard android recovery and not twrp

Anybody know what i am doing wrong.

John.
[Galaxy Tab S Android Development] NeWONEx:
Boot into Recovery immediate after flashing. This happened to me sometime
[Galaxy Tab S Android Development] LauRoman:
First off, uncheck autoreboot in odin. Second, you have to act fast. You have to reapply twrp and follow these steps because twrp was overwritten after the reboot. Go into download mode and flash twrp with odin (IMPORTANT: uncheck autoreboot). After odin confirms success flash, press button combo to get into download mode (power + vol. down + home button) but DO NOT LET IT GO INTO DOWNLOAD MODE. Act fast, as soon as you see a completely black screen ( i.e. no samsung or android logo, however depending on the bootloader you use you might see som red and/or yellow text about knox or seandroid, you can ignore that), move your finger quickly from vol down to vol up while not letting go of the other two buttons. If you fail and the tablet goes into download mode you just have to try again to go into download mode but when the screen is black move finger from vol down to vol up while holding the other buttons. However if you fail and the phone reboots into android, you must go into download mode, reapply twrp and do the button ballet again.

Once you get to twrp flash your favorite ROM (i.e. "official" CM for the SM-T800). As soon as you put a custom rom on it twrp will not be overwritten at (re)boot.
[Galaxy Tab S Android Development] Tinderbox (UK):
I manged to get into twrp, but do i have to flash a rom from twrp as i forgot to put a rom on my microsd

EDIT: I just powered off and then booted into twrp so it`s still there, shoould i flash the full MM 1.5GB over the OTA MM 800mb or do i not need to bother, Can i now install superuser with twrp?

John.
[Galaxy Tab S Android Development] NeWONEx:
Connect your tab to PC and move it or use your Sdcard adapter.
[Galaxy Tab S Android Development] Tinderbox (UK):
I just installed supersu with twrp over the OTA MM and i now have an supersu icon, I will just download a root checker, that button switch after flashing with odin is something new since OTA MM i have had downloaded rom of the New Zealand MM on my T800 and flash back and forware with lollipop and kitkat.

Is there any advantage in flashing a full 1.5GB MM rom over the 800mb OTA MM version, or does it make no difference now.?

EDIT: Root has been confirmed :)

Thanks

John.
[Galaxy Tab S Android Development] LauRoman:
If you feel adventurous you can remove your sdcard while tablet is on and in twrp mode put a custom rom on it, put it back in the tablet and reboot into twrp again from the twrp menu. However i would suggest you turn off the tablet from twrp, remove sd card and load it with a rom and put it back in the tablet. Then use button combo power + vol up + home to go int twrp and apply rom from there. Do not forget to also load the card with gapps and/or supersu (if you're into that sort of thing). Just remember, phone bust not boot into android unless you installed a custom rom because elsewise you will lose twrp.
[Galaxy Tab S Android Development] NeWONEx:
He need to reflash TWRP inside the TWRP or he can use FlashFire if he already rooted his device.
[Galaxy Tab S Android Development] Tinderbox (UK):
I have an hardcase on my T800 so getting to the microsd is a major event, I have installed Flashfire before but not used it, So i can use it to flash the full 1.5GB MM over the 800mb OTA MM and still keep root and twrp?

I dont really need to do it, but would that work.

John.
[Galaxy Tab S Android Development] ashyx:
No you dont need to install a rom or anything else.

Just boot to recovery immediately after flashing twrp is enough to make twrp stick.
[Galaxy Tab S Android Development] Tinderbox (UK):
LauRoman showed me the odin disable reboot and the quick button move after flashing twrp with odin.

EDIT: I found It. Is this new method mentioned in post 1 for other members to follow.

Thanks for all the help

John.
[Galaxy Tab S Android Development] LauRoman:
True, but i was suggesting the "by the book" method that is common to most rom flash guides, which assumes you have no root and arr on a stock rom. Using your method he/she might have to reapply supersu if they want/need it. Using the classic method supersu is not needed beforehand and cam be applied or not after the fact.

That button ballet is not new. It is done for every device with a non removable battery and has been done for years. Unless the battery is removed after flashing twrp with odin there is no way to get from download mode to twrp on most high end devices. Phones similar to the galaxy core 2 and the like can have twrp flashed from stock recovery but those are lower end and/or less secure devices.

That's true, but i was never in a position to see that part in action. Because i never flashed a custom recovery without flashing a custom rom too and as soon as the custom recovery was up i flashed the rom and what aditional bits i needed. [emoji4]
[Galaxy Tab S Android Development] ashyx:
Its in the OP.
[Galaxy Tab S Android Development] Carlosk1966:
Factory firmware

Hallo ashyx.

I want to flash factory firmware with image install. I am on Slim 6 and my bootloader is

T800XXU1CPH7. I know i need to flash BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN.

What about bootloader (SBOOT.bin)? Do i need to flash separatly with Odin or something else?
[Galaxy Tab S Android Development] Tilagoon:
Hi,

If you flash a stock Samsung ROM with Odin you have just to flash the ROM and nothing else !! :o
[Galaxy Tab S Android Development] ashyx:
Sboot.bin is a protected partition that twrp cannot flash. You would need to use ODIN.

If you are already running a Marshmallow rom then you won't need to flash the bootloader anyway.

Also if you want to flash the other partitions you'd be better flashing them all in one go using Flashfire.
[Galaxy Tab S Android Development] Carlosk1966:
I know that. I want to flash Samsumg ROM with TWRP. Thanks any way.

---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------

Thank you ashyx for the explanation. :good:
[Galaxy Tab S Android Development] LukasLudwig:
Black screen

Hi,

i flashed TWRP for 805, after the installation a Rom, i have now a Problem to Boot into the recovrry. When I press the recovery button combination, during the Tab s Bootscreen a red Text appears in the upper left corner, i remind something like " not Standard recovery. enforcing" , than the text turn into blue and after that the screen turns complete Black, i got only haptic Feedback when I Touch the Sensor Keys, to reanimate the Tablet i used the download Mode combination.

should i Flash TWRP with Odin again? this code not Touch my Rom or data, only replace the Kernel??
[Galaxy Tab S Android Development] DoubleYouEmSee:
Background: I have the SM-T807P Sprint version (Snapdragon), and I have your 2.8.5.0 version of twrp working, successfully flashed with Odin. I also got it rooted with CF-Auto-Root.

I originally had tried to flash in this recovery, because it's newer and I thought from the description that it was supported. However, while it would flash successfully through Odin, auto-reboot unchecked, rebooting into recovery immediately afterward would fail, with a message something like "couldn't do normal boot" and then drop me into download mode.

So my question is simply, does this work on SM-T807P, and if so, what did I do wrong?
[Galaxy Tab S Android Development] programator:
Works with SM-T805

Galaxy Tab S 10.5 German Telekom

T805XXU1CPH5 / MMB29K

MM 6.0.1

SuperSU 2.78

ur TWRP-3.0.2-1-T805/T807

Thanks so much...

Had to reflash to stock for Encrypting, so:

1. Flash Stock (ODIN)

2. Encrypt Internal (/data)

3. Flash Recovery (ODIN)

4. Boot Into Recovery flash (install) SuperSU from unencrypted external SD-Card

5. Reboot and encrypt external SD-Card

so now i have MM 6.0.1, TWRP, SuperSU and Encrypted Device (Internal (/data) and External SD-Card)
[Galaxy Tab S Android Development] roselanguste:
No, it works not with Snapdragon-Processor! Only Exynos!

---------- Post added at 08:05 PM ---------- Previous post was at 07:59 PM ----------

What do You mean with "this code not Touch my Rom or data, only replace the Kernel"!?

Installing TWRP don't do anything with Your Kernel? It is only a Recovery!

Sometimes something went wrong by flashing a recovery!? Try to flash it again!
[Galaxy Tab S Android Development] malosasha:
Hi di you upload your commits anywhere ? i m facing the black screen bug on T805 and i would like to check if itis possible to kick a first timeout of 1 second then restore normal timeout.

Regarding adb , my devices is not always listed with adb devices , i did not yet found a pattern for this. Any idea how to enable each time adb daemon ?

Br
[Galaxy Tab S Android Development] ashyx:
You would have to modify this in the twrp source code itself or you could modify the .twrp settings file.

However as soon as you open the settings page for timeout it will revert to the current setting.

Regarding adb it should be enabled each time as long as mtp isn't enabled.

You also need to check your PC drivers in device manager for this if you're having issues.

You could try in terminal:

start adbd

On the PC side:

adb kill-server

adb start-server

https://github.com/ashyx/TWRP_Samsung_klimtlte
[Galaxy Tab S Android Development] malosasha:
I m on linux , so this is not a device driver issue i think.

If mtp is enabled at AndroidOS level this can influence the recovery ? i tought that recovery was taking params only from /Cache ?

The mtp device appears under nemo btw.
[Galaxy Tab S Android Development] ashyx:
Mtp mode disables adb in recovery and not related to mtp in the os.
[Galaxy Tab S Android Development] malosasha:
ok thanks guess i was blind didn't saw mtp options in twrp :)
[Galaxy Tab S Android Development] codexc:
Hi,

i tried to flash your TWRP but it does not work for me, i trying to enter the recovery mode i facing a black screen .

someone can help ? i have TWRP 2.8 and it is working fine .

---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------

also this one (https://dl.twrp.me/chagalllte/twrp-3.0.2-0-chagalllte.img.tar.html) , i flashed it via TWRP and Odin but same problem (just black screen)
[Galaxy Tab S Android Development] Namoi:
It is a known issue for some devices. Search the thread for a workaround as i don't remember exactly how to solve it (disabling screen time out i think).
[Galaxy Tab S Android Development] ashyx:
It's even posted clear as day in the OP. [emoji19]
[Galaxy Tab S Android Development] Namoi:
Indeed it is... but I'm in a good day with plenty of spoons in my hand ready to be fed in ;)
[Galaxy Tab S Android Development] Vomisa:
Problem after installing this TWRP and flash SuperSU

Hi,

I installed this TWRP to my tablet (805) and flashed the following SuperSU (SR3-SuperSU-v2.78-SR3-20161103171345.zip) to my tablet.

At first sight everything worked correctly. But then I noticed, that the tablet slowed down and had frozen a couple of times and no reboot helped.

There were also problem with charging, because it could not go over 70%

Know I put back the original Marshmellow version, but I want to root the tablet.

Did some of you faced with such problems? What could I do?

Thanks,

Vomisa
[Galaxy Tab S Android Development] ashyx:
You don't have to use sr3. Pretty much any version of SuperSU will work. Try Sr1 or SR4. However I highly doubt root is causing the issues you've stated.
[Galaxy Tab S Android Development] malosasha:
i was facing the black screen bug with sm-t805; after flashing stock 6.0.1 MM and reflashing twrp ; i now don't have it anymore.