Develop Bugs

Can't reach other recovery than android system recovery3e

Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2

Revert back to recovery problem
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
Having same issue with SGH-T889. Any help? Heard of similar issue with Nexus 4. They have revert recovery disabler. Not tried on my Note 2. Is similar solution available for T889?

After flashing recovery in Odin are you booting up the phone (or is odin - i.e. auto reboot is checked)? There is a file (/system/etc/install-recovery.sh) that you need to disable to have recovery "stick". There are a few ways to do this, but my preference has been to do it within cwm/twrp recovery via adb after flashing in odin but prior to first bootup of phone.
Hope that helps!

Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2

^^ this

same prob
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.

Nintendoassasin64 said:
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Click to expand...
Click to collapse
I know you can't access CWM Recovery..
Allot of us use TWRP Recovery and it works great. I think it is safe to say it is a Superior Recovery now. I suggest you use that Recovery.
You can get it installed easily by downloading GooManager from the play store, opening the app, hit your menu button and tap Install Open Recovery Script. That's it. Quick and easy!

For the people having a hard time, are you rooted? If you are just download goomanager and use it to install twrp
Sent from my SGH-T889 using xda app-developers app

Finally got fixed
I tried by un ticking the "Reboot" in Odni and manually pulled out battery and cable and tried Recovery mode... it went smoothly as expected... thanks dude

This works when everything else fails!
dj_spore said:
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Been looking for a solution for hours and the android system recovery was feeling like a thorn in the foot that will never go away. But surprise, surprise, your simple suggestion did the trick!
Thanks a ton!! :good:

Clock work mod problem, please help

Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.

Have you tried twrp?

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly

this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see

+1 for twrp

athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.

drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.

aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help

xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.

androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you

athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.

athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?

drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks

xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you

athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.

xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks

athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM

Prevention Information ERROR

Hi i have the following error :
When i try to click on WI-FI button comes up the following
prevention information
the device has detected an application attempting unppermitted actions and has stopped loading.To protect your device it is recomended you reboot.
I have rooted my phone using the topic here
http://forum.xda-developers.com/showthread.php?t=2258633
i had to load the
http://k0nane.info/rom/SGH-M919-UVUAMDB-k0nane.7z
file first cos i was getting an failure when installing the superuser using odin 3.0.7
my recovery is TWRP 2.5.0.0 and i am on wicked v1
Anyone else have this issue?

I had the same issue if you check the build number and the baseband version they are not the same. If you re-odin the MDL build http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip again then WIFI should work again. I got it rooted after that by doing the following:
1. Load the OUDHS CWM-Based Recovery 1.0.3.3 for T-Mo GS4, via odin uncheck auto reboot and goto to recovery http://k0nane.info/rom/OUDHS-Recovery-jfltetmo-1.0.3.3.tar
2. Install Chainfire's SuperSU http://www.shabbypenguin.com/Android/Scripts/Nexus-Files/Root/SuperSU-v1.25+.zip then
3 Install [KERNEL] Stock Touchwiz MDB - SetUID Restriction Removed http://d-h.st/GcM
Between installs make sure you wipe the cache and davik cache
then you reboot you should be rooted with the newest update MDL minus the kernel lock

yes its not same the build and the baseband
Is it possible to be done using the twrp?
other recovery was little difficult?
can u send me the links i need please i just don't want to mess around and brick my phone
Thanks a lot

kaniebas said:
yes its not same the build and the baseband
Is it possible to be done using the twrp?
other recovery was little difficult?
can u send me the links i need please i just don't want to mess around and brick my phone
Thanks a lot
Click to expand...
Click to collapse
Check my post again, I couldn't get TWRP to work at first but it maybe i did not uncheck the the auto reboot box when I did that. Once the the recovery is loaded via odin you need to pull the battery then do the home-up volume-power to get into the recovery. I notice TWRP was a bit too sensitive and could not scroll down the list of folders to get to the zip files

dhonzik said:
Check my post again, I couldn't get TWRP to work at first but it maybe i did not uncheck the the auto reboot box when I did that. Once the the recovery is loaded via odin you need to pull the battery then do the home-up volume-power to get into the recovery. I notice TWRP was a bit too sensitive and could not scroll down the list of folders to get to the zip files
Click to expand...
Click to collapse
i manage to install CWM using odin and when i rooted it i install goo manager ant now i am on TWRP

I've tried installing all three recoveries using Odin, but for some reason none are working and now when I try and boot into recovery it just restarts the phone. Anyone know what I should do?

oasad92 said:
I've tried installing all three recoveries using Odin, but for some reason none are working and now when I try and boot into recovery it just restarts the phone. Anyone know what I should do?
Click to expand...
Click to collapse
You need to uncheck the auto reboot box in odin, after the recovery transfer is complete pull the battery and unplug from your computer then do a boot into recover by holding the volume up-home-power button. If not rooted follow the instructions in my post above at the very least you need to load the kernel file

