yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 General] jdonice:
Having been an android user since the HTC Desire days and always been able to follow instructions from this forum (which is excellent by the way), so I very rarely need to ask questions. All I ever do is root the device and try some custom roms.

Now using a Samsung S5 Model (SM-G900F) , UK supplied by Vodafone.

The current state is :

Android 4.4.2.

Baseband G900FXXU1ANG8

Build KOTH49H.G900FXXU1ANI3

I am trying to root this device and its failing every time.

I end up with it soft bricked and I use Kies to restore it back to the above state.

(Why am I attempting to root?) Well this new release (4.4.2) has resulted in the SD card access problem, which is well documented online as a new 'security' feature from google.

So apps like Spotify and any really that require access to the SD card are failing now :)

Towelroot doesn't work for this device which contradicts what is written on this thread (yes I have enabled unknown access).

I have tried every recovery firmware too I can find: Clockwork, TWRP and ChainFire.. All fail via ODIN 3.07 and 3.09

So any ideas what's going on?
[Galaxy S 5 General] It_ler:
1. TowelRoot only works on older firmware versions (Quote from the first post of TowelRoot thread: "Every Android phone with a kernel build date < Jun 3"). If you want to root by TowelRoot, you have to flash an older ROM (or at least an older kernel), root with TowelRoot app and then flash back the new firmware/kernel with Mobile Odin Pro from Chainfire. Here is a description.

2. If you don't care about KNOX flag, just flash Chainfire's CF-Auto-Root with Odin and be happy. This is the easiest way of rooting IMO.

3. If flashing with Odin always fails, you have another problem. Check the USB cable/port (maybe try another one), check in Task Manager of your PC that KIES and every process of KIES is killed before starting Odin. Start Odin as Administrator, re-download the files you want to flash to be sure that there is no "bad" download/corrupt files.
[Galaxy S 5 General] jdonice:
Sounds like it must be down to the PC although have used the same one with my Desire and S3 in the past without issue.

I use a VM machine on my MAC (which has never given me trouble in the past).

And the fact its writing something then leaving me with a soft bricked phone implies that the USB drivers are allowing communication with my phone.

Could be that the USB drivers from the S3 are still being used by windows even though I actually removed them and used new ones from the thread instructions?

Other than that its the stock USB cable that was supplied with phone and the release of Chainfire is direct from their website (i.e. not a re-posted zip).
[Galaxy S 5 General] It_ler:
I don't think that the issue is about the USB drivers.

Maybe you just have to pull out the battery for a few minutes after flashing, then put it back in and reboot.
[Galaxy S 5 General] spackonaut:
Locked bootloader

I have a G900FXU1ANG8, which means it is from 2014 (the F) October (the X) with android 4.4.3. As far as I know the new versions have a locked bootloader, so you cannot to anything and flashed roms with odin won't boot. Chainfire sais that cf-autoroot doesn't work on looked bootloader devices:

In download mode my device shows: Qualcomm secureboot: enable (CSB)

But that doesn't mean it has a looked bootloader according to this post:

I am confused and I still don't know how to find out if the bootloader is locked, I don't want to test and brick the device. In the end I think I have to send it back.
[Galaxy S 5 General] It_ler:
I am a little bit confused now too.

The firmware you named (I assume you meant G900FXXU1ANG8 which is Android 4.4.2) has no locked bootloader ... it's still unlocked.

And if you why do you want to check for an unlocked bootloader?

I assume that you want to flash something ... e.g. a custom ROM, kernel or recovery.

So easiest way to check would be to flash it.

If the bootloader is unlocked, you can flash it successfully. Else you need to boot into download mode and flash back the official/stock firmware.

Anyway, if you don't want to take at least a little risk, just don't do it.

It's your choice.
[Galaxy S 5 General] spackonaut:
Yes it is a G900FXXU1ANG8 with Android 4.4.2, sorry.

I was confused because I mixed up the "qualcomm secureboot enable" with a locked bootloader. But the bootloader is not locked and cf autoroot worked like a charm!

I wanted to check for a locked bootloader, because cf autoroot would possibly brick the device when used with a locked bootloader. But it seems only the verizon/att have a locked bootloader for now.

