Custom Recovery blocked as a security measure? - Samsung Galaxy Tab S6 Lite Questions & Answers

Hi Everyone,
I originally flashed LineageOS and it wirked beautifully. Then I thought I wanted root.... After trying some things that didn't work I flashed my tablet back to stock to get it working again and then attempted to reinstall LineageOS cleanly. But now, after flashing the recovery with Heimdall, when I power off with Vol-down and Power and immediately switch back to Vol-up and power, the regular warning screen shows up with the standard message: "This tablet's bootloader is unlocked and it's software integrity can't be verified..." Then the same screen with a yellow warning triangle
added and below that another warning triangle and in Red "This tablet is not running Samsung's official software" and you will have problems...
After this screen appears the tablet freezes and becomes unresponsive to all but the Power and vol-down shutdown. It then reboots and freezes again.
I can get back to Download mode and reflash the stock with Odin but loading the lineage recovery seems impossible.
I can get to the stock recovery with adb reboot recovery
Is there some way to bypass what looks like a security measure? Does someone know more about this?
In the stock recovery is has the option to enter fastboot. Is this a real fastboot, as in I could load a recovery straight from my computer?
Not sure how to get back to LineageOS, or what my next step should be.
Thanks in advance,
Murphy

Update: I got it working again and reinstalled LineageOS
What worked was using Asomeslayerg's Guide to Unlocking and Rooting the S6 Lite with updated instructions in the comments from gbeyts667. Thanks to those fine souls!
It seems some combination of using an older version of the stock image (I used the one from the guide from around last year) and patching with magisk re-enabled my ability to enter recovery mode after flashing the lineage recovery.
I hope this helps someone else.
Has anyone used magisk to root LineageOS on the S6 lite? Does it work? Can you just use the lineage recovery for that?
Would love to know! Thanks in advance.

Related

Tried to root, recovery flashed but didn't boot, now phone won't reboot.

Hey guys and gals, I decided to take my new PH-1 and root it after getting the latest OTA (this is an unlocked Sprint variant). I flashed the twrp for my build and there was an error, tried it again and the same error so I rebooted back into fastboot and it flashed but I didn't reboot into recovery. Flashed it again and booted into recovery but it was just a black screen as if the phone wasn't turned on. The closest I've gotten to recovery was the android laying down and it said "no command" but I forced a reboot at that point (I think I could have pressed up on the volume and pressed the power button to get to it from there but I haven't been able to get back to it).
I ended up flashing a modded boot image for root with Magisk 14.3 and that worked but I can't reboot my phone, it just goes to the blank screen like it isn't on and I can start it up again by holding the power button down for 15 sec. and it seems to function fine but I can't flash the OTA file to go back to complete stock or to go to the Oreo beta.
If anyone could give me some insight into this problem or a way of fixing it I would grateful, thank you.

Flashing S7E Exynos - Used Odin + TWRP, can't get any further.

Hi everyone, I tried to use this guide to root my phone.
Can confirm it's International, so Exynos.
Used Odin 3.12 and TWRP image 3.1.1 for hero2lte, which is the correct version.
Everything flashed perfectly - Got the OK from Odin, so can't see any problems that side.
Now the problem I'm getting:
When booting into recovery, I get installing updates... then 'No command' screen, like in this thread
I have factory reset via the recovery I DO have (I don't think this is TWRP, there's no touch interface, and it's all controlled via volume + power keys). This allows me to boot into the OS.
I have the option to boot into bootloader, and this takes a little while to do, but seems to fail and boot into the OS anyway.
I have no way of trying to reflash TWRP that I'm aware of, and I'm kinda stuck... could anyone help me from this point on please? Thank you!
EDIT: I'm trying to install custom ROMs and tweaks (Not sure if things like busybox/gravitybox/xPosed framework etc. exist anymore - haven't touched custom stuff for 3 years now! If you know, please let me know too!) So are there OTHER steps I should be aware of/know if I wanna proceed?
(just posting reply so I can see this thread later on, gonna do the same thing after exams, if I get same issue, this will be helpful)
P.S: By the way, when flashing TWRP, deselect auto reboot and see if you can go to recovery without booting it first. Sorry can't think of more options :S
after disabled auto reboot, then holding vol up and home and boot it booted to twrp.
Flash each of the checkboxes individually or it will send you back to download mode
Only one checkbox at a time also make sure ur oem unlock is enabled

