Cant boot my phone...Custom binary blocked by Reactivation Lock - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi I have a big problem because since I tried to reboot to install an add-blocker, I can't go into recovery and I can't start my gt-n9005 anymore because following error message comes:
Custom binary blocked by Reactivation Lock.
SECURE FAIL: KERNEL
And when I want to flash something with odin in download mode following error message appears:
SECURE CHECK FAIL: Recovery
Please help me I don't know what to do. Thank's in advanced...

Could please someone help me?

Can you boot your phone? If you, can, you can go to settings and uncheck the reactivation lock..after that, you should be able to enter recovery normally.
Regards!

empat said:
Can you boot your phone? If you, can, you can go to settings and uncheck the reactivation lock..after that, you should be able to enter recovery normally.
Regards!
Click to expand...
Click to collapse
My dear fellow please read the title of the OP , it says that mani1999 is not able to boot his phone !!! That's the major issue...

ketani73 said:
My dear fellow please read the title of the OP , it says that mani1999 is not able to boot his phone !!! That's the major issue...
Click to expand...
Click to collapse
Sorry, I misread the statement..my bad!
To the OP: what happens when you try to boot? I am asking because I just recovered my device from a similar condition...
Regards, sorry again!

empat said:
Sorry, I misread the statement..my bad!
To the OP: what happens when you try to boot? I am asking because I just recovered my device from a similar condition...
Regards, sorry again!
Click to expand...
Click to collapse
Apology not needed bro , sometimes such things happen to me as well (we are all humans & subject to making such errors) ....

Maybe a factory reset?
Regards!!

mani1999 said:
Hi I have a big problem because since I tried to reboot to install an add-blocker, I can't go into recovery and I can't start my gt-n9005 anymore because following error message comes:
Custom binary blocked by Reactivation Lock.
SECURE FAIL: KERNEL
And when I want to flash something with odin in download mode following error message appears:
SECURE CHECK FAIL: Recovery
Please help me I don't know what to do. Thank's in advanced...
Click to expand...
Click to collapse
Try flash back your country firmware with correct CSC.
Try this it might help if that is the thing you did before - http://forum.xda-developers.com/showpost.php?p=46389503&postcount=2 scroll down to section mention
HELP! I flashed N9005XXUBMJ3_N9005OXABMJ1 and now I am stuck in download mode! What do I do?!
You are mostly going to trip the KNOX Warranty at this point.
Flash this AP N9005XXUBMJ3_N9005OXABMJ1_BTU_RECOVER.tar.md5 (2.05 GB) and this CSC N9005OXABMJ3_CSC.tar.md5 (38.0 MB)
Click to expand...
Click to collapse
Factory reset won't help, as Reactivation is blocking you if you had use different country CSC and you did it before you un-tick the Reactivation Lock.

I can't boot my phone and i can't boot recovery...i always get the message "Custom binary blocked by Reactivation Lock. Secure fail: Kernel" with a yellow alert triangle underneath, even if I normally try to boot my phone. And when I than press the power button the phone turns off again.
I tried to flash cwm with odin but that also failed.
So before i go downloading another firmware (i live in a dormatory and only have 10gb internet a month) do you really think that would work?

mani1999 said:
I can't boot my phone and i can't boot recovery...i always get the message "Custom binary blocked by Reactivation Lock. Secure fail: Kernel" with a yellow alert triangle underneath, even if I normally try to boot my phone. And when I than press the power button the phone turns off again.
I tried to flash cwm with odin but that also failed.
So before i go downloading another firmware (i live in a dormatory and only have 10gb internet a month) do you really think that would work?
Click to expand...
Click to collapse
I had this exact problem recently and I booted by going into download mode and then pressing volume up to reboot. Somehow or other that would boot. Powering off and back on would always get that error that you are getting.

Thank you very much RP that let me boot and uncheck the lock. I had just installed Goo and put twrp on my device.

rp1790 said:
I had this exact problem recently and I booted by going into download mode and then pressing volume up to reboot. Somehow or other that would boot. Powering off and back on would always get that error that you are getting.
Click to expand...
Click to collapse
I put my phone into download mode but volume up mean geting into download mode. Its volume down to reboot but it still says the same when trying to boot. Custom Binary Blocked by Reactivation Lock. Secure Fail: Kernal. Kindly help please

