yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Android Development] styles420:
No doubt about it, the .7z extension indicates a 7zip archive. The tar file is inside that archive.
[Sprint  Galaxy Note 4 Android Development] dbug2008:
Ok, flashed per instructions. How do I get root?
[Sprint  Galaxy Note 4 Android Development] schlepprock:
Ding Ding Ding! I wasn't familiar with 7z. With 7z being at the end of the download i thought it was kind of a package. Its been a tough day on my end anyway. I odined this and flashed the new build and everything is running smooth. Thanks for the help..
[Sprint  Galaxy Note 4 Android Development] ThanhLongThuVan:
i use room N910PVPU3BOF5, now can use [ROM] [ODIN] [HYBRID_OB7sbl_SPT_N910PVPU4COG5] [8/10/15]
[Sprint  Galaxy Note 4 Android Development] tx_dbs_tx:
If you updated to the new android 5.1.1 rom then no you can't use this rom tar. It will fail.
[Sprint  Galaxy Note 4 Android Development] ThanhLongThuVan:
i use room N910PVPU3BOF5 5.0.1
[Sprint  Galaxy Note 4 Android Development] Krillen:
Is there anyway to get the latest version of the UNOFFICAL XPOSED installed and working on this rom? When I tried installing it, it said it needed a deodexed version. Other then then one problem I have the rom works great and I love it.
[Sprint  Galaxy Note 4 Android Development] tx_dbs_tx:
You will need to flash my other fully deodexed rom in the development thread. You must first Odin the latest TWRP recovery THEN flash the rom in the link below via recovery.

http://xdaforums.com/note-4-sprint/development/rom-t3179078
[Sprint  Galaxy Note 4 Android Development] Krillen:
I had tried it before but I couldn't get it to work completely right. When I had tried it my phone wouldn't connect to sprint's network anymore. If i try it again how do you root it? Do you install the room then supersu and BeastModeStock1.0-N910P-OG5? If you could please give me help with my problem I would appreciate it and love to use try it again.
[Sprint  Galaxy Note 4 Android Development] nimaim:
This worked flawlessly for me btw ... verified that I'm still on OB7 bootloader but OG5 build, baseband, etc. Thanks tx! Patience is a virtue ... glad I waited it out for something like this.
[Sprint  Galaxy Note 4 Android Development] tommy_2q:
Wrong thread
[Sprint  Galaxy Note 4 Android Development] samep:
It's a pre-rooted ROM with Beastmode kernel and SuperSU included, all you need is TWRP to flash it since you're already on OG5.

Refer to the OP for additional flash instructions.
[Sprint  Galaxy Note 4 Android Development] Krillen:
That is what I thought. I did fix the problem I had with my phone not connecting to sprint. I had to do a whip on my phone and restore with titanium backup. All is working as it should now. Nice work on the rom as well.
[Sprint  Galaxy Note 4 Android Development] phonetec:
Thanks for mentioning that this will wipe your internal storage ?
[Sprint  Galaxy Note 4 Android Development] schlepprock:
I think if we decide to change roms, alter our phones on a system level, flash mods and so on we should be prepared for this. JMHO

Note4 Rocking a Hybrid Rom
[Sprint  Galaxy Note 4 Android Development] samep:
+1

Especially where wiping partitions is recommended in the OP. (Backing up is implied for sure).
[Sprint  Galaxy Note 4 Android Development] phonetec:
Yeah yeah, my bad, maybe i wasnt thinking about it when i decided to do it, dont regret it at all though, this echoe 5.1.1 rom is smooth as butter
[Sprint  Galaxy Note 4 Android Development] milenkoben:
so I flashed this right about the time it was released and have been using an og5 rom but would really like to go back to an ob7 rom, how do I switch back to that modem so that they will boot correctly?
[Sprint  Galaxy Note 4 Android Development] ChodaBoyUSA:
I have a quick question.

