Soft Bricked - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

Can't root after upgrading to KitKat

When I try to flash CF-Auto-Root, my phone goes into a recovery boot loop and It just says:
"Kernel Is Not Seandroid Enforcing
Set Warranty Bit: Kernel"
Then it reboots, and goes to that page again, and so on. I reflashed stock 4.4 and tried rooting again, but with no success.
Any help please would be appreciated!
If it helps, my phone is a Rogers Canadian Variant SM-900W8.
3teenth said:
When I try to flash CF-Auto-Root, my phone goes into a recovery boot loop and It just says:
"Kernel Is Not Seandroid Enforcing
Set Warranty Bit: Kernel"
Then it reboots, and goes to that page again, and so on. I reflashed stock 4.4 and tried rooting again, but with no success.
Any help please would be appreciated!
If it helps, my phone is a Rogers Canadian Variant SM-900W8.
Click to expand...
Click to collapse
this link could be help you:http://forum.xda-developers.com/showthread.php?t=2614772
For anyone who has this issue, I found a solution. In the CF-Auto-Root thread, download and flash the "CF-Auto-Root-hlte-hltexx-smn9005.zip" instead of the one made for your carrier as the stock recovery image in that one is actually updated for 4.4. It worked flawlessly for my phone.

[Q] Kernel is not seandroid enforcing Bootloop.

I found a few of these topics but cant seem to find a solution.
1. I flashed CF-Auto-Root-klte-kltexx-smg900f using odin 3.09
2. Then flashed philz_touch_6.26.1-klte.tar using odin 3.09
3. From there booted into philz i whiped to clear for new ROM and installed http://forum.xda-developers.com/showthread.php?t=2741302 from my ExtSD
Now after this it goes into a bootloop telling me
"Kernel is not seandroid enforcing
Set warranty bit : kernel"
I then found out from there topics i had something to do with Knox, so i then flashed "Nordic_countries_G900FXXU1ANE4_G900FNEE1ANF1_NEE" using Odin 3.09.
And it boots fine, but since i want a new ROM and didn't find out what did it, it happens every time i try flash the custom ROM.
I got a Samsung SM-G900F.
What am i missing?
Kiggerbare said:
I found a few of these topics but cant seem to find a solution.
1. I flashed CF-Auto-Root-klte-kltexx-smg900f using odin 3.09
2. Then flashed philz_touch_6.26.1-klte.tar using odin 3.09
3. From there booted into philz i whiped to clear for new ROM and installed http://forum.xda-developers.com/showthread.php?t=2741302 from my ExtSD
Now after this it goes into a bootloop telling me
"Kernel is not seandroid enforcing
Set warranty bit : kernel"
I then found out from there topics i had something to do with Knox, so i then flashed "Nordic_countries_G900FXXU1ANE4_G900FNEE1ANF1_NEE" using Odin 3.09.
And it boots fine, but since i want a new ROM and didn't find out what did it, it happens every time i try flash the custom ROM.
I got a Samsung SM-G900F.
What am i missing?
Click to expand...
Click to collapse
First root a stock ROM and be sure SU is installed and on that same ROM run SU, then you should be able to disable KNOX, after that you can go and use custom ROMs.
For good step by step instructions go here:
http://galaxys5root.com/galaxy-s5-root/how-to-root-galaxy-s5/

[Q] Recovery is not seandroid enforcing

