Database Users

[FIX?] Stuck on bootloop

Hi all,
I have a UK N910F 32GB Snapdragon Note 4, with a custom Lollipop rom that I've been using with no problems for a few months (http://forum.xda-developers.com/note-4/snapdragon-dev/rom-bob4-devbase-multi-csc-safe-bloat-t3033881). Yesterday the weirdness began - my Note 4 froze randomly in normal use and rebooted. It was then fine for around 5 hours, then froze again, and when it restarted it would continue to freeze on start-up. At that stage I could still boot into recovery (Clockwork Manager custom recovery), so I tried clearing cache and dalvik, which changed nothing. But now I am unable to do even that - it just gets stuck in bootloop and won't even go into recovery.
When I turn it on, it will stay on the Samsung splashscreen for 10 seconds, then reboot and vibrate twice, then go back onto splashscreen, reboots, etc. I need to remove the battery to stop this. The only thing I am able to do is boot into download mode, where the phone works with Odin fine, and I am able to flash successfully with Odin.
So far I have tried reflashing a stock UK 5.0.1 ROM - it initially gave me the ext4 error but I then got the N910F pit file and repartitioned - Odin flashing completed fine, then still got stuck on splashscreen with "Recovery booting...."). I have also tried to flash CWM and TWRP, which both flash fine, but then the phone still won't boot into recovery - I get:
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
and doesn't boot into recovery. I'm pretty sure I'm using the correct TWRP and CWM versions.
I've spent all day trawling XDA and the wider web with no luck. Does anyone have any ideas on how to fix this? I'm hoping it is a softbrick but cannot work out how to get it back. I don't care about losing any data at this stage, just keen to bring my Note 4 back to life!
TL;DR: phone will stay on bootloop when powered on - not caused by failed software install, just started happening randomly. Cannot boot into recovery. Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.

Markachy said:
Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Click to expand...
Click to collapse
.
Have you tried flashing your variants cf-root file with auto reboot unchecked, let it Pass, remove USB abd battery, wait 30 seconds and reboot? Sounds weird.. i know, but for a while that put many users on 5.0.1 softbricks back to their previous working ROM.

I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.

Markachy said:
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Click to expand...
Click to collapse
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.

phongpan355 said:
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
Click to expand...
Click to collapse
Just tried that, same issue. When it boots after installation, it says "Recovery booting..." in top left corner, then goes into bootloop. Thanks for the tip though.
Any other ideas out on the grapevine? Or is it time for a return?

I'm having the same issue. Tried stock ANK4, BOB4 and BOC3. Only bootloops and can't reach recovery mode.
Than I tried TWRP 2.8.7.0 and "philz_touch_6.59.0-trlte" but they don't work either.
Don't know what to do now. Never had this issue before on any Samsung device
EDIT: Tried Samsung Smart Switch and it dowloaded PDA: OC3 / CSC: OB6 / PHONE: OC3 (DTM). But my Note bootloops furthermore

Saw 2 other guys with the same Problem and no solution here.
And I found this. This could be the same issue we are facing:
http://forum.xda-developers.com/showthread.php?t=1840030
Hope there is a dev that can make this for our 910F

Hi all
This is now also happening to me...
Have Odind back to stock and it works for about 4 hours,
Then issue starts...
Reboots randomly
Then reboots to blank screen... No recovery
Again uk note 4. 910f

Samsung Galaxy S5 SM-G900F 5.0 stuck during root

This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...

I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1

This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?

xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar

*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...

i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance

seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:

VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.

manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...

VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch

manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.

VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?

Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"

VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).

manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.

VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.

GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)

So I'm guessing no one knows the answer to my problem considering almost a moth has passed...

I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too

Bootlop error after root failure.