dhonzik said:
You need to uncheck the auto reboot box in odin, after the recovery transfer is complete pull the battery and unplug from your computer then do a boot into recover by holding the volume up-home-power button. If not rooted follow the instructions in my post above at the very least you need to load the kernel file
Click to expand...
Click to collapse
So I did that with all 3 recoveries like 2 or 3 times each, nothing was working I unchecked reboot then would just pull battery after reboot and hold vol up and power to try and get into recovery. Sometimes the litlte blue would appear in the top left corner saying "recovery booting" and would just stay there forever other times that would appear and then the phone would just reboot itself.
Anyway finally found instructions that allowed said to try checking auto reboot and f time reset so did that with a TWRP recovery tar and then it finished and rebooted. I then shut the phone off and held power and vol up to get into recovery and it loaded fine. I was then able to flash the chainfire superuser and kernel you posted. So Thanks a bunch man!

Rooting S4

I have tried over and over to root my device and install Jedi S4. I am going through the process for the updated S4 for the UDID problem.
I have ODIN'd TWRP, then installed MDB-SetUIDOff.zip then SuperSU. At this point everything is fine. Then when I install JediS4 it appears to go okay but not very quickly, I hit reboot and I am hit with a "It appears your device is not rooted" would you like to install superuser?.......
If I hit no and reboot it just sits at samsung screen.... What am I doing wrong here?
I have tried the file T-Mobile_OUDHS-Recovery-jfltetmo.tar in ODIN as outlined by another site to no avail as well. It apparently places the stock recovery with the UDID issues fixed then roots the device.
Would appreciate any assistance in this matter.
Thank you,
CJ

Just use the RootUVUAMDL zip in recovery and that's it. All I did was flash cwm in odin then once I rebooted into recovery I flashed the Root zip I have been straight every since then.
Sent from my SGH-M919 using Tapatalk 2

jtkknj said:
I have tried over and over to root my device and install Jedi S4. I am going through the process for the updated S4 for the UDID problem.
I have ODIN'd TWRP, then installed MDB-SetUIDOff.zip then SuperSU. At this point everything is fine. Then when I install JediS4 it appears to go okay but not very quickly, I hit reboot and I am hit with a "It appears your device is not rooted" would you like to install superuser?.......
If I hit no and reboot it just sits at samsung screen.... What am I doing wrong here?
I have tried the file T-Mobile_OUDHS-Recovery-jfltetmo.tar in ODIN as outlined by another site to no avail as well. It apparently places the stock recovery with the UDID issues fixed then roots the device.
Would appreciate any assistance in this matter.
Thank you,
CJ
Click to expand...
Click to collapse
When it says "would you like to install superuser" have you tried hitting yes? Also, if all you're seeking is root I would say to try flashing CF-Auto-Root in Original Android Development. If you want the custom recovery too, then either download and flash the Odin flashable TWRP recovery or boot into the ROM and installi Goo Manager and let it install TWRP for you.

Try CF auto root. Or if ur using the custom recovery tar in Odin, uncheck auto reboot and pull out the battery after u flash it in Odin. Then u will able to get to the custom recovery.
Sent from my GT-I9505G using xda premium

[Q] Note 3 "RECOVERY IS NOT SEANDROID ENFORCING"!!! Help!??

Ok, So I just bought the Tmo Note 3 and was looking to root it
I went on youtube and found the Auto-root method
I downloaded the auto-root files, open Odin, put the CF-Auto root.tar.md5 in the PDA section of Odin and clicked start.
when it was done my phone rebooted into a screen with 3 lines on top saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Can anyone please help me?
Phone was on 4.3
I can also still go to Download mode but cannot boot into android or into a recovery it just boots to those 3 lines above.
Help?

The same thing happen to me when I tried installing clockwork mod recovery and twrp recovery. I had to go to the website sammobile.com and download the original firmware MD5 file (2,218,421kb) put the phone in download mode and re flash the whole thing and start over. I still can't get a custom recovery to work. Can anyone shed light on this? Thanks

Reflash the recovery.
Mine shows the same, pauses and then boots into the recovery (TWRP in my case).

dbrow said:
The same thing happen to me when I tried installing clockwork mod recovery and twrp recovery. I had to go to the website sammobile.com and download the original firmware MD5 file (2,218,421kb) put the phone in download mode and re flash the whole thing and start over. I still can't get a custom recovery to work. Can anyone shed light on this? Thanks
Click to expand...
Click to collapse
Yea thats what im doing, the download is taking forever but i thought it would work... thanks!

krelvinaz said:
Reflash the recovery.
Mine shows the same, pauses and then boots into the recovery (TWRP in my case).
Click to expand...
Click to collapse
you mean re-flash the CF-AutoRoot.tar.md5 file?
How exactly did you get it to boot into a custom recovery?

No prob! Yeah it took me about an hour.
Sent from my SM-N900P using xda app-developers app