Just got a Galaxy S4 i9505 rotted it with Kingo Root, installed rashr went to flash something and it installed a recovery and now I get Recovery is not seandroid enforcing, but researched it up and used odin to get past that, but now everytime i try to get into recovery I get that error again.
How can I reflash a recovery that works? I have tried re-rooting again but nothing.
Now it just doenst seem to start just shows the Samgung logo and does nothing.
What exactly are you saying? That you can't boot into recovery?
Rooting has nothing to do with a recovery.
Install TWRP recovery with Odin.
You could also try flashing a bootloader or the stock rom again to make your phone boot. And root properly with CF Auto Root
I meant it like the root program I used that installed the original recovery, I have tried TWRP with odin but it says it is done but still wont boot or go into recovery
How owuld I flash the stock rom?
Was meant to click edit not double post sorry
You have to untick "Auto reboot" in odin. After twrp flashed turn off the phone and use the key combination to boot into recovery.
I think i flashed an older version of twrp cant find a link to a jar for 5.0.1
Ok i managed to get twrp working, but it still alwayss just shows the Samsung logo
Just to clarify one thing here for the audience, "Recovery is not SEAndroid Enforcing" is not an error. All custom recovery images are set to permissive mode to enable them to perform their magic. Since this is a hole in the device's security, the bootloader displays that message to let you know this. A similar message is displayed when a custom kernel is installed, except in that case the message is "Kernel is not SEAndroid Enforcing". Since this is an expected message, the only way to properly get rid of it is to not install a custom recovery or, in the case of the kernel warning, a custom kernel.
@Apexpredator12, with your S4 in its current state, you should flash your stock ROM via Odin and make sure your device is totally operational. After that, use Odin to install CF-Autoroot. DO NOT USE KINGOROOT! With CF-Autoroot you will have your S4 rooted. From there, if you wish you can install a custom recovery, though with the caveat that installing a custom recovery will result in a "Kernel is not SEAndroid Enforcing" message. As mentioned above, this is a normal message and not an error.
Ok thank you, where can I get a stock rom for the i505 only seeing custom ones
I am just so foncused I am used to the SP that was quite easy to do, the version I have is 5.0.1 the stocks I have found are 4.4 etc and just not sure what ones to use without bricking my phone again
If you have a 5.0.1 stock ROM, you can use that. If you really need earlier ROMs, you can get them from samsung-updates.com or sammobile.com.
Yeah I was looking but they seem to be .img files which I cant seem to flash with odin
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Strephon Alkhalikoi said:
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Click to expand...
Click to collapse
I have tried loading a .img with odin but it doesnt seem to detect them
Apexpredator12 said:
I have tried loading a .img with odin but it doesnt seem to detect them
Click to expand...
Click to collapse
You are extracting to much. You can't flash .img with Odin as far as I know. You need to flash the archive in which the .img is packed.
Lennyz1988 said:
You are extracting to much. You can't flash .img with Odin as far as I know. You need to flash the archive in which the .img is packed.
Click to expand...
Click to collapse
I have managed to get stock installed with odin everything works but I cant find CF-Autoroot for galaxy s4 i9505 version 5.0.1
Strephon Alkhalikoi said:
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Click to expand...
Click to collapse
EDIT: managed to fix the twrp thanks allot for your help much appreciated.

Kernel Is Not Seandroid Enforcing - wont restart after using the correct auto-root

Guys! I need help
I have tried to root my Samsung S7 devise using the Odin tool and identifying the correct auto-root file at autoroot chainfire eu
I have a Samsung S7 Edge model SM-G935F.
I followed the instructions to the download mode, ran the Odin tool and choose the md5-file. The Odin runs succesfully with the 'PASS!' message. The phone then starts to re-boot but stalls with the logo and the message 'Kernel is not seandroid enforcing'
I have checked several help-videos on Youtube and checked this forum, but none of them applies to my problem. The all solve it by using the auto-root file fitting their phone. But this is what I am doing!
What to do?
Thanks!
Nvinther said:
Guys! I need help
I have tried to root my Samsung S7 devise using the Odin tool and identifying the correct auto-root file at autoroot chainfire eu
I have a Samsung S7 Edge model SM-G935F.
I followed the instructions to the download mode, ran the Odin tool and choose the md5-file. The Odin runs succesfully with the 'PASS!' message. The phone then starts to re-boot but stalls with the logo and the message 'Kernel is not seandroid enforcing'
I have checked several help-videos on Youtube and checked this forum, but none of them applies to my problem. The all solve it by using the auto-root file fitting their phone. But this is what I am doing!
What to do?
Thanks!
Click to expand...
Click to collapse
Happened to me once after flashing a new rom; solved by reflashing root (magisk in my case).
But I don't know how chainfire's autoroot works, you don't have twrp? I would suggest you to flash a custom recovery and do everything from there

Help for SGH-I337M about TWRP

I rooted my phone using CFRoot and installed TWRP but then when I try to flash into recovery I received a message "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT:RECOVERY" I downloaded the twrp jfltecan.
I know this is an old post but, in case you did not, the message you are receiving is a not uncommon since you flash non-signed Samsung software to the phone.

Categories

Resources