Database Users

SM-G900F (XXU1BOJ1) rooting failed -> recovery is not seandroid...

Hi,
I try to root my (S5 SM-G900F XXU1BOJ1), but id did not work...
Here are the Steps I did:
1. Starting Odin 3.10.7 as Admin (Win10); Autoreboot on, F. Reset Time on; rest off.
2. Click on AP, choose File "CF-Auto-Root-klte-kltedx-smg900f.tar.md5" taken from here (for 5.0)
3. Put Galaxy s5 in download mode (switch off phone then hold VolDown+Home+Power)
4. Connect S5 with USB to PC and hit "Start" on Odin; Odin quits with: success: 1 / failed: 0
Phone rebooted automaticaly, but halt with:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Battery out & in, booting in recovery (VolUP+Home+PWR) result allways in Set Warranty Bit: recovery;
Battery out & in, booting in download mode still working, so I flashed "twrp-2.8.7.0-klte.img.tar" with Odin to get my Phone work...
What is wrong? How can I get my S5 rooted?
Thank you & best wishes,
cya

Try KLTExx and not dx
cyaneo said:
Hi,
I try to root my (S5 SM-G900F XXU1BOJ1), but id did not work...
Here are the Steps I did:
1. Starting Odin 3.10.7 as Admin (Win10); Autoreboot on, F. Reset Time on; rest off.
2. Click on AP, choose File "CF-Auto-Root-klte-kltedx-smg900f.tar.md5" taken from here (for 5.0)
3. Put Galaxy s5 in download mode (switch off phone then hold VolDown+Home+Power)
4. Connect S5 with USB to PC and hit "Start" on Odin; Odin quits with: success: 1 / failed: 0
Phone rebooted automaticaly, but halt with:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Battery out & in, booting in recovery (VolUP+Home+PWR) result allways in Set Warranty Bit: recovery;
Battery out & in, booting in download mode still working, so I flashed "twrp-2.8.7.0-klte.img.tar" with Odin to get my Phone work...
What is wrong? How can I get my S5 rooted?
Thank you & best wishes,
cya
Click to expand...
Click to collapse

androidtweaker1 said:
Try KLTExx and not dx
Click to expand...
Click to collapse
OK, flashed with "CF-Auto-Root-klte-kltexx-smg900f.tar.md5" taken from this Post but same here, the only different is the screen turns black and no response (waiting 20 min.).
Maybe the files is for 4.4 and not for 5.0; any idea where get kltexx for 5.0?
Also tried it with "Auto Reboot" off in Odin and rebooted manualy.

Hmm, I looked at the Chainfire Site and found both files listet for my G900F, but none of them is for the actual Stock ROM release ( G900FXXU1BOJ1).

Now I habe a rooted S5
1. copy "UPDATE-SuperSU-v2.46.zip" to phone internal storage
2. flash the "twrp-2.8.7.0-klte.img.tar" with Odin (with "Auto Reboot" OFF)
3. After battery out and in, boot into recovery (VolUP+Home+PWR)
4. In recovery with TWRP go to install zip, choose "UPDATE-SuperSU-v2.46.zip".
Reboot Phone and tested with a root Checker from Playstore and -> Congratulations! Root access is properly installed on this device!

cyaneo said:
Now I habe a rooted S5
1. copy download.chainfire.eu/696/SuperSU"]UPDATE-SuperSU-v2.46.zip to phone internal storage
2. flash the dl.twrp.me/klte/"]twrp-2.8.7.0-klte.img.tar with Odin (with "Auto Reboot" OFF)
3. After battery out and in, boot into recovery (VolUP+Home+PWR)
4. In recovery with TWRP go to install zip, choose "UPDATE-SuperSU-v2.46.zip".
Reboot Phone and tested with a root Checker from Playstore and -> Congratulations! Root access is properly installed on this device!
Click to expand...
Click to collapse
Thanks, I had the same problem and thanks to this method it workes just fine.

Does this mean you don't need CF-Auto-Root-klte-kltexx-smg900f.tar.md5 if you are using the above method?

As long as you have a custom recovery and use the flashable SuperSU.zip you don't need cf auto root. I think it's a safer method personally, as I've seen a few people on here have issues using cf auto root. I used the recovery + SuperSU method myself without problem on the G900F

Unable to gain root on SAMSUNG G900F