Custom binary blocked by Reactivation Lock
njan_ivide said:
I put my phone into download mode but volume up mean geting into download mode. Its volume down to reboot but it still says the same when trying to boot. Custom Binary Blocked by Reactivation Lock. Secure Fail: Kernal. Kindly help please
Click to expand...
Click to collapse
Hey guys.
Had the same problem with a similar message after Flashing the N3EchoeSlimV2.zip. (was running on Xnote V3 europeen firmware )
Custom binary blocked by Reactivation Lock.
SECURE FAIL: RECOVERY
Only way to boot, was the download mod
So i went back stock rom with Odin.
But i coudnt flash any Custom recovery or Cfroot. Many tries with différent Odin version.
I finally installed a recovery after took the battery off a couple of hours.
Sorry for my bad english

Same problem here with the slim version!
Anybody have an idea?

Kinoal said:
Same problem here with the slim version!
Anybody have an idea?
Click to expand...
Click to collapse
I had posted the solution here on a different thread but let me make it easier for you:
Solution.
1. download KIES 3 (for note 3)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
DONE! you are back to stock..
NOTE: This doesnt make your KNOX warranty 0x0 if it is already 0x1.
Click Thanks if it helped!!

Calm down guys
What I did was enter into download mode like rp1790 suggested and maybe he did a typing error. When in download mode press down to restart the phone. It bypassed the custom binary block error and booted as normal.

njan_ivide said:
I had posted the solution here on a different thread but let me make it easier for you:
Solution.
1. download KIES 3 (for note 3)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
DONE! you are back to stock..
NOTE: This doesnt make your KNOX warranty 0x0 if it is already 0x1.
Click Thanks if it helped!!
Click to expand...
Click to collapse
This doesn't work if you install a firmware with the new bootloaders... You CAN'T flash an older bootloader over the new one. It just sends you into a bootloop....
And thats before you include the re-activation lock error...

Kinoal said:
Same problem here with the slim version!
Anybody have an idea?
Click to expand...
Click to collapse
I have also just encountered the same error as the OP, however the above method doesn't work for me, kies 3 gives me an unknown error (i.e. it doesn't say what error) and just fails.
Same deal as me, was using X-Note and installed the add blocker, rebooted, BAM.
Any help is going to be greatly appreciated!
:crying:

yop
i've the same problem and a full wipe fix it

Just got it fixed
I recently had this problem.
I've read from this thread to boot into download mode and just cancel. It will boot normally after that. I'll never reactivate it again.

Related

