Database Users

[INFO] System OFFICIAL, TriangleAway, Binary count, Root, Recovery [UPDATED 13.10.01]

Triange Away now supports I8190 (SIII mini)
Big thanks to Chainfire for update, and infected_ for doing the beta test so we all can be safe! Give him a thanks!!
Follow this for easy root:
EASY ROOT GUIDE​
To make things clear, as it seems to be alot of confusion about rooting, custom binary count (CBC), & custom recoveries..
Custom binary count can be seen in download mode (vol- / home / power)
It's a counter to keep track of non-Samsung signed binaries flashed with Odin.
If you need to take your device to Samsung for warranty and they notice it's not at zero, you're not under warranty anymore.
Only known way to gain root without increased CBC is to flash one of the pre-rooted firmwares that you can find here.
To be safe, make sure it says something like "This does NOT trigger the flash counter." in the thread for that firmware you are about to flash to gain your highly desired root.:cyclops:
When you got root, finally download rom manager from playstore and you can get cwm recovery with ease.
From there you can flash whatever *.zip's you want without worrying about CBC.
If you do it the other way around, start with custom recovery to be able to flash a "root.zip" you will increase CBC!!
This applies if you try to flash any custom recovery.
In other words..Everything not signed by samsung will get your CBC INCREASED WHEN FLASHED THROUGH ODIN!!
System Status back to OFFICIAL
To restore system status to official you'll need to take a few more steps.
First use triangle away to reset your counter, then tick "allow tracker to run" and "system modified workaround" in triangle away settings.
Reboot device. Supersu will be bisabled for a few minutes when tracker runs and your status will become official.
Now you can uninstall triangle away. On next reboot your systemstatus will still be official, but of course it won't work with a custom kernel or custom rom.
If everything went well you should now have your binary count at 0, and a system status that says official.
Back to Stock Recovery
Most firmwares now have recovery included in the *.tar.md5-package, which was not the case in earlier firmwares for i8190.
You can take a look inside the package to ensure it's there. If it is, you shouldn'd have to mess with restoring recovery.
Open the firmware.rar.md5 with winrar. (Not unpack, just open)
Use this "i8190_stock_recovery.tar.md5". <<---This one doesn't increase custom binary count. (Flash in Odin as PDA)
Edit: This seem to not work as it used to. I'm now adding PDA-specific recovery.tar's to this thread, with continiued updates.
Thanks to Benz0nator, here is also a CWM flashable stock recovery.(Flash with your CWM / TWRP recovery)
So...is warranty back now? NO, not really. You're still rooted so you can't just send it to service in this condition.
For unroot and get warranty back you'll have to read [GUIDE] Unroot, Flash official stock firmware on Galaxy SIII Mini GT-I8190
Whats important to know here is that stock recovery is not always a part of the official firmware package so you might need to flash stock recovery before you unroot and flash firmware.
Also, If you're on 4.1.2 firmware and flash a 4.1.1 firmware you will get problems if no wipe/factory reset is done prior to flashing, as most roms are non-wipe.
Thank you.

tys0n said:
Bah, misspelled topic!haha
To make things clear, as it seems to be alot of confusion about rooting, custom binary count (CBC), & custom recoveries..
Only known way to gain root without increased CBC atm is to flash one of the pre-rooted firmwares that you can find here.
To be safe, make sure it sais something like "This does NOT trigger the flash counter." in the thread for that firmware you are about to flash to gain your highly desired root.:cyclops:
When you got root, finally download rom manager from playstore and you can get cwm recovery with ease. From there you can flash whatever .zips you want without worrying about CBC.
If you do it the other way around, start with custom recovery to be able to flash a root.zip you will increase CBC!!
That also applies if you try to flash custom recoveries, original recoveries repacked to .tar-files.
In other words..Everything not signed by samsung will get your CBC INCREASED WHEN FLASHED THROUGH ODIN!!
Custom binary count can be seen in download mode (vol- / home / power)
It's a counter to keep track of non-Samsung signed binaries flashed with Odin.
If you need to take your device to Samsung for warranty and they notice it's not at zero, you're not under warranty anymore.
Atm there is no known way to restore CBC to zero for I8190 (SIII mini)
Also, If you're on 4.1.2 firmware and flash a 4.1.1 firmware you will get problems if no wipe/factory reset is done prior to flashing, as most roms here are non-wipe.
If you find another method for any of this, please let me know and I will update this post.
Thank you.
Click to expand...
Click to collapse
Thanks for the thread man! I was getting quite confused about this binary counter thing

Re: Impirtant Info - root,recovery,binary count.
Ohhh that was very good thanks and as for me I don't even have warranty so no problem with CBC (if ut does'nt have another disadvantage. .)
sent from the super siii mini GT-I8190 using xda premium app.

Updated with CWM flashable stock recovery. (thx to Benz0nator)

Updated: Triangle away support for i8190 (s3 mini)!!

Thanks Man....
So what are the Steps ?
Only Downloading & Use "Triangle Away" App ?

cheech01 said:
Thanks Man....
So what are the Steps ?
Only Downloading & Use "Triangle Away" App ?
Click to expand...
Click to collapse
Yes

Oh yeah!
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
That's because of my ROM.

