My system is rebooting all the time, but never really open the syetem. What is wrong?
Thanks
Thanks
Bootloop?My system is rebooting all the time, but never really open the syetem. What is wrong?
Thanks
Hi,To those having Error 7 while flashing, Open the updater-script file and add TZ.BF.3.0.3-00021 (If you android 6.0) or delete the assert lines altogether.
Which LineageOS file you are using. Like I wrote my tablet keep boot system for awhile then go back to TWRP screen recovery. Mine LineageOS file was corrupt so I download an earlier version file and it worked. After that go to settings and do an system update. Please refer to my #28 post. Use this lineage-16.0-20200413-nightly-gts28vewifi-signed.zip file. It worked for me. Hope that help.Been through your process and it all appeared to be error free. Now when it has finished and rebooted, took about 9 minutes, it came back straight into the ""Team Win Recovery Project" 3.2.3-0 . How do I get out of that into a working tablet? From the TWRP screen, I hit "reboot", "Power Off" and it comes back to that screen every time.
All working fine now. Changed version of TWRP and reinstalled packages. Thanks again.Which LineageOS file you are using. Like I wrote my tablet keep boot system for awhile then go back to TWRP screen recovery. Mine LineageOS file was corrupt so I download an earlier version file and it worked. After that go to settings and do an system update. Please refer to my #28 post. Use this lineage-16.0-20200413-nightly-gts28vewifi-signed.zip file. It worked for me. Hope that help.
Did you get an answer to your question or find a solution for this issue? I'm running into the exact same thing—same challenge, I've tried the same solutions, same model...all of it. Your comment stands out because I could have written it, myself. I'm hoping you also found a solution.Hey there. Found this guide as I recently got a tab s2 and it's very well written, but one step is really hard and it's the whole "boot into recovery from download mode". Whatever I try I can't get it to work.
I assume when you say to hold the Download mode combo (pwr+home+volDown) you mean while the screen is blue with the message "Downloading....". I do this and as soon as the screen turns off I switch to recovery combo (pwr+home+volUp) but I always land at the "Samsung Galaxy Tab S2" screen and it just stays there.
Is there a way to completely turn OFF the tablet from Download mode so I can start into recovery easier? I don't know why it's not working for me tbh. I've tried timing it, tried being a second earlier, later, whatever. Always the same thing. I fear I might be doing something wrong tbh.
(A note: I don't have the "enable unlock OEM" option in my developer options but apparently that means I don't need to enable it. Odin works just fine and I get a pass after 3 seconds. Oh, and my KNOX WARRANTY VOID: went from 0 to 1 so I assume it worked).
EDIT: I want to add my TabS2 is model SM-T815, in case that matters.
If I go super fast, I get the screen that says "Samsung Galaxy Tab S2" and then below that "Powered by Android," and it just freezes there. (If I go a little slower, I get that screen, and then it boots into the stock OS.)I have just "done successfully" my Tab S2. Had same problem. Eventually found you had to be very fast between letting go the three buttons then pressing them again with the Volume Up instead of down.
Yeah, getting the same thing. There's no way I can go any faster.If I go super fast, I get the screen that says "Samsung Galaxy Tab S2" and then below that "Powered by Android," and it just freezes there. (If I go a little slower, I get that screen, and then it boots into the stock OS.)
I think I'm getting the timing, but the process seems to be freezing, as described above. Has anyone else with the same model (SM-T810) been able to solve this? Or is the timing really THAT sensitive? I can keep trying, but I've probably flashed twrp about 20 times, moving as fast as I can, and the best result I get is freezing on that one screen.
Thanks in advance for any help!
EDIT: I also see that I misspoke in my first post. The model is not the same as the comment I was replying to. Sorry for the confusion.