[Q] Not booting - Secure Fail: Recovery - any recommendations?

Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Any ideas?
Thank you
Go into Recovery mode (Vol Up + Home Button + Power Button) and Factory reset Data & Wipe Cache Partition...
moin786 said:
Go into Recovery mode (Vol Up + Home Button + Power Button) and Factory reset Data & Wipe Cache Partition...
Click to expand...
Click to collapse
Still get the same thing. It starts to boot to recovery then says something that fails then goes to the screen I have posted previous.
This is what first loads (pretty quick - had to reboot about 10 times to get it)
recovery booting...
SYS REV CHECK FAIL : no version
Secure : Secure Version Failure (recovery.img)
Set Warranty Bit : Recovery
norem0rz said:
Still get the same thing. It starts to boot to recovery then says something that fails then goes to the screen I have posted previous.
This is what first loads (pretty quick - had to reboot about 10 times to get it)
recovery booting...
SYS REV CHECK FAIL : no version
Secure : Secure Version Failure (recovery.img)
Set Warranty Bit : Recovery
Click to expand...
Click to collapse
What did you do prior to this? It looks like you flashed a custom recovery but Knox is terminating the boot process.
Have you tried to odin back to stock?
Sent from my Galaxy Note 3 ?
Trying to use Odin - downloading a stock ROM now.
No. You must get into download/Odin mode by pressing volume down + home + power simultaneously, then launch Odin, then connect phone to computer.
Sent from my SM-N900V using Tapatalk
norem0rz said:
yes, I was using clockwork and did something wrong...
doesn't the phone need to boot up before I can use Odin?
Click to expand...
Click to collapse
If you have a Verizon retail version of the Note 3, you can not use Clockworkmod recovery. Because your bootloader is locked. You can only use Hashcode's Safestrap (in the Development section).
cam30era said:
If you have a Verizon retail version of the Note 3, you can not use Clockworkmod recovery. Because your bootloader is locked. You can only use Hashcode's Safestrap (in the Development section).
Click to expand...
Click to collapse
+1
Which means you must be rooted first, then install Safestrap, which is a modified TWRP recovery. You can thank Verizon for that bullsh!t
Sent from my SM-N900V using Tapatalk
Thank you all - using Odin with this link http://forum.xda-developers.com/showthread.php?t=2483380
Got me back up and running.
Flash PIT - this will fix it
You need to flash the PIT with ODIN, latest version (3.09, I believe). Google for a download mirror that hosts the PIT for whichever type of note 3 you have, then flash it with odin (should work while in the invalid software screen). Then, if it doesn't reboot, just remove the battery and unplug that sucka. When it reboots, it should go back to download mode or just regular bootup. I recommend setting up adb, which makes it much easier to put the phone into whatever mode you desire with a simple dos command.
got out of it
this happened to me last night, I went into Odin mode "home, volume down, power button" instead of selecting odin mode from that menu I selected "reboot phone" (or something to that effect) My note 3 restarted......PHEW...... hope this helps someone
enable android recovery mode
SM-N90OV
ok so I once got to the point to where I could not but factory reset my phone and so I did settings > backup and restore > factory reset > YES I'M SURE!!! then my phone when into recovery mode as it should normally only to tell me that it could not enter recovery. Verizon's fault and now I cant access my recovery mode. is there a way to get back into it so I can finally flash a new rom. oh I had figured out how to get out of the boot loop thing by entering download mode and canceling. but it would be nice to be able to mess with this beast of a phone. please help me. I don't want to do something I wasn't supposed to. im not sure want to do with klms agent deals with knox right?
Em also one of the victim
hi
i am rooted (de la Vega ) safestrap installed using Jelly beans 6 & stock Rom as well. i don't know how but i am not being able to get in the recovery to format the device.
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
What i do is getting into the download mode and only pressing Volume down to continue boot and Viola my phone restarts every time, but the thing which is pinching me is i can't able to format the phone.. Help required please.
xaneey said:
hi
i am rooted (de la Vega ) safestrap installed using Jelly beans 6 & stock Rom as well. i don't know how but i am not being able to get in the recovery to format the device.
Getting "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
What i do is getting into the download mode and only pressing Volume down to continue boot and Viola my phone restarts every time, but the thing which is pinching me is i can't able to format the phone.. Help required please.
Click to expand...
Click to collapse
look at page one towards the bottom, the OP posted how to fix your problem
Solution
HI all
What worked for me is just ODIN
MI9 t0 MJE
and this is the beauty of ANDROID really happy to get it back..
Downloaded MJE for N900V http://www.sammobile.com/firmwares/3/?download=23535
Root through this in my case Vroot worked Kingo didn't work for me http://forum.xda-developers.com/showthread.php?t=2528707
Thn safe strap and all done
you guys and gals rock
saved my bacon ,was a little confusing to my novice self but downloaded odin to pc and ran it,downloaded clean vzw file and pit file ,plugged phone into pc and drivers loaded then ran odin and followed the steps.
Thank you very very much

[Q] Galaxy S4 i9505 Bricked - No Recovery Mode - Stuck in Bootloop

Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
menaum said:
Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
Click to expand...
Click to collapse
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
malybru said:
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
Click to expand...
Click to collapse
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
menaum said:
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
Click to expand...
Click to collapse
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
malybru said:
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
Click to expand...
Click to collapse
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
menaum said:
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
Click to expand...
Click to collapse
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
AT&T version here, same problem
malybru said:
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
Click to expand...
Click to collapse
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
ardonie said:
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
Click to expand...
Click to collapse
Hi,
Then , you should try flashing a non-knox firmware .
Unfortunately ,I do not know AT&T firmwares.
Perhaps someone HERE can help.
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
recovery is not Seandroid Enforcing
lorenzoraj said:
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
Click to expand...
Click to collapse
I also have the same problem with Galaxy s4 Active (i9295)
Flashing recovery finish successfully (tried Philz,CWM, TWRP )
But afterwards no recovery exists anymore
only:
recovery is not Seandroid Enforcing
When I flash stock ROM again, the basic recovery it there - no option for applying zip files

