yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Q&A, Help & Troubleshooting] b8213:
Good idea, but how to root, if there seems to be no way to...

towelroot:

Android 4, G900FXXU1ANE2, stock image is not running

Android 4, G900FXXU1ANG2, device is not supported in towelroot

Android 5, G900FXXU1BOD3, device is not supported in towelroot

chainfire via custom recovery:

not possible, force recovery lead to black screen

Is there another way to root one of the stock images Android 4 G900FXXU1ANG2 or Android 5 G900FXXU1BOD3?
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
CF Auto Root & ODIN
[Galaxy S 5 Q&A, Help & Troubleshooting] ebrot:
You're not alone! Im trying to root/flash custom recovery on my S5 (also G900FXXU1BOD3) since Friday, same approach as you. Tried everything I could find, nothing works.

Keeping an eye on this thread.
[Galaxy S 5 Q&A, Help & Troubleshooting] b8213:
Thanks.

I have also tried this: flashing of chainfires auto root via odin, then straight ahaed to recovery mode -> black screen (no execution of chainfires script, device is not rooted)
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Running ODIN as Admin?

Got phone in Download Mode?

Samsung Drivers installed?

Using a native PC?
[Galaxy S 5 Q&A, Help & Troubleshooting] b8213:
Yes, have tried Odin 3.07 and 3.10.6 run as administrator

yes, download mode is always possible

yes, the last one v. 1.5.51.0

yes, its a notebook with native win 7 SP1 64 bit (no vm)
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Do you have another machine you can try flashing it from?

Different USB cable?
[Galaxy S 5 Q&A, Help & Troubleshooting] b8213:
I have already tried adb sideload from an ubuntu pc - same result (black screen). At the moment, I have no other Windows machine to try flashing from.

Yes, I have tried the original white one and an old black one - same result (black screen)

Flashing the stock rom from Android 4.4 ANG2 <-> Android 5 BOD1 via odin works fine. Also flashing only stock recovery.img (via odin, packed as tar) works fine. Before I am going to try to flash a custom recovery, I made sure that stock recovery is flashed an working.
[Galaxy S 5 Q&A, Help & Troubleshooting] Jaanto:
I'm just leaving this here in case someone solves it. Running G900FXXU1BOD3 and need root.
[Galaxy S 5 Q&A, Help & Troubleshooting] worf_1977:
Try to flash back to ANG(X), boot, then flash ANE2 kernel and use toweloroot. And ignore the FC's you should be getting, and reflash ANG2 kernel.

That should do it. If not, well, I'm in the dark (you can't use Samsung's service claiming that you are not able to root the phone LOL)

Enviado desde mi SM-G900F mediante Tapatalk
[Galaxy S 5 Q&A, Help & Troubleshooting] cyberfrog77:
Bought a Galaxy S5 yesterday and tried to flash from 5.0 to 4.4.2. It´s Mission Impossible.

When i flash anything older than ANG2 the phone boots but Display stays completly black.

tried to flash from G900FXXU1BOD3 to G900FXXU1ANE2 -----> Black Display

tried to flash from G900FXXU1BOD3 to G900FXXU1ANG2 -----> works, but towelroot does not support G900FXXU1ANG2

tried to flash from G900FXXU1BOD3 to G900FXXU1ANG2 and flash the G900FXXU1ANE2 Kernel -----> Black Display
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
This ties in with what I've heard rumours of......that something in a 5.0 firmware is not erased/overwritten during a rollback to 4.4 and causes 'problems'......

I wonder if flashing a pit would sort it out? If I understand how a pit file works, I *think* it formats the partitions and re writes them......that being the case, it should erase every trace of any pre existing OS allowing you to flash onto a completely blank device......somebody please CMIIW......

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Yep, that's my understanding of PIT files too

But I have flashed back from the latest LP to KK without any problems

And CF Auto Root still works like it did with any firmwares

