yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] swoopindown:
Thanks! I did try this, but after the flashing everytime I thought I had the correct keycombo I ended up looking at a black screen again :/ I'll give this another go when I have some more time!
[Galaxy Tab S Android Development] ashyx:
You have to wait for a minute then press any button.
[Galaxy Tab S Android Development] neveser:
Will this work on a T807R4?
[Galaxy Tab S Android Development] :
Please build TWRP and Android 11-12 Custom ROM suitable for SM-T805S. The AP is Exynos 7 Octa 5433 and supports 64-bit.
[Galaxy Tab S Android Development] :
Could you also develop TWRP for SM-T805S (Exynos 7 Octa 5433)?
[Galaxy Tab S Android Development] thaynos:
BRICKED(?) DEVICE PLEASE HELP URGENTLY

https://xdaforums.com/t/help-sm-t805-doesnt-boot.4390585/

ITS RELATED TO THIS THREAD BCZ I USED THIS ROM ONLY
[Galaxy Tab S Android Development] doobre:
Hi all.. a real noob here

This was my first experience at "rooting" a device and it has turned out for the better, with better than expected results.

I had little or no hope in succeeding, but my trusty old SM-T805 that I bought in Dubai in 2014 was just laying around, still perfectly functional, but Samsung had given up on it long ago and it was stuck with Android v6.0.1, while v7 was the minimum required for me to be able to use this tablet with a popular live tv and streaming service app here in NZ.

I followed your instructions and others from this forum, and successfully installed lineage 14.1 +Gapps 7.1.1 using the twrp 3.7.0 recovery image. And somehow I managed to install the deathly kernel as well, I think during a time when I was having no luck getting the tablet to boot into the twrp a second time. I don't know what difference it makes to the tablet's performance now it's working, but you guys will know if that was a necessary step.

I'll list the files and locations below that i used in the end, but needless to say I would definitely recommend doing this to give the excellent hardware a new life.

My main problems were 1. finding the correct files that worked with eachother, & 2. Getting the tab to boot into the twrp, due to either finger trouble (not holding the right combination of buttons for the right time or in the right sequence), forgetting to UNTICK the auto reboot in Odin, and/or mistiming when to press the correct buttons. 3. After starting the lineage setup, the tab stayed at "Checking for updates" screen FOREVER. I read somewhere that you can bypass this by going back and selecting "no wifi connection" at the bottom of the list of available networks. This allowed the setup to complete and the tab found my wifi network anyway. I assume that "Checking for updates" is something to do with the phone network, and since I don't use the SIMM at all, it won't affect my usage. It may be a different story if you want to use your tab as a phone as well, so you could try the lineage setup with and without a simm inserted.. Can't help more..

Thanks to all contributors here for keeping the life in some very good hardware.. cheers CD

========================================

Original Tablet

SM-T805 tabs S 10" LTE & Wifi

android 6.0.1

baseband version = T805XXUICPH6

kernal version = 3.4.39-9086385

build number = MMB29K.T805XXS1CQD1

Bought it in Dubai.

=========================================

files used

lineage-14.1-20170206-UNOFFICIAL-chagalllte.zip

from

https://androidfilehost.com/?fid=817550096634744113

Odin3_v3.14.1

from

https://www.mediafire.com/file/mx44w784bapm2ql/odin3_v3.14.4.zip/file

twrp-3.7.0_9-0-chagalllte.img.tar

from

https://dl.twrp.me/chagalllte/twrp-3.7.0_9-0-chagalllte.img.tar.html

open_gapps-arm-7.1-nano-20210421.zip

from

https://opengapps.org/?api=6.0&variant=nano

=======================================

details today
[Galaxy Tab S Android Development] ¿GotJazz?:
Hi, [MENTION=4899305]ashyx[/MENTION]!

I have an SM-T800, and I have your latest ALL-IN-ONE version installed.

I created a new compressed backup image today that stored off Boot/System/Data.

