Database Users

[Q] Boot loop after rooting my Galaxy note 4 N910F

Hello everyone,
I tried rooting my Note 4 using Chainfire's [SM-N910*] CF-Auto-Root :
http://forum.xda-developers.com/not...-auto-root-t2897428/post55865442#post55865442
However after Odin finishes and shows "pass", the phone does not reboot in recovery mode nor shows the red android, it loops on the samsung logo and written in the top left corner of the screen 3 lines reading :
Recovery booting ...
Recovery is not seandroid enforcing
Set warranty bit : recovery
I used the correct file for my phone, and now i cannot enter recovery mode, only download mode is accessible.
Any advice is greatly appreciated.

Flash stock firmware with odin and try again

The message is normal it comes up when you root your phone. Do you have a custom recovery installed?

sawdoctor said:
The message is normal it comes up when you root your phone. Do you have a custom recovery installed?F
Click to expand...
Click to collapse
I didnt have custom recovery and it happened, i fixed my boot loop and i still want to root it but each time i try it goes back to the boot loop. My note 4 is SM-N910F

Alex_popa said:
I didnt have custom recovery and it happened, i fixed my boot loop and i still want to root it but each time i try it goes back to the boot loop. My note 4 is SM-N910F
Click to expand...
Click to collapse
indentical same problem
SM-910F
4.4.4
N910FXXU1ANKA
help please

Probably should have mentioned my build number and what not too...

healthyboy said:
Hello everyone,
I tried rooting my Note 4 using Chainfire's [SM-N910*] CF-Auto-Root :
http://forum.xda-developers.com/not...-auto-root-t2897428/post55865442#post55865442
However after Odin finishes and shows "pass", the phone does not reboot in recovery mode nor shows the red android, it loops on the samsung logo and written in the top left corner of the screen 3 lines reading :
Recovery booting ...
Recovery is not seandroid enforcing
Set warranty bit : recovery
I used the correct file for my phone, and now i cannot enter recovery mode, only download mode is accessible.
Any advice is greatly appreciated.
Click to expand...
Click to collapse
nikboss77 said:
indentical same problem
SM-910F
4.4.4
N910FXXU1ANKA
help please
Click to expand...
Click to collapse
I had a same problem but I found easy solution. If you have a bootloop install latest CWM recovery, open ODIN (I used newest version) and uncheck Auto Reboot, select CWM in AP and flash it, after that phone will stay still in Download mode. Then unplug usb from PC and remove battery for 5-7sec, give it back and turn phone on - your phone will boot into CWM recovery for sure ...then I flashed latest TWRP

bondro said:
I had a same problem but I found easy solution. If you have a bootloop install latest CWM recovery, open ODIN (I used newest version) and uncheck Auto Reboot, select CWM in AP and flash it, after that phone will stay still in Download mode. Then unplug usb from PC and remove battery for 5-7sec, give it back and turn phone on - your phone will boot into CWM recovery for sure ...then I flashed latest TWRP
Click to expand...
Click to collapse
Thanks I wanted to ask you once I am in recovery with cwm as I install TWRP? Also from odin?
And how to proceed with CF-Auto-Root?
Sorry for my ignorance....

nikboss77 said:
Thanks I wanted to ask you once I am in recovery with cwm as I install TWRP? Also from odin?
And how to proceed with CF-Auto-Root?
Sorry for my ignorance....
Click to expand...
Click to collapse
Download corespond file from cf auto root page , put your phone into download mode ( VOL - home button and lock screen button ) then select in odin AP file : CF-Auto-Root-trlte-trltexx-smn910f.tar.md5 , start , and wait a few seconds to boot ! Cheers

ManDone.vRs said:
Download corespond file from cf auto root page , put your phone into download mode ( VOL - home button and lock screen button ) then select in odin AP file : CF-Auto-Root-trlte-trltexx-smn910f.tar.md5 , start , and wait a few seconds to boot ! Cheers
Click to expand...
Click to collapse
I know what to do, I have been doing this all along but it goes into a mad boot loop. The Red Android doesn't pop up on screen either. I thought for a second I bricked my phone when it happened but luckily I was able to restore it. Any other suggestions??

Alex_popa said:
I know what to do, I have been doing this all along but it goes into a mad boot loop. The Red Android doesn't pop up on screen either. I thought for a second I bricked my phone when it happened but luckily I was able to restore it. Any other suggestions??
Click to expand...
Click to collapse
It is in fact ... I did the root samsung in many of my friends ... always the same procedure with odin. But this does not load Note4 just the red robot and immediately goes into loop.I do not understand where it can be the error or incompatibility

