Google Confirms “Android Lollipop Day” for November 3rd

A little over a week ago, Google announced the latest iteration of … more

Get Your XDA 2015 Custom Avatar and Signature Images Here

As stated in our motto, XDA Developer is for developers, by developers. The … more

Pin Your Photos on Android Lollipop with Photo Pinner

In the last few weeks,we have been talking quite a bit about Android 5.0 Lollipop. This … more

Samsung Galaxy Note Edge Hands On – XDA TV

Perhaps one of the more peculiar announcements this year was the curved edge-screened … more
Post Reply

Tutorial [q] kernel is not seandroid enforcing

OP t3tr1s_

12th March 2014, 03:42 PM   |  #1  
OP Member
Thanks Meter: 3
 
52 posts
Join Date:Joined: Oct 2013
I've installed the latest Tmobile 4.4.2 Firmware via SamMobile. I came from M17 4.3. Updated via Odin to Tmobile 4.4.2, I then rooted via CF Auto root (Don't care about Knox at this point) successfully and following that flashed Philz recovery with success.

Everything is all good, as I am familiar with other devices and rooting and booting into recovery. At this point I downloaded the latest SlimKat and Lean Kernel to flash onto my system. Reboot into recovery, flash is a success, however when I reboot the system I start to get a bootloop saying Kernel is not seandroid enforcing set warranty bit: Kernel..I've tried to JUST flash SlimKat with the same results. Following this It continues to bootloop so I am forced to Odin from my PC back to Tmobile stock 4.4.2.

Can someone assist me with a solution? TLR, Custom ROMs/Kernels are not allowing me to boot due to Kernel is not seandroid enforcing set warranty bit: Kernel bootloop
12th March 2014, 05:12 PM   |  #2  
Senior Member
Thanks Meter: 329
 
1,092 posts
Join Date:Joined: Oct 2010
My guess would be that slimkat doesn't support 4.4 bootloader yet.
12th March 2014, 05:17 PM   |  #3  
OP Member
Thanks Meter: 3
 
52 posts
Join Date:Joined: Oct 2013
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
12th March 2014, 05:18 PM   |  #4  
Senior Member
Flag Tampa, FL
Thanks Meter: 201
 
1,049 posts
Join Date:Joined: May 2008
More
Custom kernels will ALWAYS show that on boot.

Dev's turn off the SEANDROID permission crap because not all root apps deal with that permission properly.

Bootloop on the other hand would be a different issue doubtfully related to this.
12th March 2014, 05:27 PM   |  #5  
Senior Member
Thanks Meter: 329
 
1,092 posts
Join Date:Joined: Oct 2010
Quote:
Originally Posted by t3tr1s_

Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?

You have to read the op of the rom you're interested in. If it doesn't say it supports both bootloaders then it's most probably for 4.3 bl only.

Anthem here says it supports both bl.
12th March 2014, 05:48 PM   |  #6  
OP Member
Thanks Meter: 3
 
52 posts
Join Date:Joined: Oct 2013
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
12th March 2014, 06:16 PM   |  #7  
Senior Member
Thanks Meter: 329
 
1,092 posts
Join Date:Joined: Oct 2010
Quote:
Originally Posted by t3tr1s_

I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?

I am not a technical person but how I understand it is that custom recovery/rom flashes doesn't load/replace the bl.

Cm and aosp-based roms were dev'd for 4.3 until a month or two ago when they start supporting both bl and even then not all roms do.
12th March 2014, 06:45 PM   |  #8  
Senior Member
Flag Tampa, FL
Thanks Meter: 201
 
1,049 posts
Join Date:Joined: May 2008
More
Quote:
Originally Posted by t3tr1s_

I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?

Yes, it sure can.

If you're fully upgraded to the KK package completely, ex: through odin, you have to use a KK rom that has the 4.4.2/Kernel bootloader components.

If you don't fully want to commit to KK completely you can flash a KK rom that has a kernel with the older boot loader. That will allow you to go back to 4.3.

I suspect given time, 4.3 support will be slowly dropped in favor of a full KK implementation on this forum. In the transition period, be careful what you pick and choose to install.

I, like many others, have gone full KK inc. bootloader, etc for full compatibility with everything. When you go full update, you get the updated firmware and bits for the modems, etc.
12th March 2014, 07:33 PM   |  #9  
OP Member
Thanks Meter: 3
 
52 posts
Join Date:Joined: Oct 2013
Thank you very much for all your help, it was the bootloader issue. Just me not reading into things fully, very glad that I asked. I am now running Beanstalk on my Note!

Now that I have all of that cleared up, my next question is the S-PEN. I'm assuming all CM/AOSP ROMs will not support it, thus making me switch to TouchWiz. Is that true? Or are there Apps that I can still use in conjunction with my S-PEN?

As far as TouchWiz is concerned, is Xnote updated to the KK BL and compatible with our Tmobile version? I searched the thread but did not find any answer. If not, what is a suitable replacement to maintain funcionality of the S-PEN while having bloatware removed?
12th March 2014, 08:59 PM   |  #10  
Senior Member
Flag Tampa, FL
Thanks Meter: 201
 
1,049 posts
Join Date:Joined: May 2008
More
There are apps but it won't give you the full Samsung spen experience like on stock.

Sent from my SM-N900T using Tapatalk

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes