Database Users

[Q] Note 4 Bootloop!!! PLEASE HELPP!!!

2 days ago i rooted my note4 sm-n910f (with this: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428)and it was working fine, but today it when installed swiftkey it just switched off. It then turned on again and got stuck in a bootloop.
I tried to root it again and it didn't do anything. When i go in recovery mode it says at the bottom: dm-verity verification failed...
What the hell should i do!!!

Did you try to power it down completely (pull battery for about a minute to be safe), reboot into download mode and run CF auto root again? I got stuck in a bootloop early on and this fixed it for me. If it doesn't work, try the same steps, but try pushing TWRP (just released a few days ago for this phone) so you can boot into recovery and do a factory wipe and see if that helps. I'm basically a noob here, but these seem to be logically steps to start with...
Good luck!

wineguy said:
Did you try to power it down completely (pull battery for about a minute to be safe), reboot into download mode and run CF auto root again? I got stuck in a bootloop early on and this fixed it for me. If it doesn't work, try the same steps, but try pushing TWRP (just released a few days ago for this phone) so you can boot into recovery and do a factory wipe and see if that helps. I'm basically a noob here, but these seem to be logically steps to start with...
Good luck!
Click to expand...
Click to collapse
i tried that and then during the auto root is said: recovery is not seandroid enforcing at the top soooooooo what now?

Playing with his phone, now it doesn't work anymore and other people may come with a solution!
When you modify something on your phone, know first what you're doing and what todo when something goes wrong!

pfffffffffffffffffffffffffffffff my phone is working again, i downloaded the stock rom and flashed it using odin.
I rooted phone again and everything is working fine, this time i will backup everyything!! because i didn't have anything backed up :good:

fcbmootje said:
pfffffffffffffffffffffffffffffff my phone is working again, i downloaded the stock rom and flashed it using odin.
I rooted phone again and everything is working fine, this time i will backup everyything!! because i didn't have anything backed up :good:
Click to expand...
Click to collapse
I had a similar problem today when trying to boot into recovery. Thank god I had Odin running at my work to install a recovery rom.

Help
I have tghe 910f version and I used odin and its stuck in bootloop.
kevmille said:
I had a similar problem today when trying to boot into recovery. Thank god I had Odin running at my work to install a recovery rom.
Click to expand...
Click to collapse

Sprint Galaxy Note 4 bootloops before turning on
Hi so I have my Sprint Galaxy Note 4 with CM12.1 installed and all is fine and dandy when all of a sudden out of nowhere it shuts down and bootloops. I tried restoring my backup of stock TW that I had on TWRP and even then that got stuck in a bootloop. So I decided to unroot it and it still bootlooped then I did a factory reset and even then it's still stuck in a bootloop. It's like no matter what I do my phone is stuck in a bootloop. PLEASE HELP!!

same problem
i just rooted my note 4 for the firts time and is just boop loop i tried factory reset cache wipe and CF again and nothing can anyone help?n i running android 5.1.1 i think this was the problem

