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

Flashing AllianceROM to my stock, but rooted Note 4

Hello, I am new here and could use a little help please.
I would like to flash AllianceROM for my Sprint Note 4 N910P - NK2. It is running the stock Kitkat 4.4.4 and has been previously rooted via Odin.
I read that if I am coming from Kitkat, that I need to "Odin Lollipop with modem and bootloader..", and I have a vague idea what that means but no idea how to go about it.. What im not clear about is, does that mean I need to update only the bootloader and modem, or also the OS?
I really appreciate all of your help!

It's as simple as:
Odin OB7 stock tar and Odin TWRP. Flash ROM. Get stock tar and Odin from link below. PC driver will be at Samsung mobile support for Note 4.
http://forum.xda-developers.com/showthread.php?p=59483780
TWRP recovery for Odin:
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
But the 3 things to consider or note before you begin:
1) if you update beyond OB7, the bootloader gets upgraded to one with a reactivation lockable bootloader. That will prevent you from being able to Odin back to KitKat. You need to disable auto update and stop the update notices before they start; otherwise the nags persist and you may accidentally update.
2) the lollipop file system is different than KitKat do better off formatting your data and wiping cache and dalvik-cache and powering down and pulling battery prior to Odin OB7 stock tar. Let it boot and setup wizard prior to Odin of TWRP (uncheck auto reboot for recovery flash only), boot into TWRP recovery and flash the ROM.
3) dalvik gets built on initial boot of lollipop ROMs; the stock tar still not much quicker. You'll likely see the phone hang at the second boot splash screen with blue LED slowly blinking before you see the app optimization and app start pop-ups. You can expect that with lollipop. Give it 30 minutes to boot before you panic. To avoid CPU heating and slowing the process, remove your phone from its case and ventilate if it gets too warm. You need to start with battery charged to about 80% to full to be safe. It's best to not try and update apps or restore apps until you've flashed and booted the custom ROM. More apps means the process takes longer. You can format the data again prior to flashing the custom ROM to speed things along. If possible, backup your media, and downloads that you want to keep and wipe internal sdcard to get a cleaner start with lollipop. That's optional but don't lose your keepsakes. What you flash should be on extSdCard to avoid the wipe-loss if it.
BTW, the post you're referring to may have been an attempt to recover phone after attempting to downgrade to OB7 or KitKat. It's since been discovered that although Odin wouldn't downgrade, there's a possibility to flash older ROMs in recovery and immediately flash a 5.1.1 rooted kernel to get it to boot without looping. That doesn't have to apply to you; the general rule is to Odin flash the tar that matches the ROM you want to flash in recovery. But again, if you upgrade beyond OB7, you cannot go backwards with Odin. Only few exceptions apply; generally it is forward, not backwards. OB7 is the divide that separates the simple from more complex conditions. So these last 3 paragraphs shouldn't apply to you as long as you're wanting to stay with OB7 or KitKat.
Just for an idea of what to consider in other lollipop updates. The ram optimization got a bit crazy after OB7 and continued until it improved in OJ6. Personally, I think OJ6 and OK1 updates are the best lollipop updates yet. You'll certainly find more security updates in those updates. But lollipop 5.1.1 also introduced the need to root the kernel but Chainfire has recently brought us a patch to use stock kernel again; it's married from experimental to beta. I've mostly ran with stock kernel on my phone, especially before lollipop 5.1.1
Long post but felt the long threads needed some explanation. Things were once simpler but got a tad more complex as time and updates followed OB7.
Sent from my SM-N910P using Tapatalk

Wow that was an incredibly detailed post and I think it will be exactly what I needed to know, so thank you for that!
The original post I was reading was here by the way - http://forum.xda-developers.com/not...-0-1-allianceromn910p-18-themes-huge-t3066673
I will get going with this a little bit later today and let you know how it turns out, again thank you for that awesome reply! :fingers-crossed:

Just to follow up, with your instructions it went on without a hitch!
Thank you!

Currently Alliance ROM want to go back to Stock

Title sums it up. Currently on AllianceROM 5.0.1 OB7. Want to go to stock (rooted probably) so I can get MM when it (if it ever) drops. Do I need to do anything special or can I just wipe everything in TWRP, then Odin the stock zip? I get a little weary reading about bootloaders locking above OB7. What does that mean for flashing ROMs if I upgrade the bootloader? Also, does the hotspot fix work on the most recent stock ROM?
Thanks for any help. I have three little kids and no time to research this fully, otherwise I would.