I have SAMSUNG SM-G900F with firmware : FXX1BOJ1 and CSC: BOH1
I tried to root this device using CF-Auto-Root-klte-kltexx-smg900f.tar.md5 . After succseffuly flashed with ODIN, the phone din not boot anymore. No matter if I enter in recovery or normal boot on screen appear :
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING...
Set Warranty bit : recovery
Then I flashed a custom recovery in order to try to revive the phone and apply root as well. I flashed CWM : philz_touch_6.26.2-klte.tar.md5 in idea to use it and install SUPERSU. However after succesfullt flashed it with ODIN,the phone boot fine but when I enter recovery the normal ANDROID recvery was present instead of CWM.
In download mode following informations appear now on screen :
ODIN MODE (in red)
Product name : SM-G900F
Current Binary : Custom
System Status : Custom
Reactivation Lock(KK) : OFF
KNOW WARANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB) (in gray)
SWREV: S1, T1, R1, A1, P1 (in gray)
SECURE DOWNLOAD (ENABLE) (in blue)
UDC START (in red)
I understand the knox is deactivatedand there and is no known method yet to clear the bit, but I can live with it. However I don't understand what that (4) mean. It was from the beginning (when I first enter in download mode) However how to root it ?
Thank You

Flash twrp, boot in recovery, Flash supersu.zip
tapatalked

I tried to flash CWM but seem it was not flashed, because when I enter in recovery instead of CWM It was executed standard recovery. Where can I find twrp for Galaxy S5 (G900F) ?

