[ROM] [ULTIMATE Note 5 Hybrid] [N920PVPS2AOK3] [Stock] [v1.2] [updated 3/14/2016]

[LOWCOUNTRYDAVE]

Yes

Sent from my SM-N910P using Tapatalk

Awesome, thinking this might be the one im looking for. Im on the latest stock, pg1. Do i need to odin back to ok1, or should i be good to go? Kind of confused by the op, saying to start there and fully update. Thanks...

 

[samep]

Awesome, thinking this might be the one im looking for. Im on the latest stock, pg1. Do i need to odin back to ok1, or should i be good to go? Kind of confused by the op, saying to start there and fully update. Thanks...

I recommend the OK1 stock tar for anyone on marshmallow not having a backup of these Note 5 ports.

I also recommend factory reset, wipe internal memory and format data and power down first before Odin flash of OK1 stock tar so marshmallow doesn't interfere with Lollipop downgrade.

But Before you begin, make a TWRP backup to restore if this ROM should get a Marshmallow update. Make a stock backup and fully setup backup. You could go back and forth by factory resetting and wiping internal memory and restoring these backups on demand. However, you may also wish to replace the backups as needed to keep them current.

Follow this OP closely once you've got the stock tar booted.

Note: if you choose to keep backups to restore, remember to restore the appropriate bootloader from the bootloader and baseband thread in development forum when changing Android versions. You may also have to Odin stock tar to fully restore stock to update if this ROM gets Marshmallow update.

Note 2: When flashing full stock tar, bootloader and baseband is included so no need for additional tar flashes unless OP install instructions calls for that.

Sent from my SM-N910P using Tapatalk

 

[LOWCOUNTRYDAVE]

So I used odin to flash the stock OK1 tar, and it wont boot. Gets stuck at sprint spark screen for like 5 minutes, then reboots and does it over and over. Any ideas on what is wrong?

 

[herbiefilms]

Hey, just wanted to say i'm looking forward to your N7 Hybrid. I've been running this ROM for the past 5 months (played with other ROMs but always came back). Its fantastically reliable, stable, everything works perfectly, the best daily driver i've used out of the Note 4 forums. So...thanks very very much for all the hard work, thanks for keeping the Note 4 relevant, and can't wait to see what's next.

 

[ewkonzo]

I just got my hands on the 4-day old Sprint N7 tar! Fresh from Samsung build date is aug 18 2016. . I'll be working on the rom as much as i can but I'm moving in a few days so my time will be limited for a little while.

How does one join your "test team"

 

[tx_dbs_tx]

How does one join your "test team"

I recruit help with testing from people who I feel can do what i need with little to no babysitting. I already have a good group of friends that are available to help test things. If i need more people i will post in the forum and anybody is welcome to reply and volunteer. But right now i'm not quite ready for testing.

 

[ewkonzo]

I recruit help with testing from people who I feel can do what i need with little to no babysitting. I already have a good group of friends that are available to help test things. If i need more people i will post in the forum and anybody is welcome to reply and volunteer. But right now i'm not quite ready for testing.

Understood! But one more thing,

I really appreciate your time and efforts and is not that am complaining, i know N7 will be cool and all but this rom is perfect i feel sad that you abandoning it. :crying:

You even promised us radio soon, remember?

 

[tx_dbs_tx]

Well don't think of it as me abandoning it. Think of it as an evolution. With newer TW software available, I like to stay as current as possible. but i agree, this rom is as perfect as can be for a port rom. However the new N7 port will be even better

 

[TheNeatoBandito]

Hello everyone, how goes it? I'm a bit desperate for help at the moment, hoping to getting some insight from individuals that may have a bit more experience than I do.

Quick thanks to tx_dbs_tx for this ROM, it was going well for a solid min, but I've hit a major snag and I'm really trying to get things back to normal...

Basic background, I was on Marshmallow-PE2, following the instructions to properly flash this ROM, I used Odin to jump back to Lollipop OK1 using the .tar file here http://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3250864 and then followed the OP of this ROM to the letter and was up and running without any issues, and this ROM was doing great for over a month.

