Database Users

[Q] Kernel is not seandroid enforcing set warranty bit: Kernel - Boot loop ?

Hi guys,
Yesterday I updated to the new N9005XXUENA6 Leaked KitKat 4.4.2. Didn't really think much of it and finally decided to root the phone.
I rooted the phone with CF-Auto-Root thanks to chainfire. Anyway after that I installed CWM recovery as TWRP haven't really updated it since the new update for note 3.
Now i can get to the CWM recovery and after installing any rom
I tried
1. [JAN-13][hlte][1.2.4] AOSB Project (ProBAM ROM) - The End of The Line ! and then
2. [CM11][4.4.2][N9005][ROM][KERNEL][JAN13] temasek's UNOFFICIAL Build - V33
However, in both cases I get an error:
Kernel is not seandroid enforcing
set warranty bit: kernel
and keeps on boot looping.
I can get into download and recovery but cannot install any custom ROM's.
After a bit of looking around and what i gathered from similar questions,I tried installing a couple of kernels but still its a no go!.
Is it as a result of the new N9005XXUENA6 update? or me doing something idiotic?
P.S: Tried wiping data / factory reset, format partition / system, etc. Cannot find fix permissions in the new CWM however and cannot use TWRP as it just doesn't boot up into the recovery.
Thanks in advance.
Kratumay

kratumay said:
Hi guys,
Yesterday I updated to the new N9005XXUENA6 Leaked KitKat 4.4.2. Didn't really think much of it and finally decided to root the phone.
I rooted the phone with CF-Auto-Root thanks to chainfire. Anyway after that I installed CWM recovery as TWRP haven't really updated it since the new update for note 3.
Now i can get to the CWM recovery and after installing any rom
I tried
1. [JAN-13][hlte][1.2.4] AOSB Project (ProBAM ROM) - The End of The Line ! and then
2. [CM11][4.4.2][N9005][ROM][KERNEL][JAN13] temasek's UNOFFICIAL Build - V33
However, in both cases I get an error:
Kernel is not seandroid enforcing
set warranty bit: kernel
and keeps on boot looping.
I can get into download and recovery but cannot install any custom ROM's.
After a bit of looking around and what i gathered from similar questions,I tried installing a couple of kernels but still its a no go!.
Is it as a result of the new N9005XXUENA6 update? or me doing something idiotic?
P.S: Tried wiping data / factory reset, format partition / system, etc. Cannot find fix permissions in the new CWM however and cannot use TWRP as it just doesn't boot up into the recovery.
Thanks in advance.
Kratumay
Click to expand...
Click to collapse
if you are getting
Kernel is not seandroid enforcing
set warranty bit: kernel
on boot screen thats normal
try flash a rom then flash this straight after http://forum.xda-developers.com/showthread.php?t=2507403
should all work fine

jaythenut said:
if you are getting
Kernel is not seandroid enforcing
set warranty bit: kernel
on boot screen thats normal
try flash a rom then flash this straight after http://forum.xda-developers.com/showthread.php?t=2507403
should all work fine
Click to expand...
Click to collapse
Thanks for the reply,
So once again, I did a factory reset then flashed the rom and then flashed the file you recommended.
Still a no go
Same problem.