Thanks for the info.
[Galaxy S 5 General] marvinricacho:
hi guys.

im really new to android community.

and i want to root my samsung s5

would this be rootable

Model NUmber: SM-G900F

Android: 4.2.2

BaseBand Version:G900FXXU1ANG8

Build NUmber:KOT49H.G900FXXU1ANI3

please give me an exact guild on how to root my device.

thanks in advance.
[Galaxy S 5 General] Y.G.:
Anyone know if the Cricket variant / SM-G900AZKZAIO has an unlocked bootloader?
[Galaxy S 5 General] It_ler:
You can root your phone by flashing CF-Auto-Root. Easiest method IMO, but this will trigger KNOX flag.

For KNOX-free rooting, check this thread.
[Galaxy S 5 General] briankimmy:
I just recently bought a new phone yesterday and want it rooted but my model does not seem to be supported in those threads.

Model: SM-G900A

Version: 4.4.2

Baseband: G900AUCU2ANG3

Build: KOT49H.G900AUCU2ANG3

Is there an alternative method I can use to root my device? Thank you
[Galaxy S 5 General] Wzup:
Rooting issues

So, I backed up my device on kies, and attempted to root. I used Odin as directed, and when the phone went to boot up in Recovery Booting mode, it froze there. I've restarted the phone multiple times, but nothing works. It is essentially bricked. Pulled batter and all. How can I revert my phone to it's original settings?
[Galaxy S 5 General] It_ler:
The SM-G900A has locked bootloader, so you can only root it (AFAIK) with TowelRoot.

As your firmware is relatively new and has the respective exploit patched, you have to "downgrade" first, then root with TowelRoot.

It's not that easy as for other S5 variants with unlocked bootloader ... like described here.

But generally it should be able to downgrade your device too ... maybe with KIES?!

EDIT:

Found a nice guide how to root your device: AT&T Samsung Galaxy S 5 > AT&T Galaxy S5 General > [How-To] Root G900AUCU2ANG3.

This should work for your firmware too.
[Galaxy S 5 General] eltonpestana:
hi

I live at brazil then phone is 900M i can use towerroot for root my phone?
[Galaxy S 5 General] y0c0nsci3nc3:
Is the Sprint ANK4 4.4.4 build rootable?
[Galaxy S 5 General] juck401:
s5 lollipop root and recovery?

s5 lollipop root and recovery? is there any working? i've seeen lollipop 5.0 updates for g900f, g900L , g900s , g900K so far c/o sammobile
[Galaxy S 5 General] aguarello:
Try to wipe everything in recovery.

Sent from my SM-G900F
[Galaxy S 5 General] mychalek:
Question

What is size a partition for rom and gapps in galaxy S5 ?
[Galaxy S 5 General] dynospectrum:
T-Mobile SM-G900T:

platform/msm_sdcc.1/by-name/ /dev/block/mmcblk0p6

lrwxrwxrwx root root 2013-12-31 19:39 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2013-12-31 19:39 backup -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2013-12-31 19:39 boot -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2013-12-31 19:39 cache -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 2013-12-31 19:39 dbi -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2013-12-31 19:39 ddr -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2013-12-31 19:39 efs -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2013-12-31 19:39 fota -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2013-12-31 19:39 fsc -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2013-12-31 19:39 fsg -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2013-12-31 19:39 modem -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2013-12-31 19:39 modemst1 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2013-12-31 19:39 modemst2 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2013-12-31 19:39 pad -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2013-12-31 19:39 param -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2013-12-31 19:39 persdata -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2013-12-31 19:39 persist -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2013-12-31 19:39 recovery -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2013-12-31 19:39 rpm -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2013-12-31 19:39 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2013-12-31 19:39 ssd -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2013-12-31 19:39 system -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 2013-12-31 19:39 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2013-12-31 19:39 userdata -> /dev/block/mmcblk0p25

u0_a235@kltetmo:/ $
[Galaxy S 5 General] Ricky Divjakovski:
thanks mate, gonna add support to my rom kitchen and EFS tool now
[Galaxy S 5 General] zidacj:
Here is the command that I ran. Let me know if it helps.

ls -l /dev/block/platform/msm_sdcc.1/by-name/

