Hi, just bought an S5 G900F (international version)... and i wanted to install a custom recovery than root.. than flash rom. Im experienced in this matter... but ... im having all sorts of odd problems. I tried several reocvery (openrecovery, twrp, philztouch)... non stick when i reboot?
I tried several times... odin says everything installed fine.
I wanted to install cf-root... i did it win odin and when phone restarted it says: "recovery booting.... recovery is not seandoird enforcing ... set warranty bit : recovery
Who can help me??
PS Im on lollipop 5.0 if it makes any difference. All attempts were realized with different versions of odin
People have success with TWRP 2.8.7.0 and ODIN 3.10.6
Then SuperSU from TWRP if it sticks
http://forum.xda-developers.com/showthread.php?t=2727406
Tried no luck. I simply get the stock recovery all the time after restart
daniel_cassian said:
Tried no luck. I simply get the stock recovery all the time after restart
Click to expand...
Click to collapse
Try unchecking "Auto reboot" in ODIN, and once the flash has finished, pull the battery, replace and boot into recovery
just tried it... still no go (... do you think i would have more success trying from adb?
Lol this phone has smth against me.
Tried adb: as long as i have it in "desktop" mode adb devices finds it; as soon as i adb reboot bootloader, using the fastbootdevices... adb doesnt see it anymore... so i cant proceed to the flashig
I know you know what you're doing when it comes to this stuff, as you said
But just to make sure, can you post the exact step by steps you're using to try and flash CF Auto-Root and TWRP etc with ODIN?
Yes of course. As i doesn't work for me... i (even) hope im doing something wrong, so we can get to the bottom of this.
So, installed S5 drivers, Enabled usb debuggin in phone (dev menu). Put phone in dl mode (vl dwn+power+home), open odin, select at AP the recovery (tried about 3 recoveries, older versions and newer ones, twrp, phil, open). I have both (by default) checked auto reboot and f-reset time... connect phone with usb cables (tried 2) (connected directly to mb, no extension)... hit start... get the pass message.. phone resets... goes into android. I power off, go to recovery mode (vl up+power+home) and... i get the stock recovery every single time.
Tried something wierd... flashed through Odin CF-root first (with intention to flash after twrp ... as it says phone needs to be rooted first)... it flashes ok (odin says pass, successful 1), reboot (or go to recovery mode)... i get that seandroid error.
Tried to to with with apps from android as well... it doesnt let me.. obviously as most ask phone to be rooted.
What am I missing?
Those are the correct steps, it definitely should have flashed
Doing this from a native PC yes? Ive seen people trying it from Macs and it fails every time
Only thing I can think of right now is try using a different PC
You don't need USB debugging enabled for flashing with ODIN, download mode has no idea what settings you have enabled in Android
Like your method, I just do this:
Samsung Drivers (KIES3 installs them for you anyway)
Vol Down & Home & Power for Download Mode
Connect phone to PC USB
Leave ODIN defaults set (3.09 or 3.10.6)
Select CF-Auto-Root-klte-kltexx-smg900f.tar.md5 in AP/PDA section of ODIN
Wait for it to become ready
Hit start
Phone reboots, and I have root
You could try factory resetting the phone, and trying again, see if that does anything, or at least clear the caches from stock recovery first
Related
Hi all,
I am not sure whether this the right forum to post my query. It's been a year a since I bought my S4 (i9500) so O thought of rooting and installing recovery on my phone. I was on stock 4.4.2 and I was able to root my phone using the CF-AUTOROOT, but after that when i am trying to flash a custom recovery using Odin it ends up in the download mode. I have disabled knox after rooting the phone and my phone status is now custom and so I cannot get any official update.Is there anything I did wrong which is forcing the download mode to overwrite the custom recovery I am tryjng to install???? Any help is highly appreciated.
Thank you,
Bobby Thomas.
Just boot into download mode. Uncheck auto-reboot in Odin and flash the recovery. That's it.
Thanks Lenny for your prompt reply, actually I did try that but after the manual boot it again goes back to the download mode instead of recovery mode....I even tried to install it through ADB shell but with no luck...I just goes to the download mode whatever I tried to do...
I was having a problem with the system trying to enforce the stock recovery every time I flashed TWRP through Odin. Turns out I got it by simply removing the battery as soon as Odin finished the job and restarted my phone. Waited for a few seconds, put battery back on and voila.
It worked for me. Do it at your own risk.
I also had the same trouble and had to untick auto-reboot, take out battery reboot back into download mode flash again. The first time I tried that it didnt work and the only way I got it to work was you Cyanogens windows installer, then went into recovery and flash the rom of choice.
What happens when you boot your phone, download terminal emulator from the market (or use adb) and type the following:
su
reboot recovery
My Tmobile Note 3 (SM-N900T) hangs when I try to get into recovery mode and also normal mode (at the Samsung screen in normal mode, so presumably I can't use ADB).
I have installed TWRP and CWM via Odin and the same thing happens. It's like they don't have the permissions they need.
I have installed various "stock firmware" (kitkat and lollipop) but the same thing happens (with or without a custom recovery)
Initially I had a boot loop problem after a failed OTA update. So I was using Odin to put on stock firmware. and flashing ROMs. Clearly I messed something up (didn't clear cache once, maybe?).
I don't have a serial number on my sticker near the battery so I cant recover via Kies (no idea if that would even work) so if someone can get me a serial number to use that could be handy.
Does anyone have any suggestions? I am worried there is just some button in Odin I need to click or something new I need to flash to fix the bootloader. I have tried everything in these forums.
Thanks.
When you flash TWRP or CWM, are you checking the auto-reboot in Odin? If you are, try this: launch Odin, uncheck everything except auto-reboot, flash TWRP or Odin, when you see the word "reset" in the status windows, remove the USB cable, remove battery, replace battery, use button combination to boot into recovery.
audit13 said:
When you flash TWRP or CWM, are you checking the auto-reboot in Odin? If you are, try this: launch Odin, uncheck everything except auto-reboot, flash TWRP or Odin, when you see the word "reset" in the status windows, remove the USB cable, remove battery, replace battery, use button combination to boot into recovery.
Click to expand...
Click to collapse
I have been doing this (but I didn't do it every times). It does not help.
Hello Team
I have an unidentified GT-I9500, that I need to set in recovery mode.
Using Odin 3.10 and trying all different and latest versions of either CWM, TWRP or Phillipz Custom Recovery.
Even that I am able to set the phone in download mode, Odin states all OK (Pass) and I see the green bar on the phone doing progress ok, when I try to enter recovery, it always goes into stock recovery
Need to run the Screen Passcode Removal zip (only in recovery)
Any help or sugestions ?
I have tried AT&T, Verizon, International etc versions of both CWM and TWRP and none of them work
(they all go Ok on the process, but the phone never gets into Custom Recovery
Thank you in advance
Jose
What is the model number displayed in download mode?
Thanks a lot for your reply
It states:
PRODUCT NAME: GT-I9500
CURRENT BINARY: SAMSUNSG OFFICIAL
SYSTEM STATUS: Official
And in recovery mode it states Android Recovery Mode 3e
Any help is welcomed !
Make sure you're using the original cable, and move the cable to a different port if necessary. This is an Odin issue, not phone.
Thank you !
Tried with 2 different cables, will look for a third one.
Even if a see on the phone the "blue bar" that means download in progress, and Odin says OK, PASS, it can be the cable ?
Thanks a lot for your help
BTW if you know how to remove the Screen Lock password with the Stock Recovery, that sis welcomed as well
I have issues all the time with my S4 and often it just comes down to how I am pressing the buttons to get into other the boot download mode or the custom recovery rom. I swear I press them exactly at same time ,but then I do it differently and it works.
Also found cable / USB ports can affect it too. My home PC for some reason is terrible for using Odin, but then my laptop it works fine.
josecheja said:
Hello Team
I have an unidentified GT-I9500, that I need to set in recovery mode.
Using Odin 3.10 and trying all different and latest versions of either CWM, TWRP or Phillipz Custom Recovery.
Even that I am able to set the phone in download mode, Odin states all OK (Pass) and I see the green bar on the phone doing progress ok, when I try to enter recovery, it always goes into stock recovery
Need to run the Screen Passcode Removal zip (only in recovery)
Any help or sugestions ?
I have tried AT&T, Verizon, International etc versions of both CWM and TWRP and none of them work
(they all go Ok on the process, but the phone never gets into Custom Recovery
Thank you in advance
Jose
Click to expand...
Click to collapse
The solution:
Uncheck auto-reboot in Odin before flashing the recovery.
Lennyz1988 said:
The solution:
Uncheck auto-reboot in Odin before flashing the recovery.
Click to expand...
Click to collapse
Thank you
Just did so..
How do I got out of download mode then ?
Its showing the light blue that the TWRP recovery was trasferred, and Odin (using 3.10) says OK
josecheja said:
Thank you
Just did so..
How do I got out of download mode then ?
Its showing the light blue that the TWRP recovery was trasferred, and Odin (using 3.10) says OK
Click to expand...
Click to collapse
Just hold the power on button until it reboots or remove battery.
Lennyz1988 said:
Just hold the power on button until it reboots or remove battery.
Click to expand...
Click to collapse
Lennyz1988
It worked !!!! thanks a lot Lennyz !!
Tried hundred times.....even unchecking the Autoreboot Option in Odin in past tries, but seems with the wrong Recovery version.
I am on TWRP recovery now !!!
Now let me see if I can run LockScreen_Security_bypass...the reason I needed Custom Recovery...)
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
Hi All,
Got a S5 G900I here that's doing my head in! Stuck in the infamous bootloop at the Samsung logo.
I have been a long time reader of these forums and have prior experience from flashing Samsung phones but this one is driving me mad!
I can put the phone into Download mode without an issue, phone is detected in Odin and I can flash any firmware I try to it (Have tried original 4.4.2 , 5.0 and latest 6.0.1 firmwares from SamMobile). Odin goes through the entire process, reports as "Pass" but then the device goes straight back into the reboot loop and will never fully boot up.
I can also use Odin to push TWRP / CWM / PhilzTouch recoveries, however the device will never boot into the recovery partition. I get the blue "Recovery Booting" message briefly, then the device bootloops again.
Does anyone have any further suggestions to try and get this phone operational again?
I have tried multiple versions of Odin, multiple firmware versions, different computers, different USB cables, different USB ports etc.
I look forward to hearing back from you
Try this :
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
andra.soul.catcher said:
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
Click to expand...
Click to collapse
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
AS93 said:
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
Click to expand...
Click to collapse
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
andra.soul.catcher said:
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes when I am booting into recovery mode and can see the blue text "Recovery Booting" in the corner of the screen I let go of the power button - device still boot loops.
Have flashed recovery then removed battery - still cannot get it into recovery.
I have seen some Samsungs have hardware issues with their NAND chips but in these cases there are a lot of errors relating to NAND displayed on the screen when I've seen it be a hardware issue. None of these appear on this phone - convinced it has something to do with software.
I found these threads - exactly the same issue as me, and at the end it says they fixed it by flashing a specific bootloader however I have a G900I and the phone in this thread was a G900F
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926/
https://forum.xda-developers.com/galaxy-s5/help/samsung-s5-sm-g900f-stock-flash-caused-t3771105
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926
Have tried countless different versions of ODIN / recovery / stock firmware , including the "service firmware with the separate files G900IDVU1BOE1_CL4826466_QB4839040_REV00_user_low_ship_MULTI_CERT"