Database Users

Soft Bricked

Hi everyone!
So I was a complete fool and with my (rooted) galaxy s4 running 4.4.4 (or 4.4.2) kitkat I downloaded the Lolipop update for my Bell SGH-1337m.
I used an Xda module to change my status from "custom" to something along the lines of "stock" and was then able to download the lolipop update. I should mention that i had clockworkmod installed on this phone, but before the update I had also unchecked all my xposed modules. So then I went to update...
now whenever I try to boot I get "Recovery is not seandroid enforcing" with another message "set warrenty bit: recovery". These two messages also appear even after I boot into recovery (just with "Recovery Booting..." text coming first followed by the rest)
I have attempted flashing multiple ROMS through Odin, as well as a stock recovery file. I am still stuck at this boot process.
Any help would be greatly appreciated as I'm in a new city and need my phone to get around... yeah... I screwed myself :laugh:

"Recovery is not SEAndroid Enforcing" is normal. All that's telling you is that the custom recovery is still installed. With a custom kernel, the message would be "Kernel is not SEAndroid Enforcing" and would appear on the S4 splash screen.
Have you attempted to flash the ROM via Odin with a .PIT file for the I337M? If not, you should find one over in the forums where this should have been posted, http://forum.xda-developers.com/galaxy-s4-att . Fortunately, in the international S4 forums here, the question is general enough that we should be able to help you anyway.
The .PIT file provides Odin with the correct partition information for your S4, which can ensure the ROM gets installed properly.

Strephon Alkhalikoi said:
"Recovery is not SEAndroid Enforcing" is normal. All that's telling you is that the custom recovery is still installed. With a custom kernel, the message would be "Kernel is not SEAndroid Enforcing" and would appear on the S4 splash screen.
Have you attempted to flash the ROM via Odin with a .PIT file for the I337M? If not, you should find one over in the forums where this should have been posted, http://forum.xda-developers.com/galaxy-s4-att . Fortunately, in the international S4 forums here, the question is general enough that we should be able to help you anyway.
The .PIT file provides Odin with the correct partition information for your S4, which can ensure the ROM gets installed properly.
Click to expand...
Click to collapse
OK great! Hopefully I'll find the answer for a .PIT file in terms of setting it up with Odin, I suppose it has something to do with the "re-partition" option in odin, but I'm not doing ANYTHING without a tutorial first
I'll get back to you after I've tried it with a SGH-1337M .PIT file, hopefully I can find one... (Canadian S4 variant, same hardware as AT&T but just the M is different)

You are correct in that it has to do with the re-partition option in Odin. You should have an option to browse to the .PIT file, so Odin knows where to find it. Once Odin sees the file, check "re-partition", and then flash a stock ROM.

Problem with root

anyone can help me with rooting ? .. i have some issue to root S5 SM-G900F, tried both the cm and twrp with odin and after odin finishes his doing, the phone reboots, writing seandroid enforcing recovery ... and after that the phone turns off, tried diffrent versions of odin 3.09,3.07,1.85 same issue
with the cf recovery, after flash, the only way to make the phone working again is to flash G900F_BTU_G900FXXU1BOH4_G900FOXA1BOH4_Original
because it keeps writing seandroid enforcing recovery ... and after that the phone turns off.
anyone have an idia ? ;]
also tried not to tick the reboot on odin and remove battery like some thread on xda said. same ****

CF Auto Root & ODIN

i tried CF Auto Root & ODIN
it's not working

anyone have fix to this issue ?

I'l try to flash to an older version (kitkat) and see if it will help to root it, maybe the lollipop version making problems

cannot root s5 (G900F) running lollipop

Hi everyone
This is my second s5. I managed to root the first one using cf autoroot and twrp recovery.
However this new phone runs lollipop and I cannot flash either cf autoroot or twrp recovery. I used odin and the flash completes with PASS message. However when I try to reboot to recovery I just get RECOVERY IS NOT SEANDROID ENFORCING message then the screen goes blank.
I have tried downgrading to kitkat but I am still getting the same message.
Has anyone got an idea of what is going on here?
Thanks
Jeff

Try flashing TWRP 2.8.7.0 with ODIN if you haven't tried that version yet, seems to work for some people with the same problem
Try different ODIN versions too, 3.07 > 3.10.7

Brilliant!! I flashed with TWRP 2.8.7.0 and it works.
Thank you so much. Jeff

Nice one

Problem with CF autoroot (SM-G900T)

I just purchased a galaxy S5 Tmobile version SM-G900T and want to root to install CM13. I watched a youtube video about CF autoroot, downloaded it and Gapps. I run CF autoroot via ODIN and it shows that it is complete. Reboots numerous times, then loads but I never get Superuser. I notice it says recovery is not seandroid enforcing when going through the process. I also now have a set warranty bit kernel on the top when it is booting as well.
Anyone have experience with this issue and can help?

Try this
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2

*Detection* said:
Try this
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Click to expand...
Click to collapse
This worked...now running CM13! Thanks.

:good:

Chainfire auto root FAILED Samsung Galaxy J3 SM-J320R4

Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:

LeviathaninWaves said:
Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
Click to expand...
Click to collapse
Yes please help

not sure what I did differently, but I seem to have root now by using Chainfires AutoRoot for my Samsung Galaxy J3 SM-J320R4. SuperSu is installed and working

LeviathaninWaves said:
Hello all.
I went ahead and downloaded the cf auto root tar for this phone and gave it a shot through ODIN. I followed all instructions, the model number and Android version matches the autoroot file.
I have a Samsung Galaxy J3 SM-J320R4, Marshmallow 6.0.1,
Build MMB29M.J320R4TYU1APE1. USB debugging on, OEM Unlock on, Verify apps through USB off. I go into download mode, flash the autoroot file, phone gets stuck at boot.
Recovery is not seandroid enforced.
It's impossible for me to access recovery using any method (pulling battery, Volup+home+power or Volup+voldown+home+power) I can only reflash stock at this point. So I've done that, reattempted root, tried different ODIN settings, all unsuccessful. Towelroot, KingRoot and kingo root all unsuccessful as well.
My questions
1) Why is it failing?
2) What does "RECOVERY IS NOT SEANDROID ENFORCED" mean?
3) How can I pull the stock recovery.img off this device for Chainfire?
4) If nothing else, where can I find documentation on systemless root and other relevant info to cook up my own root method? Or I should ask, how does Chainfire do it? What do I need to know?
Hey thanks everyone for your time. :good:
Click to expand...
Click to collapse
It took forever to reboot. apparently the kernel was trying to hang. Ive still to get TWRP recovery to load, but we were given a big hint. I am crunching files right now, but my phone says it"s rooted, and I'll check more later.
---------- Post added at 01:53 AM ---------- Previous post was at 01:49 AM ----------
Phone is working