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

Okay to upgrade from 4.1.2?

New to this phone and I am running 4.1.2 there is a system update a 4.3 that's already downloaded and ready to install but I wanted to make sure the update didn't install any new locks on my phone before I accept. I plan on rooting soon.
Thanks
Rich

U get knox but there are ways to still root with knox so go ahead update
High Definition Note II

Uuum hold on. If you plan to root your phone there is no point in allowing the OTA which does install KNOX. Root now and save that extra trouble.

tx_dbs_tx said:
Uuum hold on. If you plan to root your phone there is no point in allowing the OTA which does install KNOX. Root now and save that extra trouble.
Click to expand...
Click to collapse
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..

I Would Accept It.
doubledragon5 said:
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
Click to expand...
Click to collapse
If I was in this position, I would accept the update as doubledragon5 said and move forward with root, etc. I have 4.1.2 right now and want the 4.3 update, but I'm rooted and trying to figure out how to unravel this to get to 4.3 myself.

flashred said:
If I was in this position, I would accept the update as doubledragon5 said and move forward with root, etc. I have 4.1.2 right now and want the 4.3 update, but I'm rooted and trying to figure out how to unravel this to get to 4.3 myself.
Click to expand...
Click to collapse
If your rooted, go back to bone stock MC2 like I have mentioned in a few other threads. accept the 4.3 udate from sprint, re-root using the tookit, then flash away...

doubledragon5 said:
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
Click to expand...
Click to collapse
doubledragon5 said:
If your rooted, go back to bone stock MC2 like I have mentioned in a few other threads. accept the 4.3 udate from sprint, re-root using the tookit, then flash away...
Click to expand...
Click to collapse
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.

flashred said:
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
Click to expand...
Click to collapse
I'm wondering the same thing. But if we root then accept the OTA won't that enable the knox counter? So that if we now, "flash away".... won't every flash be counted?
Shouldn't we root, then install the custom roms without the knox? Or do the custom roms also include the knox counter tripping mechanism?
I would like to know how this works also.
Thanks.

I just recently came from 4.1.2 rooted running a deoxided stock rom. I didn't do the OTA update to 4.3. I used the TeamRejects Deoxidexed rooted deknoxed stock rom, the updated MK4 modem, and the WiFi fix. It took about 15-20 minutes to get everything done. I needed to download Odin too for WiFi fix. I didn't run the WiFi fix till I knew there was an issue.
Not much of complaint, but I wish there was a kernel like Perseus for TouchWix based roms. The only one I found was Devil Kernel, but for whatever reason, wasn't stable with TeamReject's ROM. I didn't really care for his custom Kernel ajdustment manager and STweaks didn't work with it at all. Ideally, I prefer a stock rooted deknoxed deoxidized bare bones rom (just phone, contacts, google play) so I have a working phone and can access Google Play so I can install the apps I prefer. The closest I found was Classic Rom but it freezes on initial rom load; Plus, I'm not a fan of the colors and the few things he choose to include.

Stock 4.3 Deodexed, deknoxed, Rooted Rom Available?
lovekeiiy said:
I just recently came from 4.1.2 rooted running a deoxided stock rom. I didn't do the OTA update to 4.3. I used the TeamRejects Deoxidexed rooted deknoxed stock rom, the updated MK4 modem, and the WiFi fix. It took about 15-20 minutes to get everything done. I needed to download Odin too for WiFi fix. I didn't run the WiFi fix till I knew there was an issue.
Not much of complaint, but I wish there was a kernel like Perseus for TouchWix based roms. The only one I found was Devil Kernel, but for whatever reason, wasn't stable with TeamReject's ROM. I didn't really care for his custom Kernel ajdustment manager and STweaks didn't work with it at all. Ideally, I prefer a stock rooted deknoxed deoxidized bare bones rom (just phone, contacts, google play) so I have a working phone and can access Google Play so I can install the apps I prefer. The closest I found was Classic Rom but it freezes on initial rom load; Plus, I'm not a fan of the colors and the few things he choose to include.
Click to expand...
Click to collapse
So, you came exactly where I did except you with a different ROM. I would like to get from my 4.1.2 rooted up to 4.3 rooted stock,deodexed, deknoxed if at all possible.

