I’m surprised that lineage-21.0-20241203-nightly-gta4lwifi-signed can be installed with Samsung firmware version T500XXS8CXG1, because LOS 21.0 is based on T500XXS7CXB1.
I would be very interested to know how you reset the firmware version T500XXS8CXG1 with BIT/SW Rev. 8 including Samsung Roll back protection to version T500XXS6CWI2, because this is the only way to install /e/OS-T.
With your knowledge of Samsung devices, you should know that the old Samsung days are over, at least since the Galaxy S9 era. What used to work is generally no longer possible today. We are in 12/2024 and firmware Android 12.
Links to paid downloads are not really helpful. The /e/OS installation problem could be solved by /e/, at least for Samsung firmware T500XXS7CXB1, if /e/ would fall back on current LOS source code like @r onnz98. But this has been avoided by /e/ for months.
I would like to update this thread. I was able to load eOSU 2.6 on this device SM-T500 with the binary version T500XXS8CXG1 from the stock Samsung ROM.
This is usually associated with the device being Prenormal. Does this show on the Download mode screen ?
However some newer Samsung have a Download mode screen with very little info.
First off the best bet is to have the device online (and with SIM installed, if a phone). Sometimes it is necessary for a new or refurbished phone to have made 5 minutes of calls, sometimes checking for updates will release RM Prenormal. RM is remote monitoring by Samsung, hence the reason to connect to their servers. Alternatively Prenormal is Knox derived.
Steps to install /e/OS from recovery → Format the device
In the middle of this → ```
Wiping data ------------------------------ Done
Formatting/data ----------------------- In the middle of…
My device decided to reboot and I'm left with the terrible "Security Error” message on the Samsung Galaxy Tab A7 10.4 (model SM-T500) typically indicates that the device has been flashed with unauthorized software and is now locked."
I fixed it by flashing stock. I almost made it.:) Its late and I'll try again tomorrow.
That device is tricky, the recovery only works for one boot or it is over written by the Samsung recovery.
Once you get to the part with the USB connected and pressing all the buttons to allow sideload, if you hold them too long it just restarts. It vibrates then you sideload. I have only done this device once so going from memory but it is tricky for sure.
For Knox Guard one has to think of the history of the device. For example the device might have belonged to a “fleet”. Do you know its full history ?
The above example would involve the use of Knox by a third party. Different generations of Samsung seem to apply this Bootloader lock in different ways … your device may be “partially locked” by Samsung themselves for marketing or other reasons, one does not know.
Always a good idea to keep an eye on the availability of OEM Unlock, in case it changes. The unlock may be as simple as using the device (online) for a week or two or the “date change” method mentioned in “Know your hardware - Samsung” linked above.
Yeah I know the full history. You might be on to something. We bought it when we lived overseas.
I’ll give it a week or two and see if the KG status changes. Checking the web I see others have had the same issue with this problem. Having to wait to check-in for something I bought is annoying.
Really makes you think. Do you own your device or does the vendor?
Is this a problem on all Android at version 12 and above? Or is it device specific?
Just a thought, if you used it overseas with a Google and Samsung account for a significant length of time, then continued with same accounts at your current location, you should expect to have satisfied Knox.
Restoring such accounts might make a difference.
However if you bought it overseas then Samsung considered that you had “grey imported” it, maybe Knox was triggered against you.
A third scenario might be that when you bought it overseas it was already a grey import there, the phone was Prenormal but unnoticed in regular use.
I so wish tablet wasnt on android 12
gave it another try and I thought I was good but didnt work out…