Hi all!
I'm trying to install the BlissPop ROM (BlissPop-v3.9-jflte-OFFICIAL-20150828-2215) [Lollipop 5.1.1]. I'm flashing using the TWRP Recovery (v2.8.5.0). Here are the steps I'm doing:
Factory reset (Data/Dalvik/cache)
Wipe cache (again)
Wipe Dalkvik (again)
Flash BlissPop-v3.9-jflte-OFFICIAL-20150828-2215.zip
Reboot
When I do that, I get the error message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Unfortunately, I'm one of the ones where it's not simply a warning with it merrily continuing it's boot, it is stuck on the screen displaying "Galaxy S4 i9505".
In an attempt to get some kind of lollipop ROM installed, I came across the JFLTE-GPE ROM, and have now flashed it (JFLTE-GPE-20150919) [Lollipop 5.1.1]. I have done the exact same steps as I had tried to do with BlissPop, but obviously flashing JFLTE-FPE instead.
Voila! It works! It lingers on the message 'KERNEL IS NOT SEANDROID ENFORCING" and proceeds to boot successfully, and is now running fine. Now, I have searched for days (yes, days!) to try and find a way to get the BlissPop ROM to work properly, but all the sites/threads I've come across offer little detail on the poster's part, have no solution, or a solution that doesn't work for me. Any help is greatly appreciated! If you need any more information about my device, don't hesitate to ask.
warrior4894 said:
Hi all!
I'm trying to install the BlissPop ROM (BlissPop-v3.9-jflte-OFFICIAL-20150828-2215) [Lollipop 5.1.1]. I'm flashing using the TWRP Recovery (v2.8.5.0). Here are the steps I'm doing:
Factory reset (Data/Dalvik/cache)
Wipe cache (again)
Wipe Dalkvik (again)
Flash BlissPop-v3.9-jflte-OFFICIAL-20150828-2215.zip
Reboot
When I do that, I get the error message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Unfortunately, I'm one of the ones where it's not simply a warning with it merrily continuing it's boot, it is stuck on the screen displaying "Galaxy S4 i9505".
In an attempt to get some kind of lollipop ROM installed, I came across the JFLTE-GPE ROM, and have now flashed it (JFLTE-GPE-20150919) [Lollipop 5.1.1]. I have done the exact same steps as I had tried to do with BlissPop, but obviously flashing JFLTE-FPE instead.
Voila! It works! It lingers on the message 'KERNEL IS NOT SEANDROID ENFORCING" and proceeds to boot successfully, and is now running fine. Now, I have searched for days (yes, days!) to try and find a way to get the BlissPop ROM to work properly, but all the sites/threads I've come across offer little detail on the poster's part, have no solution, or a solution that doesn't work for me. Any help is greatly appreciated! If you need any more information about my device, don't hesitate to ask.
Click to expand...
Click to collapse
Update your recovery to the latest TWRP. You are using an outdated version.
Hi,
Thanks for the speedy reply, unfortunately updating the recovery to TWRP v2.8.7.0 didn't fix the problem. On the JFLTE-GPE ROM thread, there was a link to an alternate kernel. I managed to boot BlissPop successfully by flashing it and then the kernel. However, it is now stuck at the loading screen.
warrior4894 said:
Hi,
Thanks for the speedy reply, unfortunately updating the recovery to TWRP v2.8.7.0 didn't fix the problem. On the JFLTE-GPE ROM thread, there was a link to an alternate kernel. I managed to boot BlissPop successfully by flashing it and then the kernel. However, it is now stuck at the loading screen.
Click to expand...
Click to collapse
Are you also wiping /system before flashing? I don't see you mentioning it in the first post but it's mandatory.
After fishing new rom factory reset through recovery.good luck
Hi, so I've tried wiping /system as well, with no luck. I have also factory reset after flashing the ROM, and it still didn't work. But when I factory reset it, the computer detected the connection, but it didn't show on My Computer? I'm not sure if that means anything, am I being too impatient? I did wait a good 20 minutes.
Related
Trying to install a Custom ROM for the first time on Nexus 7 (3G).
I've been using the WF Nexus Toolkit.
I've rooted, unlocked and flashed ParanoidAndroid but I'm only getting a bootscreen loop. I waited 15 min before rebooting the device and attempted to boot into PA again. Still not getting past the Bootscreen.
I booted into recovery; did a full wipe then flashed the PA ROM again... Still not getting past the Bootscreen (waited 30 min before powering off the device)
I've tried to obtain help via IRC before posting here; as well as reading through other post directly related to the problem (even a few that were slightly indirect) but nothing I find is helping... so I've turned to you guys!
I would very much like to get this ROM working, so if there is anyone that can help I would greatly appreciate it.
I just don't know what to do next; I've never had this issue with any device in the past.. I've usually been able to figure the problem out and get it working. But now I'm just stuck.
What is your recovery? What steps did you do in recovery to install the rom?
Try these step may help.
1.Boot into recovery
2.Full wipe
3.Wipe Cache
4.Wipe dalvik cache
5.Flash ROM, GAPP
then reboot your N7.
...
If above method still doesn't work. make sure you have the right version of bootloader and stock image on your device for PA 3.15 or newer it should be 4.18 for bootloader and 4.2.2 for stock image (optional).
And if you've found that you have other version of bootloader than 4.18 check this http://forum.xda-developers.com/showthread.php?t=1907796 thread for how to get it right.
...
Finally if you've done all the solutions above and still in bootloop problem just try to do a factory reset (full wipe) again after finish flashing ROM, GAPP.
That's all I can thinks of about this problem base on my personal experience facing bootloop problem few months ago.
If you are still stuck after trying the above posts. You can just try to get back to stock. Nexus Root Toolkit maybe the easiest way to do that..
____________________________________________
Please press the thanks button if you find this helpful
Hi there.
I have a Samsung Galaxy S4 GT-I9505 and I’m using TWRP Recovery 6.0.4.4.
I tried to flash a nightly-version of CyanogenMod (cm-10.2-20131101-NIGHTLY-jfltexx.zip). I did a Factory Reset before flashing, TWRP said it had been successful.
When I tried to boot my phone, I can see the "SAMSUNG GALAXY S4 GT-I9505" logo, here it got stuck. I can not see the cyanogen boot animation.
Though MD5 hashes and file sizes are ok, I tried another ROM: SuperNexus http://forum.xda-developers.com/showthread.php?t=2407616
Here it was exactly the same. My device gets stuck even before the boot animation.
I was so desperate, that I tried to format my complete internal storage. Flashing the ROMs was successful again, I could boot both ROMs CM and Supernexus then. But after I turned off my device I can't boot any more. Again I can not see the boot animation.
I have already tried it with PhilZ and CWM. I flashed them using my current recovery.
Any advice?
I am sorry for my English, if you need more detailed explanation, please ask. I tried to describe everything as detailed as I can.
Can you get into download mode? You may have to flash a stock ROM to get it to working again. Was the phone previously rooted?
And are you currently on a stock ROM or coming from a custom ROM?
Yeah, I can get into Download mode.
Well, I am not sure what ROM I'm currently using since I wiped everything. Previously I had FoxHound ROM, samsung-based pre-rooted custom ROM.
Have you tried flashing a custom Kernel?
Sounds like what I had when I tried to flash a TW Kernel for a AOSP ROM.
If you can't get into recovery, go into download mode and flash the latest CWM. Got my phone working.
FoxHound ROM installed a custom Kernel, "Ausdim Kernel" I think.
Now I have CWM 6.0.3.2 from here: http://forum.xda-developers.com/showthread.php?t=2279579
Not sure if this is the latest version ... I can't find an Odin-flashable *.tar
Anyway it doesn't work too. This recovery can't even flash CM, it gets stuck at "opening update package ..."
Sorry its a bit late.
http://forum.xda-developers.com/showpost.php?p=46312260&postcount=149
Use them. This may help as a tutorial to follow loosely but that was for non working WiFi.
http://forum.xda-developers.com/showpost.php?p=47076192&postcount=6
Hello all, I have an issue with recovery on my i9505 which hopefully someone can assist with?
I'm using the excellent Optimised CM12.1 and had TWRP 2.8.7.2 (f2fs) as my recovery all working fine. I've recently flashed the newest 2015-11-1 ROM over the top (clear cache and dalvik, but not data wipe) and all seemed great.
However, I went to 'reboot to recovery' in order to install exposed and got stuck on the teamwin splash screen of recovery. Every time I tried to power off it would bootloop into the same splash screen!
Using Odin I was able to flash a new recovery (TWRP 2.8.6.0) and reboot the phone as normal. All worked fine until I tried recovery again and found the same issue!
I've now got CWM (6.0.4.7) flashed to see if that would help but nothing is mounted when using that and so I cannot get to the zip files! When attempting to mount within CWM it errors and cannot mount.
I'm open to any suggestions and would like to learn why this is occurring. Let me know if there's any logs or files I can post that would help.
Many thanks in advance!
Stu
StuKeeler said:
Hello all, I have an issue with recovery on my i9505 which hopefully someone can assist with?
I'm using the excellent Optimised CM12.1 and had TWRP 2.8.7.2 (f2fs) as my recovery all working fine. I've recently flashed the newest 2015-11-1 ROM over the top (clear cache and dalvik, but not data wipe) and all seemed great.
However, I went to 'reboot to recovery' in order to install exposed and got stuck on the teamwin splash screen of recovery. Every time I tried to power off it would bootloop into the same splash screen!
Using Odin I was able to flash a new recovery (TWRP 2.8.6.0) and reboot the phone as normal. All worked fine until I tried recovery again and found the same issue!
I've now got CWM (6.0.4.7) flashed to see if that would help but nothing is mounted when using that and so I cannot get to the zip files! When attempting to mount within CWM it errors and cannot mount.
I'm open to any suggestions and would like to learn why this is occurring. Let me know if there's any logs or files I can post that would help.
Many thanks in advance!
Stu
Click to expand...
Click to collapse
Do not use CWM. It's outdated and not compatible with Lollipop.
You could try flashing a stock rom with .pit and re-partition. After that flash TWRP again.
Lennyz1988 said:
Do not use CWM. It's outdated and not compatible with Lollipop.
You could try flashing a stock rom with .pit and re-partition. After that flash TWRP again.
Click to expand...
Click to collapse
Thanks for the advice. I don't like CWM myself.. just tried it as an attempt to get TWRP flashed back properly!
I will go the stock re-flash route as a last resort. I'm sure it will fix the issue but is a little drastic.
What caused this? - is it something to do with the F2FS filesystem? TWRP recovery was working fine in order for me to flash the updated CM12.1 (2015-11-1).
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
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?