flashred said:
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
Click to expand...
Click to collapse
Sorry for not getting back sooner. I have been busy with work, and family things.Use billards return to full stock with counter reset. It installs everything including recovery, boot loader,firemware etc... Then set up your phone, when prompt accept the ota update.. Once done retoot, and flash what ever 4.3 rom you want.. The knox counter will still be there, but if you need a trip back to Sprint, go back to Full MC2 stock, knox counter will no longer be there.. Most 4.3 room do not include the Knox files so no worries there.

flashred said:
So, you came exactly where I did except you with a different ROM. I would like to get from my 4.1.2 rooted up to 4.3 rooted stock,deodexed, deknoxed if at all possible.
Click to expand...
Click to collapse
Sounds like it. The odd part, I have been able to flash Reject's stock deoxidezed deknoxed rom with no problem. I tried to flash Classic 3, but it froze on Classic's initial loading page (the one after the Samsung boot loader). I had issues another rom, but turned out it was for the international model; I wasn't paying attention where I was in the forums.
If you do what I did, you'll need to flash modem update using Odin on the PC. So, you may need to download Odin.
---------- Post added at 05:04 AM ---------- Previous post was at 04:56 AM ----------
Depending on what you like to do, you may find 4.3 MK4 more limiting, espcially on the TouchWiz side. AOSP probably more mod friendly at this point. From what I've been able to find, there is only one custom kernal for 4.3 TouchWiz which is Devil's Kernal. It's solid, but my phone was unstable. Not sure if the phone since I may have taken out something it used when I was trying to debloat the phone. Didn't care for his Kernel Tweak manager. Neither the stock or devil's kernal supports Stweaks. Neither I could figure out how to change the boat loading animation.
I have nothing against AOSP projects. I like them. But as far as I know, none support the Spen, which I like to use with web browsers. Don't use the Samnsung Spen apps. Just wasn't that impressed with them, but I see how they can be useful. Although, SketchPro is really nice with it. I just find TouchWiz is more than sufficient for my needs and stock isn't as quirky.

Rooted 5.0.1 to 5.1.1 Custom Rom

Hey everyone,
I've been curious about upgrading my rooted Note 4 from Lollipop 5.0.1 to a custom rom in 5.1.1, but I don't want to take a risk and brick my phone because I didn't know what I was doing. I'm not sure what steps to get to 5.1.1 and I know for a fact that if I attempt to install a 5.1.1 rom onto a 5.0.1, I am sure that I'll run into some issues.
Can anyone assist me in getting to 5.1.1? I'm not too sure of the terminology, all I know is that I'm on an OB7.

GreenFire999 said:
Hey everyone,
I've been curious about upgrading my rooted Note 4 from Lollipop 5.0.1 to a custom rom in 5.1.1, but I don't want to take a risk and brick my phone because I didn't know what I was doing. I'm not sure what steps to get to 5.1.1 and I know for a fact that if I attempt to install a 5.1.1 rom onto a 5.0.1, I am sure that I'll run into some issues.
Can anyone assist me in getting to 5.1.1? I'm not too sure of the terminology, all I know is that I'm on an OB7.
Click to expand...
Click to collapse
Id download the latest noterized (from Android Development) and put that zip on your sd card.
Go to recovery and make a backup.
While in recovery go to wipe, advanced and wipe everything x3 except for Micro SD
Then go to install and flash the noterized zip file.
An Unlocked bootloader is such a terrible thing to waste.
If you dont like it, all you have to do is repeat the wiping procedures in recovery and restore backup.
Or beforehand, if you run into some bumps, use the search feature while in that thread to see if any problems youre running into have already been asked and answered.
Glad you brought that up, i meant to mention that also @ the loss of xposed on 5.1.1