I tried restoring that image a little later today, and then spent about 8 hours recovering from my experiment. :(

I thought that you had mentioned to me in another posting that I shouldn't restore the Boot sector because if things mess up, I could get skrewed.

When I restored from my image, I didn't select to restore the Boot sector, and the restore process failed with an error I have seen before (E:extractTarFork() process ended with ERROR=255)

My tablet wouldn't boot at all after that, and I had to go back to the latest Samsung stock image. I also couldn't get into Recovery Mode even after I loaded your ALL-IN-ONE., and fought that for quite a few hours because trying the Recovery Mode triple-key press just resulted in a normal tablet bootup instead of a Recovery Mode bootup.

I went through over 6 Odin Stock O/S & ALL-IN-ONE re-installs (with minor variations) until I was finally able to do a Factory Wipe in TWRP and get a clean boot in Samsung.

So ... I'm not mad, just a bit frustrated.

I like to change my installations occasionally, but It seems like I'm having problems with crashing restores from TWRP that I have never had before on any of my other devices. I am getting very reluctant to do anything to my SM-T800 anymore because it turns into a disaster far too often.

Questions:

Is there a problem if I store off the Boot Sector in my compressed image, but don't try to restore it when I do a restore?

Is there something else I might have done wrong?

Is my saved backup unusable now?

Thanks,

¿GJ?
[Galaxy Tab S Android Development] ashyx:
Ok I can understand your frustrations here, however I have to make a few observations and need more info.

Where did you backup to? Did you use Encryption or just compression?

The first observation is regarding booting into recovery after a crash or soft brick.

Unless you overwrite the recovery partition you will always be able to boot into it. Even if boot, system, data, cache are corrupted or completely wiped.

The problem booting to it is purely user error and timing.

I promise I have bricked this tablet in every way and always have been able to recover.

For future reference if you ever crash and can't boot, no matter what state the device is in you can get into recovery this way:

Hold POWER + HOME + VOL DOWN. As soon as the screen goes blank change to VOL UP whilst still holding the other buttons. Keep pressed until recovery boots.

The next observation is that if you restore a stock Rom you will lose custom recovery. Even if you flash it afterwards lollipop will overwrite it with stock recovery. You must boot straight into recovery after flashing twrp. This will patch it so that twrp cannot be overwritten.

You can uncheck auto reboot in Odin to make this easier.

Now I have just done some tests using the exact version posted for your device.

Using compression I made a backup of boot, system and data. I did this 3 times both to internal and external storage. I then restored each time.

On every occasion every one completed with out error.

Unless I can reproduce a problem I can't fix it.

I suggest you make a test backup of just the cache partition then restore it with the exact same settings you are using.

Report back with the results.

Lastly it may be a good idea to use Md5 checking as this will ensure your backup is not corrupted before flashing.
[Galaxy Tab S Android Development] ¿GotJazz?:
Hi, [MENTION=4899305]ashyx[/MENTION] - I'm probably using the wrong terminology, which may be adding to the confusion.

First off, I had Compression turned on, and no Encryption.. I also was storing the image to an External SD card - FWIW, I've seen that listed as a problem with TWRP a few years back.

I have always called going into TWRP "Recovery Mode", mostly because I've seen it referenced plenty of times as loading a "Custom Recovery". TWRP is what I expected to be stored and loaded with the "Boot" backup options in TWRP.

I have considered the Odin-loading Mode on Samsung "Download Mode" or "Fast Boot" Mode. I think that is what you are calling "Recovery" above. The HOME+VOL DOWN+POWER then VOL UP key sequence always worked for this. I have never had a problem getting into this mode.

When I said I couldn't get into Recovery Mode, I meant that I couldn't get into TWRP using the usual HOME+VOL UP+POWER key sequence (BTW, I always press and hold the POWER button last when I go into these modes).

Since I didn't select the Boot checkbox when reloading from my restore image, I figured that TWRP would be totally unaffected. Unfortunately, this was not the case. Is my assumption wrong here?

Yes, I know that loading a stock image wipes TWRP, but TWRP was already gone for me, and I didn't seem to have any options on how to get it reloaded The tablet just had a blank screen when booting. Maybe I should have tried reloading your ALL-IN-ONE again (I didn't think of it until now, unfortunately).

I just did a MD5 check on the previous image I had tried loading, and it did fail the MD5 check. Again, this is odd. I have used this same micro SD memory card for years with TWRP on another device (an Asus Transformer TF101), The card never had a problem storing dozens of TWRP images.

I will leave MD5 checking on from now on.

I successfully did a test backup of the cache partition and restored it previously when I chatted with you before. I also just created a new backup of my current OS install, and it appears to be restoring everything fine. I think I'll copy my External SD Card's TWRP directory over to my home NAS drive to save it off for the future.

I ordered a new micro SD card just to play it safe.

Thanks again for the hard work and great support!
[Galaxy Tab S Android Development] ashyx:
When I or anyone refers to recovery it is recovery mode we are referring to whether it be the stock recovery or TWRP recovery.

