Hi everyone. I don't know if I'm posting in the right forum or not, but right now, I'm at the end of my rope and I've run out of things to try.
I lost my 18-year old sister last week in a car accident. I visited the accident scene with my parents and we found her phone. It was hard to
recognize amid all the scrap because of how mangled it was, but her S4 was there. Everything except the motherboard was destroyed, so we went
and put the motherboard into a new S4 to see if we could get any data from it. The phone worked for a while. It was able to boot to the lock
screen and it connected to our wifi whenever we walked into the house. However, it's passcode locked. We don't know the password to her google
account either.
I searched google for solution on how to unlock the phone, but the methods I found required that USB debugging be enabled, and of course, she didn't
have it turned on.
I found one method that could work. Aroma file manager. But it can only be flashed using Custom Recovery. Naturally I tried to flash CWM, and it
appears to have been successful (according to ODIN). But when I tried to boot into CWM, I got the "RECOVERY IS NOT SEANDROID ENFORCING" error and
the phone shut off. Now the phone can't get past the S4 logo. I'm not sure if this is a problem with the battery (it kept needing to be pushed for
the phone to turn on when we replaced everything) or if I screwed up the phone entirely. Please help.
TLDR; I tried to flash CWM on a Galaxy S4 and got the "RECOVERY IS NOT SEANDROID ENFORCING" error when trying to boot into recovery. Now the
phone won't get past the S4 logo and I'm not sure if I messed up or if it's the battery's fault.
Any help would be much appreciated. I'd like to thank everyone in advance for looking and for your help.
It's the battery. The "Recovery is not SEAndroid Enforcing" warning appears on all custom recoveries installed on the S4. The warning is simply because the bootloader notices the recovery doesn't have the secure android code in it, so it reminds you of that fact.
Strephon Alkhalikoi said:
It's the battery. The "Recovery is not SEAndroid Enforcing" warning appears on all custom recoveries installed on the S4. The warning is simply because the bootloader notices the recovery doesn't have the secure android code in it, so it reminds you of that fact.
Click to expand...
Click to collapse
Thank you for the reply, Strephon. So I guess the next logical step would be to obtain a new battery? How can I at least be able to get back to the lock screen in this case?
Yes it could be the battery like Strephon Alkhalikoi suggests.
What I also would do is reflash the recovery. But not CWM, try Philz or TWRP.
Make sure to uncheck auto-reboot before flashing.
ps what's the model that you have? You can find the model in the download mode.
Lennyz1988 said:
Yes it could be the battery like Strephon Alkhalikoi suggests.
What I also would do is reflash the recovery. But not CWM, try Philz or TWRP.
Make sure to uncheck auto-reboot before flashing.
ps what's the model that you have? You can find the model in the download mode.
Click to expand...
Click to collapse
Do you mind explaining what the difference between those custom recoveries are? Sorry, I'm new to all this^^;
And I'm not able to access download mode until I get a new battery ^^ Does the model affect flashing custom recovery at all?
Thanks again for the help!
Related
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
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
Well based on the limited info you gave I'm going to assume you flashed a rom. Likely a bad download.
If so download a different rom or re download the rom and flash again. Make sure you're doing a full wipe. Also be sure you're on the latest stable recovery.
Worst case if all of the above fails, odin the stock rom and start over and you'll be fine
running DECEPTICON rom (coming soon)
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
re: RECOVERY IS NOT SEANANDROID
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
When you see "RECOVERY IS NOT SEANANDROID" as the phone
tries to boot or boots it's perfectly normal after the phone is rooted.
Here is a fix which works 90% of the time for most people with the same
issue you are experiencing with your phone.
Power down the phone, then power it backup while holding the
phone's power/volumeUp/home buttons down all at the same time
until you see tiny blue text appear on top of your screen, as soon as
you see that let go of all buttons.
The phone will boot into Recovery mode.
Once you are in recovery mode do a "factory data reset" or factory reset
which ever way the option is displayed.
After that the phone reboots itself and it should fully boot making the phone
ready to use.
Good luck!
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
Take the battery out for a minute or so, then reboot into recovery. If no go, reflash your recovery (make sure you're using the right one obviously.
RECOVERY IS NOT SEANANDROID ENFORCING is normal when you have a custom recovery installed. It's just telling you that the official samsung signature isn't there. There's many threads regarding bootlooping around, a quick read probably would have sorted you :good:
PS: For the record, if you're getting physically sick about it, maybe you should read up a bit more before messing around with your very expensive device. I might sound awful but it's the truth.
Fixed It
The problem was i flashed the wrong recovery and my phone would not load or even go into download mode. I found somewhere online that if i held the download mode buttons before i put the battery in it would work and it did which allowed me to re flash my recovery.
Hello guys, after a extensive research I decided to post thia thread and ask for help.
I recieved this phone (i9505 international version) from my cousin after it was washed in a wash machine inside his pants pocket'.
He told me he had sent it to a repair shop to have it cleaned and repaired before he sent it to me.
I recieved it, charged it's battery on a externalismo charger, put it back and it turns on ok, but gets stuck on The boot screen with a little blue message on the top that says "recovery booting" and never changes from there.
So , i tried The obvious, downloaded a official ROM, and tried to flash it. Flash was sucessful but i still had the same problems with it getting stuck in The first boot screen with the little blue text at The top.
Then i tried flashing The ROM with a pit file to rebuild The partittions. Flash was sucessful again, no errors at all, but I still had the same problem getting stuck at The boot screen.
The I tried flashing a custom recovery.
Clockwork recovery got me a error screen after i flashed it saying something got wrong during flash ask me to flash again.
Reflashed The oficial ROM with the pit file, tried again, same error. Had to reflash again.
Then I tried twrp.
This time something went different. I was still stuck at The boot screen, but The blue text changed to a red/orange 3 line text saying something like "Recovery is not seandroid enforcing".
I've read that this hás something to do with a locked bootloader and knox security.
Also, I've read that some people had this problems when their /data partition got corrupted.
So, I could not clear or format the data partition because I can't get into the recovery. The pit file never touches /data, and I don't really know if flashing the oficial ROM is enough to fix any problems in /data.
I have no idea if the data on /EFS is still OK.
And I'm still stuck with this problem.
Does anyone have any idea what else I can try in order to unbrick this phone?
I think the 3 possible problems are:
Corruption on /data
Corruption on /EFS (still it should boot)
Something wrong with bootloader vs rom version or region or something with Knox security.
Oh, I Aldo tried flashing another modem/radio. Got the same "something went wrong while flashing, try again" error.
Any help would be greatly appreciated.
Sorry if you find any typos, I'm fighting my word corrector (which is in pt-br) as I type this from my phone (n7000).
PS: flashed Samsung 4.4.2 zto (brazil) to the i9505
Another possibility is that the volume rocker shorted and when holding power it is also holding volume. Therefore booting recovery. I would check this by removing the volume rocker ribbon from the board and powering on. I know it sounds silly but could be the problem
Sent from my SCH-I605 using XDA Free mobile app
I openned the phone a few minutes ago to check this. Acctualy the button is soldered into the mainboard. I wasn't able to disconnect it.
I get a new multimeter (mine broke a few weeks ago) and check the contacts, but I don't think this is the problem, because if it was just a problem with a key getting stuck it should still boot into the recovery and do something, but it's not the case, it gets stuck in the bootscreen before booting and never really enters the recovery.
and when I go into download mode, there is a screen that asks me to presse vol up to go into download mode or vol down to cancel, I acctually have to press vol up to enter download mode, so it's probably not the problem. Thanks for the sugestion tho'.
Hello,
I tried to install TWRP on my SM-T533, using a thread on this forum. Installation went well. But when i try to boot into recovery, i get the message "set warranty bit: recovery", with the Samsung logo in the background, and nothing happens...
I'm on lolipop, with a stock firmware.
What can I do ?
Thanks !
Funny that there was no answer. I am facing the same thing right now.
@tarhoa: Did you resolve this? How?
Solved it by finding the right TWRP. The Galaxy Tab 4 SM-T533 obviously has a different hardware than the other SM-T53x models. The img provided by twrp.me does not work.
This one by @sub77 does: https://androidfilehost.com/?fid=24421527759889282
tarhoa said:
Hello,
I tried to install TWRP on my SM-T533, using a thread on this forum. Installation went well. But when i try to boot into recovery, i get the message "set warranty bit: recovery", with the Samsung logo in the background, and nothing happens...
I'm on lolipop, with a stock firmware.
What can I do ?
Thanks !
Click to expand...
Click to collapse
hey im stuck at the stock boot screen. It flashed, went threw the motions like i did i5 correctly but will not go past that screen, so i keept trying and i ended up buying a nother one same tablet almost sim card version. Ahhhh it was much easier bact when i only had a tab 2.
Hi,
There are no mirrors available, can anyone provide me with the file?
Thnks
Hi all, I recently tried to root my Telstra GalaxyTab A 8.0 (SM-T355Y) with CF AutoRoot, but must have used the wrong version. I'm now permanently stuck at the boot screen with the message "Kernel is not seandroid enforcing"
I figured I could just reboot back into download mode and re-flash, but nothing I do can get me back into download mode. I even opened the case up and disconnected the battery, hoping to force a reboot, but when I connect it back up and turn it on it goes straight to the same error message and I cannot get to either download mode or recovery mode.
Any thoughts? I've never managed to totally brick a device before.
At this point, I'd even pay for it to be repaired, as I'm crazy busy with family stuff and just want it working again.
Thanks in advance for any help.
Patrick.
patdman said:
Hi all, I recently tried to root my Telstra GalaxyTab A 8.0 (SM-T355Y) with CF AutoRoot, but must have used the wrong version. I'm now permanently stuck at the boot screen with the message "Kernel is not seandroid enforcing"
I figured I could just reboot back into download mode and re-flash, but nothing I do can get me back into download mode. I even opened the case up and disconnected the battery, hoping to force a reboot, but when I connect it back up and turn it on it goes straight to the same error message and I cannot get to either download mode or recovery mode.
Any thoughts? I've never managed to totally brick a device before.
At this point, I'd even pay for it to be repaired, as I'm crazy busy with family stuff and just want it working again.
Thanks in advance for any help.
Patrick.
Click to expand...
Click to collapse
Holding power+volume down+home doesn't work?
jedld said:
Holding power+volume down+home doesn't work?
Click to expand...
Click to collapse
Unfortunately not, I'm really confused and now totally stuck!
I just tried this again (it's been a couple of weeks since I last tried) and the actual error displayed is
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Well I've now sorted it out.
Thanks to this thread (http://forum.xda-developers.com/s7-edge/help/recovery-seandroid-enforcing-t3416719)
I just needed to hold down the buttons for an extra boot cycle (2 cycles of boot to "recovery is no seandroid enforcing", then the next boot went to download)
It all seems a bit strange, but but it did the trick and I'm back running stock.
Now to re-try rooting.
The CF Auto Root version I tried which started all this was absolutely listed for my device and version, I think I'll just go the TWRP -> supersu route this time.