You have a phone that some would rather have than one they have if the bootloader is OB7. If that is the last full update you took, it should be OB7.
If Xposed framework and modules or staying on an unlocked bootloader that allows downgrade to KitKat isn't your thing, the full update to OG5 would be OK to flash to reactivation locked bootloader. (If true, skip next paragraph)
If keeping the OB7 bootloader, there are two recommended methods to update to OG5 while retaining OB7 bootloader. One is to flash the OG5 modem then flash a OG5 ROM. See freeza ROM OP in development for his modem, kernel and ROMs for OG5. The second method is to Odin the OB7 to OG5 tar ball by tx_dbs_tx in development. Follow the OPs for instructions.
There's a guide if you just want to upgrade and root OG5. If it's a custom OG5 ROM you're looking for, you can just do the Odin flash OF5 stock tar and custom recovery. In recovery, flash a pre-rooted OG5 ROM. I'd suggest a clean install with either method.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Edit: one last comment. If you do want Xposed, it's not yet available for TW 5.1.1
Sent from my SM-N910P using Tapatalk
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
xxSTARBUCKSxx said:
Id download the latest noterized (from Android Development) and put that zip on your sd card.
Go to recovery and make a backup.
While in recovery go to wipe, advanced and wipe everything x3 except for Micro SD
Then go to install and flash the noterized zip file.
An Unlocked bootloader is such a terrible thing to waste.
If you dont like it, all you have to do is repeat the wiping procedures in recovery and restore backup.
Or beforehand, if you run into some bumps, use the search feature while in that thread to see if any problems youre running into have already been asked and answered.
Click to expand...
Click to collapse
Good advice. Posted while I was thinking somewhat on the same point of view regarding OB7.
Sent from my SM-N910P using Tapatalk

So I'm guessing once when I upgrade to OG5 I'm taking away the unlocked bootloader feature? What is OG5 technically doing to the Note 4?

GreenFire999 said:
So I'm guessing once when I upgrade to OG5 I'm taking away the unlocked bootloader feature? What is OG5 technically doing to the Note 4?
Click to expand...
Click to collapse
Reactivation lock is a theft preventative mandate. If you set it, a password is required to overwrite your locked device and account. A would be thief wouldn't be able to unlock it or flash it to become the new owner. He would brick it trying. Am I wrong? I still haven't adopted the new bootloader to see any of this first hand.
The lesser security bootloaders are blocked to Odin. Updating means you can't go back to OB7 or KitKat complete tars. Noterized can be flashed because it doesn't attempt to make your device fully compatible with OB7. But that's not making an OG5 reactivation bootloader compatible with OB7 ROMs to freely flash at will. Semi bricking occurs when users try to flash full tars or go back to KitKat. Some even make the mistake of thinking going to Noterized frees them to flash other ROMs and tars that they shouldn't. Despite some claims of success, no history of a proven method exists outside of wasted time and confusion and bricks some users couldn't figure out even with help given.
I haven't been on a reactivation bootloader but going by claims of others and reading, it appears to be something new each update. OE1 didn't get a tar so users that rooted were stuck until OF5 official tar was released. When OG5 came out, some posted OF5 backups were not flashing. OG5 also blocks root by the traditional CFAutoRoot used in prior updates for KitKat and Lollipop. It takes the exploit of kernel plus SuperSU zip to root OG5.
All this has brought the added wait until development catches up concept to update prior to taking something like an OTA if you value root. And some have reported rooting has even defeated the ability to take OTA updates as well. Add to the the latest claim that the stock OG5 kernel is required in order to Odin a fresh OG5 tar over rooted OG5 means you have to be up on current events to avoid boot loops on OG5.
No Xposed on TW 5.1.1 means I'm staying away a little longer.
Got all that? Some of it is just theory. The guide I referenced earlier also had some more advice for OG5. I believe it's as short but exhaustive as possible in a single post. It's important for newcomers to make informed decisions. Best wishes on making the right one for you. Personally, I'm on OB7 deodexed for Xposed Lollipop and Wi-Fi Calling. I chose to stay with lollipop because Wi-Fi Calling is not very good on KitKat. Otherwise, KitKat is very good but development is following the recent updates.
Sent from my SM-N910P using Tapatalk

