Develop Bugs

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.

Help me downgrade my galaxy s3 i747

Hi all.
Two weeks ago I got this device (sgh i747) was rooted and was stock 4.1.1. I installed cwm and made A backup of stock room. And flash AOKP custom kitkat rom. Now I want to downgrade back to stock. or if I cannot downgrade please suggest me a stable lollypop rom.
Things I have!
1:- rooted cwm installed (sgh i747)
Backup of stock rom 4.1.1
Please help .
Thanks

mango man said:
Hi all.
Two weeks ago I got this device (sgh i747) was rooted and was stock 4.1.1. I installed cwm and made A backup of stock room. And flash AOKP custom kitkat rom. Now I want to downgrade back to stock. or if I cannot downgrade please suggest me a stable lollypop rom.
Things I have!
1:- rooted cwm installed (sgh i747)
Backup of stock rom 4.1.1
Please help .
Thanks
Click to expand...
Click to collapse
If you are still on the original bootloader and modem you should be able to revert to stock 4.1.1 by simply restoring the backup from your recovery. Before you attempt to do so verify that you are indeed on the 4.1.1 bootloader. This can be done with the Phone Info *Samsung* app by VndNguyen (?sp) from the playstore or by a couple of terminal emulator commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
If you do not already have terminal emulator installed, it may have come with the ROM, you can get it from the Playstore. It may also be a part of CWM recovery, it is part of TWRP I know for sure.
If it turns out you are on a newer bootloader and modem then go with a stock ROM that matches the bootloader and modem on the phone. To run a lollypop rom you will need to be on at least the NE4 bootloader and modem.

Thanks for a very helpful reply. I m going to follow your instructions. Will soon replay. Thanks again.

dawgdoc said:
If you are still on the original bootloader and modem you should be able to revert to stock 4.1.1 by simply restoring the backup from your recovery. Before you attempt to do so verify that you are indeed on the 4.1.1 bootloader. This can be done with the Phone Info *Samsung* app by VndNguyen (?sp) from the playstore or by a couple of terminal emulator commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
If you do not already have terminal emulator installed, it may have come with the ROM, you can get it from the Playstore. It may also be a part of CWM recovery, it is part of TWRP I know for sure.
If it turns out you are on a newer bootloader and modem then go with a stock ROM that matches the bootloader and modem on the phone. To run a lollypop rom you will need to be on at least the NE4 bootloader and modem.
Click to expand...
Click to collapse
Okay got Samsung phone info app.
Boot loader version -------I747UCDLK3
Baseband version -----I747UCDLK3
And please explain LATEST NE4 BOOT LOADER.
Thanks

You are currently running the LK3 bootloader and modem. If I am not mistaken that's a pretty old one (original?). You will have to update to NE4 or newer firmware before you can flash any of the newer roms. They will not boot in the older ones.
Your firmware is actually the only one available for download so I recommend flashing it via Odin and factory resetting. Then update using the Software Update option in Settings > About Device.
You can download your LK3 firmware here: http://www.sammobile.com/firmwares/database/SGH-I747/
You may have to run Software update several times to fully update.
That is probably the safest and easiest course you can take.
After that, flash the latest custom recovery of your choice, then flash the rom you want.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
BTW, after flashing the LK3 firmware, you might want to consider using the free Sim unlock method. (Should be pretty easy to find).
Once you update past 4.3 you can no longer use it. It will allow the device to be used on other carriers networks, which can be beneficial if you ever want to sell it or switch carriers.
Sent from my SGH-T999 using Tapatalk

What DocHoliday77 suggests is probably the safest method to get what you want. After each update the system will force you to wait 24 hours before you can make the next update. That would be three days to get to NE4, the first 4.4.2 release by AT&T, which you need to run lollipop ROMs. If you want to update to the current release (NJ2) that would be two additional days.
You can shortcut the required waiting period by manually advancing the system date after each update.
In addition to not allowing you to use the free unlock, once you take the 4.3 bootloader it prevents you from downgrading bootloaders. Newer bootloaders do the same, downgrading will be a thing of the past. (I never took the official 4.3 bootloader until the stagefright scare came along and I went from my older custom ROM to a new release.)