Hey there, I got my S5 a week ago and had some flashing problems as well (G900F on official lollipop update). Got it after some research though, follow these steps. Also, I see you're more into CWM, but I recommend TWRP, that's what I'll be using below. Note that this method does trip Knox.
1. Not necessary, but recommended - If you can boot, go to the play store and download "Castro". Castro is a good looking app that shows you all the information about your phone, hardware and software. So you can see if you have root status, the system info, bootloader status etc. etc. This is good if you flash something you can always see how your phone was originally. Plus the root checker will be handy later on. You can export all this information to a PDF or DOC in the app using the three dot menu, then just copy this information online or on your sd card for safe keeping.
1. Boot into download mode.
2. Use Odin (you can use the one attached IF you want) and flash the stock firmware of your device to fix any problems the flashing you did might have caused, this will restore original recovery, boot and system.
2. After flashing the firmware, boot the phone into recovery to check if stock recovery is there, then boot normally to make sure the system is working fine.
3. Download the attached TWRP, it's a .tar so you can flash it in odin. Boot the phone in recovery, there should be some blue, red, and yellow writing in the top left, that's fine, it will go away within 5 seconds or so and then jump into TWRP.
4. Get the SuperSU zip attached below on your phone (if it isn't already, while in twrp you should have access to send files to your phone through usb), in TWRP, select install, then browse to where the file is. Choose it and swipe to flash. When done, reboot.
5. Look for the SuperSU app icon in your app drawer. If it's there, then that's good. Go to the playstore, search for SuperSU and select update.
6. Open SuperSU, it should be working fine.
7. Use Castro or any other root checker to test if root is working, it should be.

Just to add to the above instructions.....
Before you begin the TWRP/superSU flash process, go to .....
Settings>>Security
and disable Reactivation Lock......
Leaving it enabled *has* been known to cause problems during rooting. So whether you start by flashing full stock to your device (or not) check it.......
Edit......oh and after flashing TWRP, DO NOT let odin reboot the device......remove the battery to prevent this if you have to, make sure you boot into the newly installed TWRP and install the superSU zip BEFORE you boot up normally.....
http://i.imgur.com/rVnFwJM.jpg

spon901 said:
I tried to flash CWM but seem it was not flashed, because when I enter in recovery instead of CWM It was executed standard recovery. Where can I find twrp for Galaxy S5 (G900F) ?
Click to expand...
Click to collapse
Welcome to internet lol forum is clearly and easy for all user even me the illiterate ( you have search in tread is useful )

Thank You very much. The issue was that after flashing I was boot normally first (check auto reboot option in odin). Now after flashing (having auto reboot in odin not checked) , I power off the phone by pressing power button for few seconds, and then first time boot in recovery mode and install SUPER SU. Then boot normally and everything was fine , and I have root of course!!!
Thank again for help.

[HELP] SM-G900F stuck in a recovery bootloop

Hi,
I'm from Singapore and I believe I have the international s5 (SM-G900F), at least that's what it says in download mode. My phone was running CM13 nightly and till last night it was working fine. Last night when I charged it, I woke up this morning and my battery was incredibly overheated. I changed my battery and tried booting, but now it gets stuck in a bootloop. I flashed stock 5.0 lollipop from sammobile via odin, but it still is stuck. I can boot perfectly into download mode with the android logo. Here are the details:
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
System Status: Custom
Reactivation Lock (KK): OFF
KNOX WARRANTY LOCK: 0x1 (04)
QUALCOMM SECUREBOOT: ENABLE(CSB)
RP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I would really appreciate any help. Thanks!

Boot into recovery and factory reset, then try booting again
Sounds like the DATA partition got corrupted, or something installed to it did, flashing with ODIN doesn't wipe anything, so you'll still be bootlooped unless you wipe DATA / Factory Reset

When you go from cyanogenmod back to stock samsung firmware, a wipe data / factory reset is required in recovery or else the phone will be stuck in a boot loop or not boot up.

Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.

imbtrthanu said:
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
Click to expand...
Click to collapse
Flash TWRP 3.0.0.0 with ODIN and wipe from there, then flash stock again
https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html

Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.

Is there any other way I can do a wipe? Through adb or something? Or should I select a specific option in Odin (3.09) ? Like bootloader update, etc or something?

imbtrthanu said:
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Click to expand...
Click to collapse
Uncheck "Auto Reboot" in ODIN, flash TWRP again, when it completes, disconnect USB and pull the battery to power off the phone
Replace the battery, and boot immediately into recovery with Vol Up & Home & Power

Hi that's not working as well. Should I reflash stock and then flash twrp in the way you suggested?

Try, but something seems wrong because you should be able to flash TWRP with ODIN
Have you got the drivers installed and does ODIN give you a COM port at the top when the phone is in download mode?
You are putting the phone in download mode to flash TWRP right?
Vol Down & Home & Power

Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up

imbtrthanu said:
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
Click to expand...
Click to collapse
If the COM port lights up, the drivers are installed and working
Try ODIN 3.10.7, that's the latest version
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg

Hi, that also didn't work. Any other advice?

Use a different PC / USB lead, everything you have tried should have worked fine on a G900F

Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so

imbtrthanu said:
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
Click to expand...
Click to collapse
Didn't you flash the G900F PIT?
Flash this in the PIT section of ODIN along with the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit first

Hi, I tried flashing the stock rom with the PIT you gave me but it gave me the following response:
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what I should do now? Also, which stock rom should I be flashing? KK or Lollipop?

I don't know what you've done to your phone, and from your main post, it is definitely a G900F if that is what it says in download mode
Which PIT did you flash the first time? And did it flash successfully?
Any stock ROM should work, but might as well go for Lollipop, I know 100% this one works
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
The only thing I can think of for now is to tell KIES3 to perform a firmware recovery
Code:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
If you already have KIES installed, remove it and try ODIN again, people have reported it interferes with ODIN
If not, install KIES3, go to the firmware recovery setting and see if it can fix your phone
Other than that, it looks like it's going to need someone with knowledge of manual partitioning via adb shell or something, if the phone can enter a mode the PC can use that with
EDIT - You are using a native PC running Windows 7 or later right? Not a mac running Windows? Macs don't install the drivers properly and fail

Yup I'm running Windows 10. I'll try KIES and see if that works!

Which PIT did you originally flash? And did it actually flash?

Need Help With Rooting G900F 6.0.1

Hello, this is my first post.
Introduction
So today & yesterday I tried rooting my stock ROM, Android M 6.0.1 G900F Galaxy S5 but I've had a few problems with it.
Details
I think I've done everything correctly to try to flash TWRP onto my phone:
Downloading the lastest version of TWRP-klte (I've used 3.0.2-1 & 3.0.2-2)
Unticking 'Auto-Reboot' in Odin (I've used Odin3_v3.09 & Odin3_v3.10.6)
Pull out the battery to get out of download mode, etc.
But nothing seems to work. When I go into download mode it tells me:
Code:
[B][COLOR="Red"]ODIN MODE[/COLOR]
[COLOR="Black"]PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0[/COLOR]
[COLOR="DimGray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
[/B]
To my understanding I find it weird that it says my Current Binary and my System Status say 'Custom' but my KNOX is still 0x0.
Now, of course before I tried to flash TWRP it said I my Current Binary and my System Status said 'Official'.
What I Think Is The Problem
Correct me if I'm wrong but I think the problem is that UDC START part in the download mode.
I've read online that some people get that when their phone is in a bootloop but I have no problem with my phone.
Conclusion
In conclusion I think that the problem may be resolved by factory restoring my phone, but if you have any other ideas, please reply to this thread.
Thanks.

None of those steps would root your phone though
TWRP is a custom recovery, once you've flashed that, you need to boot into TWRP, and flash SuperSU 2.xx beta (xx = whichever is the latest version)
Then you can reboot into Android and should be rooted

*Detection* said:
None of those steps would root your phone though
TWRP is a custom recovery, once you've flashed that, you need to boot into TWRP, and flash SuperSU 2.xx beta (xx = whichever is the latest version)
Then you can reboot into Android and should be rooted
Click to expand...
Click to collapse
The problem is that it won't let me flash TWRP. I have SuperSU on my device ready to be flashed but I need to get TWRP working.

Ah I see, and you are booting straight into recovery after replacing the battery?
1. Disable auto reboot & Flash TWRP
2. Disconnect USB & Pull battery to power off once flash is complete
3. Replace battery and boot immediately into TWRP
TWRP 3.0.2.0 Klte is the version I use

*Detection* said:
Ah I see, and you are booting straight into recovery after replacing the battery?
1. Disable auto reboot & Flash TWRP
2. Disconnect USB & Pull battery to power off once flash is complete
3. Replace battery and boot immediately into TWRP
TWRP 3.0.2.0 Klte is the version I use
Click to expand...
Click to collapse
Yes I booted once into recovery straight after flashing and it never worked.
Now I have to use ADB because it's a bit finicky and it wont always boot into recovery by doing Volume Up + Power.
I'll try using 3.0.2.0 and see what happens.
Edit: I just tried with Odin 3.09 & TWRP klte 3.0.2.0, still no luck. Also couldn't boot into recovery with buttons, had to use Volume Up + Power.

-removed

Can't flash TWRP via Odin SM G900F

Can't flash TWRP on my S5 SM G900F.
-Auto Reboot is unchecked on Odin.
-I've used Odin 3.07/3.09/3.10.
-Reactivation Lock is OFF
-USB debugging is checked.
-I've tried with TWRP (TAR obviously) 3.1 and 3.0.
Am I missing something?

robertofelce said:
Can't flash TWRP on my S5 SM G900F.
-Auto Reboot is unchecked on Odin.
-I've used Odin 3.07/3.09/3.10.
-Reactivation Lock is OFF
-USB debugging is checked.
-I've tried with TWRP (TAR obviously) 3.1 and 3.0.
Am I missing something?
Click to expand...
Click to collapse
silly question have u installed drivers on pc first if not reboot to download mode and let it install drivers i never had to touch any of the settings for it to work if that dont work then try Odin3 v3.11.1

ireaper4592 said:
silly question have u installed drivers on pc first if not reboot to download mode and let it install drivers i never had to touch any of the settings for it to work if that dont work then try Odin3 v3.11.1
Click to expand...
Click to collapse
Drivers are installed. I flashed a recovery on a Galaxy S3 not so long ago and everything went fine. That's the reason I posted this thread. I do not know what else to do.
On download mode there are some things like "Download mode secure" "CBS Enabled". It has something to do?

I also have the same problem.. followed every possible guide and no matter if I successfully flash with odin, heimdall or from twrp flash app as root.. when booting my S5 immediately into recovery with volup+home+pwr it will always show the old recovery and not twrp!! Is it readonly and just acting to be flashed or what?? Some carrier might have locked the recovery preventing flashing? It's a SM-G901F klte from swissmobile...
thnks for any answer/suggestion.

Your bootloader is unlocked right?

what do you mean with unlocked?
is there a way to verify it?
and most importantly to unlock it?

Just Uncheck Auto Reboot on Odin

No autoreboot of course i unchecked and do manuale Direct boot to recovery
Anyone knows how to check if the recovery partition is protected

i have the same problem please anyone can help?

I solved it by using a short usb cable, no usb3 ports, only usb2, maybe you try different ones on your laptop/pc, also avoid any hub in between. It's incredibly picky!