lrwxrwxrwx root root 2014-01-01 04:36 aboot -> /dev/block/mmcbl

k0p6

lrwxrwxrwx root root 2014-01-01 04:36 apnhlos -> /dev/block/mmc

blk0p1

lrwxrwxrwx root root 2014-01-01 04:36 backup -> /dev/block/mmcb

lk0p18

lrwxrwxrwx root root 2014-01-01 04:36 boot -> /dev/block/mmcblk

0p15

lrwxrwxrwx root root 2014-01-01 04:36 cache -> /dev/block/mmcbl

k0p24

lrwxrwxrwx root root 2014-01-01 04:36 dbi -> /dev/block/mmcblk0

p4

lrwxrwxrwx root root 2014-01-01 04:36 ddr -> /dev/block/mmcblk0

p5

lrwxrwxrwx root root 2014-01-01 04:36 efs -> /dev/block/mmcblk0

p12

lrwxrwxrwx root root 2014-01-01 04:36 fota -> /dev/block/mmcblk

0p17

lrwxrwxrwx root root 2014-01-01 04:36 fsc -> /dev/block/mmcblk0

p19

lrwxrwxrwx root root 2014-01-01 04:36 fsg -> /dev/block/mmcblk0

p9

lrwxrwxrwx root root 2014-01-01 04:36 modem -> /dev/block/mmcbl

k0p2

lrwxrwxrwx root root 2014-01-01 04:36 modemst1 -> /dev/block/mm

cblk0p13

lrwxrwxrwx root root 2014-01-01 04:36 modemst2 -> /dev/block/mm

cblk0p14

lrwxrwxrwx root root 2014-01-01 04:36 pad -> /dev/block/mmcblk0

p10

lrwxrwxrwx root root 2014-01-01 04:36 param -> /dev/block/mmcbl

k0p11

lrwxrwxrwx root root 2014-01-01 04:36 persdata -> /dev/block/mm

cblk0p22

lrwxrwxrwx root root 2014-01-01 04:36 persist -> /dev/block/mmc

blk0p21

lrwxrwxrwx root root 2014-01-01 04:36 recovery -> /dev/block/mm

cblk0p16

lrwxrwxrwx root root 2014-01-01 04:36 rpm -> /dev/block/mmcblk0

p7

lrwxrwxrwx root root 2014-01-01 04:36 sbl1 -> /dev/block/mmcblk

0p3

lrwxrwxrwx root root 2014-01-01 04:36 ssd -> /dev/block/mmcblk0

p20

lrwxrwxrwx root root 2014-01-01 04:36 system -> /dev/block/mmcb

lk0p23

lrwxrwxrwx root root 2014-01-01 04:36 tz -> /dev/block/mmcblk0p

8

lrwxrwxrwx root root 2014-01-01 04:36 userdata -> /dev/block/mm

cblk0p25

shell@klteatt:/ $

I'm happy to run any commands that anyone may need on adb or emulated shell that may help.

Hope this helps :)
[Galaxy S 5 General] Ricky Divjakovski:
can you try listing by name? also could you pm me
[Galaxy S 5 General] zidacj:
PM Sent and post above edited.
[Galaxy S 5 General] dynospectrum:
Ditto, but I will run anything needed for SM-G900T. ;]
[Galaxy S 5 General] charrua03:
Deletion of section'm wrong
[Galaxy S 5 General] Brentpn:
SM-G900I

hey i just got the sm-g900i model here in australia, if you need any lists or anything to aid in the rooting process i can assist

Edit ->>

ran the above command in shell

shell@klte:/ $ ls -l /dev/block/platform/msm_sdcc.1/by-name/

ls -l /dev/block/platform/msm_sdcc.1/by-name/

lrwxrwxrwx root root 2014-01-01 11:00 aboot -> /dev/block/mmcbl

k0p6

lrwxrwxrwx root root 2014-01-01 11:00 apnhlos -> /dev/block/mmc

blk0p1

lrwxrwxrwx root root 2014-01-01 11:00 backup -> /dev/block/mmcb

lk0p18

lrwxrwxrwx root root 2014-01-01 11:00 boot -> /dev/block/mmcblk

0p15

