Hi!
My Note 4 n910F is not able to get root anymore.
the funny thing is that i previously installed Root with CF Autoroot. but after i installed TWRP Recovery, root was getting buggy and "SU" App says something like this: "root isnt available, you might downgrade to 4.3 " or something like this.
And after that i had no root access. an then i tryed to root it again with Odin. but Odin gave an Error Failed message.
then i Installed a Stock Rom for my N910F Yes the right one and the newest one
my Phone starts Properly, everything works Perfekt, but again if i try installing CF Auto Root with Odin its Start and then it gaves me an error.
this is the Error Message:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and my Note 4 in Download Mode displays this text in red : Secure Check Fail : Recovery
What can i do? i never experienced something like this...
Thanks
Is there any option in twrp to fix root on boot like in philz and Cwm? If there is uncheck that. Otherwise try flashing stock with odin then re root and flash twrp again
I had same problem, had to deactivate "Reactivation Lock", goto Settings - System - Security and untick then root
HTH
Lee1972 said:
I had same problem, had to deactivate "Reactivation Lock", goto Settings - System - Security and untick then root
HTH
Click to expand...
Click to collapse
THANKS Times! it worked! :*
Related
Hi all
My I9505, has turned quite weird today... I tried flashing it with latest NEE firmware, but it failed:
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
And on the handset I get in red writing:
STAT: [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I can only flash it with:
I9505XXUAMDE_I9505OXXAMD8_NEE
When entering recovery I sometimes get:
"No command" instead of the windows where it sets CSC, sometimes it sets CSC normally
When I try to reset flash counter I get
could not find triangle and counter data
I have also tried flashing with PIT, but that didn't help either...
Any help??
Kind regards
Ratata82 said:
Hi all
My I9505, has turned quite weird today... I tried flashing it with latest NEE firmware, but it failed:
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
And on the handset I get in red writing:
STAT: [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I can only flash it with:
I9505XXUAMDE_I9505OXXAMD8_NEE
When entering recovery I sometimes get:
"No command" instead of the windows where it sets CSC, sometimes it sets CSC normally
When I try to reset flash counter I get
could not find triangle and counter data
I have also tried flashing with PIT, but that didn't help either...
Any help??
Kind regards
Click to expand...
Click to collapse
read this
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Click to expand...
Click to collapse
samersh72 said:
read this
Click to expand...
Click to collapse
I have already tried all the steps, many times... This is just driving me insane
Ratata82 said:
I have already tried all the steps, many times... This is just driving me insane
Click to expand...
Click to collapse
it is something to do with bootloader
read this http://teamuscellular.com/Forum/topic/4963-★☞-support-touchwizstock-deodexed-jflteuscr970vxuamf5-☜★/?p=77401 post #51
and this http://forum.xda-developers.com/showpost.php?p=43619724&postcount=479
samersh72 said:
it is something to do with bootloader
read this http://teamuscellular.com/Forum/topic/4963-★☞-support-touchwizstock-deodexed-jflteuscr970vxuamf5-☜★/?p=77401 post #51
and this http://forum.xda-developers.com/showpost.php?p=43619724&postcount=479
Click to expand...
Click to collapse
But then I should be able to upgrade it, it fails with every single rom except the oldest. But looks like you are right
Fixed:
The problem was infact the new KNOX secure bootloader. I just upgradet it to I9505XXUDMH8_I9505OXXDMHA_BTU, and that fixed it.
Hopefully we will soon see a bootloader downgrade for new KNOX security Samsung handsets, nothing is unbreakable
Best regards
Please Explain
Ratata82 said:
Fixed:
The problem was infact the new KNOX secure bootloader. I just upgradet it to I9505XXUDMH8_I9505OXXDMHA_BTU, and that fixed it.
Hopefully we will soon see a bootloader downgrade for new KNOX security Samsung handsets, nothing is unbreakable
Best regards
Click to expand...
Click to collapse
can you please explain, how did you fix it. I am facing the same problem :crying:
You can't downgrade which means flash a previous android version
So just flash the newest android version and you'll be ok
Hi!
My Note 4 n910F is not able to get root anymore.
the funny thing is that i previously installed Root with CF Autoroot. but after i installed TWRP Recovery, root was getting buggy and "SU" App says something like this: "root isnt available, you might downgrade to 4.3 " or something like this.
And after that i had no root access. an then i tryed to root it again with Odin. but Odin gave an Error Failed message.
then i Installed a Stock Rom for my N910F Yes the right one and the newest one
my Phone starts Properly, everything works Perfekt, but again if i try installing CF Auto Root with Odin its Start and then it gaves me an error.
this is the Error Message:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and my Note 4 in Download Mode displays this text in red : Secure Check Fail : Recovery
What can i do? i never experienced something like this...
Thanks
Not sure why this is here
FWIW - I had this same error (Secure Check Fail : Recovery) when trying to flash via Odin after enabling the 'Reactivation Lock' option in 'Settings > Security> Reactivation Lock'. If this is enabled; disable it, and try again. Worked for me anyway.
dalgibbard said:
FWIW - I had this same error (Secure Check Fail : Recovery) when trying to flash via Odin after enabling the 'Reactivation Lock' option in 'Settings > Security> Reactivation Lock'. If this is enabled; disable it, and try again. Worked for me anyway.
Click to expand...
Click to collapse
this worked for me aswell, thank you only took all day
Where?
cmorebutt6969 said:
this worked for me aswell, thank you only took all day
Click to expand...
Click to collapse
Hi,
I have the same problem, but I can't find nothing helpfull.:crying:
Now i saw your thread and I asked myself where should be the settings button?
I can only see an option menu, and there isn't a Reactivation Lock
I really hope you could help me.
FighterGER said:
Hi,
I have the same problem, but I can't find nothing helpfull.:crying:
Now i saw your thread and I asked myself where should be the settings button?
I can only see an option menu, and there isn't a Reactivation Lock
I really hope you could help me.
Click to expand...
Click to collapse
here it is
Hello I was trying to root my G900F that is currently running Lollipop BNL7 with CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug but Failed at the end of the process. Had to restore stock G900FXXU1BNL7 to get phone back working.
Try it two times always fails at the end.
Any other method or have to wait for updated version of CF-Auto?
Does G900FXXU1BNL7 is rootable?
Is there a way to downgrade to 4.4 safely as I try already and end up in nightmare and dont have EFS backup that is why I want to root first.?
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
egejo said:
Hello I was trying to root my G900F that is currently running Lollipop BNL7
Click to expand...
Click to collapse
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.
Reactivation lock
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I think you already enable (Reactivation lock) from setting --> security
Just uncheck the option and i hope it will work fine
Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
lingowistico said:
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.
Click to expand...
Click to collapse
egejo said:
Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
Click to expand...
Click to collapse
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.
i cant install recovery mode on bnl7 . Tried it whole day and all i get is stock recovery mode.
Help ?
lingowistico said:
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.
Click to expand...
Click to collapse
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Lastly to let you know that now I'm in Stock G900FXXU1ANCE, dowgraded from BLN7 to BLN2, then ANJ1 and then ANCE. On all of them I have been trying to root or put a custom recovery, used CF-Auto-Root-klte-kltexx-smg900f, openrecovery-twrp-2.8.1.0-klte or philz_touch_6.57.8-klte with same results always Failing Odin at the end of process... The thing I notice is that always it shown on the dowload mode screen
"QUALCOMM SECURE BOOT: ENABLED (CSB)"
Even after downgrade, could these be the issue?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...
egejo said:
Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...
Click to expand...
Click to collapse
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762
pnr2020 said:
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762
Click to expand...
Click to collapse
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?
egejo said:
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Click to expand...
Click to collapse
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root
lingowistico said:
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root
Click to expand...
Click to collapse
I cant flash any custom recovery at all it always fails and softbricks the phone... Looks like these G900F is now bootloader Locked...
If so samsung is now selling them from factory locked not just ATT versions...
egejo said:
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?
Click to expand...
Click to collapse
dont know to be honest mine only 2 weeks old from uk was on BTU but now on polish version
egejo said:
Looks like these G900F is now bootloader Locked...
Click to expand...
Click to collapse
I don't think so, everything works fine for me..
i also cant install recovery but i dont get soft bricks , just normal stock recovery mode all over.
"qualcomm secure boot: Enabled (csb)
hello everyone
if you got error in odin when flash any custom recovery just deactivate reactivation lock from setting>security.
Hi guys I'm having problems trying to root my note 3, in fact i can't flash anything with odin.
It is a n900w8 from Telcel, with 4.4.2 stock rom.
I tried flashing to root it and tried to flash a custom recovery and nothing.
this is what odin shows:
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in the phone it shows in red letters : Secure check fail : recovery
I already checked the reactivation lock, and it isn´t checked.
Do you have an idea of what could it be?
If you need another info pleas tell me, i would appreciate any help thanks
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: HERE.
Joku1981 said:
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: .
Click to expand...
Click to collapse
thanks for the answer but i didn´t work , I can flash that rom but only that. I tried to flash the root and the same error.
I am trying to root my S5 using Odin for installing custom ROM but unable to root it. As soon as i start the root process, it gives the message of Failed.
help please?
Need a lot more info than that bud, model S5?
Method you are using step by step?
I have S5 SM-G900F
i am connecting it to my laptop in download mode with USB Debugging enabled
Odin is detecting the phone, i added the CF-Auto Root file to Odin
The Odin gave indication that this file is valid
Once i start the operation, it displays this in Message window of Odin
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The message that i get on my cell phone screen are
UDC START
SYS REV CHECK FAIL : No Version
SECURE MAGICODE CHECK FAIL : recovery
and the process ends up with a FAIL message in Odin
Are you running ODIN as Admin? (Right click > Run as Administrator)
And you've tried a couple different versions from 3.09 > 3.10.7 ?
-
If that still fails, you'll probably need to flash TWRP 2.8.7.0 with ODIN then SuperSU from TWRP recovery
Specifically version 2.8.7.0
And you don't need USB debugging enabled for flashing from download mode, only for connecting while the phone is booted into Android
Try another software
Try flashing already rooted ROM if not considered ?
Don't use kingroot !
regards
Max.
okay let me try this way now
NO DO NOT TRY KINGROOT
Only CF Auto Root or SuperSU from recovery
Anything else is likely to brick your phone
---------- Post added at 15:06 ---------- Previous post was at 15:05 ----------
stalker2106 said:
Try flashing already rooted ROM if not considered ?
Either, you could try KingRoot, it works on some devices,
but it is horribly slow.
regards
Max.
Click to expand...
Click to collapse
Don't give out advice that you have not personally tested on the S5
Are you going to fix his phone for him when you brick it?
I flashed my G900F using Odin3 but i rooted my tablet with KingRoot and it worked well, so i though he could give it a shot ! but if you say its not recommended then i will edit my post, sorry for inconvenience.
Rooting a tablet with kingroot has nothing to do with a Galaxy S5
Again, unless you have successfully performed what you are suggesting on the S5, do not suggest it, a tablet has nothing to do with an S5