Hello fellow XDA members!
First off here is a little about my device:
* Rooted using towel root, which is a one click root(No ODIN or anything else needed)
* Android version 4.2.2, stock at&t
* Galaxy S4 SGH-I337
Yesterday my phone kept bugging me to do an OTA update, it's done this before. I always have my phone in "OTA survival mode" in my SU app. Usually i just decline it and then finally it forces me to do the OTA update, giving me no option to cancel and automatically restarting in 30 seconds. Then i just restart it and boot it normally and everything is fine(Also it doesn't ask for OTA often). Unfortunately I managed to break my recovery since the last time it did this trying to install CWM and I never got around to changing it back to stock. Now when i boot my device, no matter what mode i try to boot into it starts to boot into recovery(I see the tiny blue text). Then some tiny white loading text pops up for a split second, I believe it says "SECURE: SECURE MAGIC failure (recovery mode)" then the next line says "Set warranty Bit: recovery", then it goes to a screen that has a tiny red "SECURE FAIL: KERNEL" in the top left and a big caution in the middle of the screen, then finally right below that it says "System software not authorized by AT&T has been found on your phone" this time in a little bit larger font.
I'm pretty sure the phone is done but any help is greatly appreciated. Also on a side note i did try to boot ODIN and also KIES but none seems to work.
Also let me know if there could be any other information i could provide
Thanks in advance!
Related
So i don't know exactly what has happened to get here. I have a new Verizon Galaxy S5 that I Towel Rooted and installed Safestrap. Things were going fine and I made a nandroid backup of my Stock slot. I decided to try Alliance rom in slot 1 which all went fine and i booted into Alliance. I was customizing my phone with colors and clock position etc. Some of the icons weren't there anymore so I decided to reboot to get everything loaded back in. Well when i hit reboot the screen went black and nothing came back on. Now when I turn it on I get the Galaxy S5 splash screen and blue words at the top saying "RECOVERY BOOTING...." then it shows the Android with it's chest door open and the globe spinning, then it goes to the Android laying down with a red triangle over its chest door, and then reboots. It just loops like this. Does this mean my bootloader is corrupt? Or can I Odin flash the stock firmware and PIT?
If your bootloader was corrupt, you'd either end up on the secondary bootloader page or have a nonresponsive, brick for a phone.
So corrupt bootloader was just your guess? Because I don't see any evidence for that yet. You've ended up on the Recovery mode page or at least that is what your description sounds like (a screenshot or photo would have been good). More than likely something is just messed up in your Safestrap or custom recovery configuration.
The most obvious options would be to either check and/or reinstall Safestrap /your custom recovery. Or if you prefer, revert to full stock, then proceed from there.
The last part that you wrote is unclear.. but you imply that you can't do a normal boot at this point? Can you boot to download mode then? Pull your phone battery for ten seconds.. then press and hold the volume down key, then the home key also and then the power key. You should boot to the black download screen that shows your Knox status. If this works, then you can flash a full stock firmware from there with Odin to stabilize your system.
.
Thanks fffft for your response.
As it turns out you are correct in that the bootloader is not corrupt because I can get to download mode. I tried flashing the stock firmware back on through Odin, but that didn't work, it still just looped. What finally did work is this thread http://forum.xda-developers.com/showthread.php?t=2784880 Thanks to Misterxtc. It must have needed the PIT as well.
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!
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.
Hello. I was working on a phone, an samsung galaxy s5 (chinese version) sm-g9006v and I tried to root it in order to add playstore and more to the device.
However, I used odin and a CF-autoroot file for this device.
After that the device went in a blocked white screen with a chinese log and on top left it wrote "set warranty bit recovery" and some other text.
Waited a bit since I thought it was a phase that was required for the root process to continue but it didn't do anything for a few good minutes, however i proceded to remove the battery (since the power button wasn't helping to reset the device) and now it won't start and it won't enter in a download state to use odin to eventually flash something else onto it.
Any help is appreciated as I'm kind of desperate at this point. Thank you.
Edit: if I connect it to the pc it gets in a start-up loop i believe.
scimini said:
Hello. I was working on a phone, an samsung galaxy s5 (chinese version) sm-g9006v and I tried to root it in order to add playstore and more to the device.
However, I used odin and a CF-autoroot file for this device.
After that the device went in a blocked white screen with a chinese log and on top left it wrote "set warranty bit recovery" and some other text.
Waited a bit since I thought it was a phase that was required for the root process to continue but it didn't do anything for a few good minutes, however i proceded to remove the battery (since the power button wasn't helping to reset the device) and now it won't start and it won't enter in a download state to use odin to eventually flash something else onto it.
Any help is appreciated as I'm kind of desperate at this point. Thank you.
Edit: if I connect it to the pc it gets in a start-up loop i believe.
Click to expand...
Click to collapse
Use Samsung KIES 3 and select "Emergency Firmware Recovery" or "Firmware Upgrade and Initialization". This worked for me even after a botched recovery flash that prevented me from going into Download mode.
Hello All, So I have a friend's 930V here. She let the phone "try" install the latest verizon OTA a few days ago, best I can tell 8CRK1 (I know). It did not complete. I have been attempting to fix it for a few days now. I have only been able to get the phone to actually boot into recovery twice. All other attempts say either "erasing, then installing update" or just "installing update", neither of which ever complete. The phone then reboots, says "recovery booting" and does it again. But I can not get it to boot into recovery to wipe the cache.
I have flashed it several times using odin (v3.13.1 and v3.13.1_3B) with firmware (8CRK1, 8CRJ3 and Umodel 8CRJ2). They all complete and pass in odin, yet it will not boot.
Some it will not even turn on, so let it sit for a while, when I come back it will turn on
- Will ticking erase NAND and/or REPARTITION help?
- Should I force the PIT file (HEROQLTE_USA_VZW)?
I have even gone to trying the Verizon/Samsung software upgrade utility, which fails half way through and says phone disconnected (on the phone it says unsupported dev_type)
-I'm about to rip my hair out- Any advice would be awesome!
thanks
A-
the screen grab I've attached are from the 1 of the 2 times it actually got it into recovery