dawgdoc said:
What DocHoliday77 suggests is probably the safest method to get what you want. After each update the system will force you to wait 24 hours before you can make the next update. That would be three days to get to NE4, the first 4.4.2 release by AT&T, which you need to run lollipop ROMs. If you want to update to the current release (NJ2) that would be two additional days.
You can shortcut the required waiting period by manually advancing the system date after each update.
In addition to not allowing you to use the free unlock, once you take the 4.3 bootloader it prevents you from downgrading bootloaders. Newer bootloaders do the same, downgrading will be a thing of the past. (I never took the official 4.3 bootloader until the stagefright scare came along and I went from my older custom ROM to a new release.)
Click to expand...
Click to collapse
1:- Okay I fully understood what I have to do to flash lolly pop . But confused a little bit . If I have original boodloader than it should be easier to restore my stock 4.1.1 . Backup (still not clear) .
2:- I am out of USA. The device in unlocked. I am using ZONG sim on it. So the question is can I still update the device via OTA.
Thanks

mango man said:
1:- Okay I fully understood what I have to do to flash lolly pop . But confused a little bit . If I have original boodloader than it should be easier to restore my stock 4.1.1 . Backup (still not clear) .
2:- I am out of USA. The device in unlocked. I am using ZONG sim on it. So the question is can I still update the device via OTA.
Thanks
Click to expand...
Click to collapse
When you say original bootloader I don't know which you have. My i747 came with 4.1.1 but before I could get it out of the clerk's hands they had taken the OTA to change it from DLK3/4.1.1 bootloader and stock rom to MG2/4.1.2 bootloader and stock rom. Even more confusing I have read reviews that state the SGS3 was originally released with android 4.0.4.
If your original bootloader was older than 4.3 (MJB) AND you have never upgraded to MJB or newer, then you can safely return to stock 4.1.1.
To get OTAs you need to be on the stock ROM, at least you do in the USA. I don't know if that holds true elsewhere.

I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk

dawgdoc said:
When you say original bootloader I don't know which you have. My i747 came with 4.1.1 but before I could get it out of the clerk's hands they had taken the OTA to change it from DLK3/4.1.1 bootloader and stock rom to MG2/4.1.2 bootloader and stock rom. Even more confusing I have read reviews that state the SGS3 was originally released with android 4.0.4.
If your original bootloader was older than 4.3 (MJB) AND you have never upgraded to MJB or newer, then you can safely return to stock 4.1.1.
To get OTAs you need to be on the stock ROM, at least you do in the USA. I don't know if that holds true elsewhere.
Click to expand...
Click to collapse
DocHoliday77 said:
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks men for quick response.
now I m fully confused. Don't know what to do. because I don't want to stuck on this battery enemy rom. (Aokp kitkat. Custom rom )
I am not clear about boootader version (PHONE INFO SAMSUNG APP SAYS ITS i747ucdlk3 ) but I know when got this thing. It was android 4.1.1 . Which I have back a backup. As per I am out of att network and I can't get OTA,s so I don't need to revert to 4.1.1 backup. I think I have to find out 4.3. For my device. So kindly please inform me if some one knows about . Iwill be very thankful to u people.
Again thanks

DocHoliday77 said:
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got this while searching online. Please tell me if it is helpful for.me.
http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/

Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup! I think it is. Will try . Thanks

mango man said:
Yup! I think it is. Will try . Thanks
Click to expand...
Click to collapse
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)

DocHoliday77 said:
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)