I am currently on OB7 5.01 and would like to upgrade to rooted OG5. If I install this OB7/OG5 ROM, can I then install the pre-rooted Hybrid Base OG5 or Hybrid 3.0 ROM and keep the OB7 bootloader?

Thanks
[Sprint  Galaxy Note 4 Android Development] samep:
Yes, flash this and Odin TWRP and flash the pre-rooted ROMs from OG5.

Don't try to root OG5 with CFAutoRoot; without the kernel exploit, it boot loops. Pre-rooted ROMs will have SuperSU and kernel exploit included in the flash.
[Sprint  Galaxy Note 4 Android Development] loneb:
What versions am I running?

I am officially confused. I have flashed the new Noterized ROM Stable 4 RC1. It is working fine but seems to have some slight hesitation or lagging sometimes.

This is what Synapse tells me about my system:

View attachment 3460408

It looks like I have BOB7, BOF5, and BOE1. Yet I'm running Noterized 4:

View attachment 3460419

I'm sure that someone can explain this to me and tell me if I need to do anything differently.

Thanks in advance.
[Sprint  Galaxy Note 4 Android Development] samep:
Looks like you took the OE1 OTA, flashed the OG5 modem and Noterized.

For the lag, could be synapse settings or too many cache hungry apps running. If a reboot or cache dump temporarily helps the lag, may be the memory leak that Android 5.0 suffers. There's Xposed fixes for that but now TW Android 5.1.1 has what appears to be stable Xposed but shouldn't need the memory leak fixes. Early development though.

