If you still have problems with restart options I can recommend "Quick reboot" by phongIT from playstore.
Probably because the kernel itself is faulty
youre device might be under kmm abnormal state. Firstly check for updates then pause. Then go to date and time, and set it back a month. Then reboot, recheck for update and then go to about phone, check build number 7 times, developer mode should be unlocked. Go to developer options and you ahould see oem unlock option enabled, if you dont see it at all still then repeat the date and time process again but if you do, you should go back to download mode and then go to your computer.Hello , thanks for this nice job ...butt ihave a problem
I put the recovery in stock rom the last time, I also had the rom locked with a fingerprint, because I had not read about the problem that is created and that it is not possible to mount data, so I went through stock rom again, did the litigation and finally put [ROM] SM -T825 TWEAKED and everything went well, then I wanted to try to put [ROM] [UNOFFICIAL]  [SM-T820] [SM-T825] [BETA]  LineageOS 18.1 for Galaxy Tab S3 but there are not I managed now as much as I do the process I can not put any rom except the stock ... it can not be done with anything mount data and I end up putting only the stock again ....... is there a solution please ???
thank you any way ...
thank you very match sir .....i will do ityoure device might be under kmm abnormal state. Firstly check for updates then pause. Then go to date and time, and set it back a month. Then reboot, recheck for update and then go to about phone, check build number 7 times, developer mode should be unlocked. Go to developer options and you ahould see oem unlock option enabled, if you dont see it at all still then repeat the date and time process again but if you do, you should go back to download mode and then go to your computer.
flash twrp and a pie bootloader (go to debloat rom from roymc to download) then boot to recovery and from there you can use otg (connect pc to tablet) and sideload the lineage os 18.1 unofficial rom and flash it. Id also flash the updated 3.5 twrp within twrp as well as flashing the encryption disabler, and the disable dm verity zip just in case. if you have any questions ashyx, or the guy developing the 18.1 rom for more answers or post them here and ill try to answer as best as i can.
Root will not help as it's not needed for using TWRP.
As I've read about loads of people having problems with that app I avoided to install it.
As long as Magisk isn't installed you won't have root.
I've read for other devices that downgrading the bootloader wasn't successful.When I first tried to install a rom using Odin, the error message was Fused 3 > Binary 2 (I think it was Binary 2).
This was before I used BenG7's process.
There is quite some information for troubleshooting available for this error. After some searching my understanding is, that the encryption of the device and some protection implemented with Pie disables the rollback of the Bootloader to an older version.
This is how I ended up here, trying to root the device.
Odin looks like this:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4457 M
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
One other suggestion:
The last time I was really familiar with rooting and custom roms, things looked white differenty.
It was pretty much Rocovery -> different boot loader -> custom rom.
Now it seems like Odin does it all in one step - or better in one step with several files.
Would it make sense, to focus on getting a different boot loader installed`?
This seemed to be the root cause of the original issue.
Sorry if this is a dumb question.
Is there anything I need to know about installing Magisk?
OK, I will try this tomorrow.
I am learning a lot from you.
I've always installed Magisk only via TWRP.
Looks like the kernel source is fubarred. It's not the first time Sammy source code has been unbootable and it always Qualcomm source code.Ok, just tried the AQB9 Bootloader with your first and second permissive boot.img, but didn't worked. Stucked at first boot logo with the yellow writing in the upper left corner like before. Do you maybe have a AQBB, AQC1 or AQD6 permissive boot.img?
Just to be sure that the error lies in your kernel source, I downgraded the firmware to AQB9. Ended up with the same errors for both permissive boot images like before.
The issue, as I suspected, the kernel version was mismatched to the base firmware on the device.