yulmerced said:
i just rooted my note 4 for the firts time and is just boop loop i tried factory reset cache wipe and CF again and nothing can anyone help?n i running android 5.1.1 i think this was the problem
Click to expand...
Click to collapse
hi,
Firstly, CF auto root does not work on Note 4 Android v5.1.1 you have to flash a permissive kernel for your device.(if there is one for your device /phone. I have a N910F device and had to flash the kernel via TWRP, then i was able to root.I have got no idea what model /device you got etc. so can't help.
To get out of bootloop try flashing your Android v 5.1.1 Rom again
good luck

willcor said:
hi,
Firstly, CF auto root does not work on Note 4 Android v5.1.1 you have to flash a permissive kernel for your device.(if there is one for your device /phone. I have a N910F device and had to flash the kernel via TWRP, then i was able to root.I have got no idea what model /device you got etc. so can't help.
To get out of bootloop try flashing your Android v 5.1.1 Rom again
good luck
Click to expand...
Click to collapse
its a sprint note 4 sm-910p

yulmerced said:
i just rooted my note 4 for the firts time and is just boop loop i tried factory reset cache wipe and CF again and nothing can anyone help?n i running android 5.1.1 i think this was the problem
Click to expand...
Click to collapse
I don't know if u fixed it yet, but I did and I had the same think u have.
I used Odin to flash TWRP. (Look up ur model, I had twrp dot me/devices/samsunggalaxynote4qualcomm.html (I can't post links yet))
After that I used TWRP to install CF Auto Root (look up ur model once again). I had CF Auto Root already on my phone storage from some previous attempt so if u dont have that u might need to get it on your phone somehow. I don't know how to get all that working since I'm a root newb so.
Hope this got u starting at least!
(First post!)

willcor said:
hi,
Firstly, CF auto root does not work on Note 4 Android v5.1.1 you have to flash a permissive kernel for your device.(if there is one for your device /phone. I have a N910F device and had to flash the kernel via TWRP, then i was able to root.I have got no idea what model /device you got etc. so can't help.
To get out of bootloop try flashing your Android v 5.1.1 Rom again
good luck
Click to expand...
Click to collapse
Can you please provide a link to this kernel ? I have also 910F,thanks in advance.:good:

ludoke said:
Can you please provide a link to this kernel ? I have also 910F,thanks in advance.:good:
Click to expand...
Click to collapse
hi ,
if you read my post in linked thread post #8 ( below ) i have all links to correct TWRP recovery version to use ,to permisive kernel I have all relevant info in this post how to flash etc
,plse read( link to my post .........)
http://forum.xda-developers.com/not...exed-stock-t3194008/post62691219#post62691219
good luck

Hello,
I am having a bootloop after i rooted my device using custom kernel but forgot to turn off auto update.
Does anyone know where to download Stock Lollipop 5.1.1 for 950C ?
Yes sammobile does have it but the download speed is ridiculous.

emu558 said:
Hi so I have my Sprint Galaxy Note 4 with CM12.1 installed and all is fine and dandy when all of a sudden out of nowhere it shuts down and bootloops. I tried restoring my backup of stock TW that I had on TWRP and even then that got stuck in a bootloop. So I decided to unroot it and it still bootlooped then I did a factory reset and even then it's still stuck in a bootloop. It's like no matter what I do my phone is stuck in a bootloop. PLEASE HELP!!
Click to expand...
Click to collapse
did you ever fix this problem i am currently dealing with the same thing

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.

Root fail

Hi all. New Edge + today and in trouble.
Installed Philz recovery via Odin, tried to flash Arter kernel - installation failed - and SU, bootloop. Can get to recovery, restore stock backup - bootloop. Download - fail on installing Arter kernel. Reboot - stuck on splashscreen.
I'm stuck. Flashed 100s of Samsung stuff before but this one is a doozy. (coming from note 3).
Reflashed recovery, tried TWRP, can't retry downloading kernel because I can't get a startup and hence cannot get a new kernel on device. Wiped cache etc, nothing.
Not in full panic mode (me, not dead phone) yet but nearing it. Thanks for any help. 928f, Scandinavian firmware.

sounds like you left knox enabled and OEM unlocked off.
Not sure if it helps but flashing the stock firmware "might" help? samfirmware - search for your model and give that a go.

Hi seven. No. Did my homework, know the no-nos. Been dling stock for 1 hour, 58 minutes to go.
Baffled as to why my stock backup won't play nicely.

Update - I only have download or recovery, can't reboot to normal. Can't flash anything, backup still doesn't work.
Bugger. And indeed ****. Hope stock works.

hey man, thats a pity then
hope it works!

B3311 said:
Update - I only have download or recovery, can't reboot to normal. Can't flash anything, backup still doesn't work.
Bugger. And indeed ****. Hope stock works.
Click to expand...
Click to collapse
There are only two things which can cause issues that you are having.
#1. You did not Odin flash the correct firmware for your phone's specific model.
#2. You did not flash the correct arter97 kernel for your phone's specific model.
Good luck,
Have a very Merry Christmas.
Sent from my SM-G928T using Tapatalk

Flashed stock from samfirmware (same FW as my preinstalled stock), TWRP instead of Philz, Audax ROM then Arter kernel - all fine now. Baffled but relieved. Rooted, happy and love this phone.

Misterjunky said:
There are only two things which can cause issues that you are having.
#1. You did not Odin flash the correct firmware for your phone's specific model.
#2. You did not flash the correct arter97 kernel for your phone's specific model.
Good luck,
Have a very Merry Christmas.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
#1. I didn't flash any firmware. As I clearly said, I couldn't and didn't before reinstalling stock. And since the stock is the one that came with my phone, how do you conclude that it's the wrong FW?
#2. I did.
I'm not a noob. Been flashing Sammy devices since the S1. Don't tell me what I did or didn't do. Your name seems apt. Lay off the drugs if your reading and comprehension skills are so woeful.

i feel your pain
B3311 said:
Hi all. New Edge + today and in trouble.
Installed Philz recovery via Odin, tried to flash Arter kernel - installation failed - and SU, bootloop. Can get to recovery, restore stock backup - bootloop. Download - fail on installing Arter kernel. Reboot - stuck on splashscreen.
I'm stuck. Flashed 100s of Samsung stuff before but this one is a doozy. (coming from note 3).
Reflashed recovery, tried TWRP, can't retry downloading kernel because I can't get a startup and hence cannot get a new kernel on device. Wiped cache etc, nothing.
Not in full panic mode (me, not dead phone) yet but nearing it. Thanks for any help. 928f, Scandinavian firmware.
Click to expand...
Click to collapse
I flashed a rom to my sm-g928p and am stuck in the splash bootup too, i'm able to flash as much as i want but nothing ever gets through. when i go back to stock it gives me an E: failed to mount /efs (invalid argument) along with dm-verity verification failed.....i dont know what to do...!!!!!

@frankmcquade - I'd start a new thread for your problem, it's different to mine and you'll probably get more help.
I never had the efs message and my bootloops were with flashing recovery, not a ROM. Good luck!

Stuck in a never-ending bootloop after trying TWRP for SM N9005

My phone is a Samsung Note 3 SM-9005, currently it's stuck in an infinite bootloop even after removing the battery for an hour.
I get this message:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... along with the Samsung SM-N9005 logo, a couple of beeps/buzzes and then it repeats ad infinitum.
Here's what I did over the last day to get to this sorry state of affairs:
1. Upgraded from Android 4.3 (the original operating system) to 5.0 using the Samsung N9005XXUGBOA5 ROM with Odin 3.12. This worked fine but the phone lost root.
2. I rooted the phone again using Odin and Chainfire Auto-Root. All good so far.
3. I installed TWRP (the official TWRP App 1.5, going by my records)
4. I flashed the latest custom recovery which would have been 3.0.x and this seemed to be fine. So far no problems.
5. I then got ideas above my lowly station, apparently. I wanted to flash one of the newer ROMs: [Rom][N7 Port][12.12.2016] [Multi-DPI] Phronesis Rom N7 v4.1 Feature Rich & Smooth
https://forum.xda-developers.com/ga...m-phronesis-mm-rom-v1-0-feature-rich-t3463244
6. In the instructions, it said to use TWRP recovery version 2.8.7. I found that and flashed it. (Yes, it was for the Samsung SM N9005).
7. I rebooted into recovery mode to make a backup with that 2.8.7 version.
8. Now I'm stuck in boot loop hell with ...
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... with the Samsung SM-N9005 logo, a couple of beeps/buzzes and so on (as stated above).
I've tried leaving the battery out for an extended period and this hasn't worked. The phone never gets to the stage where I can talk to it with Odin or get any kind of menu. Is the phone truly bricked now?
If so, was it a critical error to go from the 3.0.x TWRP recovery back to 2.8.7 for the purposes of this custom ROM upgrade?
If not, what can be done to regain control of the phone?
This is obviously an older phone as I've had it for about 3 years now, but I'd love to get it working again if possible. I really loved it and was planning to use it for a couple more years (hence the upgrade path I've explained above).

Can you boot into download mode? I suspect you flash the 4.3 version of twrp, you need a 4.4 version. This one https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Boot into download mode and flash it with odin.

I suggest flashing the latest stock ROM, flash the latest tar version of twrp with Odin, root with supersu.zip in twrp.

Stonedead, you were right on the money. I did what you suggested (Download mode) and that different TWRP file, and it worked.
Thanks so much.
Thanks audit13 also, although I didn't need to go that far to undo my mistake.

I got the same problem with my note 3. Thank you for the solution. Now how do I exactly get TWRP working on my phone. It is already rooted.

See TWRP thread.
Basics flash twrp tar through odin

Root is not needed to install the tar version of TWRP with Odin.

Thanks. Managed to get twrp working now. Also installed the note 8 Rom

Hi ok im having the same problem kinda follow the installation as posted,so i have note 3 sm-n9005 stock rom,root and replaced twrp 4.3 for 4.4 to install phronesis n7 v7 for note 3 followed all instructed then rebooted went to samsung boot then booted to twrp recovery ive been on it all day thinking what da hell ive done wrong?can someone instruct me of what i did or didnt do or have i completely mess stuff up?cheers anyone.

instructions .
Boot into recovery (say TWRP 2.8.7.0)

JJEgan said:
instructions .
Boot into recovery (say TWRP 2.8.7.0)
Click to expand...
Click to collapse
Sorry jjegan not following?it already reboots into twrp recovery after the galaxy note 3 logo appears for 20 seconds?I have read and followed threads that have same or similar problems but no avail im am totally lost and from reading this rom it sounds great if I can get there that is,so please simple instructions would be very helpful as I'm still learning very sorry for being dumb.

This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com

JJEgan said:
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
Click to expand...
Click to collapse
Hi JJEgan,thank you for the reply back much appreciated for your time so far,so do you mean twrp-2.8.7.0-hlte-eu.tar file?and not twrp 2.8.7.0-hlte-4.4 img.tar file?that's the one I am using to flash the rom with and having problems with.

Hi there again ok im so confused not sure which one,there are so many of the 2.8.7.0 versions with 4.3 or 4.4-img.tar im not sure if im downloading 4.4 or 4.3 as im still a noob and love tech,I have read threads upon this rom problems still can't get the grasp of the simple twrp version I have lte au version android 5,and when I read 2.8.7.0 im think is it 4.4 4.3 or just 2.8.7.0 tar file?I'm following the installation up into the problem of not booting up in stays In galaxy note 3 boot and I have removed the battery 5mi z replaced then recovery and factory reset then it does the same again and I have tried 3 times waited longer each time im thinking maybe go back to stock I don't think my phone is agreeing with me,jjEgan thanks for the info amd time im sorry if annoy you with a simple installation to you,still I have read and grasp the concept of twrp installer version yeah??

Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .

JJEgan said:
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
Click to expand...
Click to collapse
Thanks for the reply JJEgan,no I have finally fix the problem solution start over fresh instalments installed stock,flash twrp 4.4, flashd supersu threw twrp,wiped 3x install,instead of rebooting threw Aroma rebooted system threw twrp it loaded first go,thanks for the threads I took bits n pieces frm each threaded problems,cheers JJEgan love the version rom,one more thing what kernel would be better or what would your choice be cheers

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!