Also regarding not flashing boot. You may flash boot if you wish, but its unnecessary unless you need to change it for some reason. Boot is the kernel for booting android.

What I advised you not to do was not to restore the recovery partition backup unless you want to change it to a different version you have backed up.

Nothing will affect recovery as long as you leave it alone.

Try getting used to booting to recovery from a hard reset it will be handy should you need it again.

Basically boot, system and data is all you need to restore if swapping roms.

Having said that its important to have at least one full backup including EFS and MODEM.
[Galaxy Tab S Android Development] ¿GotJazz?:
Sorry, ashyx - my ignorance.

Now that I looked at all the checkboxes available, I see the RECOVERY option available. I was getting that mixed up with Boot.

So, actually, I will save and recover what I have always selected in the past: System / Data / Boot.

Since I'm coming up with a new image, I guess I can save off the EFS and MODEM right now. I didn't see anybody mention it in this thread, but what does the HIDDEN partition hold? The fingerprint and other security related stuff?
[Galaxy Tab S Android Development] ashyx:
Hidden contains nothing important, it's just some sample videos, wallpapers, etc.

I have removed that in my latest builds with F2FS support as its pointless to backup and is almost 200mb.
[Galaxy Tab S Android Development] ¿GotJazz?:
Does anybody have a good F2FS ROM for the T800 yet?
[Galaxy Tab S Android Development] meduza:
A good ROM from a real developer with passion (not ported only) would be enough already ;)

m.
[Galaxy Tab S Android Development] ashyx:
You can use any Rom with f2fs. The kernel needs to support f2fs partitions.

I am currently working on building a stock kernel with f2fs support.
[Galaxy Tab S Android Development] ashyx:
You won't get very far with that attitude. :confused:

Some people put a lot of work in on here. There is no such thing as a Rom that isn't ported. All roms are built from android source code and therefore each Rom is a port to a particular device.
[Galaxy Tab S Android Development] meduza:
...well, it's not an attitude, I just can't find a good ROM for the t800 (yet), that's a fact. Of course it's ported but what I`ve in mind, is build from scretch. That was the case on my old tab with Thor`s tegraowners ROMs. The newest Linux kernel and a fantastic ROM around it, for such an old device like acer a50x and liberty tab.

m.
[Galaxy Tab S Android Development] maxal:
I found a good a good rom for the T800 this one http://xdaforums.com/galaxy-tab-s/development/rom-aicp-nvertigo-cm-sm-t800-sm-t805-t3136250
[Galaxy Tab S Android Development] meduza:
Thx.! Looks interesting... .

m.
[Galaxy Tab S Android Development] ashyx:
Builds updated to 2.8.6.3 - http://xdaforums.com/galaxy-tab-s/development/twrp-2-8-6-1-unofficial-sm-t800-805-807-t3074633
[Galaxy Tab S Android Development] Crescendo Xenomorph:
[MENTION=4899305]ashyx[/MENTION]

Is there any problem flashing wifi T700 version on T705 LTE?
[Galaxy Tab S Android Development] eric194:
hello !

it'll work for t805w canada
[Galaxy Tab S Android Development] ashyx:
Why? :what: Just flash the T705 version.
[Galaxy Tab S Android Development] ashyx:
Should do.
[Galaxy Tab S Android Development] Crescendo Xenomorph:
Coz I wanna try the latest v2.8.7.0 from twrp.me

They only have the klimtwifi for T700 there.... So I'm wondering....

Right now I'm using your v2.8.6.3 build... ;)
[Galaxy Tab S Android Development] ashyx:
I wasn't even aware there was another release as there is no official release post or changelog. This looks like a fix up build.

Not only that there has been no changes to the source code since my last build, so there will be no difference to my build except for my modifications and fixes.

Having said that go ahead, it will flash fine.
[Galaxy Tab S Android Development] Crescendo Xenomorph:
LOL me too...I was looking for 2.6.8.3 ha3g version for my Note 3...

And I saw 2.8.7.0 but its not even mentioned on front page... so I searched for T705 which is none (T705 not even acknowledged on twrp.me)....

OK, I'll flash it later...thank you so much for conformation... ?
[Galaxy Tab S Android Development] ashyx:
Just checked it, same issues as 2.8.6.0 and new ones it seems, wont mount internal storage and log states errors regarding crypto, no f2fs support either.
[Galaxy Tab S Android Development] Crescendo Xenomorph:
Then I'll flash your 2.8.6.3 later....

I havent download the new build from twrp.me either... ?

