So the story is about 9 months ago my Galaxy note 4's USB port got messed up. I cannot charge my phone without using an external battery cradle, nor can I connect my phone to computer and sync/odin. I am stuck on a rooted BOB7 rom specifically the noterized rom stable 3. I know I cannot jump from BOB7 to COK1 etc... via flashing. I was wondering if the jump to marshmallow from lollipop would work.
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Thank you
Thank you very much tx_dbs_tx, you are a life saver! I have been stuck for the past 9 months.
tx_dbs_tx said:
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Click to expand...
Click to collapse
Is there a chance of doing the same on OG5? Using OBAR
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Can someone confirm with me, that sending picture messages won't go through. Or is it just me?
cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
Sorry for the late reply Cheryl. There is no reason not to update your software to Marshmallow 6.0. Typically updates bring improved performance and battery life as well as other software optimizations which are always better than previous software builds. You should backup your photo's etc before installing any update just in case. If you're one of those who doesn't like change and is content with your phone with it's current software then you don't have to update the software as long as there isn't a critical update that would prevent something from working on your phone unless you take the update. If everything works and your happy then you can leave it as is. But if you are interested in improved battery life and overall performance as well as new security features and policies of android, then by all means update your software the first chance you get. there are no drawbacks that i have noticed or read from any other users. Marshmallow is a go! :good:
cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Sterist said:
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Click to expand...
Click to collapse
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
cherylbaker said:
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
Click to expand...
Click to collapse
if you don't have your MSL, and don't know where to find/how to get Galaxy Tools, and you still have a while left on contract, it wouldn't hurt to downgrade and grab your MSL first then jump straight to MM
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
kjtrini1 said:
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
Click to expand...
Click to collapse
I don't know how to extract it from a .tar but I know it can be acquired it like this:
1. full backup in TWRP
2. copy the backup to pc for safekeeping
3. odin full OB7 stock tar
4. without flashing TWRP, root using CF auto root*
5. install Flashify from Google Play
6. backup recovery
7. copy the backup to pc for uploading
*I don't know which version (if applicable) as I never use that method to root. sorry
obviously you wouldn't be able to do this yourself, you would need someone on the forum with OB7 bootloader to do this, and honestly, without knowing how to extract / find it in the.tar I still think that would take a lot less time and effort than this method lol
Related
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872
Thanks enewman for writing this up.
Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!
I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!
mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse
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
I got the note 4 I am on kit kat N2K. I want to root but wanted to know the best way to go about it. Root on kitkat, then flash a rom to get on lollipop? Or accept the lollipop update, and then root and flash? Please advise thank you !
You'd have to decide what you want the most.
With Lollipop you get improved Sprint Wi-Fi Calling and latest security and bug fixes. The battery usage is notoriously higher in Lollipop and the fabled material theme is ugly to many.
KitKat has better battery and theme. Until the recent Android 5.1.1 updates, Lollipop bugs had many utilizing fixes to make Lollipop more like KitKat. The thing most important to consider is that if you upgrade to Android 5.1.1, the bootloader will inhibit you from Odin'g back to KitKat unless you use a specific Odin tar for OB7 to OG5 but it doesn't support the most recent OJ6 update. It's said you could just update the modem to OJ6 but I'd think you have to at least Odin the OB7 lollipop tar before doing that.
I wouldn't recommend rooting and then flashing a ROM outside of the base you're running. Use Odin to update to the equivalent base. OJ6 would be the latest but bootloader inhibits downgrade to KitKat.
I'd suggest rooting KitKat and trying it or a custom NK2 ROM. Next you could try OB7 to see if Lollipop is to your liking. Then you could decide if the latest is what you prefer.
Developer support is currently at OG5 and OJ6; Android 5.1.1 Keep in mind that Android 5.1.1 stock requires kernel with root exploit and SuperSU zip flashed in custom recovery to root. The updates prior can be rooted with CF Auto Root or just Odin custom recovery and flashing custom ROM or SuperSU zip to root stock.
What to flash? You'd have to ask a specific question once you have a better idea of what you prefer or direction you're starting at.
Sent from my SM-N910P using Tapatalk
Thank you for taking the time to type all that up for me! I am going to stay stock until the 14 days incase the phone has some problems before rooting but my brother and dad have note 4 also and both on 5.1.1 and phones are way smoother than mine on kit kat so I would want to be on the latest and have root. I also saw there is a note 5 rom which looks great as well. So is it cool if I PM you in a week or so to help me? I know there are threads but I dunno where to begin . Appreciate it!
Thank you,
Indels
Yes, you could PM. Are the other Note 4 phones rooted or plain stock?
Currently, the Note 5 port is one update behind latest. Maybe it will update.
You don't have to stay with KitKat. Updating won't void your return exchange. But I would recommend a factory reset before making the jump to Lollipop. You can take incremental updates over the air; KIES or Odin stock tar OJ6 from general forum would get you updated to latest in one session.
Just don't Odin custom recovery if you're concerned about Knox trip during your return period.
To get started you'll need the Samsung driver for your PC to use with KIES or Odin. You'll find that here:
http://www.samsung.com/us/support/owners/product/SM-N910PZWESPR# Run the .exe file on PC to install.
Here's a link to TWRP for Note 4:
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
Download Odin (below) and make a folder for it and put the TWRP file and stock tar in it. Find the latest tar in general forum and check the md5.
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
You can also download the zip for ROM you wish to install. Typically, you'd flash the tar that corresponds to the ROM you wish to run for maximum compatibility so you could wait on the tar and zip. Any of these could change but preparation wouldn't hurt.
Sent from my SM-N910P using Tapatalk
Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !
Ind3lible said:
Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !
Click to expand...
Click to collapse
Battery life for initial Lollipop was not so good until Beastmode kernel came out starting in OG5. I've heard OJ6 is even better but I haven't tried it.
Like I said, KitKat has better battery but worse Wi-Fi Calling feature.
Touchwiz 5.1.1 is rooted with custom kernel and SuperSU zip or any custom ROM is pre-rooted. Just don't use Chainfire auto root for Note 4 on that.
Sent from my SM-N910P using Tapatalk
"But I would recommend a factory reset before making the jump to Lollipop."
So I should factory reset on kit kat and then go to lollipop if I understand this part correctly? I have to notification to go to 5.0 right now. I can odin twrp once I go to lollipop too right? Sorry for so many questions just confused. I have not rooted a phone in quiet some time :fingers-crossed:
Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk
samep said:
Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!
Ind3lible said:
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!
Click to expand...
Click to collapse
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk
JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx
samep said:
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.
Ind3lible said:
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.
Click to expand...
Click to collapse
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk
samep said:
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir! You've been of most help!!
alwright1980 said:
JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx
Click to expand...
Click to collapse
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !
I havent keard of a firmware ending ok1 for the SM-N910P
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
Ind3lible said:
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !
Click to expand...
Click to collapse
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root RestrictionsAll of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents
alwright1980 said:
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root RestrictionsAll of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents
Click to expand...
Click to collapse
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
I don't think it would have been possible to have gon from KK - LP - MM while preserving a KK Bootloader, and if I am correct in that you won't bee able to Odin back to KK unles you can get reliable instructions on how to seperately flash bootloader, which might be a risky venture, I simply don't know there. You also may be able to get a custom rom which is KK based but I would discuss trying to use it on a phone that has been updated to MM with the DEV if they still offer support. Whatever you do be cautious and well informed before proceeding and know your risks, otherwise it can get expensive.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
I would have thought that it would have been impossible to flash 2 a lollipop and then a marshmallow ROM from a KitKat ROM while preserving the KitKat bootloader. If I'm correct in this then you will not be able to Odin Flash from your marshmallow ROM back to stock KitKat firmware. That is unless you know of a way to separately and reliably Flash your bootloader. You may be able to use a custom rom that incorporates KitKat, but I would be careful about deploying around like that after having updated to marshmallow firmware, and I would discuss it with the developer if they're still offering support for it. Whatever you do be cautious and well informed before moving forward otherwise it can get expensive!
Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
It can be done but not as you would think. The KK bootloader wouldn't flash but read the instructions in this post.
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Edit: if you still have that KK backup, you could restore that instead of the KK ROM but still need the Lollipop custom kernel and Lollipop bootloader.
Sent from my SM-N910P using Tapatalk
Like I said I don't know anything about bootloader switching betweem KK -LP -MM. So I cannot comment effectively on whether or not it would besafe or what you might lose or gain by these methods. Just don't know.
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
samep said:
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
So, now I am on PJ1 and I don't know how to put TWRP on my phone, I want to put tx_dbs_tx's UN7 hybrid on my phone and I am having issues both finding and putting TWRP on my phone... and I can't find a download or anything for it...
I've downloaded 2 different versions of twrp and used odin to put them on but I think I am doing something wrong because it isn't booting into twrp
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Curtai said:
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Click to expand...
Click to collapse
Oh your talking about installing twrp? Yeah you have to not let it reboot. And when is done pull battery and boot into recovery to get it to stick. Obviously you figured it out. But just saying. I think earlier versions you didn't need to do that but now you do.
Glad you got it going. How you like the Rom? Running smooth for me.
ROM is good
Well I obviously got it going and didn't read the first couple posts after the install and didn't notice the SMS issue so I had that problem and I can't find a lot of the menu options that I had with the OB7 original I've been running for about 18 months... It's pretty smooth now and I'm wondering how fast it will fill up my internal memory I like that it's almost 20 gigs free.. for a while I was running on less than 6 I need to find an efficient way to use my external SD card... Other than that the options are neat but it seems really bloated all the extra Google apps make me sick even though I never use them... I've got titanium backup and am freezing them and will probably uninstall them soon... I want a small ROM that I can customize myself or apps that are easily removed or whatever half the apps I don't want are in ROM which is a pain to remove or I just don't know how to unless I use TB
Wow that's a novel sorry but yeah that's my ramblings for the next week I guess... Now I'm gonna hit the rack...
I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.
toenail_flicker said:
I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.
Click to expand...
Click to collapse
You lose root updating.
Fyi: recent updates do not have developer support but maybe latest security update is your goal?
If you're not interested in rooting again and flashing custom ROM and prefer latest stock ROM, I'd recommend:
decrypt any data encrypted
backup any keepsakes to ext SD Card
remove fingerprints
make a TWRP backup (backups should be on external SD Card)
factory reset
wipe internal memory
Power down and remove battery prior to download mode
Flash latest stock tar with Odin from this thread (it may download faster- QB3 would be OK unless you want to download latest, if available. Updates usually aren't available for some time). Use Odin defaults and go through setup wizard.
https://forum.xda-developers.com/showthread.php?p=63868221
Quickest way to latest update is to install Smart Switch (unless you found latest to download for Odin).
https://www.sammobile.com/samsung-smart-switch/
Note: If you do decide to run a custom ROM, security updates are not up to date but it's recommended to install the update recommended in OP for those custom ROMs. You may lose some compatibility by not flashing the recommended update.
Stock tar updates for Odin are full updates so they're not required to be flashed in sequential order. Same for Smart Switch updates. Smart Switch likely only works for non rooted phones which is why I recommended to start with Odin stock tar.
OTA updates patch the previous update sequentially. So OTA update would only be ideal to update after getting to latest with Smart Switch. Odin updates are slower to become available as I recall.
Make your battery is charged to 80% or more. I wouldn't recommend a battery that's over a year old. Start with a fresher battery and replace batteries that have over 500 recharge cycles on them. This could save you trouble in the long run.
Also, keep your phone cool during these initial boots after flash. Forced air from a small fan or air purifier should do fine.
Sent from my SM-N920P using Tapatalk
"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.
wow. so much valuable information in your reply. this is amazing. thank you.
toenail_flicker said:
"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.
Click to expand...
Click to collapse
You do recall that once you upgrade past OB7 that you lose the ability to return to KitKat via Odin stock tar?
The TWRP backup I recommended is still useful but likely you'd need to downgrade bootloader firmware to 5.1 (OG5 to OK1 is recommended once you've upgraded beyond OB7), factory reset, wipe internal, restore backup and flash Beastmode 1.0 kernel prior to booting.
I think you also need to flash SuperSU zip after kernel to get a boot but I'm not sure on that.
Have you already been through this with lollipop 5.1 and went back to KitKat? If so, you know the drill, just make sure you have the right bootloader.
If you're looking for developer support on stock like ROM, check out dtux or UN7 ROMs with aroma flash modset mods. There's also a few modified stock ROMs that are newer.
I discovered this morning that older updates for Note 4 are vulnerable to BlueBorne exploit through Bluetooth. I keep mine off mostly and disable the options in improve location and nearby devices so it shouldn't be a issue for me. There's a BlueBorne vulnerability scanner in Google Play to check later updates if you like. Search for it in Play.
Sent from my SM-N920P using Tapatalk