kratumay said:
Thanks for the reply,
So once again, I did a factory reset then flashed the rom and then flashed the file you recommended.
Still a no go
Same problem.
Click to expand...
Click to collapse
Based on what I read so far regarding the 4.4.2 update, if you flashed it on your device, there seems to be no way to go back to 4.3 ( I'm not sure if that means custom roms based on 4.3 as well ). Best thing to do is just flash the official 4.4.2 and hang in there until custom roms based on 4.4.2 comes out or people find a way to go back to 4.3. The reason the file from firasusman didn't work is probably because there might be difference in how kit kat deals with efs compared to jellybeans which it was written for in the first place.
Sent from my SM-N9005 using xda app-developers app

You probably are right as it doesn't really work. Anyway I'll keep waiting
Sent from my SM-N9005 using XDA Premium 4 mobile app

same here

Yip you won't be able to go to a lower bootloader than you are on with KK, CM based ROMs are currently running (MJ7) _ will have to wait until the new bootloader is implemented into new(er) builds.

Thanks for that info. Will keep an eye out. Cheers
Sent from my SM-N9005 using XDA Premium 4 mobile app

kratumay said:
Thanks for that info. Will keep an eye out. Cheers
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks

tritri71 said:
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
Click to expand...
Click to collapse
Before you did this was your 4.4.2 on KitKat working well? Or did you come from 4.3? If you came from a correctly installed 4.4.2 then do go to this thread and start from STEP 8
http://forum.xda-developers.com/showthread.php?t=2614787
download the files required from STEP 8 onwards.
This is CWM recovery and not TWRP. I dont have experience with TWRP.

tritri71 said:
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
Click to expand...
Click to collapse
I'm assuming you're on 4.3, you have to use this in pda/ap on odin. After flashing phone will restart with android and texts in color. After that it will reboot again to system and you will have root. SEandroid Enforcing is normal if you're rooting you're device. Have you checked with root checker if you have root? Also, once you root your device you will have to flash a custom recovery like cwm or twrp to be able to boot to those recovery.

Hakired said:
Before you did this was your 4.4.2 on KitKat working well? Or did you come from 4.3? If you came from a correctly installed 4.4.2 then do go to this thread and start from STEP 8
http://forum.xda-developers.com/showthread.php?t=2614787
download the files required from STEP 8 onwards.
This is CWM recovery and not TWRP. I dont have experience with TWRP.
Click to expand...
Click to collapse
Thanks a lot !
It Works !

tritri71 said:
Thanks a lot !
It Works !
Click to expand...
Click to collapse
Awesome enjoy kitkat

n9005 cm11 20140226 problems
yesterday i installed cm11 nightly 20140226 on my n9005 via twrp 2.6.3.7 (before i have had 4.3)
it all works fine except 2 little problems:
1. whenever i plug the charger or usb cable to computer, the phone is turned on automatically without pushing the power button.
2. my time & date settings can't be saved, and each time on turning on it goes back to 2013 and 12:00
Thanks in advance to all answers

Same problem
I got the same problem. I have Bobcat 4.3 installed and i'm trying to install Omegarom 4.4.2 but I get stuck in bootloop with '' Kernel is not Seandroid Enforcing ''

Kjetilz said:
I got the same problem. I have Bobcat 4.3 installed and i'm trying to install Omegarom 4.4.2 but I get stuck in bootloop with '' Kernel is not Seandroid Enforcing ''
Click to expand...
Click to collapse
First you will have to update to stock 4.4.2 then you can flash any 4.4.2 roms.

Need some help.Newbie here. I just recently bought a samsung n3 tmobile n900t. I wanted to flash an international ROM to remove those tmobile apps (since im using a different carrier) So I found this ROM here http://forum.xda-developers.com/showthread.php?t=2518249
Installed CWM and flashed the rom. Now i'm in the Kernel is not seandroid enforcing set warranty: kernel loop. What should I do to fix this?

Mediaspot said:
Need some help.Newbie here. I just recently bought a samsung n3 tmobile n900t. I wanted to flash an international ROM to remove those tmobile apps (since im using a different carrier) So I found this ROM here http://forum.xda-developers.com/showthread.php?t=2518249
Installed CWM and flashed the rom. Now i'm in the Kernel is not seandroid enforcing set warranty: kernel loop. What should I do to fix this?
Click to expand...
Click to collapse
The rom you flashed is based on android 4.3, if the phone you bought already have 4.4 then that is probably the cause of the loop. Flash another rom based on 4.4 or download stock firmware from sammobile and flash using odin.

hey_joe said:
The rom you flashed is based on android 4.3, if the phone you bought already have 4.4 then that is probably the cause of the loop. Flash another rom based on 4.4 or download stock firmware from sammobile and flash using odin.
Click to expand...
Click to collapse
I just tried flashing this rom but the same thing. http://forum.xda-developers.com/showthread.php?t=2671039 will try to look for stock firmware and be back with results

I am getting same error but after that phone boots up fine

[Q] Won't boot past the Galaxy S4 screen!

First of all I just want to say I am very new to the world of rooting and custom roms. I recently got bored of the original layout of my S4 and decided to root my phone and find a custom Rom. I rooted my phone and through Twrp I flashed android Kitkat 4.4.2 from AOKP. It seems that I either messed something up or the particular rom I downloaded doesn't work right. More than likely the first one. It ran okay for a minute or two then it started freezing and rebooting itself. I thought I would just go back to stock and restore from the backup I created but when I tried it said failed. I did some research and found a stock rom through Odin and tried to just revert back that way. That failed too and now my phone is stuck at the Galaxy S4 screen and at the top left it says kernel is not seandroid enforcing. Set warranty bit: kernal.
Any help would be greatly appreciated, I miss my phone! Lol. I apologize if any of my terminology is off also!

Sounds like the odin file you got was 4.2 and I'm guessing you were already stock 4.3. Find a mk2 4.3 Odin file and give that a shot.
Here's a link to a thread where you can get the files I mentioned.
http://forum.xda-developers.com/showthread.php?t=2509605
Sent from my SCH-R970 using Tapatalk

Okay I'll give that a shot. As a side note when I tried to restore my back up TWRP displayed a messaged saying that it appeared that my phone wasn't rooted. Slide to install now. Dunno if that makes a difference or not. I know for sure it was rooted unless the root check I did was wrong.. Lol

I myself use cwm so I'm not that familiar with twrp but I'm pretty sure the link I gave You is for stock unrooted so you'll have to reroot
Sent from my SCH-R970 using Tapatalk

Sacs 4.3 v5 ultra issues
I was running Sac's Custom ROM 4.3 v 4.4 and tried to update to the most recent version 5.5 Ultra. I download the ROM copied to SD Card. Using Philz recovery (devs preference) to wipe cache/davlic/factory reset etc...reboot into recovery...installed ROM. The phone will not get past boot screen. I can't post on the devs page because i am too new to the forum. Can you help me out here?

I plugged to phone into the charger when it was off last night and noticed that at first it had the stock S4 battey life indicator but after a second it changed to the android 4.4.2 one. Is there any way im stuck between 2 roms or anything like that?

I got it! Downloaded the stock firmware and flashed it through Odin! I'll re root it but I probably won't try a custom rom again for a while.. haha.

I've tried that same rom as you akop and it had an error with PhilZ.

I know with sacs it can be a little tricky with the multiple wipes and rebooting to recovery for more wipes but aosp custom ROMs Dont have near the steps. Just wipe data/cache/dalvic and format system then flash ROM and gapps and your good to go!
Sent from my SCH-R970 using Tapatalk

Won't boot past the galaxy s4 screen
I am very new to the world of rooting. I recently tried to root my t-mobile S4 m919 running 4.4.2. I rooted my phone with http://forum.xda-developers.com/galaxy-s4-tmobile?nocache=1&z=9919900225941092#root I did everything exactly as on the video but when I rebooted after going through clockwork mod and flashing ROOT_M919UVUAMDL.zip It reboots to the galaxy s4 screen and at the top left it says kernel is not seandroid enforcing. Set warranty bit: kernel. It just stays on that screen. anyone help please. I would either like to get my phone working again or finish the root.
---------- Post added at 10:14 PM ---------- Previous post was at 09:52 PM ----------
When I try to try to boot into recovery it also stays on the galaxy s4 screen saying recovery booting... in the left corner stuck

SOLVED recovery is not seandroid enforcing set warrenty bit : recovery --> loop

after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?

Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap

fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.

hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man

TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred

thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!

nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD

Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast

Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....

Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.

Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of

Thanks!
Thank you very much,you save me a lot of trouble.

hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot

billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?

hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6

billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat

hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery

billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.

hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin

billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.

[Q] Custom Recovery Problems

I have an ATT galaxy s4 rooted with Towelroot. I've tried using GooManager to install TWRP but all it did was prevent me from booting into the recovery, I was able to get out of the loop by holding volume down and the home button and then hitting volume down to cancel going into download mode. Next I tried using Rom Manager to install CWM but the same thing happened. Now I can no longer boot into recovery, it just fails and goes into download mode. My question is should I just flash the stock recovery or is there a way to get a custom recovery?
Android Version, 4.4.2
Model Number, SAMSUNG-SGH-I337
Baseband Version, I337UCUFNC1
Kernel Version, 3.4.0-1125940
Build Number, KOT49H.I337UCUFNC1
Security Software Version, MDF v1.0 Release 2
I didn't know what you needed so I just put everything here, let me know if I missed something or you need to know anything else.

binavik said:
I have an ATT galaxy s4 rooted with Towelroot. I've tried using GooManager to install TWRP but all it did was prevent me from booting into the recovery, I was able to get out of the loop by holding volume down and the home button and then hitting volume down to cancel going into download mode. Next I tried using Rom Manager to install CWM but the same thing happened. Now I can no longer boot into recovery, it just fails and goes into download mode. My question is should I just flash the stock recovery or is there a way to get a custom recovery?
Android Version, 4.4.2
Model Number, SAMSUNG-SGH-I337
Baseband Version, I337UCUFNC1
Kernel Version, 3.4.0-1125940
Build Number, KOT49H.I337UCUFNC1
Security Software Version, MDF v1.0 Release 2
I didn't know what you needed so I just put everything here, let me know if I missed something or you need to know anything else.
Click to expand...
Click to collapse
Since you are on the NC1 firmware the only recovery software you can use is Safestrap 3.72. You can read more about safestrap in here.

tsonav peculiar
sway8966 said:
Since you are on the NC1 firmware the only recovery software you can use is Safestrap 3.72. You can read more about safestrap in here.
Click to expand...
Click to collapse
Thanks for the quick reply. I installed Safestrap 3.72 then hit Install Recovery, however the state still says Not Installed, also Reboot to Recovery option is greyed out. I tried going into the recovery manually with the same result as the previous 2.

You need to change selinux mode to permissive. The. Safestrap will be able to install recovery
Sent from my SGH-I337 running GPE using Tapatalk

means ynlyof
jmjoyas said:
You need to change selinux mode to permissive. The. Safestrap will be able to install recovery
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Sorry for the noob question but I am completely new to this, how exactly do I go about changing the selinux mode to permissive?

Ok, so I used SELinuxModeChanger to change selinux to permissive, and safestrap now installed. Now when I use the button combination Volume Up, Home and Power, it still does the same thing. If I allow it to boot normally I get a red message saying Safestrap Disabled starting system in 10 seconds, then 2 options at the bottom for booting into recovery and to continue. Is this normal or did I do something wrong?

That's perfectly normal.
Due to the locked boot loader, we cannot replace the stock recovery. Safestrap works around this by being available in normal boot mode.
Safe strap originally supported ROM slots (multi boot) and would show enabled when one of the ROM slots was selected. We can only use the stock slot, so don't worry about the disabled part.
Sent from my SGH-I337 running GPE using Tapatalk

jmjoyas said:
That's perfectly normal.
Due to the locked boot loader, we cannot replace the stock recovery. Safestrap works around this by being available in normal boot mode.
Safe strap originally supported ROM slots (multi boot) and would show enabled when one of the ROM slots was selected. We can only use the stock slot, so don't worry about the disabled part.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply and clearing that up. However I would like to know if there is any way to get back the stock recovery? It is a bit annoying that every time my phone turns off that it gets stuck in a little loop. Also this error message shows up on my phone and if anyone opens it, it immediately goes back into the loop. My mother loves playing with my phone a lot so I can see future problems coming. Anyway for me to flash the stock recovery back on?

You can uninstall recovery from the safestrap app
Sent from my SGH-I337 running GPE using Tapatalk

I did that but I am still not able to boot into the stock recovery, it just keeps getting stuck in the loop.

binavik said:
I did that but I am still not able to boot into the stock recovery, it just keeps getting stuck in the loop.
Click to expand...
Click to collapse
Check the NB1 ODIN thread and see if there's a link to just the recovery. If not you'll have to extract and flash it from the full tar with heimdall or package it in a zip or use an app or something.

DeadlySin9 said:
Check the NB1 ODIN thread and see if there's a link to just the recovery. If not you'll have to extract and flash it from the full tar with heimdall or package it in a zip or use an app or something.
Click to expand...
Click to collapse
When searching the forums I found this post http://forum.xda-developers.com/showthread.php?p=52167761. It seems like the correct stock recovery. So I just download this, go into Odin, put my phone into download mode, then what? I've never used odin before but I assume that I would need to point it to the file but not exactly sure under which slot or which options to be checked.

binavik said:
When searching the forums I found this post http://forum.xda-developers.com/showthread.php?p=52167761. It seems like the correct stock recovery. So I just download this, go into Odin, put my phone into download mode, then what? I've never used odin before but I assume that I would need to point it to the file but not exactly sure under which slot or which options to be checked.
Click to expand...
Click to collapse
Never flashed it before, but the op says to put it in the PDA slot. Just have auto robot and f.rest checked. Do not have partition checked
Sent from my Nexus 5 using XDA Free mobile app

Thanks everyone. My stock recovery is up and running again and I also now have safestrap as well. That stock recovery file worked just fine, I just had to put it under AP for odin 3.09.

Can't Root & Install CWM Recovery on Samsung Note 4

Hi Guys
I believe you guys on here will be able to help. Let me first tell you about my device and what I want to do and then what I did and what problems I encountered.
Device: Samsung Note 4 International Model SM-N910H (Exynos CPU)
OS: 6.0.1
Build Number: MMB29K.N910HXXU2DPE2
I only want to root my device and install Custom Recovery like CWM. I don't want to install a Custom ROM!
So I downloaded CF-Auto-Root-tre3g-tre3gxx-smn910h.tar.md5 and used Odin 3.12 to flash tar file to phone. After that phone rebooted and got stuck into the "Samsung Galaxy Note 4" Screen displaying in red letters on top left Corner "Recovery is not seandroid enforcing"
So I downloaded CWM Recovery v6.0.3.6.tar and flashed with Odin again, this time the phone rebooted back into my Working Phone OS and all seems fine. SO I wanted to test if CWM is installed? Powered phone down and booted into recovery & then got the same "Recovery is not seandroid enforcing" message on screen, so rebooted phone normally and it goes back into the OS. Also SuperU is not installed and phone is not rooted
So how do I solve this issue getting a Custom Recovery on my Phone Since I don't have any Recovery Mode option when booting into recovery. Your help, effort and time will be appreciated

Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.

Thanks a mil, however I did manage to fix the issue and still wanted to resolve this post. I downloaded SuperU Beta 2.74 and different version of CWM. Installed CWM 6.0.5.1 (1113).tar with Odin 3.10.7 and it worked installing CWM Recovery. Then installed the SuperU 2.74 with CWM and everything works great. Phone now rooted and CWM installed :good::victory::victory:
******** Resolved ************

wilcovh said:
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Click to expand...
Click to collapse
I have the n9100 as well with the hong kong rom. I'm having the same problem while trying to root with cf-autoroot. I really want to root the phone while keeping the stock rom.
Is there any way to do so??