Thanks for your support... ?
[Galaxy Tab S Android Development] MohamedN:
Update runs amazingly well. Thanks for all the efforts put in this [emoji106] [emoji106]

Sent from my SM-T705
[Galaxy Tab S Android Development] SkOrPn:
Quick question, is it normal for the device to get hot when transferring files from say sdcard to external sdcard? Mine gets into the 60-65c range within a few seconds, and sometimes, but not often, will completely freeze on me and I have to force a shutdown and start over. Just curious if that is normal TAB S behavior, or do I have one of the units that likes to get hot, lol? Thanks

TAB S T700

TWRP 2.8.6.3

By the way, my micro-sdcard is an old one, 16GB Transcend that I used to use on my old Nexus S. Using DiskInfo it says it is formatted using vFat? I used the stock rom to format it though. Maybe vFat is hard on the processor? lol
[Galaxy Tab S Android Development] ashyx:
I don't use recovery for copying files but it's no different to making a backup and haven't noticed any undue heat, but have heard the 8.4 model does get hotter. I use root explorer.

Vfat(Fat16/32) is pretty standard for sd cards. Mine is 64gb and exFat.
[Galaxy Tab S Android Development] SkOrPn:
Yeah I was thinking of going to exFat too, and replacing this card with a 64gb Samsung EVO I think. But for now its all I could find within arms reach, lol. I dont know why, but I couldn't get Root Explorer to work for me on this tablet. EDIT: OK, its working now but I am on CarbonROM at the moment but it failed to launch on stock for me. I got rid of the stock rom because apps kept freezing on me and I wanted to try something different in the hopes the little weird things would stop, lol. I'm starting to think that is why I got this tab so cheap at $190. Although the seller said he needed money asap and hardly ever used it (which it does look brand new thankfully) I think it just did not perform properly for him, so he listed it on CL and kept dropping the price over and over. I finally picked it up when he went below $200 lol (got it for $190) as I couldn't ignore it any longer at that cost anyway. However, it seems to have small issues, overheating and freezing. 90% of the time though it seems to be OK. I wonder if I can tear it down and improve on the thermal dissipation a tad better?
[Galaxy Tab S Android Development] ashyx:
I know the 8.4 tablets have had issues with loose a battery connector causing all sorts of issues.

Someone of your expertise should be able to address that no worries. There is a tut on YouTube how to remove the cover.

By the way I use the Samsung Evo and its a great card for the money.
[Galaxy Tab S Android Development] SkOrPn:
Yeah, I had to redo the thermal sinks/tape with a friends Teclast X98 AIR a few months back, but this TAB S is an entirely different animal as tightly built as it is. Modding in extra storage and full sized USB ports is not happening with this thing, haha. I used to refurb/repair the Vibrant phones and Nexus S devices (In XDA as part of Team Whiskey), but that was fairly simple by removing small resistors and re-positioning them. I built and sold over ten thousand Download Mode JIG's (not counting the several thousand fastboot mode cables for the Kindle world) here in the states before the Chinese got hold of the idea, but manufacturing specialty USB cables is completely different, not to mention my Electronics expertise ended in late 2001 when I left Intel and moved to Lockheed Martin at Sandia Labs, as a Computer Tech instead. The work I did on the Vibrant was work that had to be done through my magnifying station though, and even then I had to eventually slap on a eye loupe at 10x just to see the components good enough. That was 5 years ago, so components on really high tech devices could have gotten even smaller (I have a pic of a Samsung Vibrant resistor and its smaller then the valleys of my finger print, literally). Anyway, I thought I had read that the back cover can easily get damaged when dismantling, so I have refrained from any attempts until I know more.

Still though, If the processor faces the rear cover, there is a good chance that a piece of thin copper pressed against the cover and processor could pull an additional 10c or more from the cpu and be enough to solve the issue, that is assuming there isn't already something like that from the manu. I hope anyway. With that said, I really did not purchase this device for hardware modding, I just wanted something to replace my N7 for reading news articles and tech articles early morning, before arising from bed... lol.

Thanks for the heads up on the EVO :good: I have a Samsung EVO SSD in one of my computers and its a fantastic device for sure. Decided to remove the old microsd and use a Sandisk Extreme USB for now, much faster anyway. Thanks again ashyx

P.S> Today I am going to try your kernel just to rule out if my device does not like the Deathly kernel, which was default on Carbon. Thanks
[Galaxy Tab S Android Development] ashyx:
I think a few have done it without damage.

I don't know if the kernel works as it seems it depends on the firmware you're running.