mango man said:
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
Click to expand...
Click to collapse
To be able to run a lollipop rom you will need to update bootloader and modem. Update them together, this is important once you reach the 4.4.2 level of bootloader and modem that you will need to run lollipop roms. Once you reach 4.4.2 you will brick your phone if the bootloader and modem versions are not the same.
Before starting to flash any of the files you need to get you up and running on lollipop, I strongly suggest you download all you need from start to finish. Store the files you will need in the upgrade process either on an external sdcard or on the root of your internal sdcard. I haven't used CWM Recovery on my SGS3 since shortly after rooting it, I have been using TWRP since then, and I don't recall all of the capabilities of CWM recovery. If the CWM version you have will not let you flash from an external sdcard you will need to store the files you will use on the root of the internal card to be able to flash them. It will be easier to do this before you start, unless you are comfortable with pushing files from a computer using adb.
BEFORE DOING ANYTHING I AM SUGGESTING read enough that you thoroughly understand what I am saying. After reading, ask questions for clarification. Be sure you have no doubts.
Decide if you intend to install a rom along with the bootloader and modem at each upgrade; or if you are going to install updating only bootloader and modem until you get them to them point that you can run a lollipop ROM. Since you said you can not do OTA updates, either way will work. Whichever you decide, you can not skip directly to the bootloader and modem you need for lollipop.
If you are installing bootloader and modems without the rom:
From the stock 4.1.1 rom and bootloader you can go straight to 4.3 bootloader and modem, skipping the 4.1.2 (MG2) version. I have personally done this with no ill consequences. After 4.3, install the first bootloader and modem version for 4.4.2, that is NE4. Lollipop will run with the NE4 bootloader. As DocHoliday stated, you can go on the the current bootloader and modem. After NE4 is NJ1. After NJ1 you come to the current bootloader and modem, which is NJ2
If you plan to install the full ROM at each step.
The page you linked to should work if all of the downloads are available. Go from 4.1.1 to 4.3 to 4.4.2 (NE4). If you want the newer versions (NJ1 or NJ2) do them in sequence, do not skip any that are mentioned. Read the instructions on your linked page carefully. If you want NJ1 and then NJ2 they can be found in threads by enewman17, as can NE4 and maybe 4.3. I didn't provide the links so that you will hopefully read the pages carefully after searching and before downloading. Be sure you understand what you are downloading to flash and how it should be used.

dawgdoc said:
To be able to run a lollipop rom you will need to update bootloader and modem. Update them together, this is important once you reach the 4.4.2 level of bootloader and modem that you will need to run lollipop roms. Once you reach 4.4.2 you will brick your phone if the bootloader and modem versions are not the same.
Before starting to flash any of the files you need to get you up and running on lollipop, I strongly suggest you download all you need from start to finish. Store the files you will need in the upgrade process either on an external sdcard or on the root of your internal sdcard. I haven't used CWM Recovery on my SGS3 since shortly after rooting it, I have been using TWRP since then, and I don't recall all of the capabilities of CWM recovery. If the CWM version you have will not let you flash from an external sdcard you will need to store the files you will use on the root of the internal card to be able to flash them. It will be easier to do this before you start, unless you are comfortable with pushing files from a computer using adb.
BEFORE DOING ANYTHING I AM SUGGESTING read enough that you thoroughly understand what I am saying. After reading, ask questions for clarification. Be sure you have no doubts.
Decide if you intend to install a rom along with the bootloader and modem at each upgrade; or if you are going to install updating only bootloader and modem until you get them to them point that you can run a lollipop ROM. Since you said you can not do OTA updates, either way will work. Whichever you decide, you can not skip directly to the bootloader and modem you need for lollipop.
If you are installing bootloader and modems without the rom:
From the stock 4.1.1 rom and bootloader you can go straight to 4.3 bootloader and modem, skipping the 4.1.2 (MG2) version. I have personally done this with no ill consequences. After 4.3, install the first bootloader and modem version for 4.4.2, that is NE4. Lollipop will run with the NE4 bootloader. As DocHoliday stated, you can go on the the current bootloader and modem. After NE4 is NJ1. After NJ1 you come to the current bootloader and modem, which is NJ2
If you plan to install the full ROM at each step.
The page you linked to should work if all of the downloads are available. Go from 4.1.1 to 4.3 to 4.4.2 (NE4). If you want the newer versions (NJ1 or NJ2) do them in sequence, do not skip any that are mentioned. Read the instructions on your linked page carefully. If you want NJ1 and then NJ2 they can be found in threads by enewman17, as can NE4 and maybe 4.3. I didn't provide the links so that you will hopefully read the pages carefully after searching and before downloading. Be sure you understand what you are downloading to flash and how it should be used.
Click to expand...
Click to collapse
Thanks **** I need to be extra careful before taking any step. I am going to collect all relesed OTA,s. By now I onky need the links for ota. Thanks