samep said:
Reactivation lock is a theft preventative mandate. If you set it, a password is required to overwrite your locked device and account. A would be thief wouldn't be able to unlock it or flash it to become the new owner. He would brick it trying. Am I wrong? I still haven't adopted the new bootloader to see any of this first hand.
The lesser security bootloaders are blocked to Odin. Updating means you can't go back to OB7 or KitKat complete tars. Noterized can be flashed because it doesn't attempt to make your device fully compatible with OB7. But that's not making an OG5 reactivation bootloader compatible with OB7 ROMs to freely flash at will. Semi bricking occurs when users try to flash full tars or go back to KitKat. Some even make the mistake of thinking going to Noterized frees them to flash other ROMs and tars that they shouldn't. Despite some claims of success, no history of a proven method exists outside of wasted time and confusion and bricks some users couldn't figure out even with help given.
I haven't been on a reactivation bootloader but going by claims of others and reading, it appears to be something new each update. OE1 didn't get a tar so users that rooted were stuck until OF5 official tar was released. When OG5 came out, some posted OF5 backups were not flashing. OG5 also blocks root by the traditional CFAutoRoot used in prior updates for KitKat and Lollipop. It takes the exploit of kernel plus SuperSU zip to root OG5.
All this has brought the added wait until development catches up concept to update prior to taking something like an OTA if you value root. And some have reported rooting has even defeated the ability to take OTA updates as well. Add to the the latest claim that the stock OG5 kernel is required in order to Odin a fresh OG5 tar over rooted OG5 means you have to be up on current events to avoid boot loops on OG5.
No Xposed on TW 5.1.1 means I'm staying away a little longer.
Got all that? Some of it is just theory. The guide I referenced earlier also had some more advice for OG5. I believe it's as short but exhaustive as possible in a single post. It's important for newcomers to make informed decisions. Best wishes on making the right one for you. Personally, I'm on OB7 deodexed for Xposed Lollipop. I chose to stay with lollipop because it's not very good on KitKat. Otherwise, KitKat is very good but development is following the recent updates.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the great description. I think I will stick with OB7 a little longer until I find a better reason to change to OG5. Sounds like it would be more of a hassle trying to troubleshoot on OG5 if I do screw something up. I might just go down your route and pick up Xposed to see where that takes me.

GreenFire999 said:
Thank you for the great description. I think I will stick with OB7 a little longer until I find a better reason to change to OG5. Sounds like it would be more of a hassle trying to troubleshoot on OG5 if I do screw something up. I might just go down your route and pick up Xposed to see where that takes me.
Click to expand...
Click to collapse
For TW Lollipop, you'll need a deodexed ROM for Xposed framework.
Stable using official alpha 3 v4
xposed-v65-sdk21-arm-arter97-V5-krait.ziphttp://forum.xda-developers.com/show...20&postcount=1
arter97-V6 for Xposed-v71 is available but I haven't tried it. There are reports of boot loops on various devices; IDK if anyone else has had success with this phone yet? I'd suggest what's stable until you know otherwise.
Install Xposed Installer as sideload. (Install browsing to it with a root browser and tap file, selecting install.) Flash the arter zip in recovery. Initial boot after flash and the framework should be installed and ready for adding modules. Reboot to apply modules.
Sent from my SM-N910P using Tapatalk

Stuck in boot loop & No OS installed. NEED HELP!