Android 5.1.1 has some fixes for memory leak and stagefright security patch but also introduced a home screen, pull-down, and lock-screen lag (when fingerprint unlock I'd used) that I know little about because I'm not yet running it and one user reported Nova Launcher (possibly with aggressive desktop mode enabled in advanced settings) solved his problems but seems no one else confirms this or cares to try it when complaining of it. I find that very odd; rather than troubleshoot, they suggest the default launcher is bad or power saving mode helps.

This could also be added to the build.prop to use preferred launcher:

ro.HOME_APP_ADJUST=1

What's best to do about it is user preference. Knowing the ins and outs and things to try may help. An ad-blocker may help too.
[Sprint  Galaxy Note 4 Android Development] TheQuicken:
Advice needed.

I may have made a mistake, but hopefully I didn't. I never took any updates and always retained BOB7 because I rarely will update anything unless I see and read positive reviews of the newest updates to ensure little to no headaches for myself. SO after hearing about all the headaches everyone was having post-BOB7, I stayed on it.

I was on Noterized RC1 and as soon as the final version came out, I noticed this note:

If you are on BOB7, odin to full stock then odin this http://xdaforums.com/note...t/rom-t3176288 then you are good to go.

SO, after reading your thread on this, I performed a back up of RC1, full wipe and factory reset 3x's, I odined your Hybrid ROM. I am currently fully installed with your ROM. The one thing I did

not

do was this...If you are on BOB7, odin to full stock...My question is this, if I did not odin stock BOB7, but wiped RC1 and odined your ROM, will I be able to install Noterized Final Version without issue...what are your recommendations...I am not installing anything until I hear from you.

I hope this makes sense.

EDIT****

Well, I was worried for nothing. It worked flawlessly and I am on the latest Noterized without issue and am happy. Thanks for putting this together.
[Sprint  Galaxy Note 4 Android Development] jhill110:
The thing is, if you odin the rom in the OP, you will be fully up to speed for 5.1.1 but will still be on the OB7 bootloader... More flexibility that way. [MENTION=1503720]tx_dbs_tx[/MENTION] is doing some forward thinking here...
[Sprint  Galaxy Note 4 Android Development] TheQuicken:
I agree...:good:

Smartly done. I am a happy dude
[Sprint  Galaxy Note 4 Android Development] tx_dbs_tx:
You can keep the updated OG5 modem and flash back to a 5.0 rom. You can also flash an older modem if you want. It doesn't matter. It will no effect the phone booting up.

Yes. that is the whole point of the custom hybrid rom tar.

And thank you [MENTION=4894273]jhill110[/MENTION] and [MENTION=4375749]samep[/MENTION] for helping people in this thread. :good:
[Sprint  Galaxy Note 4 Android Development] merkk:
Can someone tell me what the suggested method for rooting with this is? I've tried installing supersu through twrp twice now and both times i just get a boot loop and have to reflash the rom to get the phone working again.
[Sprint  Galaxy Note 4 Android Development] samep:
OG5 boot loops without an exploited kernel. They're baked into custom OG5 ROMs.

https://www.androidfilehost.com/?fid=24052804347789588
[Sprint  Galaxy Note 4 Android Development] merkk:
Ah thanks - this (the file you linked) is an exploited kernel?

I ran a backup in twrp prior to installing this rom - would there any any issues that you know of if i just restore that backup? Should i not restore modem or any of the other partitions?

Thanks for your help - just being overly cautious since I don't want to brick the phone.

Thanks
[Sprint  Galaxy Note 4 Android Development] samep:
Yes. You should be fine either way as long it's a Lollipop backup. Flash the kernel with a cache and dalvik-cache wipe or same wipe plus format data and restore your backup.
[Sprint  Galaxy Note 4 Android Development] merkk:
thanks for the help - was able to root as well as restore the previous rom. Unfortunately for me I didn't realize TB was saving all the back ups to the internal sd card :( lesson learned
[Sprint  Galaxy Note 4 Android Development] ffolkes:
This seems to have worked well for me, thanks!

However a word of warning: This wiped ALL internal data on my phone. I had a backup of important stuff fortunately, but some misc stuff was lost. I thought there was a chance for data corruption, but I didn't know it was 100% for sure going to wipe everything. I read this entire thread, all 10 pages, and if that was mentioned somewhere, I guess I overlooked it. Just wanted to let future people know to BACKUP FIRST!
[Sprint  Galaxy Note 4 Android Development] JudasD:
Has anyone been able to go back to NK2 after using this tar? I did install this tar and then a hybrid rom. Everything worked but i would like to go back to NK2. When i try to odin NK2 it fails. Any thoughts?

JD
[Sprint  Galaxy Note 4 Android Development] merkk:
Hello - i restored my backup of the previous stock rom (n910pvpu4cog5) but now it seems like the kernel from that build no longer works. I get a boot loop at the samsung logo. I wiped cache and dalvik.

Only way the phone boots now is with the beastmode kernel, but this kernel seems to be a little bit buggy which is why i wanted to restore the previous one. Any suggestions?

Thanks
[Sprint  Galaxy Note 4 Android Development] samep:
If you rooted it, that would make sense, you'd need a kernel exploit.

If it was unrooted at time of backup, you may not be getting a full wipe to clear SuperSu. Did you try the full unroot in SuperSu? Wipe everything but extsdcard prior to backup restore?

Edit: TWRP will also try to restore root by prompting when it can't detect it. You may have to Odin the tar ball, Odin TWRP and then restore the stock backup.
[Sprint  Galaxy Note 4 Android Development] merkk:
my twrp backup is of an already rooted install. I'm pretty sure i did a full wipe prior to restoring the backup. My backup is of a stock room - it was rooted with supersu but still had the stock kernel. So i'm confused why that same stock kernel isn't working now. I thought i read this rom also changes the bootloader.

In twrp when doing the restore - are there any partitions i should not restore? Or should i restore all of them? Just to be clear, those options are:

boot

recovery

system

data

efs

modem

Thanks for your help
[Sprint  Galaxy Note 4 Android Development] samep:
If restoring all partitions causes boot loop but Beastmode allows boot, that's likely what you backed up unless it was another custom kernel. Can't say why it looped on you unless you had restored another backup that was not OG5. I think you have to flash the OB7 to OG5 tar ball to get back to the backup that's not booting, right? IDK what you've restoring.

When I said you may have to Odin the tar ball again, I was thinking you were referring to stock un-rooted OG5 from this tar ball. This one wouldn't change your bootloader but would restore the OG5 stock kernel. And it should allow you to restore your OG5 backup.

I'm guessing that maybe you restored a backup with a different bootloader and modem caused the issues. Maybe you could Odin the stock tar that pertains to the backup you want to restore? But don't use OG5 stock tar unless you want to lose the OB7 bootloader.
[Sprint  Galaxy Note 4 Android Development] merkk:
I think when i did this last restore, i didnt restore recovery or modem - i wasnt entirely sure if would cause problems. Plus i wasn't sure if this rom had an updated modem which i thought might help with the reception issue i was having, which was the original point of me trying this rom.

The backup that i currently have is basically what came with the phone when i first got it. I never installed any rom on the phone before this. I just rooted it. I wanted to keep the phone as close to stock as possible.

With my backup restored, this is what my phone is saying i have:

software version n910pvpu4cog5

android 5.0.1

build # lrx22c.n910pvpu1bob7

I don't know really know what losing the OB7 bootloader would do.

I can run a full wipe and then do a full restore of everything again if you think that'll clear things up. I was trying to be cautious the first time since I wasn't sure what could be over-written once i installed this newer rom.

Thanks
[Sprint  Galaxy Note 4 Android Development] merkk:
Just did a full restore from my backup, still boot looping unless I install the beastmode kernel.

Any ideas how I can go back to the stock kernel? This one is just s little bit flakey.

Thanks
[Sprint  Galaxy Note 4 Android Development] samep:
Are you trying to get back to stock un-rooted? If so, you'll most likely have to do the wipes, power down, Odin either the stock tar you're returning to or, if it's OG5, once again the tar ball in this OP.

If you're wanting to stay rooted on OG5 and just want another kernel, stock isn't an option but you can Google Emotion or AEL and give one of those a try.

You can try running Galaxy Tools to get a better idea of true partition revs to see what you can run. If it is truly OB7/5.0.1, the OB7 stock kernel may work or can most likely just Odin OB7 stock tar and run it stock or rooted with stock kernel.

I would suggest a cache and dalvik-cache wipe with the kernel flash. If the backup you're trying to restore is OB7, I believe you should Odin OB7. If it's KitKat, you should Odin back to it first.

Which is the best? Battery is most likely still better on KitKat. I don't think one would give a significant improvement on signal in bad coverage area but latest is most likely best choice.
[Sprint  Galaxy Note 4 Android Development] merkk:
The backup I'm trying to restore is lp, 5.0.1

It's the rom that shipped with the phone, all I did to the phone was root it. So I'm just trying to get back to that.

So far the backup I made does a boot loop unless I install that beastmode kernel. I'm not sure why it suddenly only works with that kernel since it was working with the stock kernel all this time.

It currently shows OB7 as the build number (running the restored backup).

So you think the only way to get the stock 5.0.1 build working is to odin a stock build of that?

Do you understand why it's only working with the beastmode kernel now? I'm just trying to understand what happened.

Thanks
[Sprint  Galaxy Note 4 Android Development] JudasD:
Bump. has anyone gone back to NK2 after using this tar? When i try to install an NK2 rom it bootloops. when i try to odin back to NK2 or even OB7 i get an odin error. Any ideas?

Thanks,

JD
[Sprint  Galaxy Note 4 Android Development] samep:
Are you factory resetting or formatting user data prior to Odin NK2? Lollipop and KitKat are different file systems and Odin doesn't wipe user's data on most Note 4 flashes but I believe OG5 was an exception to the norm.

If Odin flashes without error, I wouldn't suspect this tar ball had anything to do with the boot loop. If it fails, you may have already taken a update after OB7 and got on that reactivation locked bootloader.

If partitions vary, you can try to Odin flash twice. Once with auto reboot disabled and remove battery 30 seconds then flash normally with auto reboot. You can use stock recovery to factory reset. I'd do that first so the battery pull prior to second Odin flash of stock tars has the suggested power down prior to flash. Let it fully reboot and activate on second Odin flash.

To answer your question, I flashed this tar ball to keep my OB7 bootloader but haven't tried going back since Xposed works on OG5; ATM, it's only Beastmode rooted Odex with a few mods- non Xposed.

But I know [MENTION=5229744]xxSTARBUCKSxx[/MENTION] has went back to KitKat from OG5.
[Sprint  Galaxy Note 4 Android Development] xxSTARBUCKSxx:
This is true. Was onOB7 Bootloader to try and test 5.1.1 roms out for personal/experimental reasons. Flashed the OG5 tar, went to settings and saw the Reactivation Lock(never before seen from being on just an OG5 Rom) and my stomach sunk, thinking i had OG5 bootloader.

<!-- Recovery -->

<Team Win Recovery Project v2.8.7.0>

<Wipe>

<Format Data>

yes

yes

yes

</Format Data>

<Swipe to Factory Reset>

swipe

swipe

swipe

</Swipe to Factory Reset>

<Advanced Wipe>

<checked partitions>

Dalvik Cache

System

Data

Internal Storage

Cache

</checked partitions>

<Swipe to Wipe>

swipe

swipe

swipe

</Swipe to Wipe>

</Advanced Wipe>

</Wipe>

<Reboot>

<Download>

tap

</Download>

</Reboot>

</Team Win Recovery Project v2.8.7.0>

Battery Pulled, Cleared everything from Data Folder in Android Folder in SD Card, removed SD Card from Phone,

Placed Battery Back in, Odined NK2 Tar on Odin 10.0.0(this version is fine for 4.4.4).

Flashed TWRP

Restored NK2 Back up

Profit.
[Sprint  Galaxy Note 4 Android Development] JudasD:
I will give this a try again. the only thing i did not do was the battery pull. i will report back tonight. thanks for the help guys.

JD
[Sprint  Galaxy Note 4 Android Development] flynhawn2002:
@ tx_dbs_tx

WIll upgrading to OG5 thru this method prepare me for a Sac Note 5 Rom install? Will the OB& bootloader boot it?

Thanks in advance for your help!
[Sprint  Galaxy Note 4 Android Development] jhill110:
It absolutely will.
[Sprint  Galaxy Note 4 Android Development] flynhawn2002:
[MENTION=4894273]jhill110[/MENTION] ...Thank you sir!
[Sprint  Galaxy Note 4 Android Development] JudasD:
It's been a long while since i have been able to get back to trying to put KN2 back onto my phone. I tried the steps above from xxSTARBUCKSxx and it is still failing. Here is what the phone says when odin fails:

ODIN MODE (HIGH SPEED)

PRODUCT NAME: SM-N910P

CURRENT BINARY: Custom

SYSTEM STATUS: Official

KNOX WARRANTY VOID: 0x1 (4)

QUALCOMM SECUREBOOT: ENABLE (CSB)

RP SWREV: S1, T3, R1, A1, P1

SECURE DOWNLOAD: ENABLE

UDC START

SW REV CHECK FAIL : [tz]Fused 3> Binary 1

[4]eMMC erite fail: TZ

i have never taken any of the OTA software. I have only been on NK2 and then loaded this OB7 hybrid. Nothing else.

Any thoughts?

Thanks,

JD
[Sprint  Galaxy Note 4 Android Development] samep:
Are you sure you're not trying to Odin flash a zip file? You may have to open the archive and drag tar.md5 file to Odin folder with 7zip.
[Sprint  Galaxy Note 4 Android Development] JudasD:
I did unzip it first. I tried to odin the tar.md5 directly.

JD
[Sprint  Galaxy Note 4 Android Development] samep:
Good. Did you wipe the partitions in TWRP prior to Odin? If you get back into TWRP, try that.

If there's a md5 hash to compare your NK2 zip download to, check it. You may have a bad download.
[Sprint  Galaxy Note 4 Android Development] JudasD:
Yes, i wiped and formatted just like the instructions that xxSTARBUCKSxx posted above. I always verify md5s as well.

JD
[Sprint  Galaxy Note 4 Android Development] samep:
Sorry I've been repetitive. I didn't realize this conversation started that long ago.

Did you verify your bootloader with iDone Galaxy Tools or Phone Info for Samsung devices in Google Play?

If all above is good, have you tried to Odin the stock OB7 tar, first? Possibly an Odin issue? What Odin versions have you tried? 3.07 was recommended for KitKat. It's possible you still need the latest Odin to Odin OB7.

http://xdaforums.com/showpost.php?p=51767811&postcount=1

Edit: I see [MENTION=5229744]xxSTARBUCKSxx[/MENTION] mentions Odin 3.10.0 Did you also pull the ExtSdCard after battery pull as he mentions? Flash NK2 tar without the ExtSdCard? Those may be important steps to get back. (That @ mention may get a response from him soon enough; TIA).
[Sprint  Galaxy Note 4 Android Development] JudasD:
Galaxy tools does show OB7 as the bootloader.

I get this same odin error when i try stock NIE, NK2 or OB7. The error is always on TZ. Does anyone know what the TZ actually does? It's trusted zone right? still not sure what that actually is.

I am very close to trying to odin NK2 with the tz.mbm removed from the tar to see what happens. Anyone know if this is a bad idea?

Thanks,

JD
[Sprint  Galaxy Note 4 Android Development] xxSTARBUCKSxx:
No, you dont really want/need to do that. Its leaning more towards a hardware issue. For some reason your partitions are out of whack which is why the controller is sending out that argument. Never dealt with eMMC issues and a PIT file may be your only hope. But proceed with caution. On the other hand, its looks like youve got nothing to lose anyhow with it relating to a hardware issue.(Speculating)

You can either take the plunge and see if going up the ladder will fix and resolve your partition issues, or if youre trying to stay on OB7 and below.. youve tackled it from most angles possible.
[Sprint  Galaxy Note 4 Android Development] JudasD:
I went ahead and removed the tz.mbm from the stock NK2 tar. I was able to odin this modded NK2 tar with no errors. NK2 boots and works, the boot loader now says NK2 in galaxy tools.

When i try to flash the complete NK2 (with the tz.mbm in it) over the top of this modded NK2 i still get the odin error. I just decided to run this modded NK2 for a bit and see what happens.

I have been running almost 24 hours on this NK2 without the tz.mbm file and things seem to be working. Not sure what it going on with the tz stuff. At this point i dont know if i should worry about what will pop up later.

JD
[Sprint  Galaxy Note 4 Android Development] samep:
[MENTION=573904]JudasD[/MENTION]

I was considering trying the stock NK2 tar just to confirm steps or issues that may exist.

I'm becoming less of a flashaholic and tend to get complacent where content regarding updates and ROMs. But that doesn't prohibit me from trying new things within current ROM.

That said, I'm in no hurry now.

Best wishes for compatibility and serviceability from your phone for the duration of it's service to you and whomever or whatever is next for that phone. I hope it's a non-issue.
[Sprint  Galaxy Note 4 Android Development] xxSTARBUCKSxx:
Glad that work-around worked. When ya got to bypass a blown fuse and Force Trusted Zone.... thats the way to do it. This Note 4 has more work-arounds than a one-legged whore. I think its all secondary bootloader related anyhow.. so i dont think youll have any consequences until marshmallow comes out and the Note 4 has, once again, a new set of hurdles to jump. Best of Luck in the future.
[Sprint  Galaxy Note 4 Android Development] tweeker404:
So if I am coming from OB7 and 5.0.1, would i just follow the steps? No need to take OTA or the official OG5?

Thank you for your time and effort.
[Sprint  Galaxy Note 4 Android Development] jhill110:
Yes.. Follow the op carefully... Do the steps and prosper... Then have at it with... Uh hem... Tx's other great works...

?
[Sprint  Galaxy Note 4 Android Development] JudasD:
Please let me know how this works for you. I did not work for me and i had to do some workarounds.

JD