lrwxrwxrwx root root 2014-01-01 11:00 cache -> /dev/block/mmcbl

k0p24

lrwxrwxrwx root root 2014-01-01 11:00 dbi -> /dev/block/mmcblk0

p4

lrwxrwxrwx root root 2014-01-01 11:00 ddr -> /dev/block/mmcblk0

p5

lrwxrwxrwx root root 2014-01-01 11:00 efs -> /dev/block/mmcblk0

p12

lrwxrwxrwx root root 2014-01-01 11:00 fota -> /dev/block/mmcblk

0p17

lrwxrwxrwx root root 2014-01-01 11:00 fsc -> /dev/block/mmcblk0

p19

lrwxrwxrwx root root 2014-01-01 11:00 fsg -> /dev/block/mmcblk0

p9

lrwxrwxrwx root root 2014-01-01 11:00 hidden -> /dev/block/mmcb

lk0p25

lrwxrwxrwx root root 2014-01-01 11:00 modem -> /dev/block/mmcbl

k0p2

lrwxrwxrwx root root 2014-01-01 11:00 modemst1 -> /dev/block/mm

cblk0p13

lrwxrwxrwx root root 2014-01-01 11:00 modemst2 -> /dev/block/mm

cblk0p14

lrwxrwxrwx root root 2014-01-01 11:00 pad -> /dev/block/mmcblk0

p10

lrwxrwxrwx root root 2014-01-01 11:00 param -> /dev/block/mmcbl

k0p11

lrwxrwxrwx root root 2014-01-01 11:00 persdata -> /dev/block/mm

cblk0p22

lrwxrwxrwx root root 2014-01-01 11:00 persist -> /dev/block/mmc

blk0p21

lrwxrwxrwx root root 2014-01-01 11:00 recovery -> /dev/block/mm

cblk0p16

lrwxrwxrwx root root 2014-01-01 11:00 rpm -> /dev/block/mmcblk0

p7

lrwxrwxrwx root root 2014-01-01 11:00 sbl1 -> /dev/block/mmcblk

0p3

lrwxrwxrwx root root 2014-01-01 11:00 ssd -> /dev/block/mmcblk0

p20

lrwxrwxrwx root root 2014-01-01 11:00 system -> /dev/block/mmcb

lk0p23

lrwxrwxrwx root root 2014-01-01 11:00 tz -> /dev/block/mmcblk0p

8

lrwxrwxrwx root root 2014-01-01 11:00 userdata -> /dev/block/mm

cblk0p26

hope it helps :)
[Galaxy S 5 General] Darth Ziggurat:
1) Yes works splendid, I also tested it with paypal

2) No red message while booting, just the regular stock boot animation without any text.
[Galaxy S 5 General] khalid0099:
If i root my s5 can i unroot it later without losing my warranty?
[Galaxy S 5 General] Syn Ack:
Dare I try this on Verizon GS5?
[Galaxy S 5 General] el7145:
for now, once you root (with the current method), you will trip knox (0x1)...right now there is no method to put knox back to 0x0. I think we all hope that at some point someone will come up with an exploit to put the knox counter back to 0x0.

so, to sum up, once you root, your warranty is permanently void (for now)
[Galaxy S 5 General] Darth Ziggurat:
Recovery mode only goes in to manual mode.

imgur .com/XwXilX3

So I don't dare do something stupid.

Edit:

I fixed it, since I followed the steps in the order they were given I did not flash recovery on a rooted system. So I flashed the recovery again and it worked.
[Galaxy S 5 General] EliteScouter:
Does this work for SM-g900v? I just got my Verizon S5 today and I would like to root it.
[Galaxy S 5 General] kachhh:
Whst about sprint
[Galaxy S 5 General] oy2j:
I'm not sure if this is the right place to ask this..

I rooted my galaxy S5 successfully, but i tampered around with some system files and the phone froze at the Samsung logo screen every time i restarted the phone and it wouldn't pass that screen... long story short I fixed this by using kies to instal new firmware

so when i tried to root my phone now I get a:

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/003> Removed!!

why is this happening ? do I need to return the phone to stock? or is it because of the knox thing?

or a downgrade maybe?

