1. angelisawesome's Avatar
    Please help I've been trying for the last hour to root my phone I have all the necessary files and odin. When I try to install the custom recovery using odin it says pass but when I try to reboot into recovery it's the stock android recovery so I can't install superuser... please help I really want to install custom rom. I've rooted my phone before so I don't know what the problem is.

    Posted via the Android Central App
    05-03-2015 06:06 PM
  2. Rukbat's Avatar
    What carrier? If it's Verizon or AT&T, the bootloader is locked, so you can't install a custom recovery.

    Installing a custom ROM doesn't need a custom recovery, and it doesn't need rooting, rooting doesn't need a custom recovery and a custom recovery doesn't need rooting - the 3 are separate issues. (The ROM and the recovery aren't even in the same partition - except for specialized apps, you can't even see one from the other. [For example, custom recoveries can "see" the system and userdata partitions, and partitioning apps can see all partitions from the ROM partition.]) Some ROMs are distributed as specific custom recovery backups, but a ROM supplied as a zip file, an all-in-one Odin files or separate Odin files (APxxx, BLxxx, CPxxx) don't need anything but Odin, the driver installed in the computer and the Odin files.
    05-03-2015 07:23 PM
  3. angelisawesome's Avatar
    I have a Galaxy s5 Tmobile running lolipop, and either way it doesn't let me root or install recovery. On odin when I install the custom recovery it says PASS 1 successful but when I reboot into recovery it's the stock one. I've tried it with two different recoveries Phils and Twrp.

    Posted via the Android Central App
    05-03-2015 09:02 PM
  4. angelisawesome's Avatar
    Do you think maybe it's the version of odin I have?

    Posted via the Android Central App
    05-03-2015 09:02 PM
  5. Host Dolphins's Avatar
    I have the same problem, I used ODIM 4.0.7 and have galaxy s5 g900p (sprint version).

    I used the guide and downloads found at this thread: androidcentral.us/2014/04/how-to-root-sprint-samsung-galaxy-s5-sm-g900p/
    I'm supposing you did too.

    I would say users should not use that guide in the future.

    I'm now downloading the original rom and going to try and reflash the original rom using odin. It will wipe my system but luckily this is a new device with nothing on it.
    05-08-2015 03:00 AM
  6. Host Dolphins's Avatar
    ok I solved it.

    I have a g900p sprint s5. This worked for me when i got stuck at the screen:
    RECOVERY BOOTING....
    RECOVERY IS NOT SEANDROID ENFORCING
    Set Warranty Bit: recovery
    step 1:
    download philz cwm for your device
    galaxys5root [DOT] com/cwmtwrp-recovery/

    step 2:
    go into recovery mode by:
    1) unplug from pc
    2) take out battery
    3) reinsert battery
    4) hold POWER + HOME + VOLUME DOWN

    step 3:
    now in recovery, open odin 3.09, by left-click and choose RUN AS ADMINISTRATOR
    (google for it if you don't have it, I lost the link where I downloaded it)

    step 4:
    plug in your S5

    step 5:
    in odin 3.09, PDA is same as AP button.
    1) click AP and open the .tar for philz cwm
    i.e.
    Code:
    philz_touch_6.26.2-klte.tar.md5
    2) UNCHECK "Auto Reboot"
    thanks for this step goes to Hash_Slingin_Slasha from reddit:
    When you use method one on this page to root, make sure to follow the instructions up until you hit start to begin the root. For many models, when the restart, the phone will overwrite any progress you just made towards your root, and you will have to try again. So before you click start, look to the left and uncheck the automatic restart. When your phone is done and it says you succeeded, manually shut it down, press up, home, and power to get into the cwm boot manager, and follow the rest of the instructions. It worked for me and in total, once I figured out what to do, it took less than two minutes. Happy rooting!
    source: reddit [DOT] com/r/galaxys5/comments/2qhbgu/psa_a_tip_for_those_about_to_root/
    3) Press Start button in Odin
    4) WAIT for it to TOTALLY FINISH (it will say RESET then a few minutes later a big gree PASS. WAIT for it to say PASS!!)

    step 6:
    now that it says PASS, go ahead and
    1) unplug from your pc
    2) take out battery
    3) reinsert battery
    4) hold POWER + HOME + VOLUME UP
    5) wait a second once you see the previous what looks like boot loop
    after a couple seconds it will go into the purple PHILZ CWM screen

    step 7:
    in PHILZ CWM,
    1) scroll down using volume buttons to reboot device (it says reboot device or restart device, i forget, just choose that)
    2) it asks, "root isn't installed, want to install?" or something like that, i forget the exact wording.
    3) choose YES
    4) wait and it will reboot into your phone.

    success!

    p.s. just a note, after doing all this, it did get me back into my phone but my phone is not rooted (just checked with root checker).
    Yordan Yordanov1 likes this.
    05-08-2015 03:56 AM
  7. atpayero's Avatar
    thaks, this works perfect.

    when I pass the OS with out restar and then press CTRL+HOME+POWER and restar the phone when the OS restar was ok.
    09-14-2015 09:24 PM
  8. CVAngelo's Avatar
    p.s. just a note, after doing all this, it did get me back into my phone but my phone is not rooted (just checked with root checker).
    Obviously it won't be rooted...because at that point, you would simply have needed to complete the rooting process started by PhilZ recovery by installing SuperSu from the PlayStore.
    01-20-2016 11:54 AM
  9. Nike Cain's Avatar
    Ok so I've been having the issue where you are attempting to enter a custom recovery, but you keep getting the "recovery is not seandroid enforcing" in the top left corner and the phone just crashes.

    The reason for this is because you've probably been following an old guide/tutorial on youtube that was flashing the custom recovery from Android 5.0.

    In order to succesfully flash the custom recovery, you will need to begin by upgrading your phone to Android 6.0.1 and then flash the custom recovery from there otherwise it won't load for some reason.

    The easiest way to do this is to flash back to the stock rom using ODIN which you can find here: Firmware archive | Samsung Updates

    On your device, head over to settings, about device and it should read Andriod 5.0.

    DON'T attempt to root your device, as we'll need to update to Android 6.0.1.

    Samsung will let you do this with an unrooted device by going to about device and clicking Software Updates.

    The update is around 900MB and will take around 15 minutes to download and another 5 - 10 minutes to install.

    If you HAVE rooted your device, you will be presented with a message saying that you have an "unatuhroised operating system" or something along those lines... And will have to update through Samsung Kies which will take you a lot loner (just trust me!)

    Once it's flashed, check back in the about this device and it should read Android 6.0.1

    From here just flash the correct Cf-Auto for Samsung Galaxy S5 6.0.1 from this link with ODIN:

    https://download.chainfire.eu/397/CF...xx-smg900f.zip

    Leave everyhting ticked in ODIN - shoudln't matter what version of ODIN you used or whether or not it's in administrator.

    Once this has been done, boot your device and make sure you have SuperSU and are rooted.

    From here, you'll be able to flash the custom recovery succesfully without getting the seandroid error.

    I've used twrp 3.0.2.2 which you can get from this link:

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

    Download the img.tar and flash with ODIN.

    Once flashed, you just have to boot into Recovery Mode by pressing Volume UP + HOME + Power

    Hold all three buttons and at this point you may still get the seandroid text in the top left corner and the phone may keep vibrating twice and rebooting itself.

    If this happens don't worry, just hold all three buttons whilst the phone reboots and when you see the seandroid message appear in the top left, LET GO of the power button only.

    Whilst still holding the Volume UP + HOME buttons you should then be booted into your chosen custom recovery and can drag and drop CM + G Apps from your pc

    Hope this helps some people out there :]
    07-27-2016 04:43 PM
  10. ironass's Avatar
    Ok so I've been having the issue where you are attempting to enter a custom recovery, but you keep getting the "recovery is not seandroid enforcing" in the top left corner and the phone just crashes.

    The reason for this is because you've probably been following an old guide/tutorial on youtube that was flashing the custom recovery from Android 5.0.

    In order to succesfully flash the custom recovery, you will need to begin by upgrading your phone to Android 6.0.1 and then flash the custom recovery from there otherwise it won't load for some reason.

    The easiest way to do this is to flash back to the stock rom using ODIN which you can find here: Firmware archive | Samsung Updates

    On your device, head over to settings, about device and it should read Andriod 5.0.

    DON'T attempt to root your device, as we'll need to update to Android 6.0.1.

    Samsung will let you do this with an unrooted device by going to about device and clicking Software Updates.

    The update is around 900MB and will take around 15 minutes to download and another 5 - 10 minutes to install.

    If you HAVE rooted your device, you will be presented with a message saying that you have an "unatuhroised operating system" or something along those lines... And will have to update through Samsung Kies which will take you a lot loner (just trust me!)

    Once it's flashed, check back in the about this device and it should read Android 6.0.1

    From here just flash the correct Cf-Auto for Samsung Galaxy S5 6.0.1 from this link with ODIN:

    https://download.chainfire.eu/397/CF...xx-smg900f.zip

    Leave everyhting ticked in ODIN - shoudln't matter what version of ODIN you used or whether or not it's in administrator.

    Once this has been done, boot your device and make sure you have SuperSU and are rooted.

    From here, you'll be able to flash the custom recovery succesfully without getting the seandroid error.

    I've used twrp 3.0.2.2 which you can get from this link:

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

    Download the img.tar and flash with ODIN.

    Once flashed, you just have to boot into Recovery Mode by pressing Volume UP + HOME + Power

    Hold all three buttons and at this point you may still get the seandroid text in the top left corner and the phone may keep vibrating twice and rebooting itself.

    If this happens don't worry, just hold all three buttons whilst the phone reboots and when you see the seandroid message appear in the top left, LET GO of the power button only.

    Whilst still holding the Volume UP + HOME buttons you should then be booted into your chosen custom recovery and can drag and drop CM + G Apps from your pc

    Hope this helps some people out there :]
    WARNING!

    The above instructions are only for 1 of the 42 different models of Galaxy S5 and that is the international model, G900F, and no other version.
    07-29-2016 11:29 AM
  11. Yordan Yordanov1's Avatar
    ok I solved it.

    I have a g900p sprint s5. This worked for me when i got stuck at the screen:


    step 1:
    download philz cwm for your device
    galaxys5root [DOT] com/cwmtwrp-recovery/

    step 2:
    go into recovery mode by:
    1) unplug from pc
    2) take out battery
    3) reinsert battery
    4) hold POWER + HOME + VOLUME DOWN

    step 3:
    now in recovery, open odin 3.09, by left-click and choose RUN AS ADMINISTRATOR
    (google for it if you don't have it, I lost the link where I downloaded it)

    step 4:
    plug in your S5

    step 5:
    in odin 3.09, PDA is same as AP button.
    1) click AP and open the .tar for philz cwm
    i.e.
    Code:
    philz_touch_6.26.2-klte.tar.md5
    2) UNCHECK "Auto Reboot"
    thanks for this step goes to Hash_Slingin_Slasha from reddit:

    source: reddit [DOT] com/r/galaxys5/comments/2qhbgu/psa_a_tip_for_those_about_to_root/
    3) Press Start button in Odin
    4) WAIT for it to TOTALLY FINISH (it will say RESET then a few minutes later a big gree PASS. WAIT for it to say PASS!!)

    step 6:
    now that it says PASS, go ahead and
    1) unplug from your pc
    2) take out battery
    3) reinsert battery
    4) hold POWER + HOME + VOLUME UP
    5) wait a second once you see the previous what looks like boot loop
    after a couple seconds it will go into the purple PHILZ CWM screen

    step 7:
    in PHILZ CWM,
    1) scroll down using volume buttons to reboot device (it says reboot device or restart device, i forget, just choose that)
    2) it asks, "root isn't installed, want to install?" or something like that, i forget the exact wording.
    3) choose YES
    4) wait and it will reboot into your phone.

    success!

    p.s. just a note, after doing all this, it did get me back into my phone but my phone is not rooted (just checked with root checker).
    Thank you! This worked for my Samsung Galaxy J7 2017.

    At first, Odin gave me "FAIL!", for which the fix was going to developer options into the phone, and enabling "OEM Unlock".

    Then, I used Odin and only "RESET!" appeared, then my phone rebooted like usually, but if you leave it plugged to your PC with the USB cable, after 2/3 minutes, it will give you a "PASS!"

    I will leave a few file names below so people can find the solution if they encounter the same problem.

    Galaxy J7 2017, Odin3 v3.12.4_4.exe, lineage-15.1-20181121-UNOFFICIAL-j7y17lte.zip, twrp-3.2.3-0-j7elte.img.tar, twrp, fail, reset, pass, RQT_CLOSE !!, RES OK !!, Removed!!
    11-27-2018 11:13 AM
  12. craighaggart's Avatar
    I know this is an old thread, but I just bought an SM-G900T, tried to use CF root, and now I have the same problem: Trying to boot the phone gives me an message in the upper left that says
    (blue text) RECOVERY BOOTING ....
    (red text) RECOVERY IS NOT SEANDROID ENFORCING
    (yellow text) Set Warranty Bit : recovery

    I can no longer get beyond this screen no matter what I do. I tried redoing CF root (Odin gives me the green PASS each time) but nothing helps.

    I just got this phone a few hours ago so I'm not sure what version of Android kernal it has, and cannot check because I can't boot the phone. I believe it's KitKat 4.4.2. The CF file is CF-Auto-Root-kltetmo-kltetmo-smg900t.tar.md5

    Before starting I did obtain developer status by tapping the build number, but didn't write down what it was. Oh, I'm using a Windows 7 laptop, and it's recognizing the phone just fine.

    Any help? Have I bricked my new old phone after only an hour?!

    -Craig
    01-25-2019 01:08 AM
  13. craighaggart's Avatar
    Whew! Phone is working now! The fix: I reflashed a stock 4.4.2 image downloaded from androidfilehost.com. I had no idea which of the 8 versions of 4.4.2 to use, so I went with the latest date and that worked.

    So now I'm wondering if I can (and should) flash a newer Android before trying again to root with chainfire. The same site has 5.0, 5.1.1, and 6.01. There is a note saying that using anything newer than 5.0 removes the ability to revert to anything older. I really don't care much what version is on this older (but new to me) phone, I just want to be able to root it.

    It likely doesn't matter now, but since the phone now boots again I can see the relevant info:
    Baseband version is what I flashed: G900TUVU1CNK2
    Kernel version: 3.4.0-2621998 (Nov. 10 2014)
    Build number: KOT49H.G900TUVU1CNK2
    SE for Android status: Enforcing SEF_SM-G900T_4.4.2_0026
    Security software version: MDF v1.0 Release 3, VN v1.4 Release 1

    Suggestions? Is there a better starting point for trying CF autoroot again, or should I flash a new Android image? If new, is the newest one possible (6.0.1) the best way to go?

    Thanks for any help!

    -Craig
    01-25-2019 02:48 AM
  14. craighaggart's Avatar
    It's a moot point now about whether or not to upgrade from Android 4.2.2. It wasn't 15 minutes after I posted my question that the phone upgraded itself to 5.1.1! So lolipop it is, unless there's a compelling reason to use Odin to try to flash Marshmallow 6.0.1 before trying again to root with CF.

    I'd still love to hear from anyone who has rooted this particular phone with chainfire autoroot...

    -Craig
    01-25-2019 03:59 AM

Similar Threads

  1. Replies: 4
    Last Post: 09-22-2015, 11:07 AM
  2. Why isn't my easy clip/ screen shot working?
    By AC Question in forum Samsung Galaxy Note 3
    Replies: 0
    Last Post: 05-03-2015, 03:54 PM
  3. Replies: 0
    Last Post: 05-03-2015, 03:31 PM
  4. Why has my mhl to hdmi stopped working since an upgrade to 4.4.2?
    By AC Question in forum Samsung Galaxy Tab 3
    Replies: 0
    Last Post: 05-03-2015, 12:26 PM
  5. Replies: 1
    Last Post: 05-03-2015, 12:03 PM
LINK TO POST COPIED TO CLIPBOARD