yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Android Development] tx_dbs_tx:
Both stock roms updated

Ok I updated both roms and reuploaded them. I replaced the kernel with the original stock kernel without root and I also updated supersu to the latest beta 2.65. As of today both roms are current with these changes.

So what I know for now is that the new systemless root by chainfire requires a pure stock kernel in order for it to be able to properly patch the stock kernel for root. Therefore systemless root needs the untouched stock kernel or it will not work. Surely this will have an effect on custom kernels and will be a work in progress for chainfire ad these latest supersu betas are still a work in progress. Being that these roms here are stock builds they will include the stock kernel which is perfectly fine for most people for day to day usage. What all of this means is if you want to run a custom kernel such as AEL, Emotion, Freeza's Beast Mode, etc then you will need to flash the custom kernel of choice then flash an earlier supersu package that has system binaries prior to 2.50.

One important thing to note is that installing the latest Samsung security update breaks root. So you have a couple of options. 1. Go into settings and turn off auto updates and do not install the updates OR... 2. Take the updates but know that you will need to flash the supersu package again to to regain root. So have the supersu zip on your sd-card/internal storage so you can quickly & easily get root again. Keep in mind that if you run a custom kernel you may want to use an older system root package that adds system binaries the traditional way unless the kernel dev has built the kernel to be fully compatible with systemless root. Check these things before you flash custom kernels. Another thing... once you root this rom with an older traditional system binary root package then you absolutely MUST wipe everything and reflash this stock rom before attempting to root again using systemless root. Systemless root requires a pure stock unrooted kernel and system. Period. Old root methods have not changed however. So that may be the easiest and most trouble-free option for custom kernel users right now until systemless root custom kernels are fully onboard with the latest systemless supersu by Chainfire.

As far as I can tell there's not a huge advantage to systemless root right now. The concept is great and if it can cure the problem with samsung pay & android pay apps not working due to them detecting root, then that alone would be worth having systemless root. Otherwise the old traditional system binaries seems fine to me especially if running custom kernels. Speaking of which, kernel devs will need to work on making versions of their kernels compatible with the latest systemless root method and indicate if they are such or not.

That's all I have for now. Sorry for the long post but I think everybody needs to know whats going on with yhe new beta root and its evolution moving forward along with Amdroid and Marshmallow and beyond.
[Sprint  Galaxy Note 4 Android Development] tx_dbs_tx:
Update: I found a problem in my updater script that breaks supersu so i will have to fix that and reupload both roms one last time. I will remove both rom links for now and add them back with the new links asap. Sorry for the confusion.

Edit: Both roms are now updated with links updated in the OP. ROM tester's initial flash test reported that root is good to go. However everybody needs to understand that you need to immediately disable system updates in settings/system update in order to prevent auto updates from breaking root. You can install samsung security updates but you will have to flash supersu again to regain root. More details are now available in the OP. Read the instructions again if you aren't sure about this stuff. Please report any issues if you find something. I see no reason for losing root anymore.
[Sprint  Galaxy Note 4 Android Development] yo0123yo:
You committment to help is admirable, thank you. I have a question. If I flash Xposed will I get unrooted? I'm still rooted on 5.1.1 on OK1 using the previous method you had posted. Reason I ask is because when I did just the OK1 kernel root a while ago and flashed Xposed, I became unrooted and got stuck in a boot loop. Which Xposed, if any, would you recommend?
[Sprint  Galaxy Note 4 Android Development] jhill110:
Flashing xposed won't lose root.

Use arm not arm64.
[Sprint  Galaxy Note 4 Android Development] richardjrdeal:
Just installed latest update today - Android Pay does not work even with wanam xposed spoofing device status to official (without shows custom). It installs, updates your reward cards, but will not allow you to add bank, debit/credit card accts and gives the same message that it (google) can't determine if the OS is android compatible.

Previously I got around this by setting it up prior to Odining TWRP and flashing SuperSU...so basically on stock, unrooted. However, after setting it up, installing TWRP, SuperSU, and then wanam xposed to spoof device status to official, all my info would stick, but when I tried to pay via NFC/Tap and Pay, as I did 10000 times when it was Wallet, it gives that same message of OS android compatibility. Good luck on finding a fix.
[Sprint  Galaxy Note 4 Android Development] tx_dbs_tx:
Samsung Pay and Android Pay

