hey there!
i just installed this kernel: "N4_AELKernel_v7_2_010215" on my N-910F, and after i installed it, i get this messege: kernel is not seandroid enforcing set warranty bit - that was stuck like on a bootloop, like keep turning off and on on every 10 sec, something like that..
is it possible to happen beacuse i didn't wipe any cache. dalvik, or set a premesion before/after i flashed this kernel? or what? how should i know that this kernel is for my phone.. i mean i have this "N4 EchoePop v3" ROM
now i'm restoring my system..
but what did i did wrong??
?
Anyone? please help?
bagiz010 said:
hey there!
i just installed this kernel: "N4_AELKernel_v7_2_010215" on my N-910F, and after i installed it, i get this messege: kernel is not seandroid enforcing set warranty bit - that was stuck like on a bootloop, like keep turning off and on on every 10 sec, something like that..
is it possible to happen beacuse i didn't wipe any cache. dalvik, or set a premesion before/after i flashed this kernel? or what? how should i know that this kernel is for my phone.. i mean i have this "N4 EchoePop v3" ROM
now i'm restoring my system..
but what did i did wrong??
Click to expand...
Click to collapse
The kernel you flashed is for android kitkat. There is no custom kernel for lollipop just yet. Just re flash your echo Rom you should be grand.
saxobully said:
The kernel you flashed is for android kitkat. There is no custom kernel for lollipop just yet. Just re flash your echo Rom you should be grand.
Click to expand...
Click to collapse
OK thanks very much
Related
hello, i am new to this forum and please excuse me if i posted in the wrong place. so here is my problem:
i have a samsung galaxy s4 gt-i9500 with cm11 on it. i wanted to flash a new kernel. so i downloaded perseus 19.1 kernel, flashed it, but when i rebooted i got this error: unfortunately the process com.android.phone has stopped. i click ok but it pops up within a quarter of a second. i tried factory data reset, wipe cache partition and wipe dalvik cache but it keeps popping up. what should i do?
Maybe the kernel isn't compatible. There is not much point in flashing a new kernel on that rom anyway.
Lennyz1988 said:
Maybe the kernel isn't compatible. There is not much point in flashing a new kernel on that rom anyway.
Click to expand...
Click to collapse
ok, i will flash a stock kernel.
Hello !
I have a problem with flashing rom.
http://forum.xda-developers.com/galaxy-note-3/development/rom-t2891226
I will describe my step by step what i done.
I normally installed cwm for my note, its working i made backup, then i downloaded ODEX_Tweaked_S5Base_N4Style_by_g00h_V11_3rd rom and lean kernel 2.3
I gone to recovery mode wiped data,cache flashed rom, then i flashed kernel, rebooted.
Samsung galaxy note 3 screen appeared at the top was written: Kernel is not seandroid enforcing set warranty bit: Kernel then the screen turned black and thats all. So I went into recovery to get my stock rom back. Can anyone help me how to flash this rom ? I flashed a rom before, but it was 2-3 years ago on my galaxy player 5.0 thanks for answer, tell me please what i did wrong.
Sorry for my poor english, im learning it.
Hello.
I got a n9005 and had cm12 on it.
Did a full wipe except internal card.
Tried to install 2 different roms with a stock kernel so i could flash a new baseband:
But it refuse to boot with crash rom or multi x with stock kernel, But it does work with the custom kernels.
Cant get past the screen where it usually says kernel is not seandroid enforcing and the warrant bit text.
Anyone know whats wrong?
bump!
Evening. Iv had my Note 4 on a 4.4.4 Rom for ages. I decided to flash it with Resurrection Remix ROM [Android 6.0.1]
Everything flashed fine. BUT I get the "kernel is not seandroid enforcing" message at the top of the screen and the phone either boot loops or turns off. I have a had a look around but there doesnt seem to be any fix other than flash a stock rom to get the phone up and running again. I really want to get a more recent Custom Rom on this phone but Im not sure if I should bother in case I brick the thing. I have managed to restore the phone through TWRP to my previous Rom. Thanks for any help
Did you completely WIPE the phone using TWRP BEFORE flashing RR? That's a must step for stepping into any custom ROM, let alone an AOSP based ROM.
I Wiped Dalvik Cache, System, Data and Cache?
Get back to a 5.1.1 stock, root and install twrp, boot into it and wipe everything. Install your custom rom, then wipe cache and dalvic . Hope it helps
Sent from my HTC Desire 820s dual sim using Tapatalk
Tried to flash the stock 5.1.1 but TWRP fails? Is it to do with it saying that there is no MD5 file present?
Do I need to flash with Odin and select the Rom in the AP tab?
Same as me
I too have the same senandroid in red every time I boot my phone up I thought it was normal after flashing lol
I've had many roms on my 910f and had no issues ..
So I take it that it's not supposed to say this message oops..
I shall try above at the weekend by going back to stock and starting over again.. I use philz recovery btw but will try twrp
And report back how I've got on
Braggster
Any luck with this Braggster?
Braggster said:
I too have the same senandroid in red every time I boot my phone up I thought it was normal after flashing lol
I've had many roms on my 910f and had no issues ..
So I take it that it's not supposed to say this message oops..
I shall try above at the weekend by going back to stock and starting over again.. I use philz recovery btw but will try twrp
And report back how I've got on
Braggster
Click to expand...
Click to collapse
seriously guys, there are hundreds of post on this topic here on xda. No one is able to do a search?
This is so important for you, and no one do a search?
And it's not even hard to take out: see the picture in attachement.
and there is even more than a process. Just yesterday I learned another one:
Dirtyzecret said:
You can just download a setting in Xposed and this message will disappear
Click to expand...
Click to collapse
I am using Note 3 N9005 with the official rom 5.0 N9005DXUGBOK1 then I root my phone by using CF Autoroot htle N9005. Then I flash twrp 2.8.7.0 htle 4.4 by odin. Then I boot my phone in to very mode and doing wipe data/ cache/ dalvik cache and format cache/ data/ system/ preload then install Tazzy T9 Rom after finishing the installation my phone got stuck at Samsung Logo with Kernel is not seandroid enforcing and I try factory reset, restart my phone, and after 2 hours of waiting at the loop of Samsung Logo I decided to flash the official rom just so that I can use my phone again. I already tried installing others rom like Music of Life and DarkWolf but the same thing happened. So for now I have to stick with the official rom. Is there anyways to solve this problem?
I also try using philz touch to flash the rom but the samething happened.
Maybe in aroma installer you choose to install wrong kernel for n9005?
Sent from my SM-N920C
Rosli59564 said:
Maybe in aroma installer you choose to install wrong kernel for n9005?
Sent from my SM-N920C
Click to expand...
Click to collapse
The thing is I still haven't install anything in Aroma installer at all. After I try flasing rom via twrp recovery mode then I got stuck at Samsung Logo with Kernel is not seandroid enforcing.
Try cwm or philz
Sent from my SM-N920C
Rosli59564 said:
Try cwm or philz
Sent from my SM-N920C
Click to expand...
Click to collapse
Already try philz but the same thing happened again. Will try cwm soon hopefully it can get pass this loop.
There is no format option in twrp. Just wipe everything except internal and sdcard. Then flash the rom.
Sent from my SM-N920C
Rosli59564 said:
There is no format option in twrp. Just wipe everything except internal and sdcard. Then flash the rom.
Sent from my SM-N920C
Click to expand...
Click to collapse
Try this already but still stuck at Samsung Logo with kernel is not seandroid enforcing even after waiting for 1 hours. Is it because of the official 5.0 rom?
No i think it's because of recovery.
Perhaps flash again the recovery after the custom rom flash.
Did it ever ask to flash stock recovery when you were trying to exit recovery/reboot?
Sent from my SM-N920C
Rosli59564 said:
No i think it's because of recovery.
Perhaps flash again the recovery after the custom rom flash.
Did it ever ask to flash stock recovery when you were trying to exit recovery/reboot?
Sent from my SM-N920C
Click to expand...
Click to collapse
Not at all.
I already try using TWRP, CWM, and Philz Touch to flash the rom but I still get stuck in the loop of Samsung Logo with Kernel is not seandroid enforcing. Anyone know how to fix this?
Kengfishz said:
Kernel is not seandroid enforcing.
That is correct and should be seen .
I would install PhilZ recovery .
Mounts and storage
Format system Boot System Data Cache .
Remove battery .
Replace .
Flash correct stock rom via Odin .
Click to expand...
Click to collapse