Database Users

SM-N910F > Bootloop // ROM Problems || Please Help

So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
// Edit:
// It is a German Device from Telekom.
// If that helps or makes a little difference.
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.

Try Samsung care

R3dRacoon said:
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Click to expand...
Click to collapse
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)

Battlehero said:
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Click to expand...
Click to collapse
Thanks for the response.
What can I do to get a correct working System back? (Theoretically, I got time and bandwidth.)
Since flashing the Stock ROM did not quiet work.

medo sator said:
Try Samsung care
Click to expand...
Click to collapse
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.

R3dRacoon said:
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
Click to expand...
Click to collapse
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom

medo sator said:
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
Click to expand...
Click to collapse
I've already tried to flash TWRP via Odin, but I've never seen it.
Flashed recovery was for trltexx.
Getting to Recovery should be the same as getting to Download Mode, or?
Anyways. Will try it with tbltetmo and report back.
// Just installed the tbltetmo.
// Can't see how to get into the recovery.
// Am I missing something?

Update:
Just signed up at sammobile and downloaded the BOB6 (4.4 i think) for T-Mobile.
Flashed via Odin.
Seems like it does work again.
Currently its installing like 260 Apps.
Let's see.
// Edit: Nah. It got even worse.
// But I got a Recovery. So that's something.
IT ****ING WORKS NOW
Went into the recovery and cleared cache and data. (Kinda stupid I did not do it inb4)

Do a clean install in Odin. Since it came with stock android 5.1.1, then flash the 5.1.1 stock firmware in Odin. If you have a locked device of a specific carrier it will be even better to use the firmware made for that carrier only. And check the "Nand erase all" option in odin before hitting the start button to flash. That will erase all the data from ur phone and will do a clean install. Your phone must then boot normally. Also note that android 5.0 root file may not work for 5.1. Also check the model number before flashing.

SMG900A Stuck In Boot Loop

I need this fixed asap as I need my phone for school.. I have no idea what Happened honestly, I just restarted my phone and it started doing this. The only thing i recall doing is possibly disabling SuperSU on accident before I restarted my phone.
All I've done so far is download the stock firmware from SamMobile and attempted to flash it, but when i do i get an (auth) failed code from Odin, I've been searching for hours and haven't found anything that has helped..

If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?

Can you help with a newer model?

*Detection* said:
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Click to expand...
Click to collapse
i don't have anything recovery installed, its jsut the normal android recovery. I thought about reflashing supersu but I'm not sure how without a recovery..

Have you tried the factory reset from normal recovery?

*Detection* said:
Have you tried the factory reset from normal recovery?
Click to expand...
Click to collapse
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..

What about a SM-G900P?

TheAgonistxX said:
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
Click to expand...
Click to collapse
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28

*Detection* said:
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
Click to expand...
Click to collapse
Tried flashing TWRP with the same end result.. This is dumb really frustrating -.- is there any way to install Supersu without a recovery?

CF Auto Root, but it'll likely fail too due to the bootloader

II have been working on mine same model and it is because once you screw up ,which i did,the locked boot loader wont let anything by. a relative pretty much started the problem by flashing a ROM and erasing everything. this one wont even go into recovery. still wont give up until I figure out a way just because.......

TWRP not working with bph6

I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.

kociubin said:
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
Click to expand...
Click to collapse
In Odin flash an older firmware then reroot and wait for a root update from Chainfire and the TWRP team
I know a couple people that have done that.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F

When I first upgraded to the new firmware, I found the same thing that you did - I wanted to be able to flash custom roms and didn't know when or if TWRP and ROOT was going to be possible with this new firmware - so I used odin and reflashed July's Firmware and I was able to do so without any Issues - so then I decided to try to upgrade the AP/CSC/CP files from the latest update and replaced the bootloader with the bootloader from july's update and it worked.
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not an indication of future issues for rooting samsung phones....

mocsab said:
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not indication of future issues for rooting samsung phones....
Click to expand...
Click to collapse
No it isn't. Korean models had already been incompatible with official TWRP since firmware APG7 and I confirmed it working again when I replaced the kernel inside TWRP with one built from the latest source released by Samsung. So, someone needs to build a new TWRP recovery with BPH6 kernel source and everything will become fine again.

I didnt know that but it is very good news as far as I am concerned.
I have alwasy been fearful that Samsung was going to eventually lock down their international phones like they did to the US Variants - and when this originally happened to me, I started thinking that maybe my worst fears had come true. Thanks for the information....

I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user

Xlim said:
I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Click to expand...
Click to collapse
pls send related boot loader download link

same iussue .. some news??
by the way to use root now i put the old firmwere