About a month in running this ROM I had sudden shutdowns under 20% battery life, sluggish performance, lock-ups, and all that jazz. Read up on what I could find and assumed it was a bad battery, of which I was still running a stock Samsung battery, so I got a new battery assuming that was the issue, inserted it and was hoping everything would go back to the level of function that the phone was experiencing the month previous, but no luck. The new battery charges great, holds a charge like a champ, and dropouts under 20% have all been corrected, but the reboots, the sluggish behavior, minor lock-ups, and all around strange issues all continued to dag on.

Decided that perhaps the ROM needed to be redone, so I went back to full stock using the TAR file hoping that the Note 5 Hybrid ROM was just freaking out, but no dice, even stock OS had the same issues. Then I proceeded to install the Note 5 Hybrid ROM hoping it would give me another environment to work with and see something change, and still having the same issues.

I can turn the phone on, leave it running, don't touch it, and more or less things seem fine most of the time (may or may not suddenly decide to reboot or not respond to the power button). If I'm lucky I can swipe around the primary screens, maybe send a text or something, look at my gallery or read something, but eventually something will catch, could be Google search, could be my settings, sometimes even texting can cause issues, and the phone will lock and not function, maybe reboot (maybe not). Sometimes the phone will completely shutdown and won't respond to the power button until a battery pull is performed.

This one has me stumped. I've got experience rooting and un-rooting my Note 2 from way back when, tried several different ROMs on it, I've even had it completely crash on me and lose all my stuff only to rebuild it and start over. Most of what I'm doing with my Note 4 seems to be on track with what I've done in the past with my Note 2, but I've hit a serious wall and cannot afford to screw this phone up. So any help or insight is greatly appreciated, as I would love to have this ROM fully functioning again on my phone. Thanks in advance for taking any time to talk to me. Peace!

 

[CrimSin]

snipped

Just to be sure, have you created a nandroid backup and done a clean wipe? (cache, dalvik-cache, system, etc)

 

[ninja_unmatched]

@TheNeatoBandito

I was running into those issues on the N5 Moar hybrid port with each kernel option. While making sure I did his instructions for the battery. Only thing different was the phone ran hotter on the stock kernel& for me it was at about 30% when the phone would do those things.

I have flashed the Marshmallow update (official) then odin'd TWRP so I could flash TX. ... Mr......Slimmed Marshmallow PE1 ROM & the battery seems okay now. Still goes pretty quickly to me but it doesn't reboot or do those things anymore. Only thing I noticed is apps suddenly FCn at random without that message. I can be playing Madden Mobile and it just closed........... no biggie so far cause reopening the app it runs fine.

Just to give you ideas......

Sent from my SM-N910P using Tapatalk

 

[TheNeatoBandito]

Just to be sure, have you created a nandroid backup and done a clean wipe? (cache, dalvik-cache, system, etc)

I did actually create a nandroid just before going back to the stock OK1 ROM. Since the stock ROM left my phone unrooted and without superuser permissions, I opted not to try restoring that nandroid until I had rerun the install on the Note 5 Hybrid ROM. Both the stock OK1 ROM and the Note 5 Hybrid seemed to have issues with the sluggish behavior and the sudden "going dead" as I would call it, where the phone won't respond to the power button without a battery pull. I did eventually restore the nandroid, but it didn't last long as nothing really changed.

Currently I have used Odin to reflash the stock OK1 ROM, and for the better part of the day the phone was seemingly doing fine, no lagging or non-responsive button issues, and about an hour ago it wouldn't respond to the power button without a battery pull again. Nothing running, not using the phone, just picked it up and tried to turn it on and nothing much happened.

I'm starting to get concerned that this is getting down to a hardware issue and not a software issue (as many people seem to be doing just fine with the ROM's I've been using through all of this), which I don't want to drag a hardware issue out on a thread that doesn't actually cover those circumstances. I've got one or two more ideas to try, but may end up just switching lines to an older phone to get a working line again.

@TheNeatoBandito

I was running into those issues on the N5 Moar hybrid port with each kernel option. While making sure I did his instructions for the battery. Only thing different was the phone ran hotter on the stock kernel& for me it was at about 30% when the phone would do those things.