If Samsung had changed something, everyone would be having the same problems surely
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
I believe the poster is trying to roll back to KitKat in order to use towelroot.....

Something in Lollipop is stopping this even after the roll back.....so if he flashes the pit and a KitKat firmware, he *should* be able to towelroot it.....

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Unless the new ROM is changing something hardware specific, similar to KNOX, then agreed, there should be no problems rolling back with PIT

But IMO, it's something else, not being able to flash CF Auto root with ODIN tells me he has bigger problems
[Galaxy S 5 Q&A, Help & Troubleshooting] cyberfrog77:
i`m also not able to flash CF Auto root or TWRP recovery
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Which model S5?

Running which ROM?
[Galaxy S 5 Q&A, Help & Troubleshooting] cyberfrog77:
Galaxy S5 SM-G900F G900FXXU1BOD3

Bought it yesterday
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
I've seen an increase in the number of threads mentioning this over the last couple of weeks, and apparently it's being discussed on other forums too......

As for not seeing it before, maybe it's a relatively new issue......It seems to be connected with Lollipop firmwares and/or devices that have been updated to Lollipop, after all, the firmware hasn't been available for the S5 variants for that long.......It may also simply be the case that it's connected specifically with the latest Lollipop builds....

(Could really do with the input from a Dev like [MENTION=631273]Chainfire[/MENTION] here......somebody with in depth knowledge of Samsung firmwares)

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Like I say though, I've downgraded from the latest LP on the G900F to KK, and back again without any problems
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
I don't think it's downgrading and upgrading that's the problem.....it's the rooting post flash that seems to be causing problems......

And for my money, the increased frequency with which this is being discussed rules out the possibility of faulty hardware......

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] Akalsemann:
For me root on lollipop worked, but not the usual way. I had to untick auto reboot on odin, proceeded to flash philz and then manually booting to recovery directly after removing the battery after flashing.

So yeah there is something wrong, however it is very odd that it refuses to work for certain devices, i also have a sm-g900f btw, nordic pda.
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
Is that an older lollipop build? What is the date of build?

As an alternative theory, I wonder if the 'security policy updates' system app has any affect on this?

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] b8213:
I have tried this (see my first post in this thread, point 3) - that did not work for me.

For the records: Flashing of CF Auto Root, ANG2, ANE2, custom recoveries TWRP or CWM in odin is possible (result is pass with no autoboot selected). But then, after removing the battery and booting directly into recovery - the device is black/death. Then, removing the battery/long power button is necessary to boot the device into android or to use the download mode for the next try.

Regarding PIT - in my understanding repartition - is not an option for me at the moment.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
I have rooted every single LP ROM since release without any issues

Downgraded from LP to KK, fine

back to LP, rooting works as before

Something else in in play here Im sure
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
I am super newb here but have you tried to do CF Auto Root first on a stock BOD3 firmware FIRST? then push recovery via Odin? That is what I did for my S5 (G900I) that I got a few days ago. It also came loaded with the most updated LP softwear already. Towerroot didn't work on the LP. So my first step was to CF Auto Root via Odin then push twrp recovery via odin and it works fine.
[Galaxy S 5 Q&A, Help & Troubleshooting] Drwk340:
Same issue here

I have the same issue.

With a brand new S5 with factory G900FXXU1BOD3, there is no way to install a custom recovery and to root the device.

I have tried any possible custom recovery in the past two days with no success. Everytime, when trying to access the recovery menu, it stucks on the logo screen. The only way to gain access to the recovery menu is to flash the full stock firmware again.

(As a side note, my strong necessity to root the phone is due to the fact that this is my second S5 that experienced a reboot loop issue caused by some wifi networks. It looks like an Android 5.0 bug in the parsing of the wpa_supplicant.conf file. I can't explain why I'm the only one with this issue. But I will probably create a separate thread on this, because it's totally unrelated to the above, that is, apparent impossibility of rooting recent S5 models).
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
Just re-read all the posts in this thread, and BOD3 firmware seems to be a common denominator for all those who can't root........

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] ArtaxXP:
Same issue here.

Brand new S5 but with G900FXXU1POCH, the newest from O2 Germany. Impossible to root it or to install a custom recovery. always ends up in black screen or just hangs completely while trying to boot into Odin flashed custom recovery.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
BOD3 is the only Firmware I did not try, as it only landed for BTU on sammobile a day or so later than BOE5
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
In that case, I'd say....lucky you haven't tried it.....and probably best to avoid voluntarily flashing it too......

This problem REALLY IS looking more and more like it's firmware related.....

If only we could find out what changes were included between BOE5 and BOD3.....

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
The only reason I didn't upgrade, was because it didn't hit SM before BOE5, instead weirdly after, even though it was older

Maybe it's a bug, if it was intentional, then Id expect Samsung to continue with it with their latest builds

Agreed, if we can find a changelog between the two
[Galaxy S 5 Q&A, Help & Troubleshooting] Omega2513:
So what I did to my Samsung S5 SM-G900W8 was flashed down to G900W8VLU1ANF3, pulled battery, booted into stock recovery, did a factory reset, rebooted then installed towelroot; but now after reading all of this I wonder if I install LP would I still have root, and if so, should I install G900W8VLU1BOB3 or G900W8VLU1BOC1. They were both loaded onto sammobile on the same day but BOC1 seems to be newer.

Edit 1: Ok so I did BOC1, it upgraded to LP but I lost root. I'll try BOB3 tomorrow but I have a feeling that we either have to keep root on 4.4.2 and wait until there is a way to root LP without tripping knox, or have LP and trip knox with root.
[Galaxy S 5 Q&A, Help & Troubleshooting] Drwk340:
Even KingRoot fails...

I tried with KingRoot, but it fails too. Here's the message it prints:

Root strategy unavailable

no strategy now

14957 request received

Research is accelerating for you
[Galaxy S 5 Q&A, Help & Troubleshooting] GT-I9000:
I am having similar problems, unable to root using CF method, I to am on G900FXXU1BOD3.

I have also tripped the Knox 0x1
[Galaxy S 5 Q&A, Help & Troubleshooting] disobiech:
Was anybody successful with this firmware?
[Galaxy S 5 Q&A, Help & Troubleshooting] cyberfrog77:
When did you buy your S5 guys? Everyone with this problem i know bought their S5 in the last couple of weeks. Bought mine last week. My wifes S5 has the BOD3 but it´s already one year oldand i had no problems rooting it.
[Galaxy S 5 Q&A, Help & Troubleshooting] Drwk340:
Mine is 3 weeks old
[Galaxy S 5 Q&A, Help & Troubleshooting] ArtaxXP:
one week

okay, I think that all of us have two problems:

=> flashing a custom recovery with odin ends up in a black screen when trying to boot the recovery. only the stock recovery works

=> downgrading to an android 4 rom ends up in a black screen too (booting + sound, but black screen, maybe the same with the custom recovery? )

if that's a new security system in the bootloader, flashing an older bootloader should work, but I already tried that. same results.

so what can we do?
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
I mentioned earlier in this thread that flashing a pit file *might* help.....

A pit is going to erase *all* traces of any previous firmware and allow you to flash the KK firmware onto completely blank, formatted memory......

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] 33er_export:
same Problem here, new phone, G900FXXU1BOD3, can´t get any other bootloader or root to work.

flashing CF-Auto stucks always in:

Recovery Booting....

Recovery is not SEANDROID Enforcing

Set Warranty: recovery

Tried odin 3.07, 3.09, 3.10

ive also unchecked "Auto Reboot", waited ~2mins until odin3 said "pass!", removed the battery and started into recovery - but no success..

Flashing twrp-2.8.6.0-klte helps to start the phone, but no root rights aquired and no twrp recovery access.

can boot to the stock RECOVERY_G900FXXU1BOD3.tar.md5, but no root either.

here is a Video from a guy updating to bod3 and rooting his device: https://www.youtube.com/watch?v=lQw-eic1tEE

but strangely the cf-update which is shown in the Video is the old Version. in the description he links to the new one.

(and both dont work for me..)

Edit: btw: Need root..
[Galaxy S 5 Q&A, Help & Troubleshooting] Omega2513:
Can anyone downgrade to a stock android 4 rom on stock recovery? I'm seeing reports of people trying to use custom recoveries but nothing about stock. Try it like this:

1: Flash stock android 4 rom through odin with stock recovery.

2: Pull battery and boot up into stock recovery, factory rest, wipe cache.

3: Towelroot

4: If you want to go to 5.0, us CF's FlashFire, NOT MOP. He clearly has a warning on the play store page not to use it for 5.0 roms.
[Galaxy S 5 Q&A, Help & Troubleshooting] GT-I9000:
3-4 weeks ago
[Galaxy S 5 Q&A, Help & Troubleshooting] cyberfrog77:
All phones not older than 4 weeks.

bought my phone one week ago.( Returned it to vendor)

Another guy in a german forum told me that he has the same problem . he bought his phone about 1 1/2 weeks ago .

Anyone here with an older phone who has this problem?
[Galaxy S 5 Q&A, Help & Troubleshooting] disobiech:
Someone who reports downgrading to KitKat stock didn't work (3)

http://xdaforums.com/showthread.php?p=61341980
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
Can you list the step by step tutorial of how to flash a PIT file?

---------- Post added at 10:34 PM ---------- Previous post was at 10:24 PM ----------

Also did you guys enable USB debugging first?
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
Sorry fella.....having never flashed pit files before (all I know is what they are and how they work), I don't feel qualified to advise you......

I'm pretty sure you'll have to flash the pit first to 'clear erase' the device, and then I KNOW you'll have to flash the firmware BEFORE attempting to boot the phone normally otherwise there will be no OS for the phone to boot into......

Here's a list of available pit files......

http://xdaforums.com/showthread.php?p=52329647

make sure you get the CORRECT one for your device, or you'll find yourself in a whole world of hurt......

Finally, if you run a rooted phone, it's probably best to have USB debugging enabled as standard.....though I'm not certain if it's actually necessary for Odin flashing......

If someone like [MENTION=4369943]*Detection*[/MENTION] can come in and advise the procedure for the pit flash it'd probably be better for you.....

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] 33er_export:
yes did that.

but havent tried the .pit and downgrade part. havent flashed for years and don´t feel that confident.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
PIT file just needs adding to ODIN along with a stock ROM, flash them both together - ODIN will flash PIT to repartition, then it will flash the ROM
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
Thanks *Detection* wasn't sure how to do it....didn't want to advise........

If this procedure doesn't help, I'm completely outta ideas......

Sent from my rooted, debloated stocKK kn0x0 SM-G900F
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
Thank you for sharing this information. Just a to clearify, in Odin 3.09 stock rom tar.md5 file goes in the AP tab. Which tab would the PIT files go into?
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
The PIT section
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
I am sorry I just opened ODIN and saw a specific tab named PIT. I believe that's where PIT file is added to ODIN DUH!! STUPID ME.

If I flash it together wit ha stock firmware do I need to tick the re partition box?
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
3.09 should look like the image above, 3.10.6 has a separate tab

The re-partition box should tick itself when you load the PIT file, if not, yes tick it
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
Thank you or the help. Now we have all the ducks line up just need a member to try and test this. and provide feedback.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
This info was not for yourself?
[Galaxy S 5 Q&A, Help & Troubleshooting] dork997:
have the exact same problem. Also updated to latest 5.0. Downloading KK from sammobile will try rooting it and will report back if it works. cant install custom recovery either. i just called up the guy i bought this phone from and insulted him very badly i thought he gave me a damaged phone poor guy will apologize now.
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
I currently use the G900I. But I just ordered a G900F from B&H. I believe it will come with the most updated rom installed. Once I get the F version I will also try it myself.
[Galaxy S 5 Q&A, Help & Troubleshooting] adrenalize_:
Is it worth people posting their CSC and manufacturing date etc (that you can find from Phone Info Samsung app for example) on phones that custom recovery/root is not working to try and narrow it down? I've a much older manufacturing date and need to root for a couple of things now, but will report if unsuccessful as I'm on BOE5 BTU firmware.
[Galaxy S 5 Q&A, Help & Troubleshooting] Petreion:
Downgrade to kitkat with firmware end pit file for ur model end then root end flash recovery

---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------

Downgrade to kitkat with firmware end pit file for ur model end after you may root end flash recovery
[Galaxy S 5 Q&A, Help & Troubleshooting] mf1tym:
Were you sucessfull downgrading back to KK stok ROM ater flashing the PIT files?
[Galaxy S 5 Q&A, Help & Troubleshooting] dork997:
I was able to downgrade. I downloaded a stock kitkat (UAE) rom. First Flashed twrp then format >clear dalvik,cache,data,system, internal storage then from restart option of twrp i went directly to download mode flashed that kitkat rom. i rooted it with CF auto Root and install twrp again afterwards but this "recovery is seandroid enforcing" error never went away it still displays for 2-3 seconds before going into recovery. Another problem My phone is not saving Wifi passwords on any lollipop firmware. I have tried many builds but same issue.
[Galaxy S 5 Q&A, Help & Troubleshooting] enzo-ita:
I wonder if this is a problem for g900f or also for g900fd.

If I could be sure to not change my knox and If I could create an image of my g900fd beeing absolutely sure to be able to use it to take back my phone to it's original state (as it was when the image was created), I would do a flash with twrp and root to see if I incurr in the same problem.

ciao from italy
[Galaxy S 5 Q&A, Help & Troubleshooting] 33er_export:
But our Problem is to Flash a custom recovery. When did you flash twrp? after loading a pit file?
[Galaxy S 5 Q&A, Help & Troubleshooting] 33er_export:
It finally worked for me. new Galaxy S5 (SM-G900F, Androd 5.0, G900FXXU1BOD3 preinstalled, DBT)

Used:

New twrp 2.8.7.0: https://dl.twrp.me/klte/

Odin3_v3.10.6

UPDATE-SuperSU-v2.46.zip

After flashing the new twrp it still says:

But it boots into twrp after a few seconds. Here you can Flash the UPDATE-SuperSU-v2.46.zip and root acces is gained.

Finally a working phone:)
[Galaxy S 5 Q&A, Help & Troubleshooting] dork997:
i did not flash any pits...just download older version of KK. root it with cf (uncheck auto reboot option) when rooted unplug battery put it back it and boot up...it will display some error then after 4-5 seconds CF autoroot script will run. After Root download latest TWRP from their website and flash it in odin. Again when u enter recovery it will display seandroid error but will enter TWRP after 3-4 seconds. Make sure u use older version of CF auto root which was for devices on 4.0 I rooted 5.0 and 4.0 with it the newer kltedxx version for some reason does not work for me.

---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------

Glad it worked, after the above procedure i ran into a problem...i did this on 5.0 BTU but for some reason it was not saving my wifi password...i tried all flashed diff versions of firmware factory reset, clear caches and what not. So i downloaded the Build.prop editor and made necessary changes set ro.securestorage to false. it solved the problem but every now and then when i am doing stuff in TWRP (like i just created backup on phone and on sd card) MY Phone gets stuck at the booting logo....and then everything starts crashing "mtp storage has crash, touchwiz has crashed blah blah blah.....then i have to start from scratch......factory reset + Restore backup. Its happening on 5.0 Dont know if i will have the same problem on 4.0.
[Galaxy S 5 Q&A, Help & Troubleshooting] Drwk340:
What made the trick, with respect to previous attempts?