FARSHOOD said:
pls send related boot loader download link
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24671318762848807

When flashing bootloader in Odin there is an options tab, there are checkboxes - Auto Reboot which is checked - Re-Partiion which is unchecked - and - F.Reset Time which is checked, I flashed new bootlaoder and modem and now my phone will not restart no matter the key combination I press. So Are those checkboxes suppose to be checked off or unchecked

What ROMs can I install using SafeStrap on a locked Verizon bootloader?

I have a Galaxy S5 (Verizon) SM-G900V that's running stock rooted Lollipop. Safestrap is on here, but yes, the bootloader is locked. Other than going to Marshmallow (and losing root), are there any custom ROMs (I'm looking for speed and stability) that this phone can take? Or am I stuck with stock, which means I'm stuck with Lollipop if I want to stay rooted?

My choice is this one without root for CID11 or full-featured systemless devbase for CID15.

Thank you. I assume I use safestrap to install on my rooted stock CID 11, but on this new one without root won't be able to restore apps from Titanium. Are there any other alternatives an 11 can use and keep root, and if I try one can but change my mind can I restore a backup in safestrap to get back to rooted stock?
bbsc said:
My choice is this one without root for CID11 or full-featured systemless devbase for CID15.
Click to expand...
Click to collapse

androidman807 said:
1) is that right that it's possible to safestrap a different ROM with my locked bootloader?
2) If yes, how can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
3) if I have a SS backup of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL? Or could I just re-install the stock LL image?
4) can I/should I update the modem in this process, or does the locked bootloader prevent that?
Click to expand...
Click to collapse
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.

Thanks. I've tried casting a broader net, unsure if my problem was Verizon-specific or not. Turns out, it's even more specific than that, as at least some 900Vs have unlocked bootloaders and some (mine) don't.
As I look back over my journey, you were there from the beginning when I was trying to upgrade from 4.4.2 to my current Lollipop and keeping root. Following the steps of the amazing @jrkruse led to different problems, which still persist. There seems no way to fix that, from which I conclude the jrkruse stock ROM and this phone don't get along. Hence, the idea to try a different ROM other than this LL. It seems that my locked bootloader has me on stuck on this particular stock ROM if I want to keep root. There is no list of other ROMs I can put on this CID11, and I'm not sophisticated enough to know which I can try and Safestrap back safely if things aren't wonderful. This has me doing a hot reboot every day or two when I see wifi can't get DNS, but I don't see any other option other than buying a newer Galaxy with a microSD card and an unlocked bootloader (maybe the S8?). Regardless, this sums up my journey, I've learned a lot along the way, and both you and @KazuDante were extremely helpful and earned my Thanks button many many times. Thanks again.
bbsc said:
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse

bbsc said:
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.

androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.

Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
bbsc said:
androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.
Click to expand...
Click to collapse

androidman807 said:
Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
Click to expand...
Click to collapse
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.

Titanium is a big reason why I want to keep root. So BOK3 and DQI2 are ones I can root and still return to PB1. Thanks, I'll start looking for them and their rooting procedures.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse

androidman807 said:
So BOK3 and DQI2 are ones I can root and still return to PB1.
Click to expand...
Click to collapse
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.

androidman807 said:
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.
Click to expand...
Click to collapse
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.

Thank you. I was hot on the modem idea when I was going to switch to Lineage or something else as a natural step. But since it's tied to 4G and cell service and not my sporadic DNS-on-wifi issue, I'm not sure I see the benefit, but then I could be wrong. I figure a different ROM will have different drivers for the wifi radio and solve things. At least that's been my hope all along.
KazuDante said:
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.
Click to expand...
Click to collapse

Thank you! I will likely flash this with Odin over the weekend (or with SafeStrap?). I've found QI2 here, the first of the two links. Just to be prepared, what steps will I take to rooting this new ROM?
bbsc said:
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse

Where can I find BOK3, and how do I root it after installation if I don't have TWRP (but only safestrap)?
Edit: here's OK3 with steps on how to root it, but they're quite scary and possibly outdated.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse

Thanks again - I flashed with Odin the DQI2 I found but didn't know how to root it (Safestrap erased and no TWRP). Maybe the answer is the same as the other post I just replied to. That's obviously a blind spot I have that has me stuck on PB1 - I don't know how to root anything else on this CID 11.
bbsc said:
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse

Help recovering data

