Develop Bugs

[q] kernel is not seandroid enforcing

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

My guess would be that slimkat doesn't support 4.4 bootloader yet.

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

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.

t3tr1s_ said:
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Click to expand...
Click to collapse
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.

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

t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
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.

t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
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.

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?

There are apps but it won't give you the full Samsung spen experience like on stock.
Sent from my SM-N900T using Tapatalk

As long as I have a note taking app I think i would be good to go. It's really the only feature I use.

also having this problem

Bootloader question, Android Pay related

I am currently running an OG5 based ROM, with the OB7 bootloader.
I had been keeping the OB7 bootloader, instead of upgrading to OE1/OF5, because it allowed me to go back to Kit Kat NK2, after evaluating the initial lollipop release.
Now that OG5 is out, I am pretty happy and can't imagine going back to KK.
So I've been trying to get Android Pay to allow me store a credit card and no fix has worked. I am thinking that it might be because my rom and bootloader don't match up (OB7 & OG5)?
I was going to give it a shot, but now wondering if there is any reason to keep OB7 bootloader, other than having the option to downgrade?
If I decide to go all OG5 (ROM and bootloader) is there any easier way than starting with the OTA?
Thanks,

Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card

Also... any chance its possible to set up a card on Android Pay from another unrooted device then use as normal from your rooted phone once a card is added to your account? I don't have a secondary device to try
Sent from my SM-N910P using XDA Free mobile app

ch3ck3rs said:
Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card
Click to expand...
Click to collapse
Do you also have the OB7/OG5 combo?
I wonder if anyone with OG5/OG5 has had any luck. from what I've read plenty of people with unlocked bootloaders have been successful.
FYI there is an app called Keyring that does a decent job with loyalty cards.

Yep. I have the same combo. Running Saintz OBAR

A lot of variables are at play here. Most root users of any device are hitting roadblocks when it comes to getting AP to load their cards. In my instance I am on OG5/OG5 running HybridX 3. I've explored nearly all of the 'fixes' out there short of flashing the stock build.prop. Some reports are saying it is checking against known good OS (ie: CM12 stable vs. CM12 nightly). Others are saying it is checking directory level instances of root (ex: system/bin/su or system/xbin/su). Still more are just unlucky and are hitting the wall for no explained reason (there is a reason I'm sure, the info provided isn't helping). What it is going to boil down to is some smart cookie is going to unlock the secret, and we're going to say 'you've got to be kidding, that was too easy'.

With Android Pay, it will block root users and I haven't found a way that gets around it on the Note 4, even with Root Cloak and No Device Check to mask root and custom ROM's to get it to work.
From what I saw, Android Pay does have SafetyNet built in to it to check if your device and your firmware match up. I ran into the same issue with running the OB7 bootloader and CM12.1 ROM which doesn't work. I'm assuming you are having a similar as me issue with using the 0B7 bootloader and a 0G5 ROM. Unfortunately, you will probably have to unroot and go back to stock to get it to work since none of the workarounds I've tried hasn't worked.
Sent from my SM-N910P using Tapatalk

ThatGuy94 said:
FYI there is an app called Keyring that does a decent job with loyalty cards.
Click to expand...
Click to collapse
I use beep and go, works with older infrared barcode scanners

I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!

Quick answer is OB7 allows you to go back to KK OG5 will not

dh350nwo said:
Quick answer is OB7 allows you to go back to KK OG5 will not
Click to expand...
Click to collapse
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?

duongdn said:
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?
Click to expand...
Click to collapse
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk

duongdn said:
I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!
Click to expand...
Click to collapse
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl

cherylbaker said:
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl
Click to expand...
Click to collapse
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk

SafetyNet is just 1 part of the puzzle. If it was the only thing then the Xposed module 'No Device Check' would be enough to bypass. There are multiple checks taking place.

OG5 and non OG5 roms
samep said:
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.

Iceburn1 said:
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.
Click to expand...
Click to collapse
I recall reading that but couldn't recall the steps. Makes sense. Thanks.
Edit: I wouldn't recommend Odin any tar. I believe you still cannot go backwards regarding Odin. The OG5 bootloader won't allow downgrade flash.
Sent from my SM-N910P using Tapatalk

nacron said:
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So your saying unless you are running stock rom and no root there is no way to get android pay to work
cheryl

In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.

dh350nwo said:
In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.
Click to expand...
Click to collapse
What if you went stock set it up avd than flashed back custom rom... does it do the same ssfety checks even after it is setup?
cheryl