Bootloop and I can't access the Bootloader

I've had a Galaxy SM-T510 for about 18 months. I installed a custom ROM and it worked fine. When it booted up I received a message "Bootloader is unlocked and security cannot be guaranteed, press power button" and when you pressed the power button it booted up fine. Recently, I installed TWRP and when I rebooted it goes to the some "Bootloader is unlocked, etc" error message, but when you press the power key it restarts and loops to the same point. Holding the power key, with volume up, volume down or both makes no difference. I installed Fonepaw which appears to only work in Download mode which I can't access. If I run Odin or Kies it doesn't recognise that there is a phone attached. Any suggestions?
I've solved the problem. Holding down both volume up & volume down at the same time, and plugging it in puts the device into download mode.
Actually, I haven't solved the problem. I can now install an OS thru either Odin or TWRP, but all the OS I have tried go into a bootloop and the device never finishes booting up.
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
BillSchutt said:
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
Click to expand...
Click to collapse
You aren't getting help because you are posting in the wrong place. And, if you are coming from an old custom ROM, you have to first flash the right stock ROM. I no longer have a 510 so I'm not sure which stock ROM you need but if you check the first post for the custom ROM you want in the ROMs, kernels and recovery thread, it should tell which one it is based on.

A205YN not booting custom ROM after flash through TWRP

It seems every ROM I’ve tried installing never boot after “successfully” through TWRP. (Like even 10 mins of waiting)
My idea is that unlocking the bootloader (where it gives you warnings every time the thing boots) has something to do with it, seeing as the flashing guides don‘t mention this in depth.
Factory reset through TWRP after flash, that wipe after flashing that has the button on the finished page
Now it can’t boot into TWRP, or download mode, just stuck between the power screen and black (seemingly turned off)
Did you flash Magisk-v23.0.apk through TWRP?
burningcreation said:
Did you flash Magisk-v23.0.apk through TWRP?
Click to expand...
Click to collapse
No, I was following this and this which don’t list Magisk as a step
Would that have been important to do?
Also any ideas on how to get it to download mode? So far it just gets stuck on the Galaxy A20 screen with a warning about it being unlocked, no button combo gets past that, even though it does reboot

When flashing TWRP it goes back to bootloader downloading and I can't do anything until i flash original firmware again.

Hey! I guess you can see from the title that I am a toootal noob in terms of custom recoveryes, roms and rooting, but I was trying to flash pixel experience on the phone, because my warranty recently expired and wanted to try it out. So I searched and I found to flash a rom on any phone I need a custom recovery and found that TWRP is the most popular and supported the phone so I installed odin and the samsung usb drivers, turned on bootloader and usb debugging in the developer settings, booted into the bootloader, connected the phone to my pc and used odin(tried by running it with and without adminstrator) to flash the tar file, with auto reboot turned off, it says it's installed succesfully, but when I hold the power and volume down button to exit bootloader and hold the power and volume up button to boot into recovery mode , instead of showing the phone model and then powered by <whatever it is> it shows me the phone model and under it it says that i have an unofficial OS that may harm my phone or something like that and sends me back to bootloader this time with "<!>" in the upper left corner and something about vbmeta. If I understand it right vbmeta is verified boot which as the name suggest makes the phone boot into the official os and you turn it off when you turn on bootloader. The only way to get out of that is to flash the official firmware again. I would really appreciate it if someone helps me with this. If not I guess I will try to flash Orange Fox recovery.
Try flashing this first, then TWRP

Categories

Resources