So I have a friend who decided to mess with his phone, of course without doing a backup, and now he's stuck in a situation that it can't boot even into recovery.
Currently all I see when booting to recovery:
Recovery Booting. . . . .
Set Warranty Bit : recovery
The phone is G900F
He has no idea what version was installed on it before.
I don't need the phone to boot, I need to recover the files on it.
Being a oneplus person myself, I'm not that familiar with samsung phones (my latest samsung was s2).
I've tried to install with odin (3.0.7 - if that matters) the following recoveries:
official twrp 2.8.7
twrp
cwm
All these recoveries showed "Recovery is not seandroid enforcing" message as well as the above when trying to boot into recoveries.
I've tried the official recovery as well:
https://forum.xda-developers.com/galaxy-s5/general/sm-g900f-stock-recovery-5-0-lollipop-t3228871
which removed the "seandroid" message, but that's all.
Not sure what I'm missing.
Any help would be appreciated!

Tahvok said:
So I have a friend who decided to mess with his phone, of course without doing a backup, and now he's stuck in a situation that it can't boot even into recovery.
Currently all I see when booting to recovery:
Recovery Booting. . . . .
Set Warranty Bit : recovery
The phone is G900F
He has no idea what version was installed on it before.
I don't need the phone to boot, I need to recover the files on it.
Being a oneplus person myself, I'm not that familiar with samsung phones (my latest samsung was s2).
I've tried to install with odin (3.0.7 - if that matters) the following recoveries:
official twrp 2.8.7
twrp
cwm
All these recoveries showed "Recovery is not seandroid enforcing" message as well as the above when trying to boot into recoveries.
I've tried the official recovery as well:
https://forum.xda-developers.com/galaxy-s5/general/sm-g900f-stock-recovery-5-0-lollipop-t3228871
which removed the "seandroid" message, but that's all.
Not sure what I'm missing.
Any help would be appreciated!
Click to expand...
Click to collapse
Hmm...
I see that your friend messed up his phone very well .....
Hopefully the eMMC memory is not corrupted becuase then only motherboard replacement would be necessary.
Summarising what you wrote:
1. you flashed "official recovery 2.8.7" -> where did you get it from? 2.8.7 is the very old version!
2. you flashed unofficial TWRP very old (2014) recovery (I checked your link)
3. you flashed unofficial CWM very old (2014) recovery (I checked your link)
4. finally you flashed stock, from old OS 5.0 Lollipop recovery provided from entrusted source - nobody reported that it works in the thread.
I listed this for you in order to underline one thing - READ, READ, READ, ASK, ASK, ASK .... before flashing anything to the phone and tell it to your friend.
Le's start with flashing from ODIN ver 3.12.7 (I am using it) this version of TWRP:
twrp-3.1.1-0-klte.img.tar for G900F which is the latest official recovery:
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Read how to flash it with odin method (when you open the link).
Edit: Are you sure the phone is SM-G900F? Please check model number on the label under battery (inside the phone).
Edit2: When you enter odin mode check phone model version as well - it is provided by installed bootloader.

Many40 said:
Hmm...
I see that your friend messed up his phone very well .....
Hopefully the eMMC memory is not corrupted becuase then only motherboard replacement would be necessary.
Summarising what you wrote:
1. you flashed "official recovery 2.8.7" -> where did you get it from? 2.8.7 is the very old version!
2. you flashed unofficial TWRP very old (2014) recovery (I checked your link)
3. you flashed unofficial CWM very old (2014) recovery (I checked your link)
4. finally you flashed stock, from old OS 5.0 Lollipop recovery provided from entrusted source - nobody reported that it works in the thread.
I listed this for you in order to underline one thing - READ, READ, READ, ASK, ASK, ASK .... before flashing anything to the phone and tell it to your friend.
Le's start with flashing from ODIN ver 3.12.7 (I am using it) this version of TWRP:
twrp-3.1.1-0-klte.img.tar for G900F which is the latest official recovery:
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Read how to flash it with odin method (when you open the link).
Edit: Are you sure the phone is SM-G900F? Please check model number on the label under battery (inside the phone).
Edit2: When you enter odin mode check phone model version as well - it is provided by installed bootloader.
Click to expand...
Click to collapse
First, thank you for trying to help me!
Please see attachments:
https://drive.google.com/folderview?id=1euC7-CoBeeUQxTGXQnPPgRE2-5VxFXLh
You can see that it is indeed g900f. I've also checked under the battery.
I've flashed the recovery you asked, however I could not find odin 3.12.7 only 3.12.10, so I've flashed with that (the odin thread on xda does not provide a link for 3.12.7 download).
You can see that it's still not booting with that recovery, it's just stuck at "booting recovery" screen.
I'm thinking perhaps it has a bad bootloader? How would you suggest to proceed?