Just had this happen to me also. I just downloaded philz recovery .tar and flashed through odin. I still cant get a custom recovery but it got me out of my bootloop and back into my system
Sent from my SM-N900T using xda app-developers app

Sammydr10 said:
Ok, So I just bought the Tmo Note 3 and was looking to root it
I went on youtube and found the Auto-root method
I downloaded the auto-root files, open Odin, put the CF-Auto root.tar.md5 in the PDA section of Odin and clicked start.
when it was done my phone rebooted into a screen with 3 lines on top saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Can anyone please help me?
Phone was on 4.3
I can also still go to Download mode but cannot boot into android or into a recovery it just boots to those 3 lines above.
Help?
Click to expand...
Click to collapse
You should have done the 4.4 update then rooted. .........
Sent from my SM-N900T using Tapatalk

bipoler said:
You should have done the 4.4 update then rooted. .........
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thats what I did now lol

Sammydr10 said:
Thats what I did now lol
Click to expand...
Click to collapse
Lol good papi
Sent from my SM-N900T using Tapatalk

Ok so I updated to 4.4 and then flashed the CF-AutoRoot.tar.md5 file
I now have root
I downloaded Rom manager and tried installing CWM Recovery -- it installed but when i tried rebooting into recovery Im just stuck in a boot loop with the screen I had at the start of this thread which is
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Any help!??

Sammydr10 said:
Ok, So I just bought the Tmo Note 3 and was looking to root it
I went on youtube and found the Auto-root method
I downloaded the auto-root files, open Odin, put the CF-Auto root.tar.md5 in the PDA section of Odin and clicked start.
when it was done my phone rebooted into a screen with 3 lines on top saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Can anyone please help me?
Phone was on 4.3
I can also still go to Download mode but cannot boot into android or into a recovery it just boots to those 3 lines above.
Help?
Click to expand...
Click to collapse
That is where I was getting my issues, I downloaded the 6.19.3 .tar from http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte and flashed through odin twice in order for it to stick.

Sammydr10 said:
Ok so I updated to 4.4 and then flashed the CF-AutoRoot.tar.md5 file
I now have root
I downloaded Rom manager and tried installing CWM Recovery -- it installed but when i tried rebooting into recovery Im just stuck in a boot loop with the screen I had at the start of this thread which is
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Any help!??
Click to expand...
Click to collapse
Download philz recovery and flash with ODIN. The warning about recovery is normal once you have a custom recovery installed.
This thread should help you. http://forum.xda-developers.com/showthread.php?t=2672393

prycem said:
Download philz recovery and flash with ODIN. The warning about recovery is normal once you have a custom recovery installed.
This thread should help you. http://forum.xda-developers.com/showthread.php?t=2672393
Click to expand...
Click to collapse
Thanks for putting on the right path.
Thanks to everyone who helped me out

I would highly suggest twrp 2.7. Less compatibility issues. Its more than just a personal preference thing.
Sent from my Nexus 7 using Tapatalk

prycem said:
Download philz recovery and flash with ODIN. The warning about recovery is normal once you have a custom recovery installed.
This thread should help you. http://forum.xda-developers.com/showthread.php?t=2672393
Click to expand...
Click to collapse
DUDE THANKS, YOU SAVED ME.I WAS VERY NERVOUS. U SAVED ME FROM MY DAD
#10000 repped if I can.. but really, Thanks dude I really appreciate it

No problem man. Glad that I helped.
Sent from my SM-N900T using XDA Free mobile app

prycem said:
Download philz recovery and flash with ODIN. The warning about recovery is normal once you have a custom recovery installed.
This thread should help you. http://forum.xda-developers.com/showthread.php?t=2672393
Click to expand...
Click to collapse
I flashed philz through odin and saw the warning about recovery. recovery still booted though, but i wasnt sure if i was in trouble. So its normal you say?

Yes. That message is normal for any non stock recovery.
Sent from my SM-N900T using XDA Free mobile app

Today a miracle occurred.
I have a n900-p Sprint that was rooted months ago and today I stupidly was messing with ROM manager and hit "reboot into recovery"
My phone went in to a boot loop with this "recovery is not seandroid enforcing" message right before bed time and I was in boot loop hell.
Some quick googling brought me here and gratefully I used some of your info to save myself on first try.
Step-by-step for any Googlers passing through:
1. Download Odin and your stock android rom (by pure dumb luck I remembered the last three letters from when I was screwing around on the settings screen earlier in the day.
2. Run As Administrator Odin and put your phone in download mode (pull battery, wait ten seconds, hold down VOL down + Power + front key)
3. Plug in your busted phone
4. Hit AP button in Odin and find your stock android rom you d/l earlier
5. after you get a blue box under ID:COM in Odin, hit start
6. pray
7. boom, when its done everything is back to normal.
If a monkey as dumb as me can pull it off, so can you. Good luck internet strangers.