Plz Help
Sorry for posting on this forum but i cant find any help on the N910H forum. Hi am having the exact same problem phone cant boot to download mode and not recovery. i tried to odin back to stock same problem, i tried twrp, philz and cwm recovery. it says pass in Odin but the phone wont reboot past the android logo and cant boot to recovery.Model number is SM-N910H

Had the same issue, fixed it however flashing CF auto root always results in a boot loop.

Is there any other way of rooting the note 4 without Odin?

At this point I realized that more than anyone has this problem of our loop in doing root on your Notes 4, now in addition to figure out if there is a solution to this problem, I would like to know if this problem is present on the Notes 4 with the same model, firmware updates etc. etc .... or this Note 4 that we are "bad"?

I successfully rooted my note 4 SM-N910F using this method.
Search zedomax note 4 root. It should be the first result.
Sorry I wasn't able to link the video I was not allowed to submit an external link until I have 10 posts.
My phone did this weird thing where it erased twrp so straight after passing in odin I took out the battery and entered twrp. From there it was easy. Hope this helps anyone else with this problem

Alex_popa said:
Is there any other way of rooting the note 4 without Odin?
Click to expand...
Click to collapse
You can flash a flashable SuperSU from chainfire's website using CWM or TWRP recovery.
But if you are on stock TW 5.1.1, you can't root it just yet, it will cause bootloop.
Flash stock 5.1.1 again to fix bootloop

i flashed again to the stock 5.1.1 and i still get stuck on Samsung Galaxy Logo i tried every thing wipe data and wipe cache and i remove battery for million time and i even rooted the phone and start but still freezing on galaxy logo and then Re download the latest Official Rom From sammobile and still Stuck on Galaxy logo the problem came to me when i install Twrp on my rooted note 4 and it's stucked on twrp so i downloaded the latest Rom and still get freeze on Galaxy Logo please help me :/

Same problem here. Flashed SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip but stuck in bootloop, all i get is the threeuk logo and the music. Tried with auto reboot on and off but with no luck.

breeg said:
Same problem here. Flashed SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip but stuck in bootloop, all i get is the threeuk logo and the music. Tried with auto reboot on and off but with no luck.
Click to expand...
Click to collapse
If you're on 5.1.1 then you need a root capable kernel to be flashed too...

[Q] Bootloop Recovery is not seandroid enforcing after trying to root

I need help for my galaxy note 4. I tryed to root it following the instructions on http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428 with CF-Auto root but i think i broke my phone. It nows is always booting and saying "Recovery is not seandroid enforcing " and continue booting always with that message. What can i do? Please help me. I can enter download mode but i don´t know what to do. Thank you

Have the same, looks like our phones are unrootable. Download a full firmware for N910F or C, depends on model you own and flash it, should work.

same thing happened to mine 910f what i done was booted in to download mode flashed custom recovery in odin then flashed super user 2,46 think it was then i was rooted job done

strikerdj2011 said:
same thing happened to mine 910f what i done was booted in to download mode flashed custom recovery in odin then flashed super user 2,46 think it was then i was rooted job done
Click to expand...
Click to collapse
same happened with me first i was stuck like in OP then i flashed twrp recovery using odin but when i rebooted into recovery as it happened twrp wasnt installed , which recovery did you install using odin?? when i press volume up , plus home, plus power button i didn't enter into twrp recovery even after flashing it via odin.
---------- Post added at 08:59 AM ---------- Previous post was at 08:55 AM ----------
darkslayer said:
I need help for my galaxy note 4. I tryed to root it following the instructions on http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428 with CF-Auto root but i think i broke my phone. It nows is always booting and saying "Recovery is not seandroid enforcing " and continue booting always with that message. What can i do? Please help me. I can enter download mode but i don´t know what to do. Thank you
Click to expand...
Click to collapse
same like you.....we all need help...some one please help us .....

Battery pull, boot into recovery via hardware buttons, factory reset and it will boot
Sent from my iPad using Tapatalk

adrianr514 said:
Battery pull, boot into recovery via hardware buttons, factory reset and it will boot
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
but how about rooting...??? the device is not rooting...any idea how to do that???

Is it an Att note 4?

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

Stock recovery doesn't replaced by custom recovery?

I have Samsung Galaxy grand prime SM-G531H. I tried to flash a custom recovery with odin, and "PASS". But the problem is the custom recovery doesn't installed on my device (stock recovery doesn't changed into custom recovery. Can someone help me to solve this problem. Thanks.

Just go to developers options and click the manufacturer unlock. Then try,I think you should be succeed.

