Database Users

[Q] need help with custom recovery

Hey guys I'm new to android had an iPhone for 6 years. Just got the gs4 two months ago. I rooted the phone took out bloat ware apps using titanium back up. Have a few other rooted apps. Got Interested in ROMs and kernels so did some research looked around on here to how to do it. I downloaded infamouses newest ROM. I have ROM manager and I downloaded cwm recovery through the Rom manager. When I go to back up my current ROM and everything it boots into recovery mode but it isn't cwm recovery. The emblem doesn't come up and I believe its the stock recovery. My question is how can I get the cwm recovery so I can back up my current ROM and then wipe it and install the new one. I'm new so sorry if this is easy or anything I appreciate all the help

Download goo manager and let it install twrp then just flash cwm thru twrp . Or keep twrp and remember to flash loki doki if needed.

Wait!
What firmware is your phone currently on? MDL OR MF3?
If MF3, stop now. Do not flash anything.
Sent from my SGH-I337 using xda premium

Okay I figured out the problems. When I hit reboot and superuser is supposed to grant root permissions an error comes up saying superuser has stopped working then goes into the stock recovery mode. The only thing I found with MDL in it was the baseband version 1337UCUAMDL

Your safe to continue flashing custom recovery on MDL Baseband
Sent from my SGH-I337 using xda app-developers app

Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.

Division4thor said:
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Click to expand...
Click to collapse
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.

scott14719 said:
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
Click to expand...
Click to collapse
Yeah Idk I'm so over this getting so frustrated. I'm new to this I read that post. Not all 51 pages hope you didn't mean that..

This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you

TheAxman said:
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
Hey thanks for the help. I got twsp recovery through goo manager and worked perfectly. I'm having such a bad experience trying to install this rom. I went into the recovery mode after backing up my current rom and system. I wiped everything out then went into my sd card amd installed the zip that is listed in the infamous page in the developers part. I hit install and then said I'm not rooted and would I like to install superuser. I slide the thing and then went to reboot and now has been stuck saying samsung and custom with an open love under it. Pulled the batter went back into twsp and tried to reboot and still stuck. This is all after I thought I installed the rom already and nothing changed except wiped my phone. Can anyone help
Click to expand...
Click to collapse

Are you installing loki doki after the rom ?

[Q&A] [RECOVERY LOCKED/NCG] Safestrap Recovery v3.75 [2014-06-26 B03]

