Database Develop

stuck to fastboot when try to flash recovery [Lenovo K3 Note]

Hello there, after an hour of search and no useful results, i've decided to ask my question (sorry, if it's already been answered, but i didn't find anything)
I used the following procedure to flash the CWM recovery, but something goes wrong:
( http://forum.xda-developers.com/android/development/ufficial-thread-lenovo-k3-note-t3102997 )
1. "adb devices" shows the phone correctly (At this state the phone is properly shown in my windows device manager)
2. "adb reboot bootloader" pushes the phone to boot in fastboot mode
... but ...
3 "fastboot devices" doesn't find it anymore. (At this state the phone is shown as an unknown device in my windows device manager)
4. after some attempts I tried "fastboot flash recovery recovery.img" anyway, but as I expected, i was unable to reach the device, the image should be written to.
5. every the phone stucks in fastboot mode, and the only way to restart it is by pulling out the battery.
So, what is the possible reason, to loosing connection to the device after the reboot in fastboot mode? (phone drivers already installed, pc rebooted, ADB SDK installed too)
Thanks in advance for any help!
Regards!

thudrumble said:
Hello there, after an hour of search and no useful results, i've decided to ask my question (sorry, if it's already been answered, but i didn't find anything)
I used the following procedure to flash the CWM recovery, but something goes wrong:
( http://forum.xda-developers.com/android/development/ufficial-thread-lenovo-k3-note-t3102997 )
1. "adb devices" shows the phone correctly (At this state the phone is properly shown in my windows device manager)
2. "adb reboot bootloader" pushes the phone to boot in fastboot mode
... but ...
3 "fastboot devices" doesn't find it anymore. (At this state the phone is shown as an unknown device in my windows device manager)
4. after some attempts I tried "fastboot flash recovery recovery.img" anyway, but as I expected, i was unable to reach the device, the image should be written to.
5. every the phone stucks in fastboot mode, and the only way to restart it is by pulling out the battery.
So, what is the possible reason, to loosing connection to the device after the reboot in fastboot mode? (phone drivers already installed, pc rebooted, ADB SDK installed too)
Thanks in advance for any help!
Regards!
Click to expand...
Click to collapse
Hi,
I have the same problem. Any solution exists for that?
Thanks.

Same here. Some one saying it's driver issue, but I didn't have any errors installing the drivers and I tried different PCs, all the same...
Another reason I said it might not be a driver issue was that I used that PC to root the device successfully a while ago. But after updating to the newly released stock ROM, now this rooting method stuck in the fastboot mode.

I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did someone tried other ways to root the K3 Note (apps etc.)?
Regards!

marskingbeatgates said:
Same here. Some one saying it's driver issue, but I didn't have any errors installing the drivers and I tried different PCs, all the same...
Another reason I said it might not be a driver issue was that I used that PC to root the device successfully a while ago. But after updating to the newly released stock ROM, now this rooting method stuck in the fastboot mode.
Click to expand...
Click to collapse
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did you tried other ways to root the K3 Note (apps etc.)?
Regards!

thudrumble said:
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did you tried other ways to root the K3 Note (apps etc.)?
Regards!
Click to expand...
Click to collapse
Hi,
I tried this method.. I can not add link. Try to find "How to root and install Google Play Store on Lenovo K3 Note" in youtube . And it did work for me. Root checker showed that root access is not fully. But I manage to install another rom.

This might help:
Go to the main thread...and jump to page 73 and read post #722
http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
For a change, you could use another method:
Lenovo K3 Note Manager by Pr1nc3V located here: http://forum.xda-developers.com/k3-note/general/tool-lenovo-k3-note-manager-t3261285

freelancer81 said:
This might help:
Go to the main thread...and jump to page 73 and read post #722
http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
For a change, you could use another method:
Lenovo K3 Note Manager by Pr1nc3V located here: http://forum.xda-developers.com/k3-note/general/tool-lenovo-k3-note-manager-t3261285
Click to expand...
Click to collapse
Thanks dude! The first method is the one, that won't work with my K3Note, but I'll try your plan B later today. Fingers crossed

cloudinio said:
Hi,
I tried this method.. I can not add link. Try to find "How to root and install Google Play Store on Lenovo K3 Note" in youtube . And it did work for me. Root checker showed that root access is not fully. But I manage to install another rom.
Click to expand...
Click to collapse
Thanks! I found the video and try this one too, if the freelancer81's method fail.

Mission accomplished

Mission accomplished? Kindly share how you were able to resolve it as I am still faced with the problem. I have tried all the recommendations here

same issues..
ADB sees the phone. but fastboot doesnt seem to connect / see it..
And no thats not the issue of not booting into the recovery as suggested, its not even able to flash the recovery.

stinvilla said:
Mission accomplished? Kindly share how you were able to resolve it as I am still faced with the problem. I have tried all the recommendations here
Click to expand...
Click to collapse
Anyone?

No one?

Lenovo k3 note stuck on logo
I want volte support in k3 note so I know the cm14 is with volte support when I am trying flash cm14 with twrp the zip file successful install. But in log show "E: unknown commad[log] two rows
After that when I power on the phone its stuck on logo.
Sorry for grammar errors
Give me solution....

How to Root Samsung Galaxy S6 SM-G920T T Mobile Runing 6.0.1 Marshmallow

Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet.I Dont Know if it Will Work on Other Firmware. I Tried On 6.0.1
"CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip" Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
Download And Install the Samsung USB Driver in your PC.
Extract the CF-Auto-Root files in your PC.
Switch off your Mobile.Enter into Download mode->Volume Down+Home+Power Buttons.
After entering into Download Mode it will say Warning Press Volume Up button to continue.
Connect Your Mobile With PC via USB Cable.
Launch Odin Application.It Will Show the message added.If you did not get this message Repeat the above steps.
After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file Select it.Tick the Auto reboot.
Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
Reboot again.
You can See the Superuser after the Reboot in your Applications list.

This will trip Knox correct?
Sent from my SM-G920T using Tapatalk

I am also curious will this trip Knox?.. I'm assuming anything involving odin is an automatic yes?.

Yes All Rooting trips knox

Do you need to turn on OEM unlocking?

It failed for me did all the steps.

Copied and pasted the OP and adding my own notes:
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.

ktrinh4213 said:
Copied and pasted the OP and adding my own notes:
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Click to expand...
Click to collapse
Been searching all day and found this and am curious if it works on the EPF1 build of the s6. I keep hearing that my bootloader is locked and it will brick my device so just wanted some confirmation that someone has done this with the same phone and build that i have and that it works without messing anything up. thanks in advance

kenpachi100 said:
Been searching all day and found this and am curious if it works on the EPF1 build of the s6. I keep hearing that my bootloader is locked and it will brick my device so just wanted some confirmation that someone has done this with the same phone and build that i have and that it works without messing anything up. thanks in advance
Click to expand...
Click to collapse
It works, because I was on stock before I rooted. You have to unlock your OEM bootloader using steps 5 and 6 that I mentioned, or you will soft-brick your phone.

ktrinh4213 said:
It works, because I was on stock before I rooted. You have to unlock your OEM bootloader using steps 5 and 6 that I mentioned, or you will soft-brick your phone.
Click to expand...
Click to collapse
So youve done this on your phone?
I have already toggled the oem unlock option but i was told by samsung support that it doesnt unlock the bootloader.
Sorry not trying to be annoying i just really dont wanna mess my phone up. Just to be certain my s6 is stock ota 6.0.1 from tmobile with the EPF1 build.

kenpachi100 said:
So youve done this on your phone?
I have already toggled the oem unlock option but i was told by samsung support that it doesnt unlock the bootloader.
Sorry not trying to be annoying i just really dont wanna mess my phone up. Just to be certain my s6 is stock ota 6.0.1 from tmobile with the EPF1 build.
Click to expand...
Click to collapse
I know for sure it works because I did it the wrong way, and found out the right way. When you Unlock OEM, it unlocks your FRP (Factory Reset Protection). Without that being unlocked, you will be in a bootloop with the Samsung splash screen with the words FRP Locked (or something similar) at the top left hand corner until you flash the stock ROM from Sammobile via Odin.
Without following the steps I prescribed, you will soft-brick your phone, and ultimately, you will lose all data and information saved on your phone anyway. Unlocking it will remove the FRP lock so that when you reboot after rooting with CF-Auto-Root, you can log into your phone as usual (fingerprint, password, PIN, etc.) rather than being met with that Samsung splash screen.

ktrinh4213 said:
I know for sure it works because I did it the wrong way, and found out the right way. When you Unlock OEM, it unlocks your FRP (Factory Reset Protection). Without that being unlocked, you will be in a bootloop with the Samsung splash screen with the words FRP Locked (or something similar) at the top left hand corner until you flash the stock ROM from Sammobile via Odin.
Without following the steps I prescribed, you will soft-brick your phone, and ultimately, you will lose all data and information saved on your phone anyway. Unlocking it will remove the FRP lock so that when you reboot after rooting with CF-Auto-Root, you can log into your phone as usual (fingerprint, password, PIN, etc.) rather than being met with that Samsung splash screen.
Click to expand...
Click to collapse
So you were on 6.0.1 stock ota when you did it?
Also will doing it this way wipe my data or just install root?
Also also would i just flash twrp via odin after doing this or..?

kenpachi100 said:
So you were on 6.0.1 stock ota when you did it?
Also will doing it this way wipe my data or just install root?
Also also would i just flash twrp via odin after doing this or..?
Click to expand...
Click to collapse
Yes
No, it just installs root.
This does not automatically flash TWRP for you, it's something you have to do yourself.

ktrinh4213 said:
Yes
No, it just installs root.
This does not automatically flash TWRP for you, it's something you have to do yourself.
Click to expand...
Click to collapse
I know it doesnt automatically flash TWRP i was asking how i would flash twrp afterwards. I guess it would have to be odin since you cant flash it from the phone without a custom recovery. Also, again just trying to clarify, your build number had EPF1 when you did this also?

kenpachi100 said:
I know it doesnt automatically flash TWRP i was asking how i would flash twrp afterwards. I guess it would have to be odin since you cant flash it from the phone without a custom recovery. Also, again just trying to clarify, your build number had EPF1 when you did this also?
Click to expand...
Click to collapse
Go to the TWRP website and find the latest build number, or download the TWRP Manager app on the Play Store and you can download and flash it from there.
Yes, my ROM was STOCK OTA.

ktrinh4213 said:
Go to the TWRP website and find the latest build number, or download the TWRP Manager app on the Play Store and you can download and flash it from there.
Yes, my ROM was STOCK OTA.
Click to expand...
Click to collapse
Okay, thanks for answering all my questions and the help!

works like a charm. thanks for sharing!

Will this work for this Build Number which is MMB29K.G920TUVU4EPF1?

php111 said:
Will this work for this Build Number which is MMB29K.G920TUVU4EPF1?
Click to expand...
Click to collapse
Yes it will.

I took the 6.0.1 OTA Update. So is this what I need to do?
First, download 6.0.1 from like the site Sammobile and Flash via ODIN and should I check or uncheck Auto reboot?
Than once I flashed than follow all 13 steps given in post #7 of this thread
Once I followed the 13 steps than flash TWRP? Should I flash via ODIN or recovery? If in ODIN should check or unchecked Auto reboot?
Once I got TWRP than install Super SUPER SU from Play Store

Grand Prime FRP lock and root problem!

So I tried to root my device using Kingo root first but after 73% it failed to root the device.
Then I tried to do it manually. First I tried to install TWRP but even it failed and some green notice appeared in recovery mode saying "Custom binary FRP lock on" or something like that (Cannot remember the exact phrase.)
Then again I searched and found out this bypassing apk and tried to off the FRP lock and it was successfully done and after that I booted the TWRP even that was successfully completed (as the odin said) :fingers-crossed:
But when I tried to boot to TWRP mode it gave some kind of error message and again I went in to the same old stock recovery mode. That means booting the TWRP wasn't successful as odin mentioned and then I noticed again "FRP lock ON".
What is the solution for this problem? I seriously need to root this device but I don't want to use pre rooted firm wares cause it will give base band problems and such things! Any solutions guys? :highfive:

Doesn't anyone have a proper solution for this?

chamathka_sooriyapala said:
So I tried to root my device using Kingo root first but after 73% it failed to root the device.
Then I tried to do it manually. First I tried to install TWRP but even it failed and some green notice appeared in recovery mode saying "Custom binary FRP lock on" or something like that (Cannot remember the exact phrase.)
Then again I searched and found out this bypassing apk and tried to off the FRP lock and it was successfully done and after that I booted the TWRP even that was successfully completed (as the odin said) :fingers-crossed:
But when I tried to boot to TWRP mode it gave some kind of error message and again I went in to the same old stock recovery mode. That means booting the TWRP wasn't successful as odin mentioned and then I noticed again "FRP lock ON".
What is the solution for this problem? I seriously need to root this device but I don't want to use pre rooted firm wares cause it will give base band problems and such things! Any solutions guys? :highfive:
Click to expand...
Click to collapse
What is your Galaxy Grand Prime model

tasnim_tamim said:
What is your Galaxy Grand Prime model
Click to expand...
Click to collapse
It is SM-G531F Model!

FRP lock off
Remove google and Samsung account
And lockscreen passcode
Then it turn off FRP
It works for me ??

Oneplus3T stuck while trying to unroot using SuperSu

Hi,
I use a oneplus 3T
I had previously rooted my phone successfully using SuperSu and TWERP and I used it for 6 months. Now I tried to unroot it and did a full unroot using SuperSu. But my phone is stuck now. when I restart it oneplus logo comes. If I go to recovery mode, it just restart again and if I go to fastboot, nothing happens. When I connect my device to pc, it doesnt show up there. So I am not able to do fastboot because when I tried typing it, an error came.
Please someone help me out with this and guide me with a solution.
Thanks
EDIT:
Hey Guys after 5 hours of research and experimentation, I found the solution. If anyone in future have a similar problem, please PM me.

Abhimanyubadola said:
Hi,
I use a oneplus 3T
I had previously rooted my phone successfully using SuperSu and TWERP and I used it for 6 months. Now I tried to unroot it and did a full unroot using SuperSu. But my phone is stuck now. when I restart it oneplus logo comes. If I go to recovery mode, it just restart again and if I go to fastboot, nothing happens. When I connect my device to pc, it doesnt show up there. So I am not able to do fastboot because when I tried typing it, an error came.
Please someone help me out with this and guide me with a solution.
Thanks
Click to expand...
Click to collapse
Just download and flash your rom, assuming it's the stock OOS.
It will be unrooted afterwards.
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
Just download and flash your rom, assuming it's the stock OOS.
It will be unrooted afterwards.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
Hi, thanks for the reply.
I found out, I can fastboot because when I typed fastboot devices, it showed me the serial number.
Now I can't switch on my phone, because it gets stuck on the oneplus logo screen. I tried going in recovery but it still restarts. but i'm not able to access any screens other than fastboot.
I tried flashing TWRP. On pc it said successful. but no changes on my phone. I think I have accidentally deleted my OS and TWRP. but I cant figure out how to install these again.
How do I flash a ROM, if I can't access the storage of my phone.
I don't know what to do now.

Abhimanyubadola said:
Hi, thanks for the reply.
I found out, I can fastboot because when I typed fastboot devices, it showed me the serial number.
Now I can't switch on my phone, because it gets stuck on the oneplus logo screen. I tried going in recovery but it still restarts. but i'm not able to access any screens other than fastboot.
I tried flashing TWRP. On pc it said successful. but no changes on my phone. I think I have accidentally deleted my OS and TWRP. but I cant figure out how to install these again.
How do I flash a ROM, if I can't access the storage of my phone.
I don't know what to do now.
Click to expand...
Click to collapse
Try flashing another version of twrp using fastboot...open recovery....if it stuck on boot logo then wait for few minutes....it will work
Use power button and volume down button to boot into recovery!
Sent from my OnePlus3T using XDA Labs

Solved
Hey admin I got the solution. Please close this thread

Note 8(SM-N950F Exynos) Root problems.

I am not an expert user but have always been able to root and install custom ROMs over the past years to devices including ASUS A500, Nexus 4 and 7, Samsung P605, Note 4, and note 8.
However, I have obviously done something to my Note 8 and can no longer install TWRP or SU or anything in fact. This happened after I moved from the official Samsung Pie release to the Lineage 17.1 (Android 10) which I ran successfully for a couple of weeks; but I missed the Samsung DEX support and I used this heavily for streaming to my non-smart TV. So whilst I loved the Lineage experience I moved back to the standard Samsung Pie.
This caused a couple of problems in that I could no longer use some of the Samsung apps since the device recognised that it had been rooted and it burned in the warranty bit, and Samsung ell me that the only way around this on the note 8 is to replace the processor board; and this seems to be correct.
So, I now want to go back to Lineage 17.1, since it was stable and I have lost interest in anything Samsung after this experience.
I can no longer install TWRP (or SU or Magisk) to allow me to root and install Lineage. I have done everything on all the helpful forums, including wipes etc, followed install instructions to the letter (many times) and whilst the loading of TWRP via Odin goes through the motions and completes properly, when I try to go into it all I get is the regular Samsung boot stuff. I have tried SU etc via an SD Card but these always give errors, I have tried the no verify software but it too won’t install.
Many attempts have been made to load TWRP and sometimes it screws up the phone but I can always load the latest Samsung software via Odin; here is the latest Samsung software I am using:-
- AP_N950FXXSADTC4_CL16983991_QB29943831_REV00_user_low_ship_meta_OS9.tar.md5
- BL_N950FXXSADTC4_CL16983991_QB29943831_REV00_user_low_ship.tar.md5
- CP_N950FXXSADTB1_CL1300388_QB15232239_SIGNED.tar.md5
- CSC_OLN_N950FOLNADTB1_CL16983991_QB29490845_REV00_user_low_ship.tar.md5
I would appreciate any help whatsoever. Perhaps someone has done the same thing? Maybe I am screwed!

@neilgoodyer
Did you remember to turn OEM unlock on?
When the phone is in download mode, does it say "prenormal" anywhere? If it does, you won't be able to flash TWRP until that disappears, I don't know the exact way to get rid of it, but I usually sign in to my Samsung account on the phone, then check for an update which registers the device, then it soon disappears for me (prenormal)

stonedpsycho said:
@neilgoodyer
Did you remember to turn OEM unlock on?
When the phone is in download mode, does it say "prenormal" anywhere? If it does, you won't be able to flash TWRP until that disappears, I don't know the exact way to get rid of it, but I usually sign in to my Samsung account on the phone, then check for an update which registers the device, then it soon disappears for me (prenormal)
Click to expand...
Click to collapse
Thanks for the advice:
Yes, OEM unlock on. In fact it seems to turn it on automatically when I invoke developer mode. When in download mode I don't get "prenormal" anywhere. The only somewhat negative comment on that screen is the the warranty count is 1 because I previously loaded Lineage 17.1 Odin completes normally indicating all was well but still only the Samsung bootloader.
Samsung Account is working and I am always able to get my backup loaded whenever I have to reload the current Samsung software,.
It's got me bamboozled and without TWRP I can't do anything......, can't even load a previous custom rom and work my way forward from that. I did think about a previous Samsung software release for the Note 8 Exynos but the "archive" at sammobile doesn't show any.

neilgoodyer said:
Thanks for the advice:
Yes, OEM unlock on. In fact it seems to turn it on automatically when I invoke developer mode. When in download mode I don't get "prenormal" anywhere. The only somewhat negative comment on that screen is the the warranty count is 1 because I previously loaded Lineage 17.1 Odin completes normally indicating all was well but still only the Samsung bootloader.
Samsung Account is working and I am always able to get my backup loaded whenever I have to reload the current Samsung software,.
It's got me bamboozled and without TWRP I can't do anything......, can't even load a previous custom rom and work my way forward from that. I did think about a previous Samsung software release for the Note 8 Exynos but the "archive" at sammobile doesn't show any.
Click to expand...
Click to collapse
When you flash TWRP with Odin, does it pass or give any error code? Have you tried a different TWRP version, maybe the one you have has become corrupt somehow.

stonedpsycho said:
When you flash TWRP with Odin, does it pass or give any error code? Have you tried a different TWRP version, maybe the one you have has become corrupt somehow.
Click to expand...
Click to collapse
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.

neilgoodyer said:
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
Click to expand...
Click to collapse
Tried a different TWRP?
Like you said above, I too am bamboozled too.

neilgoodyer said:
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
Click to expand...
Click to collapse
Have you tried ticking on the format option in odin so it deletes everything before flashing the firmware? I would have tried to flash just twrp with the format option ticked to see what happens. I would do a little research before just trying to do that though.
Edit: With the phone connected to your PC using command prompt (in your adb location) type in fastboot boot recovery.img and see what happens.

MrMike2182 said:
Have you tried ticking on the format option in odin so it deletes everything before flashing the firmware? I would have tried to flash just twrp with the format option ticked to see what happens. I would do a little research before just trying to do that though.
Edit: With the phone connected to your PC using command prompt (in your adb location) type in fastboot boot recovery.img and see what happens.
Click to expand...
Click to collapse
Thanks, I will research further that suggestion with odin. I did try doing things with adb, however, it doesn't seem to work with the samsung note 8 (mine anyway).