Database Users

What's "secure download=enabled" in download mode

Hi, I recently flashed lollipop to my galaxy s4 and I want to root it but when I go in download mode, there is a new text in blue saying "secure download=enabled"
Can I still root my phone using Odin and CF auto root with this enabled ? And if not how can I disable it ?

k0spwn said:
Hi, I recently flashed lollipop to my galaxy s4 and I want to root it but when I go in download mode, there is a new text in blue saying "secure download=enabled"
Can I still root my phone using Odin and CF auto root with this enabled ? And if not how can I disable it ?
Click to expand...
Click to collapse
I am not sure but as far as i know you should unlock your bootloader. But like i said i am not sure,if you do more research about this it will be good for you. Sorry for bad English :good:

k0spwn said:
Hi, I recently flashed lollipop to my galaxy s4 and I want to root it but when I go in download mode, there is a new text in blue saying "secure download=enabled"
Can I still root my phone using Odin and CF auto root with this enabled ? And if not how can I disable it ?
Click to expand...
Click to collapse
Ignore the message. Everyone has it.

EmreAskin said:
I am not sure but as far as i know you should unlock your bootloader. But like i said i am not sure,if you do more research about this it will be good for you. Sorry for bad English :good:
Click to expand...
Click to collapse
No need to unlock the bootloader. Secure download was introduced on the Lollipop release and it doesn't act anything on your bootloader, even if you flash insecured file (.tar without .md5) via ODIN.

ive been through thousands of pages of forums and so far this is best answer to this question lol so this secure download enabled will not stop u from flashing causing odin to fail write and if so what will stop it from flashing stock or any rom ?

secure download enabled have one purpose... you CAN'T download (flash) old or low baseband (firmware) to your device... so you can't flash anything old than the one you already have installed.. well not by odin itself.. but you still can flash recoverys if your device support it, and flash any custom rom also..
edit: this not applied to old s5, s4, etc devices.. but s6 and new 2016 devices because the hardware checks

Serge Winters said:
secure download enabled have one purpose... you CAN'T download (flash) old or low baseband (firmware) to your device... so you can't flash anything old than the one you already have installed.. well not by odin itself.. but you still can flash recoverys if your device support it, and flash any custom rom also..
edit: this not applied to old s5, s4, etc devices.. but s6 and new 2016 devices because the hardware checks
Click to expand...
Click to collapse
You can!! I have same problem! on S7 herolte phone screen i have blue " Secure Download : Enable " and " RP SWREV: B:6 K:4 S:5 . And heimdall give "permission denied" message when i try load TWRP. With Patched Odin it write TWRP it to phone without problem. Than TWRP whipe all do sideload by heimdall and instal new system Thanks! picture https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29

pawelnrg said:
You can!! I have same problem! on S7 herolte phone screen i have blue " Secure Download : Enable " and " RP SWREV: B:6 K:4 S:5 . And heimdall give "permission denied" message when i try load TWRP. With Patched Odin it write TWRP it to phone without problem. Than TWRP whipe all do sideload by heimdall and instal new system Thanks! picture https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29
Click to expand...
Click to collapse
I was walking about Binarys (bits) you cant flash old binarys.. but you can flash recoverys or same bits even if they are from different OS versions but the bit itself is the same number.

Please Help Very Frustrated.

hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:

dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that

Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens

Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann

vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?

dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk

dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom

Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.

I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue

SM-G900S bootloop after trying to root

Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet

Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.

toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet

need masive help rooting the g900f plz

hi i have a g900f (s5) i have been rooting phones for years using odin but for some reason every time i try i get recovery is not seandroid enforcing i have tried older version of odin 1.85 ect but nothing seems to work please can somone help me i really want to put a custom rom on this phone
im using the CF root for the g900f too (CF-Auto-Root-klte-kltexx-smg900f.tar)
only way i can get it back on is to flash philz_touch_6.26.6-klte.tar
i have also downgraded the phone to kitkat 4.4.2 thinking that i could use towelroot after but it failed

Follow the below steps
1) Flash TWRP
2) Download SuperSU zip file
3) Boot to TWRP recovery
4) Flash SuperSU zip
you are rooted
stuartdb said:
hi i have a g900f (s5) i have been rooting phones for years using odin but for some reason every time i try i get recovery is not seandroid enforcing i have tried older version of odin 1.85 ect but nothing seems to work please can somone help me i really want to put a custom rom on this phone
im using the CF root for the g900f too (CF-Auto-Root-klte-kltexx-smg900f.tar)
only way i can get it back on is to flash philz_touch_6.26.6-klte.tar
i have also downgraded the phone to kitkat 4.4.2 thinking that i could use towelroot after but it failed
Click to expand...
Click to collapse

androidtweaker1 said:
Follow the below steps
1) Flash TWRP
2) Download SuperSU zip file
3) Boot to TWRP recovery
4) Flash SuperSU zip
you are rooted
Click to expand...
Click to collapse
i flashed CF-Auto-Root-klte-kltexx-smg900f.tar again took battery out booted into download mode again and flashed TWRP after and it work im a happy man thank for your help

Great :good::highfive:
stuartdb said:
i flashed CF-Auto-Root-klte-kltexx-smg900f.tar again took battery out booted into download mode again and flashed TWRP after and it work im a happy man thank for your help
Click to expand...
Click to collapse

Chainfire auto root FAILED Samsung Galaxy J3 SM-J320R4

Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:

LeviathaninWaves said:
Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
Click to expand...
Click to collapse
Yes please help

not sure what I did differently, but I seem to have root now by using Chainfires AutoRoot for my Samsung Galaxy J3 SM-J320R4. SuperSu is installed and working

LeviathaninWaves said:
Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
Click to expand...
Click to collapse
It took forever to reboot. apparently the kernel was trying to hang. Ive still to get TWRP recovery to load, but we were given a big hint. I am crunching files right now, but my phone says it"s rooted, and I'll check more later.
---------- Post added at 01:53 AM ---------- Previous post was at 01:49 AM ----------
Phone is working