Hello,
I decided to try and root my phone yesterday in order to use flux and the AdAway for my Samsung Galaxy Note 3 SM-N9007. However when i used Odin instead of saying "Pass" it was saying "Reset". As it was my first time doing anything like this, I unplugged my phone which seemed to have been the wrong move. My phone would vibrate once or twice and then reboot to show me the Samsung logo and the words "Recovery is not Seandroid forcing". It would show that screen for approximately 2 seconds where it turns off and repeats the process. Whilst off for that period of time I cannot enter recovery mode. However I can enter the download mode (vol. down + power). I have researched a bit on what to do however I am still a bit unsure.
*It seems the main problem is I can not enter recovery mode at all. As the logo shows it just turns off instantly and then turns back on getting stuck in a loop.
What I gathered online.
- Download the stock firmware for it. (The file I'm downloading is roughly 1.3 gb)
- Load the file the same way I tried to root the phone.
Is this correct? Could I get some assistance please?
Thank you

I have managed to resolve the error by loading in the stock firmware with Odin.

Heize_July said:
I have managed to resolve the error by loading in the stock firmware with Odin.
Click to expand...
Click to collapse
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted

ShaDisNX255 said:
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted
Click to expand...
Click to collapse
Yea I made the mistake of choosing the wrong CFRoot file. The one I installed was for Android version 4.3 whereas my device was 5.0. After retrying I manged to get the root to work. Thanks anyways!

Download Mode is gone

Hey. I tried to root my phone with CF Auto Root but it stuck with the Samsung Logo (no bootloop, just stuck there). I managed to restart it. But when I went to the Download Mode I saw a blue screen with a "!" in a yellow warning sign and the line "no command". Then I am in the stock recovery mode.
The system dont allow OTA because I modified the system. I dont have a problem with that, but I need to get into the download mode to flash TWRP.
p.s.: When I am in the stock recovery mode I tried to "boot into bootloader", but it didnt work.

Ok, I give up on android. I just tried it two more times and suddenly all worked fine. DAFUQ?!?!!?
Edit: Ok, I always get the message "Custom Binary blocked by FAP Lock".
What does this mean? It blocks my acces to TWRP. Also I cant flash things with download mode.

Rookie1919 said:
Ok, I give up on android. I just tried it two more times and suddenly all worked fine. DAFUQ?!?!!?
Edit: Ok, I always get the message "Custom Binary blocked by FAP Lock".
What does this mean? It blocks my acces to TWRP. Also I cant flash things with download mode.
Click to expand...
Click to collapse
I usually heard about an FPR lock message but FAP lock is the first time (samsung really needs to rename that one :laugh: ) anyway , FRP lock happens if you forgot to enable OEM unlock in dev option before trying anything on your phone so if you can access download mode reflash stock firmware and do all the process again otherwise you'll need someone more experienced of me but I'm afraid that if you can't access download mode you're in a bad situation..
If you want to be helped in a better way provide more info about your phone for example wich model you have got, wich firmware were you on before all of this happened and so on
Hope you'll find a solution!

Ok, I managed to reset it. I use the G935F with Exynos. But now I have another problem: The CF-autoroot AND the TWRP make my phone stuck in the Samsung Boot Logo (no bootloop, just stuck). DAFUQ? Why?

Rookie1919 said:
Ok, I managed to reset it. I use the G935F with Exynos. But now I have another problem: The CF-autoroot AND the TWRP make my phone stuck in the Samsung Boot Logo (no bootloop, just stuck). DAFUQ? Why?
Click to expand...
Click to collapse
It might be necessary to wipe data maybe? In TWRP --> wipe --> format data --> type yes and reboot but be carefull, I didn't use this autoroot since I prefer the "standard way" so make sure you have a backup! Ah, and leave it at least 5 mins at boot logo.. mine takes that much to boot after every flash

Thx, Format Data worked. Now I´m fine.

Samsung A20 Bricked?

Hi, I tried to install TWRP. I used fastboot. Something has gone wrong. The phone boots with the three warning screens and then displays the TWRP splash screen. It will not respond at all after this point. I can reboot using Vol down and Power but the same screens appear and then stays on the TWRP screen. The phone cannot be seen by the PC using ADB or Fastboot via USB cable. Any ideas please? Is there a way to boot and install new recovery etc from SD card perhaps?

Are you able to force a reboot to download mode?
If you click one of the Volume buttons when the bootloader warning screen comes up, you should be able to select an option to power off or reboot to fastboot.

V0latyle said:
Are you able to force a reboot to download mode?
If you click one of the Volume buttons when the bootloader warning screen comes up, you should be able to select an option to power off or reboot to fastboot.
Click to expand...
Click to collapse
Hi, thanks for taking the time to help. The only thing it seems I can force is a reboot (using Vol down and Power) It won't switch off and there are no options to get to recovery. The bootloader screen doesn't appear. The only screens which appear on boot up are those I've uploaded images of! It is now powered off due to battery being drained.

[email protected] said:
Hi, thanks for taking the time to help. The only thing it seems I can force is a reboot (using Vol down and Power) It won't switch off and there are no options to get to recovery. The bootloader screen doesn't appear. The only screens which appear on boot up are those I've uploaded images of! It is now powered off due to battery being drained.
Click to expand...
Click to collapse
I think you're misunderstanding me, and I need to clarify some things.
First, the only button needed to force a reboot is Power. Holding one of the Volume buttons during and after the phone restarts tells the device what mode you want to boot into.
Second, you ARE getting a bootloader warning, and you shared a picture of it. This is what I'm talking about:
When this screen appears, you should be able to click Volume Up or Down, and a menu should appear on the screen.
All of this is irrelevant, because what you need to do is start the device in download mode, and reflash via Odin. Starting with the device OFF and NOT PLUGGED IN, hold both Volume buttons (DO NOT PRESS POWER) and plug the USB cable from your PC in. This should start the device in download mode.
If you see KG STATUS: PRENORMAL, you cannot flash any custom binaries such as TWRP, and can only flash official firmware.
Once you do this and get your device running again, we can move on to the next step.

Thanks again for your help. My phone was fully discharged. I followed your unstructions and reflashed TWRP V3.3.1-0 (recovery.tar) using Odin 3.14.4. There was no KG STATUS message. Odin signalled success. It rebooted but am now back to square one, showing the TWRP screen. The power button does not power off even after being held for minutes. Because it has minimal charge it soon switches itself off. When the bootloader warning appears the Vol +/- does not have any effect. I have repeated this process twice.

Development! Thanks to your info I've managed to reinstall Samsung A20e stock image. Phone boots (unlocked) but normally now. I'm thinking that originally I installed the wrong version of TWRP which led to the "semi-bricking". Can you point me at the relevant download or identify the the exact TWRP file I need to install please?

Setback! I tried another version of the TWRP file, again hangs on boot at TWRP splash screen. Help please, I'm convinced now that I'm using the wrong TWRP files.

I found these instructions - https://forum.xda-developers.com/t/guide-twrp-and-root-for-a20e-a202f-updated.4384841/ - and now am able to boot to TWRP recovery. This is where I am now, looking to install Lineage.

V0latyle said:
I think you're misunderstanding me, and I need to clarify some things.
First, the only button needed to force a reboot is Power. Holding one of the Volume buttons during and after the phone restarts tells the device what mode you want to boot into.
Second, you ARE getting a bootloader warning, and you shared a picture of it. This is what I'm talking about:
When this screen appears, you should be able to click Volume Up or Down, and a menu should appear on the screen.
All of this is irrelevant, because what you need to do is start the device in download mode, and reflash via Odin. Starting with the device OFF and NOT PLUGGED IN, hold both Volume buttons (DO NOT PRESS POWER) and plug the USB cable from your PC in. This should start the device in download mode.
If you see KG STATUS: PRENORMAL, you cannot flash any custom binaries such as TWRP, and can only flash official firmware.
Once you do this and get your device running again, we can move on to the next step.
Click to expand...
Click to collapse
Happy New Year. I have now got TWRP installed. I tried to move on with Magisk (that's what one thread told me to do!) I've tried various Magisk files but again it just hangs my phone. I waited for it's battery to flatten, reboot into download and reflash original firmware and then TWRP. So, TWRP is installed ok (I think) what is the next step to install Lineage please?

[email protected] said:
Happy New Year. I have now got TWRP installed. I tried to move on with Magisk (that's what one thread told me to do!) I've tried various Magisk files but again it just hangs my phone. I waited for it's battery to flatten, reboot into download and reflash original firmware and then TWRP. So, TWRP is installed ok (I think) what is the next step to install Lineage please?
Click to expand...
Click to collapse
Sorry, life has kept me busy.
To install Magisk on the stock firmware, all you have to do is flash the Magisk .apk in TWRP. Make sure you're using the latest version.
To install a GSI, you can follow my guide here, and start at the Multidisabler section since you've already unlocked bootloader and flashed TWRP. For LineageOS specifically, refer to the thread on the build you want to use. I personally have used the LineageOS 20.0 A13 GSIs by @AndyYan , they're quite good. However, many of them do not have GApps preloaded so you'll need to do that. Regardless of what GSI you decide to install, you'll have an .img file which is the system image; you can then use the instructions in my guide to install it.

Thanks for your input. I tried your guide but I think that I'm using the wrong combination of .img and GAPPS files. I ended up with a hung very dark blue blank screen after boot. I'm going to try AndyYan's .img file but I'm unsure which Open GAPPS goes with Lineage 20, is it 11?

REMOVED

I had the message in bootloader "KG STATUS - LOCKED" so I re-locked the bootloader. Re-unlocked it and had the message KG STATUS - CHECKING. so far, so good. Tried to install TWRP file "twrp-3.7.0_9-0-a20e.img" Odin reported success but now in download mode get the message "Recovery: Error validating footer.....(Rest of message hidden under camera lens)...." BVMETAA202FXXU4CVK1, 59051 788A. Phone is stuck in download mode and will only reboot to download mode with the above error message. Will wait for battery discharge and then reinstall stock OS and wait for your input please.

[email protected] said:
I had the message in bootloader "KG STATUS - LOCKED" so I re-locked the bootloader. Re-unlocked it and had the message KG STATUS - CHECKING. so far, so good. Tried to install TWRP file "twrp-3.7.0_9-0-a20e.img" Odin reported success but now in download mode get the message "Recovery: Error validating footer.....(Rest of message hidden under camera lens)...." BVMETAA202FXXU4CVK1, 59051 788A. Phone is stuck in download mode and will only reboot to download mode with the above error message. Will wait for battery discharge and then reinstall stock OS and wait for your input please.
Click to expand...
Click to collapse
you installed wrong twrp

deleted

CamiloSaenz said:
This is nat related to the main matter... but.
I have a problem, recently I installed stock rom on my J6+, tried to flash TWRP, but cant, it said: KG STATUS: PRENORMAL ..-.. so, I made a format factory, format cache using the stock recovery, but then the KG STATUS changed, from Prenormal to: CHECKING
it dont allow me to flash anything but Stock ROM.. Do you know how can I change that? ... from the KG STATUS: Checking .. to KG STATUS: NORMAL
Click to expand...
Click to collapse
Boot into Android, connect to the Internet, enable Developer Options, check for the presence of the OEM Unlocking toggle. It should be visible but grayed out. You may have to force a check for firmware update in system settings.
Once OEM Unlocking is visible again, KG STATUS should be "COMPLETED", and you'll be able to flash custom images.

deleted

CamiloSaenz said:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-J610G
CURRENT BINARY: Samsung Official
FRP LOCK: OFF
OEM LOCK: OFF
KG STATUS: Checking
WARRANTY VOID: 0x1 (0x20c)
QUALCOMM SECUREBOOT: ENABLED (CSB)
RP SWREP: S1, T1, R1, A7, P1
RP SWREP: K 7, S 7
SECURE DOWNLOAD: ENABLE
DID: 0056c0f88Bc9
DOWNLOAD MODE !!
this is the current state.
Click to expand...
Click to collapse
Did you follow the instructions I gave you?

deleted

CamiloSaenz said:
yes I did, but does not work, KB STATUS: Checking
Yesterday I locked the OEM, nothing changed, then Unlocked OEM, the status is the same, ... having an active google account it shows FRP: OFF ... it doesnt matter, having or not a google account, it shos FRP: OFF
Click to expand...
Click to collapse
Leave OEM Unlocking on and don't change it.
Try this