[Q] Rooting Note 3 LTE

Dear all..
im facing a problem trying to root my Note 3 LTE
i have done all steps to the rooting process
1- enabled the USB debugging mode
2- put my phone in download mode
3- started odin
4-installed the Samsung drivers
5-choose the CF-Auto-Root-hlte-hltexx-smn9005
6- clicked start button on ODIN 3.9 and done the same thing with ODIN 3.7
2 mins later odin says DONE
the phone stuck on
Recovery Booting ....
recovery is not senandroid enforcing
set warranty bit : recovery
although the odin says DONE
but the phone is stuck on that screen
Thanks and regards ...
Mr.SpY said:
Dear all..
im facing a problem trying to root my Note 3 LTE
i have done all steps to the rooting process
1- enabled the USB debugging mode
2- put my phone in download mode
3- started odin
4-installed the Samsung drivers
5-choose the CF-Auto-Root-hlte-hltexx-smn9005
6- clicked start button on ODIN 3.9 and done the same thing with ODIN 3.7
2 mins later odin says DONE
the phone stuck on
Recovery Booting ....
recovery is not senandroid enforcing
set warranty bit : recovery
although the odin says DONE
but the phone is stuck on that screen
Thanks and regards ...
Click to expand...
Click to collapse
Press volume up + menu + power button and data factory reset and then try to reboot or try pressing power for about 10 seconds or flash a custom recovery in download mode.
gee2012 said:
Press volume up + menu + power button and data factory reset and then try to reboot or try pressing power for about 10 seconds or flash a custom recovery in download mode.
Click to expand...
Click to collapse
i want to continue my rooting process , i can acsess my phone by going to download mode and choosing
cancel ( restart phone )
but my question is WHY i cant root the device ???
i don't have any problem accessing the phone ....
but my problem is that i want to root the device
thanks and regards
Mr.SpY said:
i want to continue my rooting process , i can acsess my phone by going to download mode and choosing
cancel ( restart phone )
but my question is WHY i cant root the device ???
i don't have any problem accessing the phone ....
but my problem is that i want to root the device
thanks and regards
Click to expand...
Click to collapse
If i we`re you i would flash a custom recovery (.tar file) with Odin in downloadmode from here here http://d-h.st/users/xiaolu/?fld_id=31963 (check for the right file like hlte) and flash the latest superSU.zip (1.94 i think) in recovery and that should work. BTW did you disable Kies in windows task manager?
Mr.SpY said:
i want to continue my rooting process , i can acsess my phone by going to download mode and choosing
cancel ( restart phone )
but my question is WHY i cant root the device ???
i don't have any problem accessing the phone ....
but my problem is that i want to root the device
thanks and regards
Click to expand...
Click to collapse
Did you follow and download the cf-auto root from here?http://forum.xda-developers.com/showthread.php?t=2466423
And you didn't mention about reactivation lock
Mr.SpY said:
Dear all..
im facing a problem trying to root my Note 3 LTE
i have done all steps to the rooting process
1- enabled the USB debugging mode
2- put my phone in download mode
3- started odin
4-installed the Samsung drivers
5-choose the CF-Auto-Root-hlte-hltexx-smn9005
6- clicked start button on ODIN 3.9 and done the same thing with ODIN 3.7
2 mins later odin says DONE
the phone stuck on
Recovery Booting ....
recovery is not senandroid enforcing
set warranty bit : recovery
although the odin says DONE
but the phone is stuck on that screen
Thanks and regards ...
Click to expand...
Click to collapse
Which os do you have 4.3 or 4.4.2?
hey_joe said:
Which os do you have 4.3 or 4.4.2?
Click to expand...
Click to collapse
YES I followed the instructions in the previous post
its is
4.3
Mr.SpY said:
YES I followed the instructions in the previous post
its is
4.3
Click to expand...
Click to collapse
You probably used the file meant for 4.4.2. Use this one for 4.3. It has the same name as the one for 4.4.2 so delete the one you previously used or extract on a different folder. No need to enable usb debugging as it's useless when in download mode but you need to make sure reactivation lock is off in settings>security.
thanx fellows
Yeah , that worked fine , im now rooted and voided my knox warranty :angel:
Thanks - TEAM
Mr.SpY said:
Yeah , that worked fine , im now rooted and voided my knox warranty :angel:
Thanks - TEAM
Click to expand...
Click to collapse
Welcome to the club Flash away my friend, lots of goodies await you.

[Q] [HELP] Soft - Bricked my Note 3

Hi,
today i soft bricked my Note 3 because i tried to install CWM Recovery with Reactivation Lock on.
Now it shows a yellow triangle and says "Custom binary blocked by Reactivation Lock" and under that: "Secure Fail: Recovery"
I read that i can go back flashing the original stock firmware but i dont have any idea what my product code/csc is.
On the package it says ART code: SM-N9005ZWENEE
The Booklets in the package are printed in Swedish/Finish
Is there any help or do i have to send it back to Samsung?
Thanks in advance
Chris
hexacetat said:
Hi,
today i soft bricked my Note 3 because i tried to install CWM Recovery with Reactivation Lock on.
Now it shows a yellow triangle and says "Custom binary blocked by Reactivation Lock" and under that: "Secure Fail: Recovery"
I read that i can go back flashing the original stock firmware but i dont have any idea what my product code/csc is.
On the package it says ART code: SM-N9005ZWENEE
The Booklets in the package are printed in Swedish/Finish
Is there any help or do i have to send it back to Samsung?
Thanks in advance
Chris
Click to expand...
Click to collapse
No better way on Earth to welcome you on XDA than a soft brick.
Long story short:
0. I hope you've learned your lesson. READ, READ, THEN WHEN YOU'RE SURE THAT YOU'LL MANAGE, READ SOME MORE.
1. You need your cable and a PC, on the PC you need the latest Samsung USB drivers. You can obtain them most easily by downloading Samsung Kies, it will install the drivers for you.
2. Download, for example, this: https://mega.co.nz/#!Ld03nbgB!N5xbTBnOKrwKmsalRrmLdBY-RF8-01YbNk2QpQEcj1k + Odin (for example, from here http://www74.zippyshare.com/v/18196321/file.html )
3. Unzip the file somewhere easily accessible.
4. Turn the phone off and put it in download mode (hold simultaneously Vol Down + Home Button + Power button), until you see that big yellow triangle and some Samsung nonsense about custom OS harming your phone. Press Vol Up to confirm you want to do it.
5. Unzip Odin somewhere, then start Odin 3.07.
6. Plug the phone to the PC with the cable.
7. Odin should put out a message "Added !!"
8. Click on AP and find the .tar.md5 file you extracted in step 3, and click Open.
9. Odin will process the file and when it puts out the message "Leave CS..." see if only F. Reset Time and Auto Reboot are checked. NOTHING else. And THEN click Start.
10. After the operation finishes and your phone reboots, perform a Factory reset.
11. Go on with rooting and CWM, but check the Reactivation lock.
Good luck.
7.
sirobelec said:
No better way on Earth to welcome you on XDA than a soft brick.
Long story short:
0. I hope you've learned your lesson. READ, READ, THEN WHEN YOU'RE SURE THAT YOU'LL MANAGE, READ SOME MORE.
1. You need your cable and a PC, on the PC you need the latest Samsung USB drivers. You can obtain them most easily by downloading Samsung Kies, it will install the drivers for you.
2. Download, for example, this:XXX + Odin (for example, from here XXXX )
3. Unzip the file somewhere easily accessible.
4. Turn the phone off and put it in download mode (hold simultaneously Vol Down + Home Button + Power button), until you see that big yellow triangle and some Samsung nonsense about custom OS harming your phone. Press Vol Up to confirm you want to do it.
5. Unzip Odin somewhere, then start Odin 3.07.
6. Plug the phone to the PC with the cable.
7. Odin should put out a message "Added !!"
8. Click on AP and find the .tar.md5 file you extracted in step 3, and click Open.
9. Odin will process the file and when it puts out the message "Leave CS..." see if only F. Reset Time and Auto Reboot are checked. NOTHING else. And THEN click Start.
10. After the operation finishes and your phone reboots, perform a Factory reset.
11. Go on with rooting and CWM, but check the Reactivation lock.
Good luck.
7.
Click to expand...
Click to collapse
Thank you verry much.
I had a galaxy s and a note 2 rooted and with custom rom but still this didnt prepare me for this knox **** :/
Still you are right, i was way to carelessle for such an expensive phone.
The Android Version you supplied is UK branded, shure this will work on my phone?
I know i have 4.4.2 on the phone, the version that came out before the latests big patch.
Sorry but i dont want to flash the wrong things even further.
Regards
Chris
OMG,
Flashed it and everything is working perfectly again. BIG Thx mate, supply me with your paypal id and ill invite you for some beers!
THANKS
hexacetat said:
OMG,
Flashed it and everything is working perfectly again. BIG Thx mate, supply me with your paypal id and ill invite you for some beers!
THANKS
Click to expand...
Click to collapse
Support the devs that make unbricking, flashing, etc. possible.
And have fun with the Nope 3, the ugliest phone on Earth, but still I wouldn't change it for anything but (probably) a Note 4 with Exynos 5433.

Can't get my SM-G900F rooted... ("Recovery is not SEAndroid enforcing"?)

Hello there, beginner here.
I'm having issues getting my SM-G900F rooted, which is running Android 5.0. My phone doesn't reboot into recovery after flashing cf-auto-root, and the trouble shooting section about this issue doesn't help me too.
I used this cf-auto-root release, as it states to be the one for SM-G900F and Android 5.0.
I then followed these steps with the Odin version included in the download.
However, after flashing, my phone does not reboot into recovery, and just stays in Download mode, with Odin saying PASS.
I know that there's a trouble shooting section below in the steps I linked, but it is not helping me, or I don't understand it. In fact, I have several questions about these steps, and maybe someone can help me about it. Let me cite the original post and my questions about it.
...
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
Click to expand...
Click to collapse
First question arises here. How should I put my device into download mode if I wanted to use the "ADB reboot download" command? According to the steps, it is not connected to my PC at the moment. So I chose to get into download mode with VolDown+Home+Power.
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
Click to expand...
Click to collapse
As said, my phone does not reboot, even after Odin states "PASS". So I tried the steps explained in the following note:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens.
Click to expand...
Click to collapse
What is meant with "do the entire procedure again"? My phone is now sitting in download mode, with Odin saying PASS. Should I just press "Start" again in Odin? That does nothing on my phone.
Should I pull the battery? My phone is still on then, since it takes the power from the USB connection. So I disconnect it too? If I do that and put the battery back in, it immediately automatically boots, and I get the following error on my screen:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
And then it just hangs there, and installs nothing. If I try to restart it normally, it goes back to this screen, all the time.
If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
This does not work together with the behavior I stated before. When I pull the battery and the USB connection to turn it off, and insert the battery back in, it immediately boots up. I'm not sure if I was too slow pressing VolUp+Home+Power, but my phone still says the aforementioned SEAndroid error.
Can anybody help the noob I am? In what state is my phone now? Do I understand correctly that it indeed wants to boot into Recovery, but does not like it because it is not fulfilling some "SEAndroid security stuffs"? =3
Thanks for all the help in advance.
PS: These are the lines if I get back into download mode:
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
Looks like I go another way now... just installing TWRP, what I mostly wanted (I think at least)...
When I was stuck with the SEAndroid boot all the time, I turned it off again and booted back into download mode, then flashed TWRP from here dl.twrp.me/klte/ (using the most recent *.tar file, and selecting it in ODIN as the PDA file).
After I did that, my S5 booted normally again. But as soon as I turned it off and tried to enter Recovery mode with VolUp+Home+Power, it first still spit out the 3 SEAndroid lines, but then TWRP showed up a second later... it offered me to install SuperSU as I wanted to reboot, which worked. When entering the SuperSU installer after my system booted, I selected the TWRP method to finally root my phone, and that seems to have worked. moving on now...
I just wonder if this is a normal procedure, or if I messed up somewhere so that it became so complicated.
Or maybe I'm just dumb.

Categories

Resources