Re: [UPDATE] Triangle Away - root,recovery,binary count.
Same here, development is getting better and better let's hope that we will get CM support.
Sent from my GT-I8190 using xda premium

bycluir boxed
Good news! thanks to all (developers and testers!) :good:

Benzonat0r said:
Oh yeah!
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
That's because of my ROM.
Click to expand...
Click to collapse
fix system status : http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346 download and odin flash

Re: [UPDATE] Triangle Away - root,recovery,binary count.
Couldn't we just Factory Reset through CWM?
Sent from my S3 Mini whilst rollin a fat one

furuko1231 said:
fix system status : http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346 download and odin flash
Click to expand...
Click to collapse
CaseyS said:
Couldn't we just Factory Reset through CWM?
Sent from my S3 Mini whilst rollin a fat one
Click to expand...
Click to collapse
Yes. These two steps are basicly the same.
It will clear /cache & /data

Re: [UPDATE] Triangle Away - root,recovery,binary count.
Alright...I can know edit my guide. with that my tutorial will be empty of faults and disadvantages maybe tomorrow I will do it
hit thanks if I helped you
sent from the wonderfull s3 mini GT-I8190 using xda app

Question
Hi!
I am a little bit confused. I flashed a pre-rooted I8190XXALJL firmware.
When I go to download mode,
on the bottom of FIRST screen is a yellow triangle with an exclamation mark.
When I press Volume Up, on the SECOND SCREEN is following text:
ODIN MODE
PRODUCT NAME: GT-I8190
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Please explain somebody, why the yellow triangle? What is the CBC count then? I'm now in official or in custom mode?
Need I run the Chainfire's Triangle Away tool or not?

ladislav.heller said:
Hi!
I am a little bit confused. I flashed a pre-rooted I8190XXALJL firmware.
When I go to download mode,
on the bottom of FIRST screen is a yellow triangle with an exclamation mark.
When I press Volume Up, on the SECOND SCREEN is following text:
ODIN MODE
PRODUCT NAME: GT-I8190
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Please explain somebody, why the yellow triangle? What is the CBC count then? I'm now in official or in custom mode?
Need I run the Chainfire's Triangle Away tool or not?
Click to expand...
Click to collapse
The yellow triangle have always been there. It's just a warning that a custom os can harm the function of the device.
official / custom can be fixed. Please read the Triangle away post by Chainfire on how to use it.

Added Stock recovery.tar.md5 to use with Odin.

furuko1231 said:
fix system status : http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346 download and odin flash
Click to expand...
Click to collapse
you mean this will enabled the official status and kies will be working? in odin flash as pda? phone?

Sv: [UPDATE] Triangle Away - root,recovery,binary count.
nazri5363 said:
you mean this will enabled the official status and kies will be working? in odin flash as pda? phone?
Click to expand...
Click to collapse
No, it will make a factory reset. Wipe all user data.
For status to official use triangle away
Sent through time and space from my s3mini.

Triangle Away worked like charm on my Galaxy S3 mini. My phone couldn't get past the samsung logo and couldn't get into stock recovery no matter what, so after hours of trying and flashing stock roms, I flashed CWM via odin and I my phone was working again. Afterwards I have purchased Triangle Away and my phone is like new again Thanks Chanfire :good:

[Q] have i lost root forever ? help !

all.
I have an i9505 on 3 UK that has been rooted for over 6 months. I've been running the excellent TW based Echo Rom but wanted to try an ASOP rom but quickly wanted to revert.
I tried to restore my Nandroid but this failed and screwed up the phone (dont ask)so back to ODIN and i flashed back to stock 4.4.2 firmware for the UK via Sammobile (NG8)
Now back to square 1 so attempted to reroot with CF Autoroot again via ODIN. all show pass and i get the black screen on the phone with the red android logo and line stating stock recovery restored. I then used ODIN to flash Philz recovery again shown as Pass, however when i try to get into recovery i get some small white text on the bkack background that is there too briefly to read before the phone reboots as normal.
The Su superuser app is there but states the Su binary is outdated and the phone has no root access.
Ive read a few methods to get round this but they all seem to follow the same process ive tried a few times now.
The Rom for Echoe is auto root so id have thought if i could get to recovery somehow i could just flash this ?
Any one any views or have i screwed up for good ? .

You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.

Lennyz1988 said:
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Click to expand...
Click to collapse
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?

robinta said:
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
Click to expand...
Click to collapse
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?

Lennyz1988 said:
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Click to expand...
Click to collapse
GTI9505...(Bootloader i9505xxegng8)
Originally I tried philz_touch_5.15.8-i9505.tar.md5
and then updated to philz_touch_6.23.9-i9505.tar.md5 with no avail.

Try redownloading it. If you say that if passes, then it should just work.
If it still fails then try TWRP. Uncheck auto-reboot before flashing.

Could it be connected to me flashing a generic unlocked UK firmware on a 3 UK handset ?

That's sorted it ! Flashed CWM recovery and am now running Echoes v28.
Thanks for the help. I was really panicking for a while.
I wont be changing roms for a while but I guess if I did I won't lose root ?

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.

SM-G900S bootloop after trying to root

Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet

Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.

toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet

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!