thank you in advance
[Galaxy S 5 General] Ricky Divjakovski:
Seems like samsung patched the exploit In an update, the G900F was the first variant to be exploited, I sugget waiting until I get home and I will make a flashable .zip ito root the device.
[Galaxy S 5 General] oy2j:
I would be so grateful if you do, i stopped using it since I can't root it and restore some of my stuff..

if you don't have the time to make a flashable .zip please instruct me on how to downgrade
[Galaxy S 5 General] Ricky Divjakovski:
Ill be home soon so ill make it then :)
[Galaxy S 5 General] bchalker:
Any word on root fro Sprint users?
[Galaxy S 5 General] kamieniarz:
When will it work with official Android 5.0 ?
[Galaxy S 5 General] lvnatic:
I tried towelroot on my girlfriend's new s5 and it says device not supported. She has 4.4.2, what's wrong?
[Galaxy S 5 General] ragz:
Don't take this the wrong way, but if you don't know the answer to this, you probably haven't read enough about rooting to know the other issues ( knox, warranty, etc) that you may be getting into… just a suggestion

SM-G900W8, 0x1

A recovered flashaholic since Aliance Rom 5.5
[Galaxy S 5 General] lvnatic:
I'm well aware of the knox trigger, and it's not an issue here in Romania from the store she bought it. Just wanted to know if an easier method is working, otherwise odin will be fine too.
[Galaxy S 5 General] ragz:
Good, glad your informed, towel root only works on earlier model versions that had an open exploit, this exploit was patched in later versions, so not working with all later phones. There are no easier ways, but chainfire (cf-auto root) is a good one, but it triggers knox.

SM-G900W8, 0x1

A recovered flashaholic since Aliance Rom 5.5
[Galaxy S 5 General] lvnatic:
That's the way I rooted my note 3, worked on the s5 without any issues. Thanks for the kind answers!
[Galaxy S 5 General] elliwigy:
knox will be triggered just about any time you flash a recovery.. if he wants to keep knox at 0x0 then he needs to odin to an older firmware, root, the odin the newer firmware.. however if he ever wants custom recovery hell most likely have to trigger knox
[Galaxy S 5 General] Galaxy Strafe:
Hi guys, I recently bought a galaxy s5

Model: SM-G900F

Android Version: 4.4.2

Baseband version: G900FZHU1ANI2 (hong kong version)

and have been wanting to root this phone. I tried to follow the steps indicated to use towelroot and once I clicked make it rain it said the phone is not supported. I then tried using the mod strings but they did not work either.

I then read on the towelroot website "should support all phones < jun 3 2014"

Not entirely sure what I am meant to be comparing that to? The kernel version makes mention of Wed Sep 10, if that is what it is indeed comparing it to. Then how do I go about changing it so that the phone is pre june 3 2014? Much appreciated with any help. Can I use an old firmware from a different country?
[Galaxy S 5 General] It_ler:
1. The Build version is important with the build date of the ROM (or kernel) ... not the baseband version.

2. You have to flash either an older firmware/ROM or just an older kernel and then root with TowelRoot.

You may flash the a newer firmware/kernel again after rooting with Mobile Odin Pro app from Chainfire to keep root.

Here you can find some (stock) firmware version for the S5: S5 Firmware Thread
[Galaxy S 5 General] fullboogie:
Just used Towelroot to root my T-Mobile NE6 with a build date of May, 2014. Rooted just fine, SuperSU and Titanium Backup are working perfectly. Thanks OP!

I will note that for whatever reason, Towelroot would not download through the Dolphin mini browser - it seemed to rapidly reset the download procedure constantly. When I tried the stock browser, it downloaded just fine.
[Galaxy S 5 General] nawazdj:
Will it Work for Octa core version(SM-G900H) too?
[Galaxy S 5 General] acesarodrigues:
this method serves to g900md
[Galaxy S 5 General] adizz131:
Help required

Hi all.

I rooted my G900I using this method - http://androidxda.com/root-samsung-galaxy-s5-sm-g900i and it worked fine (I have root).

However I plan to flash ROM's etc soon, so will need a recovery system.

I have looked at the Philz CWM recovery and that seems to be ok.