I believe once you odin TWRP you trigger the custom os flag. I don't see any way around this and spoofing doesn't actually change the flag back to stock. The thing is, once you odin a non official tar, it triggers the custom os flag no matter what you flash. And the only way to flash a custom rooted rom is to odin a custom recovery which triggers the custom os flag. I see no easy way around this. So for people who want to be able to use the pay apps you will need to stay on the stock unrooted rom.

Edit: the only thing I can think of that might allow the pay apps to work on rooted custom roms is to modify the pay app itself to disable the root and custom os check. But that may break the app. Not sure, i haven't messed with it yet.
[Sprint  Galaxy Note 4 Android Development] Stryprod:
I had the same issues as previous posters - fine and dandy and then the infinite boot loop.

I went ahead and followed the new instructions to a "t" and it looks like I lost root even withe new ROM. Odds are I'm doing something wrong, but I keep trying over and over and it looks like it is gone.

Specifically I add Titanium Backup. Open, grant privileges via SU, and unistall a couple programs. Reboot and the deleted programs are there again and working.

Never had these issues. I'm lost. Anyone else?
[Sprint  Galaxy Note 4 Android Development] mrtito32:
Thanks for the new upload, two days solid and I still have root. One thing I do have a question about is writing to SD card. One app I use is saying it can write to SD card, but my TB is on my card and it is working fine. Ran the SD Fix app from the playstore and got an error. Any suggestions? Thanks
[Sprint  Galaxy Note 4 Android Development] awilson77584:
Having the same experience with Titanium Backup
[Sprint  Galaxy Note 4 Android Development] awilson77584:
Is anyone using a 2015 Gear VR with this ROM?

Thx!
[Sprint  Galaxy Note 4 Android Development] pcmanager:
Try folder mount from the Play Store.
[Sprint  Galaxy Note 4 Android Development] Slypnslyde:
When i do go into system settings update it still says can't take software update because of modified system
[Sprint  Galaxy Note 4 Android Development] xyojimbox:
You have to odin back to stock to take an update
[Sprint  Galaxy Note 4 Android Development] Slypnslyde:
I thought systemless was able to get ota's
[Sprint  Galaxy Note 4 Android Development] wmatheney:
I'm not sure what's wrong but I odined the OK1 update coming from OB7 and my phone just keeps rebooting. I verified the md5 is good. I tried it twice. Anyone else experienced this?
[Sprint  Galaxy Note 4 Android Development] Erod730:
Try odin again and uncheck auto reboot, and then pull battery when it's done, I had to do that to get trwp to stick
[Sprint  Galaxy Note 4 Android Development] wmatheney:
[/COLOR]

I gave it a try but to no avail. I'm able to install twrp. It should, though, boot up before installing twrp, right? It gets to the point of "Preparing your device for first time use. This could take 3-4 minutes.". Then it keeps looping this way.

---------- Post added at 11:37 AM ---------- Previous post was at 11:29 AM ----------

To clarify, the looping issue is happening just after I odin the OK1 update, before installing twrp and this rom.

---------- Post added at 11:57 AM ---------- Previous post was at 11:37 AM ----------