I have flashed the Marshmallow update (official) then odin'd TWRP so I could flash TX. ... Mr......Slimmed Marshmallow PE1 ROM & the battery seems okay now. Still goes pretty quickly to me but it doesn't reboot or do those things anymore. Only thing I noticed is apps suddenly FCn at random without that message. I can be playing Madden Mobile and it just closed........... no biggie so far cause reopening the app it runs fine.

Just to give you ideas......

Sent from my SM-N910P using Tapatalk

Thanks for the insight, I may play around with the idea of going to another ROM series entirely, not overly excited about the idea. In all honesty the biggest issue I have with Marshmallow is the default app design... by far the dumbest thing I've ever dealt with and left me enraged when I first used the Marshmallow OS. I'd be willing to use an outdated Kit-Kat setup to avoid that again. If someone has fixed the default app system in Marshmallow, then I'll give it a run.

 

[ninja_unmatched]

I did actually create a nandroid just before going back to the stock OK1 ROM. Since the stock ROM left my phone unrooted and without superuser permissions, I opted not to try restoring that nandroid until I had rerun the install on the Note 5 Hybrid ROM. Both the stock OK1 ROM and the Note 5 Hybrid seemed to have issues with the sluggish behavior and the sudden "going dead" as I would call it, where the phone won't respond to the power button without a battery pull. I did eventually restore the nandroid, but it didn't last long as nothing really changed.

Currently I have used Odin to reflash the stock OK1 ROM, and for the better part of the day the phone was seemingly doing fine, no lagging or non-responsive button issues, and about an hour ago it wouldn't respond to the power button without a battery pull again. Nothing running, not using the phone, just picked it up and tried to turn it on and nothing much happened.

I'm starting to get concerned that this is getting down to a hardware issue and not a software issue (as many people seem to be doing just fine with the ROM's I've been using through all of this), which I don't want to drag a hardware issue out on a thread that doesn't actually cover those circumstances. I've got one or two more ideas to try, but may end up just switching lines to an older phone to get a working line again.



Thanks for the insight, I may play around with the idea of going to another ROM series entirely, not overly excited about the idea. In all honesty the biggest issue I have with Marshmallow is the default app design... by far the dumbest thing I've ever dealt with and left me enraged when I first used the Marshmallow OS. I'd be willing to use an outdated Kit-Kat setup to avoid that again. If someone has fixed the default app system in Marshmallow, then I'll give it a run.

Actually so far I don't have a problem with it. I like that it asks for each permission when installing an app. Some apps Like Facebook messenger do not need all those permissions.

I'm also not totally sure what you mean though. I'm a little behind in my stuff right now. You talking about the auto closing of apps?

Sent from my SM-N910P using Tapatalk

 

[TheNeatoBandito]

Actually so far I don't have a problem with it. I like that it asks for each permission when installing an app. Some apps Like Facebook messenger do not need all those permissions.

I'm also not totally sure what you mean though. I'm a little behind in my stuff right now. You talking about the auto closing of apps?

Sent from my SM-N910P using Tapatalk

What I was referring to in my previous post was the default app preference design between Lollipop and Marshmallow. On Lollipop (and to the best of my memory from back in the day on Kit-Kat as well) when select a file such as a video or PDF, or pressed a link in Google, the phone would offer a selection of apps that you could use to either view the file or open a link or whatever. You could then choose to say "just once" or "always" after selecting the app you wanted to use.

On Marshmallow the first app you select automatically becomes your "always" app and you have to clear your app preferences literally every time you want to use a different app for any reason. I searched online for a solution for a short minute and the only option was to use a 3rd-party app to regain the basic function of the "just once" option. As simple an issue as it sounds, this one single function was a deal breaker for me with Marshmallow, at least until it's corrected.

I will agree with you that I do like the permissions system they introduced in Marshmallow, where apps are given permission one at a time, but I knew I was going to root the phone and use a custom ROM at some point, so I opted to go with Lollipop to regain the default app selection design.

 

[ninja_unmatched]

