yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] Deltadroid:
Yes, heimdall can be used to only update partitions that lineage does not touch.
[Galaxy Tab S2 Original Android Development] tzinaski:
Could you give me more detailed instructions?

I haven't used heimdall and to be honest, it seems a little intimidating.

Can i download the latest bootloader file (as a separate file from the stock rom) and flash it using twrp?

Is this something feasible?

And where can i download the bootloader as separate file, from sammobile?

Thnx for your help
[Galaxy Tab S2 Original Android Development] Deltadroid:
You would have to download latest stock rom on sammobile or whatever and extract it. After extracting the tar, each file inside is a separate partition on the tablet. You want to flash all of them with heimdall, except cache, boot, recovery, and system partitions. You would not want to overwrite any partitions that TWRP or Lineage uses. This will require Linux and building heimdall from latest sources. You can figure out how to flash the various partitions on your tablet by using heimdall to print the pit file first.
[Galaxy Tab S2 Original Android Development] bono82:
flashed my sm-t713 with the 20190809 build and all seems to work great, managed to disable the h/w keys using generic.kl , strangely though it doesnt seem to stick after reboot, keys are commented out but still they work :/

only thing i did was to disable root access for apps in lineage settings, maybe this messed with it somehow? have tried to edit the file again and saving + rebooting, but no help..
[Galaxy Tab S2 Original Android Development] :
I have never managed to use heimdall (Windows version) with this device. Every time I try to do a print-pit, it fails saying that it can't start the protocol or something to this extent. I am now using Odin to update to the latest stock firmware and then I'll go back to LOS. Quite annoying.
[Galaxy Tab S2 Original Android Development] :
Guys, very slightly off topic... Has anybody tried to install LOS starting with the latest Samsung firmware (for Switzerland it's dated April 4, 2019).

I can install TWRP without any issues but it won't start. When I try to boot to recovery the tablet says "cannot do normal boot" and goes into download mode.

Otherwise everything works.

If I downgrade the firmware, I won't be able to install newer versions of LOS, so I'd like to understand what's the problem here.

Any idea?

P S

Never mind. I flashed everything one more time and now the problem disappeared. Go figure...
[Galaxy Tab S2 Original Android Development] Deltadroid:
If you booted into stock ROM, then make sure your device is OEM unlocked and you have formatted the data partition.
[Galaxy Tab S2 Original Android Development] :
OEM unlock is selected and I can't format the data partition if I can't start TWRP! Any other ideas?

I almost finished downloading a slightly older firmware release to see if it makes a difference.

P.S.

See above: I tried once again with the latest FW and for some inscrutable reason it worked.
[Galaxy Tab S2 Original Android Development] sliding_billy:
I have been using my T713 with [lineage-16.0-20190803-nightly-gts28vewifi-signed] installed for almost a week now. Originally, no matter what I did the first reboot after finishing setting up the device and rooting would get hung at the lock screen (I was using a PIN), so I installed once with no PIN and everything worked. On a whim a day or so ago, I enabled the PIN in security. Multiple reboots were fine including a fresh boot (after being powered down for the day) a few hours ago. I did a reboot about a 1/2 hour ago, and again it loops back to the lock screen endlessly after entering my PIN. I know it is accepting the PIN (if I enter a wrong one it tells me it is incorrect), and processes are running since notification chimes continue after the loop. I am rooted with Magisk 19.3 and using [twrp-3.3.1-0-gts28vewifi.img] and [open_gapps-arm64-9.0-nano-20190803]. I would love any ideas that don't involve me reinstalling again since it took me about 1/2 dozen installs to get it working the 1st time.
[Galaxy Tab S2 Original Android Development] rlw6534:
I have had the same problem periodically. Flash the attached zip from TWRP and reboot. It removes the PIN config. Credit to [MENTION=5480152]followmsi[/MENTION]...
[Galaxy Tab S2 Original Android Development] sliding_billy:
Thanks, [MENTION=4758417]rlw6534[/MENTION]. The .zip worked, and I had no issues adding the PIN back and rebooting/entering PIN. I assume the user is doing something that causes this to happen but who knows what. If it was random, you'd think eventually it would work on a hard reboot. Also, hard to believe that it is not better documented. I never saw this searching (here and Google) the first bunch of times I installed or before I posted this question a few hours ago. I get that it hasn't been fixed yet, but it not showing in the OP of any impacted lineageos threads or even in the los install guide is hard to believe since it is such an easy short term fix. At least the the .zip is sitting safely on the device now for the next time.
[Galaxy Tab S2 Original Android Development] rlw6534:
I never figured out what specifically triggered it, but it seems to occur almost always at some point after a ROM update using the integrated LineageOS updater. Did you recently update to the latest build, perhaps? Maybe I will try the update from TWRP next time. Glad that I could help!
[Galaxy Tab S2 Original Android Development] sliding_billy:
No, in fact I only started using LineageOS on this device during my initial install last week. (I had been using stock rooted for a long time). I actually installed it the first time with the 0802 build but started over from scratch with 0803 since it was available by the time the first install failed to get past lock screen. I have ran the updater and refreshed, but that was just for my own curiosity since I had read (I think on the LOS wiki) to not use the updater but to sideload through TWRP. That was actually what my next step was if I didn't get this resolved. I was going to try dirty installing 0810 since there was not an update yesterday when I looked in the updater last night.

Question for you. Are you rooted with Magisk, and if so do you use any modules? The only thing that changed before reboot last night was a Magisk module updated (MagiskHide_Props_Config-v4.0.1-v52).
[Galaxy Tab S2 Original Android Development] rlw6534:
Yes, I'm rooted with Magisk (19.3). The only module I have installed is QuickSwitch (with Lawnchair set as recents provider)... I've been having this problem for months, which is why I had the PIN removal zip. I have not yet figured it out. The first few times I had to do a clean install... :(

I may try to root with the lineage root module, rather than magisk to try and narrow it down some...
[Galaxy Tab S2 Original Android Development] sliding_billy:
[MENTION=4758417]rlw6534[/MENTION] - Instead of continuing to blast this thread with new posts, I just edited my last one. I had some time today to see if I could for it to lock/re-lock. First, I ran all of my apps and normal OCD type checks. The only change was a definitions update to adaway, yet it locked up again. There was no adaway update last night before it locked, so I figured that wasn't the issue. I thought you might have been onto something with updater despite me never having ever used it for anything other than manually checking for updates and turning off notifications from the auto-check. It occured to me that I turned that notification off last night when I was notified that there were lineage updates available, so clearly the auto-check had ran last night. I remembered that it was set to weekly, and that I might have tried checking other times when I would get stuck on lock screen at 1st reboot. So after messing with some things related to that module that updated last night, i ruled it out and went to the updater. I did nothing but manually check for updates after a successful boot, and on reboot it hung. I cleared the loop, reset my PIN and booted clean again. This time, I opened the updater but didn't check. I just changed the auto-check frequency to never. I rebooted with no issues. Unless there is something else that I haven't found, the thing I can pin the PIN loop down to is updater checking either manually or automatically. If you feel like testing, you could try manually checking and change it to never if my hypothesis is correct.
[Galaxy Tab S2 Original Android Development] Limitscrw:
Anyone else notice a huge improvement in battery life with the more recent builds?

This is awesome now!

Props to the dev. :good:
[Galaxy Tab S2 Original Android Development] grmcdorman:
The latest SM-T713 ROM (PDA T713XXS2BSG1, CSC T713XAC2BSB1) from Sammobile only contains a *_HOME.tar.md5. Other files I expect to see - AP, BL, CP - are missing. I don't think the single available file is suitable for updating just the bootloader (BL) and modem/radio (CP).

EDIT: That's via Odin. I don't know how to use Heimdall, and it does not seem to work for me (W10, Samsung drivers installed; get "libusb error: -12").
[Galaxy Tab S2 Original Android Development] Deltadroid:
Rename *.tar.md5 to *.tar and then extract it with "tar -xvf *.tar"
[Galaxy Tab S2 Original Android Development] grmcdorman:
Yes, or on Windows use 7Zip, which understands tar files (I believe I mentioned I'm running Windows 10). But Odin doesn't support individual files, and Heimdall doesn't work for me. I suppose I could use TWRP to flash boot.img? ... but if that messes up the bootloader I've got a problem.

It looks like, under Windows, that Heimdall requires installing a special USB driver, as well; I'm kind of reluctant to do that as the documented procedure included with Heimdall Suite (1.4.0) does not seem to be correct for my situation.

Question I have, though, is: is there a way to flash the specific bits using Odin? I'm presuming that the bootloader is not enough.
[Galaxy Tab S2 Original Android Development] Deltadroid:
You do *not* want to flash boot.img. The boot.img is the kernel, not the bootloader. Updating the firmware, ie; bootloader and trustzone, should *not* be done with TWRP. Use only Odin or Heimdall.

The Windows version of Heimdall does not work with this device because it is too old. In order to use Heimdall, it must be built from latest sources with Linux.

Just flashing the bootloader file is not enough.

Hint: this is the command that I use with Heimdall and all of these components must be flashed at the same time:

heimdall flash --SBL1 sbl1.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --HYP hyp.mbn --SEC sec.dat --KEYMASTER keymaster.mbn --CMNLIB cmnlib.mbn --DSP adspso.bin --MODEM modem.bin --APNHLOS NON-HLOS.bin

I can't really tell you much about Odin because I've never used it.
[Galaxy Tab S2 Original Android Development] rlw6534:
[MENTION=4609886]sliding_billy[/MENTION] - Yes, I triggered the PIN loop simply by checking for LineageOS updates. I fixed it with the PIN removal zip and reinstalled the PIN and tried checking for updates multiple times and it did not loop again (which seems odd). I'm pretty sure that was the first time I had checked for updates after upgrading yesterday. I already have the latest build installed (8/12) so I can't actually upgrade to see if that makes a difference (i.e. checking versus checking AND updating). The only difference I noted was that when I checked the first time (and PIN looped), I got a connection error (the update check failed, please check....) and the subsequent checks did not. Maybe that is a clue...
[Galaxy Tab S2 Original Android Development] sliding_billy:
Interesting. I wonder if it has to do with an update being "found" (like would happen if you processed a daily with updater), and since your subsequent checks found nothing new it didn't loop. It is like it is writing a system file that jacks up the PIN when one is available and added to the list of available updates in updater (even though you are not downloading and installing ). Either way, I will be keeping the automatic check on "never" at this point since I would be downloading from the computer and not the phone anyways. Thanks for checking.
[Galaxy Tab S2 Original Android Development] :
Hello. I installed LOS on top of the latest Samsung AUT firmware (April 4, 2019) and I noticed that wifi is now slightly unstable. When I try to download large files it tends to disconnect after one or two minutes. I also had a few other random drops.

I performed a clean install: flashed the full firmware, flashed TWRP, wiped system and formatted data and finally installed LOS, GApps and Magisk.

Has anybody else seen this issue?
[Galaxy Tab S2 Original Android Development] rlw6534:
[MENTION=4609886]sliding_billy[/MENTION] - Checked for update - found todays build (8/13) - rebooted / no PIN loop; Installed todays build - booted automatically / no PIN loop. Rebooted a couple of times including Power Off / no PIN loop. Updated AdAway hosts (not systemless) -

rebooted to a PIN loop

. Repaired PIN, - rebooted - disabled adaway - rebooted / no PIN loops. Enabled systemless hosts in Magisk - rebooted / no PIN loop. Enabled adaway (systemless) - rebooted / no PIN loop. Not sure what's going on but figured you might want an update. Of course I can recover, but it is a mystery and a head scratcher... As I said before, I never have figured it out... I just keep the PIN removal zip handy.... ;)
[Galaxy Tab S2 Original Android Development] sliding_billy:
That is too funny since the 1st PIN loop I got was after installing Magisk systemless hosts and systemless Adaway I am starting to think the safest course of action is juts not to turn on the PIN ever. Hard to believe nobody in this thread is seeing this and/or knows anything about it.
[Galaxy Tab S2 Original Android Development] RoterfuX:
Thanks that will help me too, I also need to update. I've got heimdall running on my laptop and can detect the device. How do I know which Firmware I need to download from Sammobile? I couldn't find any information which product code my tab has or is this unimportant and I can just take any?
[Galaxy Tab S2 Original Android Development] Deltadroid:
Choose the latest T713 version for your region.
[Galaxy Tab S2 Original Android Development] RoterfuX:
Wasn't sure which one I should take, but checked the manual and the package and everything is French. Took a bit to find it...

Thanks!
[Galaxy Tab S2 Original Android Development] bart3005:
Latest build install 20190813 error

I just tried to flash the latest build 20190813 and I get an error.

Assert failed: samsung.verify_trustzone

Compaing TZ version

Using the latest TWRP, do I need to update something else?
[Galaxy Tab S2 Original Android Development] RoterfuX:
You need to update the bootloader etc. Just check the first posts on this page and you get all information
[Galaxy Tab S2 Original Android Development] bart3005:
The latest region firmware was very old on sammobile, so I just downloaded another region which would be similar. Now fixed and working.
[Galaxy Tab S2 Original Android Development] sliding_billy:
So tonight after about 12 hours with the device powered down after doing literally nothing (other than letting it settle in for a little while after boot) but getting a boot with no PIN loop, the first power on gets a PIN loop. That's the end of me bothering with a PIN unless/until this issue gets resolved.
[Galaxy Tab S2 Original Android Development] dwedw:
I have exact the same problem, cannot flash any update anymore after Aug 7th. Can you please tell me how you downloaded another region?
[Galaxy Tab S2 Original Android Development] :
Has anybody seen this?
[Galaxy Tab S2 Original Android Development] Deltadroid:
https://www.sammobile.com/samsung/galaxy-tab-s2/firmware/SM-T713/
[Galaxy Tab S2 Original Android Development] rjmohit:
Can someone please upload the last LOS file that worked without updating the bootloader (Aug 7 I believe)? I can't seem to get the latest firmware downloaded without getting premium membership at SamMobile, and free links if available are excruciatingly slow. Thanks much!
[Galaxy Tab S2 Original Android Development] dwedw:
It took me a while to find the right files, many shady websites and slow downloads.

Aug 7

Latest original firmware (EU)
[Galaxy Tab S2 Original Android Development] rjmohit:
Thanks a lot, updated my tab to the Aug 7 version. :)

If anyone has the North American version files for the stock firmware available, would you please upload it somewhere quick to download from? I think it'll be useful for a lot of us. I currently have it being downloaded at the snail's pace (says it'll take a few days :rolleyes: ) If I do end up having the completed download, I will upload and share. Downloading this T713XXS2BSG1 with July 2019 security patches.
[Galaxy Tab S2 Original Android Development] lmacmil:
This site is usually much faster than Samobile but the latest they have is March 2019.

https://updato.com/firmware-archive-select-model/
[Galaxy Tab S2 Original Android Development] takkischitt:
Does anyone else have issues with the wifi disconnecting, then not reconnecting on device wake? Mine does this quite regularly and I have to turn the wifi off, then on again for it to connect. Sometimes I have to 'forget' the network and re-enter the wifi key to get it to connect. It might be only on 5GHz networks. I haven't got round to checking.

If someone wants to let me know how to get logs, I'll be happy to provide those for someone more knowledgeable than me to check them.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Enable usb debugging in developer settings and use adb to get a logcat and dmesg right after the disconnect.

adb shell dmesg > dmesg.txt

adb logcat > logcat.txt

Zip up the log files and post back here.
[Galaxy Tab S2 Original Android Development] sliding_billy:
I had some time to kill Saturday morning, and took the 0816 update (PIN was already disabled) along with switching to Adaway 4.2.8 (XDA signature) and reinstalling the Magisk systemless hosts module. Kind of a pain in the a$$ disabling ad blocking, installing systemless hosts and 4.2.8 and rebooting (at every step) and getting the hosts installed while checking a known ad launching app to see if it was getting blocked yet while hoping that when I turned the PIN back on and rebooted it would continue to work. After 4 days of testing with many reboots and running every app on the device along with checking for LineageOS updates every time with the updater (and finding but not installing a daily each day but one I think), AdAway finally found new hosts this morning. I wasn't going to be comfortable until a reboot after new hosts were installed and I successfully rebooted without a PIN loop. I have no idea if anything during the dailies between my original 0802 build and your 0813 and my 0816 builds might have changed anything. I am almost certain that my steps when trying Systemless AdAway/module on 0802 were the same as on 0816, but the important thing is that it appears to be working now. Thanks for keeping up with it in your side.
[Galaxy Tab S2 Original Android Development] fastsquatch:
I'm getting about 100kB/s from https://samsung-firmware.org/model/SM-T713/ for my region (XAR worked for me as a region before, it's a US firmware for my US-purchased tablet) - that makes it about a 5hour download

Then I intend to use commands from [MENTION=5227588]Deltadroid[/MENTION] here #335 - thanks everyone for helping keep this tablet relevant!
[Galaxy Tab S2 Original Android Development] Pr0metheus2:
Same problem with trust zone error 7 on August 21 2019 update, did you solve it somehow?
[Galaxy Tab S2 Original Android Development] :
Guys, seriously, have you at least looked briefly at the forum before posting your questions? This issue has been answered already several times. Just read the posts on this very page!
[Galaxy Tab S2 Original Android Development] KeepingItCuttingEdge:
Could someone post just the bootloader from the recent OEM update? (Would like to just ODIN flash the bootloader/BL to the phone and not go through downloading the whole .tar file.)

I'm VERY happy with the official LineageOS 16.0 ROM, but would like to stay current if there were any firmware updates by Samsung.

Please correct me if I'm wrong that the Lineage .zip files don't include the bootloader image file...

I saw some previous posts regarding this, but didn't really understand if anyone would like to enlighten me. Haha

Because this is WiFi-only I assume there is no CP to flash and wouldn't want AP since I'm using Lineage, but what about the CSC?

THANKS
[Galaxy Tab S2 Original Android Development] Deltadroid:
LineageOS builds do not ship with bootloader files. There are 11 files in total that should be flashed simultaneously when updating Samsung's bootloader.

heimdall flash --SBL1 sbl1.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --HYP hyp.mbn --SEC sec.dat --KEYMASTER keymaster.mbn --CMNLIB cmnlib.mbn --DSP adspso.bin --MODEM modem.bin --APNHLOS NON-HLOS.bin

It is also possible to create a custom Odin package containing only the bootloader files mentioned above and update that way.

The process for updating the bootloader files on Samsung's T713 and T813 are exactly the same. The only difference between updating T713 and T813 is that they use different files of course, although the file names are identical.

The different CSC on the stock ROMs should not make any difference when comparing bootloader files. As long as the PDA is the same, then the bootloader files should be the same too. The files from the CSC are not used for LineageOS.
[Galaxy Tab S2 Original Android Development] KeepingItCuttingEdge:
So there's a modem file even though these are WiFi only?

Would I get the .tar file and extract them with 7Zip?

Thanks for enlightening me!
[Galaxy Tab S2 Original Android Development] Pr0metheus2:
I know, but I was looking for another way to avoid flashing stock rom and wiping all data. But it seem there is no other way except this one.
[Galaxy Tab S2 Original Android Development] Deltadroid:
You don't have to wipe data if you use heimdall or use a custom odin package.
[Galaxy Tab S2 Original Android Development] RoterfuX:
yes

you don't have to this post and the last page should help you

https://xdaforums.com/showpost.php?p=80114459&postcount=362
[Galaxy Tab S2 Original Android Development] lmacmil:
After waiting almost a year for a security update from Samsung, I flashed LOS 15 last year. I'm now on a recent LOS 16 build can't imagine ever going back to the stock ROM. I'm curious why you think the Samsung bootloader image might have been updated when they've only issued security updates (as far as I know.). And why you think it's important to stay current on Samsung updates. Thanks.
[Galaxy Tab S2 Original Android Development] fastsquatch:
I might be missing something here, but as I understand it "stay current on Samsung updates" includes updating the firmware, which includes the bootloader etc, which might be a part of a security update. Specifically: imagine there was a new Bluetooth protocol-level attack, and it was a problem in the firmware. Wouldn't it be patched by a Samsung security update? that specific example may not be the bootloader per se but of the 11 files that apparently need to flash together out of the Samsung security update, it's one of them yes?

So I'm happy to flash the important bits of the new ROMs, while keeping LineageOS itself up to date. It's the only way to get all the security updates being released as far as I know
[Galaxy Tab S2 Original Android Development] lmacmil:
Are there other updates beyond the monthly Android security updates that Google issues? The monthly Android updates generally appear in the LOS nightlies about mid-month. Samsung issues updates only once or twice a year, not what I'd call stellar support.