im trying to install root but it fails, writes in download mode "SECURE CHECK FAIL: RECOVERY".
have N9005 with 4.4.2 XXUENB3.
Gabi014 said:
im trying to install root but it fails, writes in download mode "SECURE CHECK FAIL: RECOVERY".
have N9005 with 4.4.2 XXUENB3.
Click to expand...
Click to collapse
I rooted my n9005 using cf root yesterday and it worked. Which method are you using?
Sent from Galaxy Note 3 SM-9005
thahim said:
I rooted my n9005 using cf root yesterday and it worked. Which method are you using?
Sent from Galaxy Note 3 SM-9005
Click to expand...
Click to collapse
Cf root i guess?
Gabi014 said:
Cf root i guess?
Click to expand...
Click to collapse
You must not be doing it the way it should or may be you have not downloaded the correct cf root for your rom.
Sent from Galaxy Note 3 SM-9005
thahim said:
You must not be doing it the way it should or may be you have not downloaded the correct cf root for your rom.
Sent from Galaxy Note 3 SM-9005
Click to expand...
Click to collapse
i also tried to install recovery instead of the stock recovery but the same fail. doesnt matter what i install, it dont install recovery. dunno why.
Gabi014 said:
i also tried to install recovery instead of the stock recovery but the same fail. doesnt matter what i install, it dont install recovery. dunno why.
Click to expand...
Click to collapse
I dont know whats recovery I just flashed cf root.
Sent from Galaxy Note 3 SM-9005
someone help please.
Gabi014 said:
im trying to install root but it fails, writes in download mode "SECURE CHECK FAIL: RECOVERY".
have N9005 with 4.4.2 XXUENB3.
Click to expand...
Click to collapse
Gabi014 said:
someone help please.
Click to expand...
Click to collapse
1. asked before, just to reconfirm : which CF-Autoroot version you are using ? the 4.4.2 right ?
3. did you follow the instructions on how to flash through ODIN ?
2. have you uncheck the Reactivation Lock inside security setting ?
Normally if following his step with a correct files, u should be fine.
antique_sonic said:
1. asked before, just to reconfirm : which CF-Autoroot version you are using ? the 4.4.2 right ?
3. did you follow the instructions on how to flash through ODIN ?
2. have you uncheck the Reactivation Lock inside security setting ?
Normally if following his step with a correct files, u should be fine.
Click to expand...
Click to collapse
1. 4.4.2
2. positive
3. in the download mode it says "REACTIVATION LOCK(KK): ON "
Gabi014 said:
1. 4.4.2
2. positive
3. in the download mode it says "REACTIVATION LOCK(KK): ON "
Click to expand...
Click to collapse
3) is your problem. Setting>General>Security
Gabi014 said:
1. 4.4.2
2. positive
3. in the download mode it says "REACTIVATION LOCK(KK): ON "
Click to expand...
Click to collapse
I knew it.
To flash root, recovery, and custom rom, reactivation lock must be OFF.
Sent from N9005 NC2 ROM.
Rosli59564 said:
3) is your problem. Setting>General>Security
Click to expand...
Click to collapse
antique_sonic said:
I knew it.
To flash root, recovery, and custom rom, reactivation lock must be OFF.
Sent from N9005 NC2 ROM.
Click to expand...
Click to collapse
Thank you very much guys!!
antique_sonic said:
I knew it.
To flash root, recovery, and custom rom, reactivation lock must be OFF.
Sent from N9005 NC2 ROM.
Click to expand...
Click to collapse
In security settings i do not see this reactivation lock anywheres
NasTraDooMis said:
In security settings i do not see this reactivation lock anywheres
Click to expand...
Click to collapse
Try to go into download mode. See down there whether ur reactivation lock is on or off.
If on, don't do anything like rooting or custom recovery or custom rom.
Try to look for reactivation lock option first to off it.
Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.9.3 OC
antique_sonic said:
Try to go into download mode. See down there whether ur reactivation lock is on or off.
If on, don't do anything like rooting or custom recovery or custom rom.
Try to look for reactivation lock option first to off it.
Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.9.3 OC
Click to expand...
Click to collapse
Binary and status are "official"
knox void 0x1
qualcomm secure boot: enable(csb)
reactivation lock ?
NasTraDooMis said:
Binary and status are "official"
knox void 0x1
qualcomm secure boot: enable(csb)
reactivation lock ?
Click to expand...
Click to collapse
by the way, what is your device ? and which firmware you are running ?
antique_sonic said:
by the way, what is your device ? and which firmware you are running ?
Click to expand...
Click to collapse
Its 4.4.2 kitkat , n900pvpucnab . Evidently i think some firmwares versions do not have the reactivation lock. Im just getting ready to try to root again, i am confused about witch cf auto root to try and use. Cf has updated files now:
https://plus.google.com/+Chainfire/posts/NuBxE9dEeXv
the last time i tried was with the CF-Auto-Root-hltespr-hltespr-smn900p tar, but someone said to use the smn9005 tar. :
http://forum.xda-developers.com/showpost.php?p=51446272&postcount=1392
What to do ?
* Also i am worried about this note :
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
NasTraDooMis said:
Its 4.4.2 kitkat , n900pvpucnab . Evidently i think some firmwares versions do not have the reactivation lock. Im just getting ready to try to root again, i am confused about witch cf auto root to try and use. Cf has updated files now:
https://plus.google.com/+Chainfire/posts/NuBxE9dEeXv
the last time i tried was with the CF-Auto-Root-hltespr-hltespr-smn900p tar, but someone said to use the smn9005 tar. :
http://forum.xda-developers.com/showpost.php?p=51446272&postcount=1392
What to do ?
* Also i am worried about this note :
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Click to expand...
Click to collapse
Just use ur sprint file. Don't use n9005.
If urs is the locked version, u might want to unlock first.
Sent from N9005 NC2 ROM.
antique_sonic said:
Just use ur sprint file. Don't use n9005.
If urs is the locked version, u might want to unlock first.
Sent from N9005 NC2 ROM.
Click to expand...
Click to collapse
Not sure if its locked version. How to unlock ?
I downloaded the updated cf root, both the 9005 and 900, retried root thru oden with the new 900 and it failed,got message in red "unsupport dev type", the blue bar was stuck at the halfway mark. Did batt pull and on reboot triangle : reboot firmware upgrade encountered an issue,select recovery mode in keis and try again". keiv could not find device and said "connected device not supported".tried to do emergency recovery but i have no code to use and it no show my device anyway. I went back into download mode and connected with oden and flashed the 9005 tar, and that got me phone back up. Refollowed those other instructions: http://forum.xda-developers.com/showpost.php?p=51446272&postcount=1392&nocache=1&z=288570789389558,
and i just got to the factory wipe and reflash in oden. its auto updating apps right now, im waiting now to install root checker and see if indeed i may have root.
**** Right on, yeahhhh i have root !!!
NasTraDooMis said:
Not sure if its locked version. How to unlock ?
I downloaded the updated cf root, both the 9005 and 900, retried root thru oden with the new 900 and it failed,got message in red "unsupport dev type", the blue bar was stuck at the halfway mark. Did batt pull and on reboot triangle : reboot firmware upgrade encountered an issue,select recovery mode in keis and try again". keiv could not find device and said "connected device not supported".tried to do emergency recovery but i have no code to use and it no show my device anyway. I went back into download mode and connected with oden and flashed the 9005 tar, and that got me phone back up. Refollowed those other instructions: http://forum.xda-developers.com/showpost.php?p=51446272&postcount=1392&nocache=1&z=288570789389558,
and i just got to the factory wipe and reflash in oden. its auto updating apps right now, im waiting now to install root checker and see if indeed i may have root.
**** Right on, yeahhhh i have root !!!
Click to expand...
Click to collapse
Welcome m8.
Glad u make it
Sent from N7105, DN3 with AGNi kernel.
Related
So I just used Odin3 v 1.85 and CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 to try and root my device but its stuck at the booting screen with " RECOVERY BOOTING... RECOVERY IS NOT SEANDROID ENFORCING Set Warranty BIt : Recovert"
I'm using an Australian, Telstra, SM-N9005. How do I get it to work again
143bubblepop said:
So I just used Odin3 v 1.85 and CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 to try and root my device but its stuck at the booting screen with " RECOVERY BOOTING... RECOVERY IS NOT SEANDROID ENFORCING Set Warranty BIt : Recovert"
I'm using an Australian, Telstra, SM-N9005. How do I get it to work again
Click to expand...
Click to collapse
Try flashing cwm by chenglu or philz. Both will give you root access as well. Either way you seem don't mind flagging knox to 0x1. Is your phone international n9005 and network unlocked?
I'm new to the rooting world
Rosli59564 said:
Try flashing cwm by chenglu or philz. Both will give you root access as well. Either way you seem don't mind flagging knox to 0x1. Is your phone international n9005 and network unlocked?
Click to expand...
Click to collapse
Yeah so I don't mind tripping knox, but I'm not sure how to do either of types steps.
Also, my device it's an international unlocked phone
143bubblepop said:
Yeah so I don't mind tripping knox, but I'm not sure how to do either of types steps.
Also, my device it's an international unlocked phone
Click to expand...
Click to collapse
Just the same as you did using cf auto root but you'll need this instead.
http://forum.xda-developers.com/showthread.php?t=2454079
Choose the one either jb or kk.
Did you turn off reactivation lock before trying to root?
Afraid that's the one causing your phone to hangup at the screen. Remove battery and turn on your phone if it can boot normally in OS
Rosli59564 said:
Just the same as you did using cf auto root but you'll need this instead.
http://forum.xda-developers.com/showthread.php?t=2454079
Choose the one either jb or kk.
Did you turn off reactivation lock before trying to root?
Afraid that's the one causing your phone to hangup at the screen. Remove battery and turn on your phone if it can boot normally in OS
Click to expand...
Click to collapse
Ok, so my reactivation lock is off. I re-downloaded the CF-Auto-Root and I got my phone to work.
Now, with the CWM Based recovery, do I place into the PDA slot in Odin? Or is it not necessary anymore?
On root checker, it hangs and doesn't give me a definite answer
So I'm pretty sure my phone isn't rooted, but for now, its working fine.
143bubblepop said:
Ok, so my reactivation lock is off. I re-downloaded the CF-Auto-Root and I got my phone to work.
Now, with the CWM Based recovery, do I place into the PDA slot in Odin? Or is it not necessary anymore?
On root checker, it hangs and doesn't give me a definite answer
So I'm pretty sure my phone isn't rooted, but for now, its working fine.
Click to expand...
Click to collapse
So you flash again cf auto root successfully?. If yes your phone should be rooted now so you dont need cwm anymore except you want to flash custom rom or mods.
Can't remember when i flash cf last time whether there is superSU in the app drawer or not. Can you see it in the phone?. Try install superSU from Playstore and update binary and rerun root checker.
Still if you want to flash cwm just put it in pda
Rosli59564 said:
Just the same as you did using cf auto root but you'll need this instead.
http://forum.xda-developers.com/showthread.php?t=2454079
Choose the one either jb or kk.
Did you turn off reactivation lock before trying to root?
Afraid that's the one causing your phone to hangup at the screen. Remove battery and turn on your phone if it can boot normally in OS
Click to expand...
Click to collapse
Rosli59564 said:
So you flash again cf auto root successfully?. If yes your phone should be rooted now so you dont need cwm anymore except you want to flash custom rom or mods.
Can't remember when i flash cf last time whether there is superSU in the app drawer or not. Can you see it in the phone?. Try install superSU from Playstore and update binary and rerun root checker.
Still if you want to flash cwm just put it in pda
Click to expand...
Click to collapse
I installed SuperSu and restarted my phone and that, opened up root checker and BAM, I'm rooted.
If I were to install CWM, would I need to rewrite my binary for SuperSU
143bubblepop said:
Ok, so my reactivation lock is off. I re-downloaded the CF-Auto-Root and I got my phone to work.
Now, with the CWM Based recovery, do I place into the PDA slot in Odin? Or is it not necessary anymore?
On root checker, it hangs and doesn't give me a definite answer
So I'm pretty sure my phone isn't rooted, but for now, its working fine.
Click to expand...
Click to collapse
Yes in PDA slot in ODIN...
143bubblepop said:
I installed SuperSu and restarted my phone and that, opened up root checker and BAM, I'm rooted.
If I were to install CWM, would I need to rewrite my binary for SuperSU
Click to expand...
Click to collapse
I don't think you'll need to
Rosli59564 said:
I don't think you'll need to
Click to expand...
Click to collapse
i started flashing CWM and its been stuck on the downloading, set warranty bit: cache page for a while now. Would it normally take a while or does it depends on the computer?
143bubblepop said:
i started flashing CWM and its been stuck on the downloading, set warranty bit: cache page for a while now. Would it normally take a while or does it depends on the computer?
Click to expand...
Click to collapse
It shouldn't. Which cwm version you used?
Rosli59564 said:
It shouldn't. Which cwm version you used?
Click to expand...
Click to collapse
http://d-h.st/users/xiaolu/?fld_id=31963
That one,
So what do I do now?
143bubblepop said:
http://d-h.st/users/xiaolu/?fld_id=31963
That one,
So what do I do now?
Click to expand...
Click to collapse
Just to be sure n9005 for kk?. Redownload and reflash. If still hangup at the screen try boot up normally. Perhaps can try with terminal emulator to flash cwm
Rosli59564 said:
Just to be sure n9005 for kk?. Redownload and reflash. If still hangup at the screen try boot up normally. Perhaps can try with terminal emulator to flash cwm
Click to expand...
Click to collapse
Do i stop the flashing right now and unplug?
Now that i think of it, my device isnt even KK
143bubblepop said:
Do i stop the flashing right now and unplug?
Now that i think of it, my device isnt even KK
Click to expand...
Click to collapse
As i guess. You phone is 4.3 right? Download for 4.3 i think 6.0.4.5. Remove battery, reenter download mode & reflash the correct file
Rosli59564 said:
As i guess. You phone is 4.3 right? Download for 4.3 i think 6.0.4.5. Remove battery, reenter download mode & reflash the correct file
Click to expand...
Click to collapse
i cant find the 4.3 one, yes i tried google
please help
also my phone boots normally
143bubblepop said:
i cant find the 4.3 one, yes i tried google
please help
also my phone boots normally
Click to expand...
Click to collapse
i tried their website but all i could find were .img files
also, im sorry with my delayed replies, my gmail isnt refreshing constantly
143bubblepop said:
i tried their website but all i could find were .img files
also, im sorry with my delayed replies, my gmail isnt refreshing constantly
Click to expand...
Click to collapse
First check setting>general>about phone. Check what is android version either 4.3 or 4.4.2.
If it is 4.3 download either the followings
https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
You need to install mega from playstore to download it
Or try twrp
http://forum.xda-developers.com/showthread.php?t=2494245
Rosli59564 said:
First check setting>general>about phone. Check what is android version either 4.3 or 4.4.2.
If it is 4.3 download either the followings
https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
You need to install mega from playstore to download it
Or try twrp
http://forum.xda-developers.com/showthread.php?t=2494245
Click to expand...
Click to collapse
Its 4.3
Install mega?
143bubblepop said:
Its 4.3
Install mega?
Click to expand...
Click to collapse
If you would like twrp no need mega. Just download it from the site
Edit: This has been [ SOLVED ] please refer to last post, my idea is that if updating through kies it either turns usb debugging off ( even though it shows on, and or turns reactivation lock on ( even if it appears to be off) , all in all this might just be an issue where wiping the system cache on Clean Master did the trick I have no idea.
Thank you to all who had a hand in providing information
Story goes like this.
Updated through kiies and lost root, so I figured I'll just use Cf auto root to get it back, flash in Odin fails and produces in red text "secure check failed : recovery" have tried different USB ports, cables, battery pulls, wiping of cache. I'm just confused as to why it is A) giving me "secure check failed: Recovery " and if there is any way to fix this so I can actually succeed and get this device rooted.
Thanks in advance
http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/
Did this on my n900w8 and still 0.0. CF root sent me into the same loop.
Cabooch said:
Story goes like this.
Updated through kies and lost root, so I figured I'll just use Cf auto root to get it back, flash in Odin fails and produces in red text "secure check failed : recovery" have tried different USB ports, cables, battery pulls, wiping of cache. I'm just confused as to why it is A) giving me "secure check failed: Recovery " and if there is any way to fix this so I can actually succeed and get this device rooted.
Thanks in advance
Click to expand...
Click to collapse
Things to check;
- make sure reactivation lock is off
- make sure the cf file you're using is for your os, 4.3 cf auto root won't work on a 4.4 bootloader
hey_joe said:
Things to check;
- make sure reactivation lock is off
- make sure the cf file you're using is for your os, 4.3 cf auto root won't work on a 4.4 bootloader
Click to expand...
Click to collapse
Yes sir, never have turned reactivation lock on and it appears to be off in settings.
I have also used the 4.4 versions of the CF Auto-root to no avail
When trying to flash CWM Recovery i also receive " secure check fail [FMM]: Cache"
When trying to flash TWRP i receive " secure check fail: Recovery"
Any further advice?
Cabooch said:
Yes sir, never have turned reactivation lock on and it appears to be off in settings.
I have also used the 4.4 versions of the CF Auto-root to no avail
When trying to flash CWM Recovery i also receive " secure check fail [FMM]: Cache"
When trying to flash TWRP i receive " secure check fail: Recovery"
Any further advice?
Click to expand...
Click to collapse
DID you tick at USB debugging box?
Cabooch said:
Yes sir, never have turned reactivation lock on and it appears to be off in settings.
I have also used the 4.4 versions of the CF Auto-root to no avail
When trying to flash CWM Recovery i also receive " secure check fail [FMM]: Cache"
When trying to flash TWRP i receive " secure check fail: Recovery"
Any further advice?
Click to expand...
Click to collapse
For root, use this file.
For custom recovery, I've only used this CWM file ever since updating to Kit Kat. Haven't tried TWRP so can't comment on that one.
hhai2pth said:
DID you tick at USB debugging box?
Click to expand...
Click to collapse
hey_joe said:
For root....
For custom recovery, I've only use t. Haven't tried TWRP so can't comment on that one.
Click to expand...
Click to collapse
Yes USB debugging is on
I have attempted with both the exact files, as well as the sm900w8 Cf auto to no avail, I think my last resort is going to be to re flash a fresh version of 4.4.2 and if that sticks I'm going to try this all over again. I'll let you guys k ow what's happening..
[SOLVED]
So, got home and was thinking about what i could attempt to do before i just straight up flashed stock and retried, i decided to Toggle off usb debugging and turn it back on, then turned on reactivation lock, and then turned it off. I then proceeded to clean my system cache using Clean master, popped into download mode, and i flashed the Cf Auto-Root for the sn9500 Worked like a charm passed and rooted my device.
Would like to note that this did not trip Knox i am still 0x0 ( can provide pics if needed) Thank you to all that provided some help thanks will be given appropriately
There are so many threads, I am lost. My S5 is G900F ANE2. So some questions as I want root and a debloated custom rom while keeping 0x0:
I want to keep 0x0, what root method is available for my model?
Once rooted and flashed; how can I go back to non-rooted stock rom if necessary?
what custom rom and installation method are there for my model?
yeahman45 said:
There are so many threads, I am lost. My S5 is G900F ANE2. So some questions as I want root and a debloated custom rom while keeping 0x0:
I want to keep 0x0, what root method is available for my model?
Once rooted and flashed; how can I go back to non-rooted stock rom if necessary?
what custom rom and installation method are there for my model?
Click to expand...
Click to collapse
You can use Towelroot to root and keep KNOX on 0x0. and install Xposed framework. You could also flash the pre-rooted latest NeatRom http://forum.xda-developers.com/galaxy-s5/development/rom-neatrom-v1-t2828562 with Odin 3.09 and also keep KNOX to 0x0. Thats about it, most other custom roms need to be flashed with a custom recovery.
Towelroot says my device is not compatible ... for neatrom, which installation procedure should I use?
"Installation Instructions: If you're coming from a Samsung stock NON-Rooted ROM before NG2/NG7/NG9/NH4/NH6 (KNOX 0x0)"??
what is NG2, etc...? How to know if mine is after or before that??
edit: neatrom says it needs towelroot to root the phone but towelroot says my phone isn't currently supported
yeahman45 said:
Towelroot says my device is not compatible ... for neatrom, which installation procedure should I use?
"Installation Instructions: If you're coming from a Samsung stock NON-Rooted ROM before NG2/NG7/NG9/NH4/NH6 (KNOX 0x0)"??
what is NG2, etc...? How to know if mine is after or before that??
Click to expand...
Click to collapse
Download Neatrom and flash it according to these instructions (from the NeatRom thread) with Mobile Odin Pro:
Installation Instructions: If you're coming from a Samsung stock NON-Rooted ROM before NG2/NG7/NG9/NH4/NH6 (KNOX 0x0)
1. Backup your Internal SD to your PC
2. Go to Settings/Security/ and UN-TICK "Reactivation lock"
3. Go to Settings/Security/Security policy updates/ and UN-TICK "Automatic updates"
4. Go to Settings/Security/ and UN-TICK "Send security reports"
5. Go to Settings/About device/Software update/ and UN-TICK "Auto update"
6. Root your phone with Towelroot---pic1---pic2
7. Reboot and install SuperSu from the PlayStore
8. Run SuperSU and select "Continue", "Normal" and "OK". ---pic1,---pic2,---pic3 Wait a few seconds and then reboot device
9. Run SuperSU again and select "Try to disable KNOX"---pic1,---pic2
10. Reboot and download NeatROM onto your phone
11. Check the md5sum of the NeatROM.zip
12. Purchase and install Mobile Odin Pro
13. Run Mobile Odin Pro---pic1---pic2
14. Load the NeatROM.zip file with "OTA / Update ZIP"---pic1,---pic2
15. UN-TICK "Enable EverRoot" (NeatROM is already rooted)---pic1
16. UN-TICK "Wipe data and cache"---pic1
17. UN-TICK "Wipe Dalvik cache"---pic1
18. Select "After flash..." then select "Download mode"---pic1,---pic2
19. Select "Flash firmware"---pic1
20. Once the Aroma Installer starts, select the options that you would like to install
21. When the ROM has finished installing, and at the end of the installation process in Aroma, UN-TICK "Reboot Device"---pic1
22. When the phone goes into Download Mode, download and open PC Odin
23. Extract and flash MODEM (load as CP) and BOOTLOADER (load as BL) in ONE STEP---pic1---pic2
24. If something goes wrong and your device will not boot after flashing, try to remove the battery for a few moments and then put it back in, press and hold VolumeUP + Home + Power to boot the device into recovery mode and do a "wipe Data/factory reset" then "reboot system now"
25. Go to Settings/Security/ and UN-TICK "Reactivation lock"
26. Go to Settings/Security/Security policy updates/ and UN-TICK "Automatic updates"
27. Go to Settings/Security/ and UN-TICK "Send security reports"
28. Enjoy your NeatROM with KNOX 0x0
Basicaly root the phone, install superSU and BusyBox from Play, install Mobile Odin Pro and flash the rom with it. But follow the steps closely as discribed in the tutorial.
I am getting "phone is currently not supported" on towelroot..... got that also last time... have been searching for that issue for my model and can't find a solution...
http://www.naldotech.com/how-to-fix-towelroot-phone-isnt-supported-problem/
tried the solution here but still cannot root.. still gets "this phone isn't currently supported", tried all 3 modstrings
yeahman45 said:
http://www.naldotech.com/how-to-fix-towelroot-phone-isnt-supported-problem/
tried the solution here but still cannot root.. still gets "this phone isn't currently supported", tried all 3 modstrings
Click to expand...
Click to collapse
Try booting in recovery and wipe the cach, bootup and try TR again.
recovery? how to boot to samsung's recovery? there is wipe cache in the official samsung recovery??
yeahman45 said:
recovery? how to boot to samsung's recovery? there is wipe cache in the official samsung recovery??
Click to expand...
Click to collapse
Sure, power down the phone, wait a few seconds and press volume up + menu + power and it will boot into recovery. Then sesect wipe caches.
cache wiped... still cannot root what is wrong? is my S5 "fake" or what?
yeahman45 said:
cache wiped... still cannot root what is wrong? is my S5 "fake" or what?
Click to expand...
Click to collapse
Install CPU-Z or Phone Info for Samsung from Play to identify the device., but probably its not a fake one.
does not look fake.. seems genuine in cpuz. My baseband is actually G900F ANE2 but build number is G900F ANI3 ... is that normal?
yeahman45 said:
cache wiped... still cannot root what is wrong? is my S5 "fake" or what?
Click to expand...
Click to collapse
yeahman45 said:
does not look fake.. seems genuine in cpuz. My baseband is actually G900F ANE2 but build number is G900F ANI3 ... is that normal?
Click to expand...
Click to collapse
Baseband should be at least ANG8 for that firmware afaik. ANE2 is an old modem. You can download and install new modems from the XtreStoLite thread and flash it with Odin, will not trip KNOX. Was the device new when you bought it?
gee2012 said:
Baseband should be at least ANG8 for that firmware afaik. ANE2 is an old modem. You can download and install new modems from the XtreStoLite thread and flash it with Odin, will not trip KNOX. Was the device new when you bought it?
Click to expand...
Click to collapse
are you sure? Can I revert back if something goes wrong?
yeahman45 said:
are you sure? Can I revert back if something goes wrong?
Click to expand...
Click to collapse
Yes you can flash a modem sepereatly or flash a stock rom with Odin. BTW if you want to flash a modem you have to flash the latest bootloader first with Odin. BL are also posted in the XtreStoLite thread.
gee2012 said:
Yes you can flash a modem sepereatly or flash a stock rom with Odin. BTW if you want to flash a modem you have to flash the latest bootloader first with Odin. BL are also posted in the XtreStoLite thread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52210611&postcount=4
XtreStoLite thread says Bootloader: XXU1ANJ1 and Modem: XXU1ANJ1....these are the ones I need to flash?
yeahman45 said:
http://forum.xda-developers.com/showpost.php?p=52210611&postcount=4
XtreStoLite thread says Bootloader: XXU1ANJ1 and Modem: XXU1ANJ1....these are the ones I need to flash?
Click to expand...
Click to collapse
Yup, power down the phone, pull the battery, wait 20 seconds, uncheck Auto Reboot in Odin and flash the BL, when done pull the battery again, wait again and flash the modem and reboot. Place the bootloader in BL and modem in CP in Odin.
gee2012 said:
Yup, power down the phone, pull the battery, wait 20 seconds, uncheck Auto Reboot in Odin and flash the BL, when done pull the battery again, wait again and flash the modem and reboot. Place the bootloader in BL and modem in CP in Odin.
Click to expand...
Click to collapse
thx going to try it now
yeahman45 said:
thx going to try it now
Click to expand...
Click to collapse
updated bootloader and modem but still cannot root with towelroot ... still same message " This phone is currently not supported" How come? I have everything as described in its requirements
Hi
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.
hey guys iam new at the S5 and i have done some research on how to root s5 on 5.0 lolipop and i so i saw odin with cf root when i put the flash with odin i get a fail and when i see the screen it says something on red letters about the security check
Any help plz?
Januh said:
hey guys iam new at the S5 and i have done some research on how to root s5 on 5.0 lolipop and i so i saw odin with cf root when i put the flash with odin i get a fail and when i see the screen it says something on red letters about the security check
Any help plz?
Click to expand...
Click to collapse
What model of s5 is it?
Sent from my SM-G900A using Tapatalk
sorry forgot to mention that is the s5 international, SM-G900F
Try flashing TWRP 2.8.7.0 with ODIN 3.10.6, then flash SuperSU zip from inside TWRP
I can confirm this works. Also, you might want to try "Android Toolkit".
Deleted
*Detection* said:
Try flashing TWRP 2.8.7.0 with ODIN 3.10.6, then flash SuperSU zip from inside TWRP
Click to expand...
Click to collapse
i cant put the recovery nor super su it says in red letters "Secure check Fail : Recovery"
i start on Odin and in half the way it says FAIL and appear that mensage
After many research i found the issue...
For ppl that may have the problem try this -> Settings security.. Reactivation lock untick...