It seems anything running BEO2 firmware or later will not boot with an earlier kernel and vice versa, so I'm gonna build a kernel using the later sources also.
[Galaxy Tab S Android Development] SkOrPn:
OK, thanks for the heads up on the kernel. I can wait. What I don't like about Deathly is that in CPU-Z it says its set from 100 to 2100 mhz. And if I'm not mistaken I read that 2100 can be unstable. On my N7 overclocking was pretty much mandatory just to prevent it from getting on my nerves. But this device seems like 1900 or even 2ghz is just fine to me. So I want closer to stock for now until I get used to this device and have some experience using it.

Thinking of making a backup, and installing stock again, but the rooted deodexed version, or a rooted debloated version if I can find one. I'm here to test any version kernel you need me to test. I'm now home bound 24/7 so almost always available. :good:

EDIT: OK, I think something is wrong with this micro sdcard, as its been about 3 hours and its still trying to format to exFat, lol. Going to give up soon and just use usb for external storage until the EVO comes in.
[Galaxy Tab S Android Development] ashyx:
You're safe to try the kernel just back up your boot, system and data partition in twrp before converting to f2fs.
[Galaxy Tab S Android Development] ashyx:
All builds updated to 2.8.7.1
[Galaxy Tab S Android Development] deadman96385:
Earlier builds of Deathly were set to 2.1 ghz as the default max but i switched it back to the stock 1.9 ghz before i went on my trip
[Galaxy Tab S Android Development] SkOrPn:
OK thanks deadman. It just said in CPU-Z that it was 2.1ghz so I just thought that is what it is.

TWRP 2.8.7.1 seems to run great so far. Going back to stock rom to see if I can get the storage benchmark apps to work though. I want to compare F2FS to EXT4 on this device but I cant get any of the apps to run. I spoke with the developer of StoreBench and he said after I sent him some logcats and screenshots of terminal scripts, that FIO was not supported or not working on my device. So I have to try stock rom, or a different kernel or both, as part of my troubleshooting.

Thanks guys for the help and fantastic work on this device. :good:
[Galaxy Tab S Android Development] Monster212:
thank you for the update to this awesome recovery.... flashed it and works great
[Galaxy Tab S Android Development] deadman96385:
2.1 Ghz is the maximum you can clock the cpu anything higher is uber unstable, also cpu-z reports the A7's are at 2.1 ghz which is not right they can't go up that high they can only go too 1.6ghz
[Galaxy Tab S Android Development] SkOrPn:
[MENTION=4899305]ashyx[/MENTION], was the reboot to Download Mode removed from the SM-T700 by chance? I can't find it on 2.8.7.1, it seems to be back to the default reboot options, with Bootloader button only rebooting to the system?
[Galaxy Tab S Android Development] ashyx:
Damn I forgot to fix that on the t70x models! Update on its way. :banghead:
[Galaxy Tab S Android Development] Monster212:
i was just going to post about this too..but i see you are on the fix already...
[Galaxy Tab S Android Development] ashyx:
Ok should be fixed now! Sorry. :sly:
[Galaxy Tab S Android Development] Monster212:
yup its fixed thank you so much....
[Galaxy Tab S Android Development] Monster212:
never mind....lol i flashed wrong version..lol
[Galaxy Tab S Android Development] MohamedN:
Backups and restore and all other functionality working amazingly well.

Update is solid, the usual [emoji106]

Sent from my SM-T705
[Galaxy Tab S Android Development] meduza:
short feedback

TWRP 2.8.7.1 + T800 = everything fine :)

m.
[Galaxy Tab S Android Development] SkOrPn:
2.8.7.1 working great on my T700 as well. Thanks
[Galaxy Tab S Android Development] mbl1979:
Been a long time since I've had a Samsung. So the only way to update twrb is with OdIN?? I usually use twrp or flashify. Sorry if you guys think this is a worthless post lol.
[Galaxy Tab S Android Development] rookie12:
Ypu can extrac the recovery.img from the tar file and flash that via flashify or flash with odin using odin method or boot into recovery select instal and select on the bottom right images and flash the recovery img tick recovery you have to extrac the recovery img from the tar file that you downloaded
[Galaxy Tab S Android Development] mbl1979:
Sweet thanks.
[Galaxy Tab S Android Development] rookie12:
Glad I could help
[Galaxy Tab S Android Development] ashyx:
Or flash as is with FLASHFIRE ;)
[Galaxy Tab S Android Development] mbl1979:
That's a new one to me. Going to check it out, I assume its a play store app. :)