If you're looking to stay OTA capable without going through Odin again to update to MM (weeks to go possibly, IDK?), you most likely wouldn't be able to add hotspot mod without losing OTA capability.
- Use the updated Chainfire Auto Root for Note 4 mostly stock with OTA capability.
*You'd use the full un-root option in SuperSU to update. It's supposed to work if no system mods or system mounting occurs but no guarantee or confirmation I'm aware of on that. You could test that with OJ6, full un-root and take OK1 OTA update if so inclined to test it.
==================================
If upgrading to the reactivation locked bootloaders, alternate ROMs really have little limitation if done without Odin downgrading (only where the ROM you seek or return to is on an older update- that applies to alliance whether you're restoring a backup or flashing a ROM zip). But that also requires Odin again at some point unless you wait and do it only when necessary. You must flash ROM zip or restore a backup and flash a 5.1 kernel like Beastmode rather using Odin to downgrade. The kernel had to be flashed in order to get it to boot. Only limitation that I'm aware of is that your screen may not auto-dim on handset call when you put phone to ear. I had that issue with OB7 ROM with 5.1 kernel; I used the power button to dim the screen but you can't have power button set as an option to dismiss call or that happens when you don't want it to.
=================================
Moar 2.1 ROM is coming soon. That may help with the anticipation of waiting long for MM. But again, that means Odin for OK1 update, then Odin for MM. There's a chance that OTA to MM could be achieved even if dm-verity gets detected in stock recovery while trying to OTA. I think you'd have to clear and download the MM OTA again but first root with Chainfire Auto Root, full un-root in SuperSU app then try the OTA again. Odin OK1 by itself may not clear the modified status but systemless root and un-root may clear it. Just thinking ahead though; no guarantees. May have to wait for MM stock tar.
If not interested in current or future Lollipop rooms, you could just wait, Odin OK1 and OTA to MM when the update is available. Easy?
To answer the Odin question, you're correct on the update though. I tried to answer any questions you might have but may confuse you. I'd need more information on direction you're considering to answer more thoroughly if that leaves more questions.
Sent from my SM-N920P using Tapatalk

I'll have to find a time when I have time and can be without a working phone for a few hours and try to play around with some of this stuff. I'm sure I'll be back on here with questions at some point. Thanks for the initial guidance.
Sent from my SM-N910P using Tapatalk

Okay. I think today is the day. I've downloaded MOAR 2.1 and am going to try this for now. I also have the OJ6 stock (I know it's not the absolute most current) downloaded and ready for standby if I so choose. Here is my plan.
1) Wipe Factory Reset in TWRP 3x's (actually include internal storage as well, correct?)
2) Install TWRP 3.0 via Odin (currently 2.8.5)
2a) Per MOAR install instructions, install stock OJ6 via Odin and activate, etc, etc. Ensure everything works, maybe take the OTA to OK1.
3) install MOAR via TWRP from micro SD card
4) Profit!
If I want to install stock, all I need to do is install the stock ROM via Odin and I will be able to update OTA since I will by default be unrooted, correct?
Thanks for the help. I plan to attempt this later today.

I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk

samep said:
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?

pilotmills said:
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
Click to expand...
Click to collapse
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk

samep said:
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I think I need to slow down my postings . I looked around and found out basically what you just told me. Flashing the stock OK1 now, then I'll redo TWRP. Thanks for the timely replies. I'll try to keep it to only issues I run into that I can't resolve after some Google research. I really do appreciate the help.

Progress, but now I can't get the GPS to lock. Tried GPS status app, GPS Status and toolbox. Occasionally I get one or two satellites that show a signal being received, but never locking onto them. Eventually they will drop completely to zero signal. On the other hand, somewhere between OB7 and OK1, Samsung actually addressed the barometer issue that had plagued the N4 since launch where above about 3,000', it would not register anything but a sea-level pressure. Baby steps. . .

Is GPS failing to lock on stock OK1 tar update or the port? The port has GPS a release with fixes pending. But most were only reporting GPS navigation in Google Maps lagging or losing sync during navigation.
Sent from my SM-N910P using Tapatalk

Sorry, should have specified. I'm on stock OK1 now.

pilotmills said:
Sorry, should have specified. I'm on stock OK1 now.
Click to expand...
Click to collapse
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk

samep said:
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
The GPS chip in this phone is horrible. I had the phone up against the window as a last resort and still nothing from the GPS. Went outside and it grabbed a lock within 30 seconds. I didn't opt for the anti-NSA snooping coating on the windows when we had them installed either. . . Backing up OK1 in TWRP now, then attempting to flash MOAR.
Thanks again. Stay tuned. . .

Got MOAR up and running. I had an activation issue the first time which was strange since I was able to send and receive texts and calls, but I kept getting an activation not complete message popping up and persisting. I did exactly as posted in the OP as well. Anyway, went back to OK1 stock and waited even longer after the data established before reflashing MOAR. Works like a charm now. Thanks for the patience and assistance!

Marshmallow upgrade from Rooted BOB7 and no Odin

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

Upgrade Help Please

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