Stuck in boot loop

I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1

Thuganomics said:
I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1
Click to expand...
Click to collapse
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin to flash custom recovery would be a prerequisite for rooting stock with those zips or custom ROM zip.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk

samep said:
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin would be a prerequisite for rooting stock with those zips or custom ROM zip.
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the TWRP 2.8.1.1 and im able to access the menu in recovery mode however I still get stuck on the boot loop with no kernel even though I had one on the phone before starting the process

Have you flashed the Beastmode kernel and SuperSU zip linked in the post I linked you to above? Are you getting a message indicating no kernel installed? A ROM flash or those zips would get a kernel onboard.
If you're stuck, just try OBAR ROM on a clean install. You can find it in development forum.
Sent from my SM-N910P using Tapatalk

I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.

Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
The link is live in the post above. Scroll down to where SuperSU zip is linked as well. Flash both those in TWRP recovery.
You'll still need to freeze or remove Knox. There's some other notes that apply to stock in that post, like the build.prop edit.
Sent from my SM-N910P using Tapatalk

Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.

jhill110 said:
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.
Click to expand...
Click to collapse
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?

Thuganomics said:
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?
Click to expand...
Click to collapse
Odexed is better for performance, deodexed is a better choice for moding. I always use deodexed as the performance of this device is outstanding.
As for the battery issues, I use GSam battery monitor (there are many others). It helps you see what is using up battery.
Go through the system settings and turn off things that aren't necessary for you. Many of them contribute to battery drain. It's a drip, drip, drip thing... Not any one thing. A process of learning what helps and what doesn't. There's no catch all answer... You've got to work at it.

Update ROM without losing kernel?

A while back I flashed an old OS using ODIN in order to root my device, and I wasn't sure what the best way of upgrading back was. I have TWRP installed so I can flash that way, but I could also use ODIN if I will keep root with it.
Anyway, I'd like to upgrade to the latest version of KitKat possible, which I think is T800XXU1ANK1. I found a very specific kernel, SkyHigh, which reportedly will only work on KitKat ROMS, and I'd like to keep using it as it's the only kernel I've found that will let me use my wired Xbox 360 controller (with a USBtoGo cable). What's the best way to upgrade to this KitKat ROM? I found the download from samsung-updates.com, but I know I need to use ODIN for that, and won't that take away my root? Thanks for any advice!

I'm pretty sure upintheair has updated his skyhigh kernel to work with lollipop, so why stick with an older outdated os?
As for updating. Just go ahead and flash it with odin. You will lose root but getting it back it is a mere trivial matter of flashing CFautoroot again or rooting with twrp.
EDIT: Yep here you go LL version.
http://forum.xda-developers.com/showthread.php?t=3132652

Thank you so much! Sorry, I think I was confusing different root methods, and didn't realize I could flash CFautoroot again on any firmware. Thanks again, especially for the LL version of skyhigh, I had no idea that existed.
ashyx said:
I'm pretty sure upintheair has updated his skyhigh kernel to work with lollipop, so why stick with an older outdated os?
As for updating. Just go ahead and flash it with odin. You will lose root but getting it back it is a mere trivial matter of flashing CFautoroot again or rooting with twrp.
EDIT: Yep here you go LL version.
http://forum.xda-developers.com/showthread.php?t=3132652
Click to expand...
Click to collapse

Proper system root for marshmallow?

I'm looking for a proper system root for a marshmallow note 4 Rom. Systemless is causing problems. Is it possible? Preferably with a stock Rom.

tooandrew said:
I'm looking for a proper system root for a marshmallow note 4 Rom. Systemless is causing problems. Is it possible? Preferably with a stock Rom.
Click to expand...
Click to collapse
You can try flashing freeza's Beastmode kernel trough TWRP & then flash SuperSU 2.65.
Everything will work properly!

tooandrew said:
I'm looking for a proper system root for a marshmallow note 4 Rom. Systemless is causing problems. Is it possible? Preferably with a stock Rom.
Click to expand...
Click to collapse
yea i been having issues with it too
i noticed that when i flash 5.1 i have a boot logo
with 6.0 i dont get that just a samsung screen and then it boots
when it used to say samsung then sprint then boot.

Still looking for system based SuperSU root?
Try freeza's Note 4our beta 3 for MM PE1/PE2. includes integrated Xposed framework and a few custom Xposed mods as well. Requires clean install.
http://forum.xda-developers.com/showthread.php?p=63028063
Sent from my SM-N910P using Tapatalk