Flash MJB and NE4 from the site you linked to above. Then use enewman17's thread for the NJ1 and NJ2 updates. He also has NE4, in case you want to get all the OTA'S from him. (Downloads will be a lot faster) They've all been used many times. I'll try to post a direct link in a few...
Sent from my SGH-T999 using Tapatalk
---------- Post added at 09:48 PM ---------- Previous post was at 09:39 PM ----------
NE4
http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
NJ1
http://forum.xda-developers.com/showthread.php?t=2941792
NJ1 and NJ2
http://forum.xda-developers.com/showthread.php?t=2985006
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Flash MJB and NE4 from the site you linked to above. Then use enewman17's thread for the NJ1 and NJ2 updates. He also has NE4, in case you want to get all the OTA'S from him. (Downloads will be a lot faster) They've all been used many times. I'll try to post a direct link in a few...
Sent from my SGH-T999 using Tapatalk
---------- Post added at 09:48 PM ---------- Previous post was at 09:39 PM ----------
NE4
http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
NJ1
http://forum.xda-developers.com/showthread.php?t=2941792
NJ1 and NJ2
http://forum.xda-developers.com/showthread.php?t=2985006
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got this site having all ota, s . And is linked to the enewman17.
www.androidayos.com/samsung-galaxy-s3-stock-firmware-2/

Lol, I guess they thought they had to provide it somehow! It's a shame they didn't at least acknowledge enewman17 in their article there, but at least they direct linked to his thread.
Anyway, good luck! And if you have any other questions come up, let us know.
Sent from my SGH-T999 using Tapatalk

Odin (fail! auth) Note 4 SM-N910P

A month ago I needed to get an extra Note 4 I had back to 5.0.1, it was on 5.1.1. I flashed it in Odin everything worked perfectly, rooted it, phone works great. A bout 2 weeks ago, I helped someone out that needed a phone temporarily, so I let them borrow it being the phone is unlocked. The person reset the phone and updated it before giving it back to me, they thought they were being nice because I let them borrow the phone. I wasn't mad but the unlock went away, no big deal, but now I can't get it off 5.1.1, and back to 5.0.1. I tried 4.4.4 and 5.0.1 a few times now Odin keeps giving me a fail. Here is what I have done:
-Tried both Odin 10.6 & 10.7 (use as admin)
-Tried 4.4.4 and 5.0.1
-There is no Google account on the phone
-Reactivation lock is off
I had flashed this phone and 2 other same model without any issues. Like I stated I have done this a few times on the SM-N910P, not to mention I'm not an expert but have been rooting and using Odin for a few years. Any help would be greatly appreciated, and I will answer any questions as far as what I did. I'm not looking for the fix to be spoon fed to me, but maybe some other options I should look at.
"long time listener, first time caller"

If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7 shouldn't be attempted.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk

Thanks for the quick reply
samep said:
If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened

Alex215 said:
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened
Click to expand...
Click to collapse
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk

samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I left the phone at the shop and will be picking it up tomorrow to try to figure it out. I have a feeling it was updated beyond the OB7, I will use PhoneInfo to verify the current bootloader.

Bootloader version...
samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.

Alex215 said:
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.
Click to expand...
Click to collapse
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk

Thanks
samep said:
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...

Alex215 said:
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...
Click to expand...
Click to collapse
I just can't understand why it won't at least allow me to return to the stock firmware.

Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you trying to get your MSL? Or UICC unlock?

Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk

samep said:
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.

ianmb said:
Are you trying to get your MSL? Or UICC unlock?
Click to expand...
Click to collapse
MSL

Alex215 said:
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.
Click to expand...
Click to collapse
Presently, the only tars that will restore are OJ6 OK1. OK1 is on Sammobile now.
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
Alex215 said:
MSL
Click to expand...
Click to collapse
MSL doesn't change. If you had it before, it still works. If not, there is a galaxy tools version that still works. If your phone is paid in full, Sprint will release it in chat session.
Sent from my SM-N910P using Tapatalk

[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.