What I was referring to in my previous post was the default app preference design between Lollipop and Marshmallow. On Lollipop (and to the best of my memory from back in the day on Kit-Kat as well) when select a file such as a video or PDF, or pressed a link in Google, the phone would offer a selection of apps that you could use to either view the file or open a link or whatever. You could then choose to say "just once" or "always" after selecting the app you wanted to use.

On Marshmallow the first app you select automatically becomes your "always" app and you have to clear your app preferences literally every time you want to use a different app for any reason. I searched online for a solution for a short minute and the only option was to use a 3rd-party app to regain the basic function of the "just once" option. As simple an issue as it sounds, this one single function was a deal breaker for me with Marshmallow, at least until it's corrected.

I will agree with you that I do like the permissions system they introduced in Marshmallow, where apps are given permission one at a time, but I knew I was going to root the phone and use a custom ROM at some point, so I opted to go with Lollipop to regain the default app selection design.

Oh okay yeah it doesn't always do that with everything. I've been given a choice of a few apps at times & other times it just gives you that popup showing you where you can change it.

So far as I can tell if you do have more than one option installed it will ask you which one to use. If not the popup shows. Other times if an app needs another app to do something so far that has not given you the option. The times it has asked me it was the initial question but never again asked. That actually starts to get on my nerve when being asked each and every time to open the same app. If say I choose to use another app one day to open a PDF I'll just use the app itself to open it.

I get it though but it's more about finding your favorite & best ways to open & handle files you use. Once you do that it saves you that extra finger tap from doing what you do repetitively. If you change your mind about an app just clear the default for the action...

I notice though certain actions it will ask each time. Sharing of course & related actions. PDF files I noticed it does do that if you say open it through the default My Files manager. But if you open through ES File Explorer it will ask each time unless you check off that box. I bought ES File Explorer cause it was good & like the extra features plus the paid version looks better anyways. So that auto default hasn't been a real issue for me so far...... but asking everytime has been a Lil annoying lately.... especially if I'm rushing through the day. Maybe the ES File Explorer will be what makes Marshmallow okay for you.

Sent from my SM-N910P using Tapatalk

 

[sliverr7x]

Well don't think of it as me abandoning it. Think of it as an evolution. With newer TW software available, I like to stay as current as possible. but i agree, this rom is as perfect as can be for a port rom. However the new N7 port will be even better

Hey i know this isnt all request hour tx if and when u do make a n7 port anyway way i can implement the mipop app that was in your moar port.. that was very handiest app. That would be awsome thanks

Sent from my SM-N910P using Tapatalk

 

[liquid307]

Can someone hook me up with the InCallUI.apk from this rom, it's in system/app?
I need it to replace the one in Moar rom.

Thanks in advance
------------------------------------
Edit: Nevermind got it already.


Sent from Nowhere

 

[androiddiego]

Can someone hook me up with the InCallUI.apk from this rom, it's in system/app?
I need it to replace the one in Moar rom.

Thanks in advance
------------------------------------
Edit: Nevermind got it already.


Sent from Nowhere

Here it is straight off my phone.
Love this ROM.

 

[hammerchucker]

Note 5 ROM: "Activate this device", "More", "Reset Cellular Data"

So I went and chose this option b/c I was throwing back on 3g.

I backed up my ROM before I did this. Afterward, after a few days I realized I had no phone and text, only data. I restored to no avail.

I flashed OK1 via ODIN, wiped internal, and flashed OK1 and it booted and now have all services. Then restored my OK3 Note 5 OS with no probs.

I am assuming that the option I chose in "activate device" was never ported and N5 stuff was written when I chose this option it wrote to a Note 5 partition address.

 

[Consumers]

Was having problems not receiving texts from iPhones so I tried resetting the carrier through the ##72786# dialer code knowing that it could mess with the working cell services moving from OK1 to OK3. It did and now I can't reactivate; is the only choice to Odin and reflash? Just want to check if there's an easy fix first.

Also was wondering if anyone had similar issues with receiving iPhone SMS on this ROM or in general. Never registered any devices or numbers with Apple but wondering if deregistering iMessage worked in this case (tried on Apple's site quickly but didn't get the verification code back).