Tahvok said:
First, thank you for trying to help me!
Please see attachments:
https://drive.google.com/folderview?id=1euC7-CoBeeUQxTGXQnPPgRE2-5VxFXLh
You can see that it is indeed g900f. I've also checked under the battery.
I've flashed the recovery you asked, however I could not find odin 3.12.7 only 3.12.10, so I've flashed with that (the odin thread on xda does not provide a link for 3.12.7 download).
You can see that it's still not booting with that recovery, it's just stuck at "booting recovery" screen.
I'm thinking perhaps it has a bad bootloader? How would you suggest to proceed?
Click to expand...
Click to collapse
Ok. Let's continue ... I hope (as I had very similar situation) that the phone is not hardbricked and eMMC memory is not corrupted -> I faced this on my phone and finally had to replace motherboard.
But let's be optimistic:
1. For data recovery - I don't have a silver bullet for this but I found this software: http://www.recover-android-iphone.com/recover-android/how-to-recover-data-bricked-samsung.html
It needs working odin mode so under condition that it supports s5 G900F it should be able to restore some data.
2. For unbricking - I recommend to flash via odin the latest official Samsung stock firmware dedicated to your friend's country/region:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/
You must be registered to download the software. Link for odin 3.12.7 is available on the bottom of the download page.
Just to underline - odin flash most probably (anybody please confirm that) will wipe your data so be aware of that.
Good luck.

Many40 said:
Ok. Let's continue ... I hope (as I had very similar situation) that the phone is not hardbricked and eMMC memory is not corrupted -> I faced this on my phone and finally had to replace motherboard.
But let's be optimistic:
1. For data recovery - I don't have a silver bullet for this but I found this software: http://www.recover-android-iphone.com/recover-android/how-to-recover-data-bricked-samsung.html
It needs working odin mode so under condition that it supports s5 G900F it should be able to restore some data.
2. For unbricking - I recommend to flash via odin the latest official Samsung stock firmware dedicated to your friend's country/region:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/
You must be registered to download the software. Link for odin 3.12.7 is available on the bottom of the download page.
Just to underline - odin flash most probably (anybody please confirm that) will wipe your data so be aware of that.
Good luck.
Click to expand...
Click to collapse
Why a full firmware is needed? Perhaps I can flash only the parts required to get into recovery? I count mount the phone from recovery, that's why it's my priority.
I would like to know also if odin will wipe everything if flashing a full firmware?

Tahvok said:
Why a full firmware is needed?
Click to expand...
Click to collapse
Because it is commonly recommended way to unbrick a phone.
Perhaps I can flash only the parts required to get into recovery?
Click to expand...
Click to collapse
Perhaps, yes. But:
1. I don't exactly know what restricts your recovery to run properly. Flashing separate recovery failed.
2. You, for example, could try flashing separately one of the latest bootloaders dedicated to G900F from BL section with odin but I doubt it would help.
I count mount the phone from recovery, that's why it's my priority.
I would like to know also if odin will wipe everything if flashing a full firmware?
Click to expand...
Click to collapse
As far as I know yes but I am not 100% sure because I didn't try that myself on s5.
I would appreciate if somebody else confirms that.

Many40 said:
2. You, for example, could try flashing separately one of the latest bootloaders dedicated to G900F from BL section with odin but I doubt it would help.
Click to expand...
Click to collapse
Can you suggest a bootloader for me? I would like to try that first.

Tahvok said:
Can you suggest a bootloader for me? I would like to try that first.
Click to expand...
Click to collapse
In my opinion, if odin mode works then bootloader should be OK. But as you wish -
tell me first what stock firmware will you later on trying to flash on your friends phone or in which country the phone will be operated.

Many40 said:
In my opinion, if odin mode works then bootloader should be OK. But as you wish -
tell me first what stock firmware will you later on trying to flash on your friends phone or in which country the phone will be operated.
Click to expand...
Click to collapse
Hong Kong

Tahvok said:
Hong Kong
Click to expand...
Click to collapse
Latest available Firmware version for Hong Kong is G900FZHS1CQD1 however I can't find a separate flashable bootloader for you.
Generaly, in my opinion you might try any of the latest bootloaders compatible with SM-G900F phone (here you can find a collection: https://forum.xda-developers.com/showpost.php?p=54094068&postcount=3, I am on G900FXXS1CQI4) but again:
1. I doubt it will help for entering recovery;
2. I still recommend to flash complete stock firmware to unbrick the phone.
However if you anyway decide to try with a bootloader, flash it with odin from BL section (untick auto reboot). Also turn off the phone before and after flashing and pull out battery for about 30 sec. It happens that bootloader doesn't flash properly at once even the odin says "PASS" so some people reported that they needed to repeat flashing a few times. I managed to flash bootloader at first time.

Unfortunateely the phone is not with me anymore, so I won't be able to continue testing. Thank you anyway for trying to help me! I really appreciate your help!