Q&A for [RECOVERY LOCKED/NCG] Safestrap Recovery v3.75 [2014-06-26 B03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Safestrap does not work
Hi, this is my first time ask for help. I have verizon samsung galaxy s4 and currently with hyperdrive 18.1 and safestrap 3.75. For some reason, I found my safesrtrap does not work. I touch the screen, nothing happened. I lock screen and swip to unlock, nothing happened. Feel like touch screen does not work. Could anybody help me? Thanks

doubletong said:
Hi, this is my first time ask for help. I have verizon samsung galaxy s4 and currently with hyperdrive 18.1 and safestrap 3.75. For some reason, I found my safesrtrap does not work. I touch the screen, nothing happened. I lock screen and swip to unlock, nothing happened. Feel like touch screen does not work. Could anybody help me? Thanks
Click to expand...
Click to collapse
are you using the safestrap from the s4 or from the s5 thread? if so, try using the s4 ss apk
Sent from my SM-G900V using XDA Free mobile app

Splash screen shows after apk removal of SS 3.75
I have read numerous threads and can not find a clearly define method for removing all traces of safe strap 3.75 if there is one kindly point me to it.
device VZW Note 3, running Kit kat, rooted via geohot towelroot method, Su pro version 1.99
1. I have removed SS by uninstalling recovery then uninstalling the app.
2. On initial start up no safe strap screen.
3. On reboots "custom "pad lock shows as if Safe Strap is still installed.
4.After Safe Strap apk removal SU binaries wont update either even after the 5 reboots attempts
I have seen the manual remove method for SafeStrap versions 3.62 and lower:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Can I do this manually for the 3.75 version of safe strap? I just want to remove all traces of safe strap (all splash screens ) and update SU binaries post its removal.
Thanks!

Backups being removed
I installed SafeStrap 3.75 on my s5 and it runs, and says it backs up properly to the sd card, but when I reboot back into Android, the backup file is no where to be found. The TWRP folder on the sdcard is empty. Does anyone know why the file would that it exists inside safestrap, but disappear after reboot?
I've got NCG installed, I've rooted, installed SuperSU, Installed the latest busybox and I've installed and run sdfix to fix the permissions on the SD Card, yet every backup I make is removed from the sd card.
It DOES backup successfully to the internal device storage, thoughts?

did not find delete option for posts...

ahbeeneverywhereman said:
did not find delete option for posts...
Click to expand...
Click to collapse
You can not remove your own posts. It has to be deleted by someone with the authority to do so.

Verizon Galaxy S5 Safestrap and NI2 ROMS
Hello everyone,
First time poster, long time lurker.
I usually just lurk until I find the answers to my questions. I figured I can become an active member of the community now.
I have a rooted Galaxy S5 running on the NCG build. I want to install a custom ROM using Safestrap 3.75. Then I want to install Optimal ROM which is running on NI2. For which I believe I will have to install the NI2 firmware tar.
What exactly is the NI2 firmware tar (is this the kernal)? And if I install it, will it remove root (I'm logically assuming no but I need some confidence on the quesion)?
Much appreciated!

safestrap help!
i have a verizon galaxy s5, model number sm-g900v, android version 4.4.4, baseband version ending in ank2, kernel version 3.4.0, build number ending in ank2. i have flashed back to baseband NCG via odin v3.09, rooted via towelroot, verified root via root check lite, flashed back to baseband version ending in ANK2 via odin v3.09, verified root via root check lite, installed superSU by chainfire, installed busybox by jrummy apps inc, installed titanium backup and performed backup.... so my question is, will the current safestrap for verizon gs5 work with my phone? the thing that kinda worries me is the link >> Safestrap-KLTEVZW-NCG-3.75-B03.apk<< shows "NCG". does this mean NCG and up or NCG only? if it means NCG only, where is the ANK2 safestrap? what are my options for a recovery?

LLG BAD HABIT CC said:
i have a verizon galaxy s5, model number sm-g900v, android version 4.4.4, baseband version ending in ank2, kernel version 3.4.0, build number ending in ank2. i have flashed back to baseband NCG via odin v3.09, rooted via towelroot, verified root via root check lite, flashed back to baseband version ending in ANK2 via odin v3.09, verified root via root check lite, installed superSU by chainfire, installed busybox by jrummy apps inc, installed titanium backup and performed backup.... so my question is, will the current safestrap for verizon gs5 work with my phone? the thing that kinda worries me is the link >> Safestrap-KLTEVZW-NCG-3.75-B03.apk<< shows "NCG". does this mean NCG and up or NCG only? if it means NCG only, where is the ANK2 safestrap? what are my options for a recovery?
Click to expand...
Click to collapse
No worries SafeStrap works fine with all the kernels so far. Just use the updated one here.

thanks!
Misterxtc said:
No worries SafeStrap works fine with all the kernels so far. Just use the updated one here.
Click to expand...
Click to collapse
thats what i assumed but didnt want to try until i got a confidence boost (its my only phone at the moment). i tried downloading your beta but got a 404 not found error. again, i assume thats because its out of beta with known issues having been fixed as its kind of an old post. the one i downloaded (from the same thread) seems to be working just fine (have yet to flash a rom... that will come tomorrow). thanks for the quick response; thats part of what makes great communities. BTW i hit that thanks button.

LLG BAD HABIT CC said:
thats what i assumed but didnt want to try until i got a confidence boost (its my only phone at the moment). i tried downloading your beta but got a 404 not found error. again, i assume thats because its out of beta with known issues having been fixed as its kind of an old post. the one i downloaded (from the same thread) seems to be working just fine (have yet to flash a rom... that will come tomorrow). thanks for the quick response; thats part of what makes great communities. BTW i hit that thanks button.[/QUOT
Did you try SS on ANK2? did it work? I just got the phone back from Samsung, don't wanna mess it up Thanks!
Click to expand...
Click to collapse

dj_ox said:
LLG BAD HABIT CC said:
thats what i assumed but didnt want to try until i got a confidence boost (its my only phone at the moment). i tried downloading your beta but got a 404 not found error. again, i assume thats because its out of beta with known issues having been fixed as its kind of an old post. the one i downloaded (from the same thread) seems to be working just fine (have yet to flash a rom... that will come tomorrow). thanks for the quick response; thats part of what makes great communities. BTW i hit that thanks button.[/QUOT
Did you try SS on ANK2? did it work? I just got the phone back from Samsung, don't wanna mess it up Thanks!
Click to expand...
Click to collapse
Yes sir. Worked fine. NK2 baseband, android version 4.4.4
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse

outpost785
Sorry if this has been asked already ,safestrap for s5 on rooted stock 5.0 .Safestrap says its installed but will not work.Thanks inadvance.

outpost785 said:
Sorry if this has been asked already ,safestrap for s5 on rooted stock 5.0 .Safestrap says its installed but will not work.Thanks inadvance.
Click to expand...
Click to collapse
I had to run the SS and SuperSu step again.

Rapunzl said:
I had to run the SS and SuperSu step again.
Click to expand...
Click to collapse
Are you saying that you are able to access the safestrap recovery while running the 5.0 kernel? All reports state that ss will no longer work on the 5.0 kernel.

That's what I have found myself that ss is a no go on 5.0 hopefully someone finds a work around, I can't boot into stock recovery

outpost785 said:
That's what I have found myself that ss is a no go on 5.0 hopefully someone finds a work around, I can't boot into stock recovery
Click to expand...
Click to collapse
The ss recovery will work on a 5.0 build by downgrading the kernel back to nk2.

But can/can't run 5.0 on nk2 kernel?

outpost785 said:
But can/can't run 5.0 on nk2 kernel?
Click to expand...
Click to collapse
5.0 will not boot on the NK2 kernel.

[Q] Custom recovery install bricks or overwrites

I can't get a custom recovery install to work. I've been at it for hours and I need to go to bed. For some reason, I can't install a custom recovery on my USA AT&T i337. I'm going to list what I've tried, it will be easier:
Installing TWRP through TWRP manager (TWRP manager crashes while flashing, soft brick)
Installing TWRP through Flashify (says it worked, then soft brick on reboot)
Installing CWM Touch through ROM Manager (says it worked, even shows version of currently installed recovery, soft brick on reboot)
Install/root with CASUAL (says it worked, soft brick on reboot)
I've never had this much trouble getting a custom ROM onto a new phone. Any idea what's going on? Seems like everything I read applies to everyone but me.

http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.

jmjoyas said:
http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
EDIT: found the list, ignore dumb obvious question.

v1nsai said:
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
Click to expand...
Click to collapse
Yes, you're limited to the roms you can flash. See this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app

Installing Custom Roms On Newly Rooted Phones With BOK3,BOG5 and BOE1 Bootloader

Instruction for installing a custom rom using safestrap
1. Choose a Lollipop Rom from the Verizon Galaxy S 5 Android Development. OnlyLollipop 5.0 TW based roms will work
2. If you already got safestrap working skip to step 10. Otherwise install the apk's in this zip View attachment Safestrap_Apps.zip
3. Once all are installed Click On Busybox Grant Super User Access and click on install
4. Now open Lollipop Safestrap and click on Install SafeStrap Grant Super User Access
5. Click On Install Recovery Once Installed It will Say State: Installed
6. Click the Back Button to take you to Lollipop Safestrap Recovery Main Screen
7. Click On Recovery Reboot. Grant Super User Access.
8. On the next screen click FLASH then when dialog comes up asking CLICK HERE TO REBOOT TO SAFESTRAP click on that and your phone will reboot to safestrap. May take a few seconds for the Recovery Screen to come up
9 In Safestrap Under Boot Options LEAVE THIS ALONE Install everything to STOCK ROM SLOT
10. Now If you have not I would make a backup of your current Rom so if something happens you can get back to where you are at now.
11.. Click on Wipe You will see 3 options Advance Wipe, Format Data And Swipe To Factory Reset. If you dont see these and you see a dialog asking something about entering Yes just hit the back button
12 To Install a new rom click on Advance Wipe And Check Dalvick Cache,Data,Cache,System Then click Swipe To wipe.
13. Now Click The Home Button
14 Now Choose Install. Underneath the header on the next screen You will see a black box it will either say Storage: Micro SDcard or Storage: Internal Storage. You can switch between the 2 by clicking that black box
15 Locate the zip you want to install and click on it
16. In next screen Click Swipe To Confirm Flash and your install will begin
17. When Finished Do Not Click Reboot Now Or Reboot System. Click The Home Button. All Older Roms should run fine on latest BOK3 Firmware so if your on BOK3 firmware simply flash BOK3 kernel.
18. Once That is installed you can reboot to system
19. If you get some kind of warning about unauthorized software all you need to do is delete SecurityLogAgent folder from the system/app
20 Now If you want to select a different Firmware Zip you only need to do this once. It will remain that Firmware untill another Firmware Zip is flashed. If you flash A Firmware Zip There is no need to flash a Kernel Zip during the same installation.
21. Most Deodexed Lollipop Roms will Take Up to 10 Min to boot. If it seems longer than that simple pull the battery and restart phone.
22. If something goes wrong! If the rom fails to boot or bootloops you are not screwed if you flashed with safestrap.
23. To get back to safestrap from a bootloop. Pull the battery. Boot to download mode Power+Volume Down+Home
24. Plug into your computer.
24. Open Odin make sure phone is connect blue box saying comport whatever will be lit up. In the AP section locate the NI2_stock_kernel.tar.md5 and flash kernel.
25. When phone reboots watch screen and click on the Recovery Button when the SafeStrap Screen comes up. If you miss it pull the battery and try again.
26. Once in Safestrap you can restore a back up or what ever you need to do
Just a note. You can also use flashfire to flash rom. Flashfire is a great tool. Just know that if you flash a rom with flashfire and have safestrap installed you will loose your safestrap installation. So after you flash a rom with flashfire if you want to use safestrap you will have to reinstall it. If something goes wrong during the the install when flashing with flash fire you will not be able to get back to safestrap and your only method if your bootlooped is using odin and flashing full factory tar image and going through the root process again!

Install Kit Kat Roms On All Bootloaders
Edit: I updated the method and added new firmware zips ran into some hardware issues these fixed the problem
This method should work for All Bootloaders Without having to wipe data on Internal storage
Download This one NK2_Firmware_No_Bootloaders_V3.zip should work for all Kit Kat Roms. This is a 4.4.4 Version I tested it on 4.42 Version and it worked fine . If you want to use a differen versions, all Version listed below
Reboot To Safestrap Wipe cache, system, data, dalvik cache then flash above zip
Go back and Wipe cache, system, data
Install Kit Kat Rom
Reboot to system and go through setup.
Remember when using Kit Kat Roms there is no reason to flash kernel in safestrap as you are all ready running kit kat kernel. Also do not use Lollipop Safestrap on kit kat roms you can reach safestrap by simply rebooting rom and choosing safestrap recovery when dialog comes up
All Firmwares
NCG_Firmware_No_Bootloaders_V3.zip
NE9_Firmware_No_Bootloaders_V3.zip
NHA_Firmware_No_Bootloaders_V3.zip
NI2_Firmware_No_Bootloaders_V3.zip
NK2_Firmware_No_Bootloaders_V3.zip

can i use the Optimal Rom if i have BOK3?

coopmaster said:
can i use the Optimal Rom if i have BOK3?
Click to expand...
Click to collapse
Yes. I just added some instructions in OP that may be helpful

jrkruse said:
Yes. I just added some instructions in OP that may be helpful
Click to expand...
Click to collapse
Just a question so if i have BOK3 when i go to flash the firmware do i need to wait till that rom has a BOK3 firmware or can i flash any of them?

coopmaster said:
Just a question so if i have BOK3 when i go to flash the firmware do i need to wait till that rom has a BOK3 firmware or can i flash any of them?
Click to expand...
Click to collapse
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.

jrkruse said:
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
Click to expand...
Click to collapse
sweet thank you.

Might be stupid question but I was wondering if Extreme Syndicate and Cyanogemod are compatible.

jrkruse said:
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
Click to expand...
Click to collapse
Am I understanding you correctly that newer firmwares are backwards-compatible? Are you referring to only Lollipop ROMs, or does this also apply to older KitKat ROMs?
If I were to update past BOD, that does slam the door on downgrading to a KitKat bootloader as we have already discussed. I understood this to mean I wouldn't be able to use any KitKat ROMs.

painiac said:
Am I understanding you correctly that newer firmwares are backwards-compatible? Are you referring to only Lollipop ROMs, or does this also apply to older KitKat ROMs?
If I were to update past BOD, that does slam the door on downgrading to a KitKat bootloader as we have already discussed. I understood this to mean I wouldn't be able to use any KitKat ROMs.
Click to expand...
Click to collapse
You can get kitkat roms to boot just by flashing the rom the kernel and the NON_HLOS.bin but I dont know if your bootloaders will let the NON-HLOS.bin flash or not. You have to wipe data and internal storage also

Plasma ROM steer clear of, doesn't wanna play nice. However Optimal ROM works perfectly but hopefully the developer updates it to BOK3. Is anyone working on a debloat.bat for this firmware? or can someone?

DimitrieRetezatu said:
Might be stupid question but I was wondering if Extreme Syndicate and Cyanogemod are compatible.
Click to expand...
Click to collapse
Not sure about Extreme Syndicate. ROMs must be touchwiz based. No AOSP based ROMs, so Cyanogenmod is not compatible. You have to look for ROMs in the Verizon Galaxy S5 Android Development forum. Cannot flash anything in the Original Android Development forum. Also probably not any or possibly just a couple from the Unified Development forum.

landshark68 said:
Not sure about Extreme Syndicate. ROMs must be touchwiz based. No AOSP based ROMs, so Cyanogenmod is not compatible. You have to look for ROMs in the Verizon Galaxy S5 Android Development forum. Cannot flash anything in the Original Android Development forum. Also probably not any or possibly just a couple from the Unified Development forum.
Click to expand...
Click to collapse
Thanks for the response. Makes more sense when you put it like that. Hopefully people will see that the new root is available and update some ROMs!

secandRRe said:
Plasma ROM steer clear of, doesn't wanna play nice. However Optimal ROM works perfectly but hopefully the developer updates it to BOK3. Is anyone working on a debloat.bat for this firmware? or can someone?
Click to expand...
Click to collapse
There are several debloater zips I have made just check the OP on my rom threads

If you like a very debloated rom that is super fast and great on battery I recommend my BS Free Roms. @CVertigo1 made a new BOK3 version of my BS Free roms its only 800 mb in size thats half the size of normal roms. Check out his thread

Sticking to OptimalROM seems to be everything I need.

jrkruse said:
There are several debloater zips I have made just check the OP on my rom threads
Click to expand...
Click to collapse
I gave your zips a try on BOK3 with no luck?

secandRRe said:
I gave your zips a try on BOK3 with no luck?
Click to expand...
Click to collapse
You need to use the debloat script on a clean install of rom flash rom the flash debloat script. This way you haven't updated a bunch of apps

I'm tempted to try your ROMs I just like the S6 Keyboard on OptimalROM it's probably one of the best keyboards I have used.

My BOG5 BS Free Rom and BS Free Google Rom both have s6 keyboards

Help with root on an uncommon S5 build

Hi guys, I'm tired of searching for a safe root method for my G900F, but I can't find any solution which considers my build number:
MMB29M.G900FXXU1CPEM
Although my baseband shows:
G900FXXU1CPC9
Can you guys help me to understand what I need to root my S5?
Thanks in advance for your time.

Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537

6Maverick6 said:
Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
Thanks man. That thread warns about using roms which aren't exactly our model number and that seems to be my problem.
Although I have a S5 G900F (kltexx) my build ends in ...XXU1CPEM and chainfire's auto-root doesn't have it listed.
For what it's worth, sammobile lists my rom as having PDA G900FXXU1CPEM and CSC G900FTPH1CPE2
Also, chainfire's thread where we're supposed to point to new published stock roms doesn't allow me to comment, so I guess it's a dead end.
Is there anywhere where I can search?
Thanks again mate.

All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find

*Detection* said:
All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find
Click to expand...
Click to collapse
Thanks for your reply.
Although I also usually lecture people, in my own field of expertise, on how they shouldn't come to me with a problem without trying everything to fix it, I also try to be helpful in showing them the path that may enable them to help themselves.
Your answer does nothing for me, but thanks. I'm also aware that it shouldn't do anything for me, because of (insert jibber jabber about how these foruns are for developers and how rooting and custom roms will never be mainstream because the casual user isn't smart enough to press all the buttons in the correct sequence and developers need their time to be developing and not answering programming-illiterate people).
Anyway, if anyone else could point me, tip me, give me an innuendo in the right direction, I would be thankful. I'm not an expert, but since I've rooted my S4 (i9505) with chainfire's auto-root and loved CM12.1 and now CM13 roms, I was expecting to find a way to root my S5 (G900F) with these uncommon baseband and build numbers I've printed.
By the way: a search in xda-developers with my baseband shows 7 results, none of which concerns a rooted rom or specific method to root it. I know, because I've checked it before I bother everybody on this forum.
Thanks in advance guys.

You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP

*Detection* said:
You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP
Click to expand...
Click to collapse
Thanks man. Could you just answer me one last question? From your pointer and what I've read so far, this is what I think I understood already, could you let me know if this is by any chance a misinterpretation or am I in the correct path?
1) Since there's not an auto-root package with my baseband and build number I should resort to conventional root: installing a custom recovery, superuser and a custom rom like CM13.
2) Also, I now understand that, CF-Auto-Root would never help me to install CM13, because it just provides root access, nothing else, like CF's says.
3) Rooting with Supersu after installing a custom recovery isn't build or baseband dependent. Auto-root is, because it's basically your ROM rooted. Rooting with TWRP/SuperSu is just model dependent, so I would be fine with klte specific TWRP at https://dl.twrp.me/klte/ and a compatible SuperSu build.
My last question if you have the time, because I've searched for it and cannot find a clue: is it possible that my SIM-free G900F variant, has a locked bootloader? How can I check it?
Thanks again for your patience.
EDIT: dumb numbering.

G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM

*Detection* said:
G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM
Click to expand...
Click to collapse
Thank you so much man. The fact that you took the time to include the version numbers is awesome. I'll use TWRP because that's what I had in my S4 and worked really great. I believe I'll encounter small issues, but after your push I'll search for them in the forum. You're right, I was forgetting that CM13 has a built-in superuser manager. Thanks again.
The really scary part for me is the custom recovery install, because of bootloops or bricks.. but from what I've read so far I just need to be careful with checking and unchecking the right stuff in Odin and removing the battery after the green pass and before the device reboots. In some threads it's said that one should uncheck "auto-reboot", others say it should be checked, which is a bit confusing. I've seen in this thread http://forum.xda-developers.com/galaxy-s5/help/g900f-stuck-odin-mode-t3378907 that you advise to "uncheck it". Is it always the case?
Ok. This was really the last question.
Thanks again mate. You were really helpful and I'm sorry if I came across as annoying.

Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it

*Detection* said:
Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it
Click to expand...
Click to collapse
Hey man, just to let you know that everything went smooth like you said it would. Thanks again.

No probs, glad to hear it

lol
i was searching for a theard like this.
After 5 years i found it. I have the same baseband and build number. I have android 6.0.1.
will it still work? Im so much afraid of bricking my phone :crying:
Edit: Rooted succesfully.
Thanks a lot