I tried to root and flash a room onto my Sprint Note 4 (N910P) and ended up in a weird bootloop. No biggie I've done this before with my S3 and S4 and a few S6 Phones.
NOPE!! I have NO OS installed.
I would post photos but since I am new here I cant. I have TWRP intalled (v.2.8.7.0) and it says "No OS installed! Are you sure you wish to reboot?" I only wiped dalvik cache and regular cache. and factory reset per instructions for rom. (Rom that was being installed was AllianceROM©N910P
I was running on Android version 5.0.1 not the latest OTA 5.1.1 I didnt update it to that since I never had a good time with OTA's and rooting.
Any assistance would be helpful as i just got the phone and now I dont have a working one at all
Thanks!

Do you know what release of Android 5.0.1 you had? Alliance is only compatible with the OB7 release.
Without much detail of what actually happened, I'd suggest rebooting the recovery and trying that flash again or another ROM like Noterized that should flash over the other builds.
Did you uber wipe or wipe everything but ExtSdCard maybe? If you used Odin, what did you flash and did you get any error messages?
Sent from my SM-N910P using Tapatalk

samep said:
Do you know what release of Android 5.0.1 you had? Alliance is only compatible with the OB7 release.
Without much detail of what actually happened, I'd suggest rebooting the recovery and trying that flash again or another ROM like Noterized that should flash over the other builds.
Did you uber wipe or wipe everything but ExtSdCard maybe? If you used Odin, what did you flash and did you get any error messages?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually found that I had the the one before OB7 Just spent 10 hours of trial and error and fixed my problem Basically just installed the OF5 stock rom and got rid of the other roms that wernt working.
Thank you for replying and assisting me :good:

Ninja Danny said:
I actually found that I had the the one before OB7 Just spent 10 hours of trial and error and fixed my problem Basically just installed the OF5 stock rom and got rid of the other roms that wernt working.
Thank you for replying and assisting me :good:
Click to expand...
Click to collapse
Good. FYI, OF5 came after OB7. It's important to know for a few reasons. Custom ROMs are limited for OF5 (Noterized and CM12 mostly; maybe some stock ones available also).
That OF5 (including OE1 and OG5) bootloader is reactivation locked to the point that Odin of a previous tar like OB7 or KitKat is going to cause a lot problems trying to flash something that actually boots again.
For some reason, a few have complained of inability to Odin latest OG5 from OF5 but had to first Odin OF5 and OTA update to OG5.
But if you want a custom ROM there's newer development going on in OG5. I'd try KIES or Odin OG5 stock tar if wanting to go that way. I think most on OF5 were able to Odin OG5 but not positive on that. Sorry to say that Alliance is not for you with that bootloader.
Sent from my SM-N910P using Tapatalk

samep said:
Good. FYI, OF5 came after OB7. It's important to know for a few reasons. Custom ROMs are limited for OF5 (Noterized and CM12 mostly; maybe some stock ones available also).
That OF5 (including OE1 and OG5) bootloader is reactivation locked to the point that Odin of a previous tar like OB7 or KitKat is going to cause a lot problems trying to flash something that actually boots again.
For some reason, a few have complained of inability to Odin latest OG5 from OF5 but had to first Odin OF5 and OTA update to OG5.
But if you want a custom ROM there's newer development going on in OG5. I'd try KIES or Odin OG5 stock tar if wanting to go that way. I think most on OF5 were able to Odin OG5 but not positive on that. Sorry to say that Alliance is not for you with that bootloader.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I would like to root and get a rom on my note soon but I haven't run a big problem like this in my years of modding (mind you its here and there modding and nothing fancy) for now im gonna stick with bloated stock until a decent non-buggy rom is released for the OF5 bootloader. I didnt know which was which since im new to the Note Family. Been in the S2-4 series most of my time.
Looking for a good stable rom with no bloat and adblocking, nothing fancy
Thanks again.

Ninja Danny said:
I would like to root and get a rom on my note soon but I haven't run a big problem like this in my years of modding (mind you its here and there modding and nothing fancy) for now im gonna stick with bloated stock until a decent non-buggy rom is released for the OF5 bootloader. I didnt know which was which since im new to the Note Family. Been in the S2-4 series most of my time.
Looking for a good stable rom with no bloat and adblocking, nothing fancy
Thanks again.
Click to expand...
Click to collapse
I would suggest @tx_dbs_tx 's Hybrid x 3.0. You can unzip it and remove whatever you don't want re-zip and then flash it.
Find it here :
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and you'll be good to go.

jhill110 said:
I would suggest @tx_dbs_tx 's Hybrid x 3.0. You can unzip it and remove whatever you don't want re-zip and then flash it.
Find it here :
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and you'll be good to go.
Click to expand...
Click to collapse
Would that work for my phone thats running OG5? android version 5.1.1 ?
*Edit*
I am going to try to flash this and see if it works. I will update on progress.

Ninja Danny said:
Would that work for my phone thats running OG5? android version 5.1.1 ?
*Edit*
I am going to try to flash this and see if it works. I will update on progress.
Click to expand...
Click to collapse
I will repeat this (not with condescension) read the OP carefully... And you will be good.

jhill110 said:
I would suggest @tx_dbs_tx 's Hybrid x 3.0. You can unzip it and remove whatever you don't want re-zip and then flash it.
Find it here :
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and you'll be good to go.
Click to expand...
Click to collapse
jhill110 said:
I will repeat this (not with condescension) read the OP carefully... And you will be good.
Click to expand...
Click to collapse
It worked fine, phone runs like a dream. Only issue is the stock camera is very poor quality so I might mod that next.

[ROM] [N910PVPS4COK1] [100% Stock, Root, Odexed&Deodexed, No KNOX/Itson] [12/15/2015]

[ROM] [N910PVPS4COK1] [100% Stock, Root, Odexed&Deodexed, No KNOX/Itson] [12/15/2015]
Once again I bring to you two completely stock builds of Android TW-Lollipop 5.1.1 (N910PVPS4COK1) for the Sprint Samsung Galaxy Note 4.. Both ROMs are built from the official Samsung tar ball. The ROM will self root upon flash and it has init.d/busybox support. Knox and Sprint Itson has been removed. Both ROMs are completely stock with all of the original factory installed apps. Available in odexed and deodexed. Both ROMs are identical other than one being odexed and the other deodexed. Also included in both ROMs in this thread is the stock OK1 modem and APN patch to ensure you have the latest modem & APN's from the latest OK1 software.
Other than the removal of Knox and Sprint Itson, these roms are 100% stock in every other way. They are stock and will stay that way. Please don't ask for mods, changes, etc in this thread. These roms are intended for those people who want the stock roms in their original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base ONLY if you contact me prior to using it. If I find users using my work without proper credits I will report you and make you look like a fool I promise. Do the right thing and give credits to people for their time and work. It's a curtesy and respect thing nothing more. With that said, I highly recommend other rom chef's/dev's to use this base rom because it is bug-free and built from the official Samsung tar ball. Last but not least, if you appreciate my work please press that Thanks button, rate this thread and consider a kind donation! Enjoy!
Mods and fixes will be in post #2 below.
Important Notes: Before flashing ANY Lollipop 5.1.1 TW-based ROM, including this one, you MUST first do one of the following:
1. Take the Lollipop OK1 ota update on your phone. (Start by being on the stock unrooted OJ6 rom then take the OK1 ota update)
2. Odin flash the stock OK1 rom tar using odin on your PC. Thanks @samep
http://forum.xda-developers.com/showpost.php?p=64337077&postcount=115
Once you have correctly updated your Note 4 to Lollipop 5.1.1, software version N910PVPS4COK1 DO NOT... I repeat, DO NOT attempt to root your phone with CF-auto root or other methods. It will soft brick your phone. Instead, you ONLY need to flash the latest TWRP recovery using odin on your pc. Nothing else. The ROM zip will automatically root your phone.
If you are still on any KK or Lollipop 5.0 TW-based ROM such as NIE, NK2, OB7, OE1 , OF5, OB7 or OJ6 (including any KK AOSP/CM-based roms) then you MUST first update to Lollipop 5.1.1 OK1 by one of the two methods I mentioned above BEFORE flashing this ROM. Failure to properly update your device partitions to 5.1.1 OK1 firmware absolutely WILL cause problems. You have been warned. Please don't ask for help if you did not follow my simple instructions and warnings.
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal and external storage to another location just to be safe.
2. Download the rom using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the MD5!!! Once the download has finished, compare the androidfilehost MD5 using a MD5 tool on your pc. (Google "md5 checksum windows") for a good MD5 tool for your pc.
4. Put the downloaded rom onto your internal storage or external micro sd card.
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT micro-sd card and internal storage. Internal storage is optional but recommended when first updating to a major software revision such as 4.3 to 4.4 or 5.0.1 to 5.1.1. The reason is to remove left-over data from previous version of Android and start with a clean slate.
7. Choose the "Install" option and select the rom "Sprint_Stock_N910PVPS4COK1_XXX" from either your internal or external micro-sd card. It will flash the rom and give a confirmation once completed.
8. Press "Reboot" then "reboot system". You will get a prompt warning about not having root. Please IGNORE IT and DO NOT allow TWRP to apply root! If you do then you MUST wipe everything and start over at step 5 above and reflash the rom in order to get rid of the traditional root system binaries. ***Please pay attention and DO NOT let TWRP install root. Ignore the "No Root" warning.***
9. Initial rom "optimization" will take several minutes for the deodexed rom while ART builds its cache (the odexed rom takes much less time for first boot). The phone will remain on the yellow Sprint Spark screen for about 10 -13 minutes during this time. Let the phone optimize for at least 13 minutes (for the deodexed rom) and the screen will eventually turn off or show the setup wizard once it finishes. When the screen turns off, simply turn it on and proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically install the Sprint apps. You must either "accept" or "disagree" with each and every google prompt for these apps or else the installs pause until you do so.. Also you will be prompted for the "connections optimizer". Quickly set it to what you want and close it. That's it! You're done!
One last bit of important information... If you allow any system update or Samsung security update to install it WILL break root. I advise everybody to disable automatic updates which is located in Settings/System update.
You can allow an update to install but you will then need to flash the beta systemless SuperSU packages located in HERE in order to regain systemless root.
Credits:​@Chainfire for root and SuperSU. Without him we would not have root. Thank you!​@TeamWin for TWRP recovery. http://teamw.in/project/twrp2 and here​
General disclaimer:​flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device. However, all of my roms, mods, etc are pre tested by myself and other testers prior to public release.
Sprint_Stock_N910PVPS4COK1_Odexed​Sprint_Stock_N910PVPS4COK1_Deodexed​
XDA:DevDB Information
Stock-Rooted-N910PVPS4COK1, ROM for the Sprint Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910PVPS4COK1
Based On: SPR-N910PVPS4COK1-20151209172046
Version Information
Status: Stable
Stable Release Date: 2015-12-15
Created 2015-12-16
Last Updated 2015-12-16

Mods & Fixes​---------------------------------------------------------------------​Odexed-Deodexed-N910PVPS4COK1-Hotspot-Mod (This can be flashed on odexed or deodexed OK1 roms)
N910PVPS4COK1-PrivateMode-Fix (This can be flashed on odexed or deodexed OK1 roms)

Reserved

Thanks tx. I'll take the update in the morning, and flash this. We appreciate all that you do.
Sent from my SM-N910P using Tapatalk

Nice work! Just in time!

So far so good as usual.
Interesting thing, Software OK1, Baseband OJ6, Bootloader OB7.
Thanks for this Tx. It will help the anxiety while we wait for Marshmallow. :thumbup:
Yep, didn't flash the stock tar.
Now to see about wanam xposed.

jhill110 said:
So far so good as usual.
Interesting thing, Software OK1, Baseband OJ6, Bootloader OB7.
Thanks for this Tx. It will help the anxiety while we wait for Marshmallow. :thumbup:
Yep, didn't flash the stock tar.
Now to see about wanam xposed.
Click to expand...
Click to collapse
That's interesting. You should still have the OK1 modem after flashing either of these roms because I included it in the rom zips.

tx_dbs_tx said:
That's interesting. You should still have the OK1 modem after flashing either of these roms because I included it in the rom zips.
Click to expand...
Click to collapse
I'll play with it tonight, backup and flash the stock tar. Go from there and see.

Well if you flash the OJ6 tar then take the OK1 ota update then you will definetely get the OK1 modem. No worries do as you want. I was just suprised to hear that the OK1 modem didn't stick when flashing this rom. You really should update your entire firmware, bootloader etc to latest OK1. Unles you want to run older KK and Lollipop 5.0 software.

tx_dbs_tx said:
Well if you flash the OJ6 tar then take the OK1 ota update then you will definetely get the OK1 modem. No worries do as you want. I was just suprised to hear that the OK1 modem didn't stick when flashing this rom. You really should update your entire firmware, bootloader etc to latest OK1. Unles you want to run older KK and Lollipop 5.0 software.
Click to expand...
Click to collapse
First thing in the morning. I'm all blurry eyed. ?
Thanks again Tx.
EDIT:
Flashed OK1 Tar, wiped everything, flashed this rom, restored all my apps and I picked up 9gb of internal storage. Lotta leftover junk.
Wanam xposed is working perfectly.

I rooted my daughters phone back in March and left it stock. Didn't even put TWRP. She wanted some updating... Ao I flashed back the stock tar from ANIE (which is what she had on the phone)
It downloaded 1 update. The cok1. 1.7 gb.
So that phone should be good to go...?

JohnnyEpic said:
I rooted my daughters phone back in March and left it stock. Didn't even put TWRP. She wanted some updating... Ao I flashed back the stock tar from ANIE (which is what she had on the phone)
It downloaded 1 update. The cok1. 1.7 gb.
So that phone should be good to go...?
Click to expand...
Click to collapse
Yes sir you will be good to go with this rom or any OK1 base Touchwiz rom.
I will try to start on a new custom OK1 rom soon. I gotta juggle my free time so not sure how much time i'll have to spend on it. I will have to manually redo all of the mods, etc.

Thank you, tx_dbs_tx!

I was on OJ6 when I flashed this rom and it still says that I'm on OJ6.

dbug2008 said:
I was on OJ6 when I flashed this rom and it still says that I'm on OJ6.
Click to expand...
Click to collapse
You didnt odin to the latest COK1 tar file.

Anyone else notice they patched the ability of iapps to get msl and unlock again
Sent from my 0x1 Note 4...... I love tep

I'm on your oj6 rom, my phone and pc doesn't detect sdcard but root explorer does. Is their anyway I can update to this rom without a working sdcard?
Sent from my SM-N910P using Tapatalk

allcity187 said:
I'm on your oj6 rom, my phone and pc doesn't detect sdcard but root explorer does. Is their anyway I can update to this rom without a working sdcard?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
If by detect you mean can't write to it use sdfix from the play store.
As this rom is stock without knox & itson it has the same issue with same fix.
Tx may (or not) update his rom (hybrid series) to OK1 in which case it would not be an issue.
I would suggest you Odin the stock OK1 Tar after backing up EVERYTHING including internal storage and wipe everything including internal storage. Then flash this rom.
But thats just me...
Edit.
Just reread your post...hmm pc and phone don't detect the card... Get to OK1 just the same. ..

jhill110 said:
If by detect you mean can't write to it use sdfix from the play store.
As this rom is stock without knox & itson it has the same issue with same fix.
Tx may (or not) update his rom (hybrid series) to OK1 in which case it would not be an issue.
I would suggest you Odin the stock OK1 Tar after backing up EVERYTHING including internal storage and wipe everything including internal storage. Then flash this rom.
But thats just me...
Edit.
Just reread your post...hmm pc and phone don't detect the card... Get to OK1 just the same. ..
Click to expand...
Click to collapse
I have the ok1 tar, so when I Odin to ok1, how can I install this rom without a working sdcard? Thanks for the help.
Sent from my SM-N910P using Tapatalk

kaos420 said:
Anyone else notice they patched the ability of iapps to get msl and unlock again
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
You mean Galaxy tools? I had a hell of a time getting it to install. Ended up doing a complete wipe , flashing this rom and installing gt then restoring my apps. Took me a couple hours to figure it out. :sly:
Luv that app for easy access to hidden menu.