Hello all Xda members, I think I need some help with rooting Sprint Galaxy S5 because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
This is a 10 day-new phone. Any help would be appreciated.
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Turn off your phone and remove the battery for 30 or so seconds. Then try bootting it up. On first boot ir does take a bit before os comes up. But usually it shows samsung logo.
Related
Ok so today was my first time trying to root and put a rom on my phone, rooting worked out great. but I tried using flashify to load a rom (slimbean) on my i337 S4 now whenever it boots it sometimes shows a grey bar with 2 shades of grey and/or the samsun galaxy s4 logo with "kernel is not seandroid enforcing" on the top left and then the screen cuts straight to black and it appears that my phone is turned off. Happens every time, how can i fix this?
That's because you probably can't flash that rom.
You need to look up information about safestrap in the section for you phone, the i337.
If you want to get your phone working again, just flash a stock rom.
Good Night All,
I come in peace. I am inbetween a rock and a hard place at this point, I am in need of some urgent assistance. I have a SM-T530NU and all i did was replace the battery and it ended up tripping the Knox unknownly. After that happened i decided to follow some searches and the posts said to re-flash the tablet which i did like 4 times and all that happens is that the tab just boots up to the samsung galaxy tab 4 logo and on top says Recovery Booting... Set Warranty Bit: Recovery. Can anyone out there in the universe help me please. It will be greatly appreciated. Thanks Alot
Hello,
I'm new here and new to all the android modding/flashing/etc stuff since I just transferred from iPhone 5 to Galaxy Grand Prime SM-530H
I've already done the basic rooting and flashing custom recovery and custom rom
Right now, I'm using PhilZ Touch Recovery since I can't seem to make TWRP work and I'm using Cyanogenmod 13.
Right now, The problem I have is that when I boot my phone up, right after the samsung logo where the boot animation is supposed to play, it's just black then after a while I can just press the power button to check if its already booted up. Another thing is that when I lock my device, The screen goes black but it stays on. I'm not sure if it's called the screen backlight or anything but it's the same as the black screen when my boot animation is supposed to play. This issue drains my battery so much when not in use.
I've used ResurrectionRemix custom ROM too and its the same case so I don't think its in the ROM. However, whenever I do boot my phone up, it says on the top right "Kernel is not SEAndroid. Enforcing" and whenever I boot to recovery, I get "Recovery is not SEAndroid. Enforcing". That's it.
Any help from you guys is appreciated. Thank you.
(Note: I'm new to XDA so i have no idea how threads work.) I have a Samsung Galaxy Grand Prime SM-G530T, it's rooted, and after the first attempt of trying to root it, a little message popped up saying, "Kernel is not Seandroid enforcing". When i tried to enter recovery mode, my phone restarts, sending me back to the Samsung Galaxy Grand Prime screen, and this time, the message says "Recovery is not Seandroid enforcing". I had no idea what these meant, so i didn't mind them. But when i recently bricked my phone from flashing a file, my phone gets stuck at the T-Mobile screen, so since i can't go to the recovery mode to factory reset, I don't know how to fix this. But, I can enter "Download mode" I'm a noob with this stuff. So I have no idea what to do. Please help. EDIT: I Forgot! It's a Samsung Galaxy Grand Prime SM-G530T!
Hi, I recently rooted my Galaxy S7 edge (G935W8) and everything works but whenever I reboot my phone it says Kernel is not Seandroid Enforcing in red on the top left corner. I did a bit of research and apparently people who have encountered this issue are not able to boot their phone at all, whereas I can boot it without problem. Any idea why this is happening? Is it indicative of some sort of system error?
Thanks.