I think the one I need is this one - http://xdaforums.com/showthread.php?t=2706253 (Anyone care to double check for me?? :) I have downloaded the philz_touch_6.57.8-klte.zip.md5 file )

So can I follow the steps on page 1 of this thread to install this? Or should I unroot, install Philz CWM, then re-root?

Also, how can I tell if my bootloader is locked?

Thanks in advance
[Galaxy S 5 General] Floody97:
hello guys, so it seems that this doesnt work for my S5 G900F which is baseband G900FXXU1ANG8 and build KOT49H.G900FXXU1ANI3 . if anybody can help please can you reply or message me.

thanks in advance.
[Galaxy S 5 General] beck_jeffrey:
Galaxy S5 SM-G9006V

Hi folks, This is my first experience with Galaxy S5 so please bear with me. If this has been asked and answered, my apologies. I looked for an answer and could not find one. I have a question regarding this Galaxy that I just bought. It is I believe a HK version with Android 5.0 OS on it I believe., at least the "about device" screen says so. Baseband version is G9006VKU1ANCD. I used the root checker app and it appears that phone already has root access because it says "Congratulations! This device has root access" and then it says Current device : SM-G9006V but the android version shows as 4.2.2. So I am not sure what is correct whether is has 4.2.2 or 5.0. What I really want to find out is it possible to flash this phone with stock TMOUS firmware. The phone is working fine as is and only reason for me to try and get TMOUS firmware on this is I would really like to use TMO wifi-calling on this phone. Any help would be greatly appreciated. Thanks
[Galaxy S 5 General] dhanasekar_83:
rooting

Hi, will the above method work on my SM-G900H android 4.4.2
[Galaxy S 5 General] pizzaman79:
Towelroot has been obsolete for ages. Please update the first post in this thread or un-sticky it.
[Galaxy S 5 General] hunt3r.pl:
What is an up-to-date method for rooting the device?

I want to root my G900F, I don't need android 5.0 for now, just get root.

From what I read here, I assume, that using the described method:

1. I can use TWRP recovery (http://xdaforums.com/showthread.php?t=2697762)

2. I will not loose any data (no wipe during the procedure) nor settings.

3. Knox will not be void (stays 0x0).

4. I'll get root on my stock ROM.

Is all above correct?

What about OTA?

Regards
[Galaxy S 5 General] Micrologos:
Hi all,

I tried using the existing CF-Auto Root (for SM-900F for 4.4.2) with 5.0 (Malaysia version, PDA: G900FDXU1BNL3, CSC: G900FOLB1BNL3, MODEM: G900FDXU1BNL1), the rooting seemed to go well initially but after booting into recovery once to test that it still worked (thanks to CF Auto Root the old recovery that came with 4.4.2 was flashed rather than the latest one that came with 5.0) it ended up with unavoidable "Mediaserver has stopped working" on boot that rendered the phone otherwise non functional and required re-flashing of 5.0 via Odin (restoring stock recovery and unrooting in the process) to fix.

Anyway I extracted the recovery.img from the .tar.md5 of 5.0 using 7zip to try and facilitate an update to CF-Auto Root for SM-G900F that will work properly with 5.0 (I believe that is what is required?), but I can't submit it to the central CF-AUTOROOT thread at http://xdaforums.com/showthread.php?t=1980683 (less than 10 posts) so I'm attaching it here as well as in the CF-Autoroot Q&A thread in the hopes that someone else could repost it over there, if it hasn't been posted there already.

Thanks!
[Galaxy S 5 General] xrayone911:
Thanks works great!!!
[Galaxy S 5 General] Rezvonflux:
Hello all!

FIrst off, man i love these threads...... they can be so handy. With that being said...

I'm a little out of practice when it comes to rooting/installing recoveries, etc.

I've done a LG Optimus 2x, an S3 and now i got myself a S5.

Will this method trip anything,....KNOX, etc?

Also, i'm using the

Fido Canadian

variant, the G900W8 running 4.4.2

...will i have any issues?

i'm currently downloading files, installing whatever is missing on this machine and was willing to try.... i really miss my ad blocker, custom recovery, TB

Thanks for the help!
[Galaxy S 5 General] Rezvonflux:
YAY, it worked! from what i can tell, nothing has been tripped ;)