I just went ahead and installed twrp and this rom and it's booting up fine. Don't know why it kept boot looping after I installed the stock OK1 but at this point it really doesn't matter since I'm up and going.
[Sprint  Galaxy Note 4 Android Development] j_svas:
I just googled through to buy a vr and realized that later gear vr is no more compatible with note 4 :(.

Anyone else using?
[Sprint  Galaxy Note 4 Android Development] awilson77584:
There is a thread for the 99 dollar gear vr. It requires some slight physical file work to make it fit.

I'm wondering about the performance with a note 4. The alternative is to upgrade to a note 5. I'm not certain how well relying on cloud storage would work out. A power bank can cover the battery design.

http://xdaforums.com/showthread.php?p=64424147
[Sprint  Galaxy Note 4 Android Development] pereth:
I am unable to install twrp after flashing the stock OK1 tar using ODIN. It fails in ODIN even though activation lock is off.

The twrp file is .img which ODIN doesn't see, so I converted it to a .tar.md5 using this script http://xdaforums.com/showthread.php?t=2446269 .

Am I missing something about how I should go about installing twrp? Why do they provide a .img when ODIN can't even see that to flash it?

---------- Post added at 06:06 PM ---------- Previous post was at 05:48 PM ----------

Nevermind, Sorry guys, finally found the proper TWRP download at https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar.html .

I was using the EDGE version, which was the only Sprint Note 4 that came up after clicking devices... I dont know why they don't list trltespr there...
[Sprint  Galaxy Note 4 Android Development] pereth:
Xposed Boot Loop

What version of Xposed are you guys using that is successful?

I am getting a boot loop after TWRP flashing the latest xposed-v79-sdk22-arm.zip on the deodexed rom. Any other tips to get Xposed running?
[Sprint  Galaxy Note 4 Android Development] samep:
Did you stop the auto updates as mentioned in the OP as one more important thing...?

If not, I'd recommend just flashing another kernel. The one linked below is the replacement for current kernel but you can also flash SuperSU 2.65 beta

http://xdaforums.com/showthread.php?p=64610967

Did you wipe cache and dalvik-cache when you flashed Xposed framework. It may take a while to boot.

Edit: didn't realize the quoted file was official rovo89 Xposed framework. We use Wanam unofficial Xposed for Samsung stock based ROMs. He caught that later...
[Sprint  Galaxy Note 4 Android Development] pereth:
I didnt stop the updates as i would rather get them, then install supersu 2.65 beta.

I didn't know to wipe cache and davlik, but unfortunately it still boot looped on the yellow sprint screen after starting over, installing beast kernel (was using ael before), and flashing xposed as you suggested. :( I let it loop many times before i restored a backup from just before installing xposed.

Thanks for the help, any more ideas?

---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------

And i double checked, I am using the deodexed version.

Need xposed for amplify and greenify... the battery gains from amplifying especially are insane!
[Sprint  Galaxy Note 4 Android Development] samep:
Why SuperSU 2.65? Installing custom kernel, I'd recommend a system based SuperSU. I don't know if SuperSU systemless root works or works well with custom kernel? Anyone?

If you've flashed the SuperSU 2.65 and custom kernel and it doesn't boot, try flashing unSU, kernel and SuperSU 2.52 or less and wipe cache and dalvik-cache before booting. Flash in that order; I'd also recommend busybox installer after that. See links below.

I've only tried SuperSU 2.52 beta so far with no issue. Running Xposed with deodexed ROM. Get unSU and busybox installer zip for recovery from osmOsis OP below.

http://xdaforums.com/showpost.php?p=40409356&postcount=1
[Sprint  Galaxy Note 4 Android Development] pereth:
I just said 2.65 cause thats what you had mentioned above that i could use.

I will try go back to stock deodexed rom, and try flashing unSU, beasrmode kernel, and SuperSU 2.52 (in that order) and wipe cache and dalvik-cache before booting, restart, then install xposed framework and see if I still loop.

For the record it booted fine after the beastmode kernel, and i already had supersu 2.65 beta, it just looped after installing xposed framework.
[Sprint  Galaxy Note 4 Android Development] samep:
Thanks for the follow up. When you flashed Xposed, did you wipe cache and dalvik-cache? Can't recall but IIRC, it suggests a wipe before reboot, correct? I think TWRP even pops-up a button for that? Watch for it and reply if you don't mind clarifying.

Also, when using systemless SuperSU, always ignore TWRP prompt to install SuperSU; TWRP doesn't properly recognize or advise regarding systemless root.
[Sprint  Galaxy Note 4 Android Development] pereth:
I had wiped cache and dalvik before installing xposed, not after. I just tried again wiping them after installing xposed, and unfortunately it still looped. Yep, after flashing xposed TWRP did in fact have the wipe cache and dalvik-cache as an option.

Yep, I have been ignoring the install SuperSU prompt each time.

Back at the drawing board on this Xposed boot loop. Any more ideas? Just fyi, I have tried installing the apk before the framework as well, didn't make a difference.
[Sprint  Galaxy Note 4 Android Development] samep:
I don't think it makes a difference when you wipe cache and dalvik-cache. I usually do it before, myself.

Only thing I can think of Is your download of Wanam framework is bad.

And when you booted prior to flashing Xposed, were you fully rooted to system SuperSU. IOW, was your SuperSU installed in system partition and launching? Correct install if true.

I'd suggest download Xposed again and make sure you're not getting the arm64 version. Maybe bad download? Can't imagine you'd have to start over if it booted before flashing Xposed and its download was good. It's been suggested that system be flashed anew to unSU but the script has worked for me. You may have to flash the ROM, kernel and SuperSU again.
[Sprint  Galaxy Note 4 Android Development] pereth:
I just checked, and yep, SuperSU was in the system partition (in the apps folder yeah?) and launching, tested that root was active. Verified it's not the arm64 version. Will try another download of it, but im afraid that's not it.

There were some others in boot loop after installing Xposed, anyone figure it out?

---------- Post added at 04:30 AM ---------- Previous post was at 04:02 AM ----------

Got Xposed working. Saw an xposed file on my sd card with TW (touchwiz) in the name. Googled the file name (since i forgot where i got it originally) and found the source, straight from Wanam. Link below to the latest version, updated just a few days ago. It is the Wanam framework, but customized to be compatible with touchwiz roms. Correct version is V79 SDK22 Arm for N910P.

http://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960

I tested it out, works great! I had to use this before on the hybrid ROM, apparently I need to use it on this one as well. Case closed! (and yes I did wipe cache and dalvik cache after flashing the framework, before rebooting).
[Sprint  Galaxy Note 4 Android Development] samep:
I might have missed the fact you got the original Xposed official framework from rovo89?

You are correct in this reply; use Wanam unofficial Xposed framework for Sammy stock. If that's the case, my mistake.

Sorry, man.
[Sprint  Galaxy Note 4 Android Development] JFay22:
Just fyi I am on deodex version with xposed v79 Wanam build and everything was working beautifully until I decided to update supersu to 2.66...once I did I booted up fine but lost mobile data. Luckily I had downloaded zip of 2.65 and flashed back and all was good again. Not sure why 2.66 made me lose connectivity...I read changelog and 2.66 was a minor update still systemless. If anyone knows I am curious to find out. Other than xposed I was on this ROM and kernel deodexed but I did install busybox with busybox pro app but installed to /su/bin which I researched to be the right install for supersu systemless versions. Thanks for any advice or feedback. Love this ROM...perfectly stable.
[Sprint  Galaxy Note 4 Android Development] samep:
Just what I know... I got a PM from [MENTION=4496540]LinuxGuru007[/MENTION] suggesting if I hadn't tried SuperSU 2.66 beta to skip it. That's all I know about the version until you confirmed. I haven't been using the systemless root since testing 2.65 but even that was temporarily losing reboot with my heavy modification which isn't recommended for systemless root. However, a reboot would recover root without boot looping.

Running deodex ROM with Xposed? Systemless root is not for you, IMO. I prefer Beastmode with permissive SELinux mode (pre-systemless SuperSU like 2.52 beta or 2.50 or 2.49). I haven't had issue with either of those.

Chainfire recommends leaving system stock untouched. Same for kernel. Patch stock. The intent was to retain OTA capability and it's only being tested on Marshmallow last I read.

I'd recommend the osmOsis unSU script and one of the earlier SuperSU betas flashed in recovery for you. I think SuperSU 2.50 was the last SuperSU targeted to Samsung 5.1x Lollipop but I've been using SuperSU 2.52 beta.
[Sprint  Galaxy Note 4 Android Development] JFay22:
You are right...thanks for the feedback. I wanted to try deodexex simply because I hadn't run deodexed on my N4. Personally I tried AEL, Emotion, Plasma on my stock rooted OK1 setup and while I enjoyed tweaking kernel settings I lost the stability I need since my phone is work/personal. Too many bootloops and FC's to make sense for me. My problem is I love xposed and the customization offered within so I probably do need to stick with odex with a permissive kernel like beastmode that stays close to stock. Thanks bro, you always give great guidance.
[Sprint  Galaxy Note 4 Android Development] Aloupha:
Hi Guys,

I have been getting stuck on a boot-loop, and I am not sure what the problem is. The first time it happened, I did a clean/fresh install, and I got passed the boot-loop. That was the day before today. Today, I rebooted the phone, and I am having the boot-loop issue again.

I did notice a security update that I tried not to install, but it somehow install itself. I am not sure if that is what's causing the boot-loop.

Anybody else experiencing the same issues?

Just to be clear, I am mostly using the rom as is... no xposed or anything. I just install simple market apps.
[Sprint  Galaxy Note 4 Android Development] jbuggy1:
Hey [MENTION=1503720]tx_dbs_tx[/MENTION] are you still working on 5n port or hybrid-x?

Or are you waiting for marshmallow?
[Sprint  Galaxy Note 4 Android Development] ianmb:
Patience brother, things are happening behind closed doors!
[Sprint  Galaxy Note 4 Android Development] hitdog44:
I know its not recommended, but has anyone dirty flashed without doing a clean wipe? Just curious to know if you are running into any issues. Thanks!
[Sprint  Galaxy Note 4 Android Development] shawn01:
I'm on COG5 hybrid 3.0, what's the best way to update to this ROM? Yes I read the directing but figured I would double check first.
[Sprint  Galaxy Note 4 Android Development] ianmb:
Depends on your current baseband and if it is OB7 whether or not you want to keep it.
[Sprint  Galaxy Note 4 Android Development] shawn01:
Baseband is cog5
[Sprint  Galaxy Note 4 Android Development] ianmb:
You're best bet would be to simply follow OP instructions. You can't go wrong...just do what it says.
[Sprint  Galaxy Note 4 Android Development] tommy_2q:
What is the easiest way to increase speakerphone volume on this ROM with minimal distortion?
[Sprint  Galaxy Note 4 Android Development] JFay22:
I use Viper 4 Android...works well

http://xdaforums.com/showthread.php?t=2191223
[Sprint  Galaxy Note 4 Android Development] jhill110:
Hey ian... Echoing your comment... Like I have said many times... READ THE DAMN OP! Look folks, if you want to go down path of bettering your device put in the work. Hand outs here are luxury not an obligation. Do your research... You will be justly gratified buy your own efforts...
[Sprint  Galaxy Note 4 Android Development] tommy_2q:
I've tried v4a and it doesn't work in all apps or situations.

I think pongoface surround sound mod might be the best solution?
[Sprint  Galaxy Note 4 Android Development] ianmb:
http://xdaforums.com/showthread.php?t=2952137

Try this. It has V4A and other mods rolled into one. Works and sounds great, even on bluetooth. Works for Pandora and other apps using sound, games, youtube, blah blah...
[Sprint  Galaxy Note 4 Android Development] Erod730:
I followed op for install and it says I'm rooted but some rooted apps say I'm not, I tried flashing super su zip, but my phone wouldn't stop rebooting, help?
[Sprint  Galaxy Note 4 Android Development] samep:
You fix it with a backup restore or get SuperSU fixed yet? Which SuperSU did you flash? System based SuperSU 2.52 and below will break systemless root.

Do you have the ROM before or after revision in post #121 of this thread? kernel and SuperSU were changed to stock and systemless SuperSU 2.65 beta.

There was an issue with updating systemless SuperSU to v2.67 The apk for SuperSU didn't install properly for some. That may be where your problem started? Flashing a system based SuperSU after that may break root and could explain the boot loop?
[Sprint  Galaxy Note 4 Android Development] h4kudoshi:
I cannot get rid of the "Activation Not Completed" notification. I followed the directions to install very clearly. I've disable auto-updates. Any clues how to get rid of it?
[Sprint  Galaxy Note 4 Android Development] ThanhLongThuVan:
Odexed ? Deodexed ? how difference ? not same rom ?
[Sprint  Galaxy Note 4 Android Development] samep:
I thought you were upgrading with stock OK1 tar to go to the Note 5 Ultimate port? You don't need this for that. You did find the stock tar in general, right?

To answer your deodexed question, deodexed is what is required to modify applications and framework. For users, Deodex ROMs are easier to modify system after Xposed framework is applied regarding Samsung stock.

Odex is what the original ROM is. It may be slightly faster in some ways but only slightly. It's closer to stock and if you care about that rather than heavily modifying the ROM, you could run Odex. With Lollipop and possibly Marshmallow, you'll likely find less mods in Odex ROMs but they can also be a hybrid mix of Odex applications and framework with some deodexed applications framework. As a user, you'd have to careful about flashing mods on Odexed ROM for compatibility reasons.

Your choice would depend on how you use it.
[Sprint  Galaxy Note 4 Android Development] uapyro:
Please delete, accidental post
[Sprint  Galaxy Note 4 Android Development] baltazargoodger3rd:
Need help

Can anyone provide me with the Stock OK1 .tar for the N910P? There seems to be gone from the links that are posted. Thanks?
[Sprint  Galaxy Note 4 Android Development] LMMT:
The link in this post works for me: http://xdaforums.com/showthread.php?p=63868221
[Sprint  Galaxy Note 4 Android Development] Zeekayy:
Just out of curiosity, is LTE supposed to work on this Rom?
[Sprint  Galaxy Note 4 Android Development] 2WhiteWolves:
Yes
[Sprint  Galaxy Note 4 Android Development] redxblood85:
How's the performance of this rom? I'm currently on the note 5 port and it's really fast. Want to go back to stock but not if it's super laggy.