@Elie.G said:
I have Samsung Galaxy grand prime SM-G531H. I tried to flash a custom recovery with odin, and "PASS". But the problem is the custom recovery doesn't installed on my device (stock recovery doesn't changed into custom recovery. Can someone help me to solve this problem. Thanks.
Click to expand...
Click to collapse
require rasher.apk for android phone
extract recovery.img file from recovery.tar.md5 by 7zip in pc/windows
place recovery.img in internal storage
make sure your phone is rooted:fingers-crossed:
not rooted install kingroot or use pc version
then open rasher select recovery from storage ask to boot hit yes:good:
done
don`t forget hit thanks:victory:
---------- Post added at 03:21 AM ---------- Previous post was at 03:15 AM ----------
above method failed then try firmwre to flash by odin
http://d-h.st/B3U
Password: halabtech

while flashing the recovery via Odin untick the auto reboot option.
and manually remove the battery and boot into recovery after flashing.

After Odin says pass, pull out your battery put your battery back in then boot to recovery. If you allow the phone to restart on it's own then the custom recovery cannot patch your rom.
Steps.
1. Enter download mode.
2. Plug into computer.
3. Flash TWRP via Odin.
4. Immediately after pass, pull out your battery.
5. Turn on your phone holding Home + Volume Up + Power button.
Hope it helps.

Galaxy s7 edge odin fail

Hi Guys
please anyone help me. i think i have lost my phone.
after i had installed custom kernel i wanted to flash the stock boot. img file what extracted from ap.tar.md5
Now i have a phone what doesnt boot into recovery or system, only or in download mode.
When i want to flash the stock ap&bl&cp&csc file i have a message from odin: "fail" and it says deviceInfo.
Please help me if anyone can
thank you very much

Are you sure that you have the good stock files ?
And you have to flash your old kernel

NeoVander said:
Are you sure that you have the good stock files ?
And you have to flash your old kernel
Click to expand...
Click to collapse
Thanks.
But how to flash my ol kernel?
i can boot only on download mod.
odin always say: FAIL(DEVICEinfo)

Does odin fail when you start the process or after flashing ?
Try to find your stock kernel on internet

NeoVander said:
Does odin fail when you start the process or after flashing ?
Try to find your stock kernel on internet
Click to expand...
Click to collapse
It always fails before flashing process.
It seems to start the flashing method but after 4-5 second it says fail.
i didnt find any stock kernel to my nougat galaxy s7 edge.
i hope that i didnt destroy my phone totally.

You can't boot to twrp right ?
Because your kernel is on the "boot.img", you have to flash it.
---------- Post added at 10:10 AM ---------- Previous post was at 10:00 AM ----------
Maybe you can try this :
http://www.spflashtooldownload.com/2016/01/flash-stock-boot-MTK-android-sp-tool.html?m=1

NeoVander said:
You can't boot to twrp right ?
Because your kernel is on the "boot.img", you have to flash it.
---------- Post added at 10:10 AM ---------- Previous post was at 10:00 AM ----------
Maybe you can try this :
http://www.spflashtooldownload.com/2016/01/flash-stock-boot-MTK-android-sp-tool.html?m=1
Click to expand...
Click to collapse
I had the exact same problem and was having the same error even trying to flash stock form Odin.
Solution:
Restart Odin
Boot into TWRP
Boot back to Download mode but from TWRP not from the button combo
Flash stock ROM (available from Sammobile) through Odin
That worked and I didn't lose anything but of course it will overwrite TWRP.

DenisEhm said:
I had the exact same problem and was having the same error even trying to flash stock form Odin.
Solution:
Restart Odin
Boot into TWRP
Boot back to Download mode but from TWRP not from the button combo
Flash stock ROM (available from Sammobile) through Odin
That worked and I didn't lose anything but of course it will overwrite TWRP.
Click to expand...
Click to collapse
He cannot boot into TWRP

NeoVander said:
He cannot boot into TWRP
Click to expand...
Click to collapse
Ah yes ok I misread. I want to say it would work even if you went directly to download mode, but if it doesn't, I would try flashing TWRP again after killing all involved processes.

Solution here
https://www.sammobile.com/forum/showthread.php?t=38591
Code:
2) Boot into download mode by pressing ( power + volume down + Bixby button) and stop at the screen of continue and reboot.
Press volume down to restart phone
Quickly boot back into download mode by pressing (power + volume down + Bixby button)
Press continue
Congratulations fully working now
3) Install firmware with Odin
4) Wait for the firmware to be installed
5)Ready)))

Anyone with idea to restore imei. I have unknown imei error.