Develop Bugs

[Q] Help! Root Issues! Expertise Needed!

I recently rooted my phone, Samsung Galaxy S4 SGH-M919, and I edited the build.prop folder to get soft keys on my device. After I restarted my phone, the wallpaper changed to all black and about every 5 seconds I would get a message saying "Unfortunately, System UI has Stopped" so then I Un-rooted my phone through SuperSU and i still ended up getting the same problem. So then I decided to Factory Reset my phone, and afterwards the problem still didnt go away, I still got the same annoying message. I don't know what to do, please help ASAP, Thanks.

Rooting wasn't the problem, it was the edit.. So you can either edit the build prop back to what it was, or restore to stock/reflash your ROM
Sent from my SGH-M919 using Tapatalk

bkboss1 said:
I recently rooted my phone, Samsung Galaxy S4 SGH-M919, and I edited the build.prop folder to get soft keys on my device. After I restarted my phone, the wallpaper changed to all black and about every 5 seconds I would get a message saying "Unfortunately, System UI has Stopped" so then I Un-rooted my phone through SuperSU and i still ended up getting the same problem. So then I decided to Factory Reset my phone, and afterwards the problem still didnt go away, I still got the same annoying message. I don't know what to do, please help ASAP, Thanks.
Click to expand...
Click to collapse
That build.prop edit doesn't work on TouchWiz. From my research I saw that Sammy gutted the framework for the soft keys, so enabling them on TW causes nothing but problems. AOSP is the only way to have the real-deal soft keys.. you can use LMT on TouchWiz, although, to me, the whole pie thing is clunky compared to having dedicated soft keys.

serio22 said:
Rooting wasn't the problem, it was the edit.. So you can either edit the build prop back to what it was, or restore to stock/reflash your ROM
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I can't edit the build prop anymore, because I'm un-rooted now. Are you sure that restoring to stock ROM would make the problem go away, and if so, how would I be able to restore to Stock ROM? I have no idea how to do that, Thanks

bkboss1 said:
I can't edit the build prop anymore, because I'm un-rooted now. Are you sure that restoring to stock ROM would make the problem go away, and if so, how would I be able to restore to Stock ROM? I have no idea how to do that, Thanks
Click to expand...
Click to collapse
Yes if you flash the stock ROM you'll get the original unedited buildprop.
If you made a nandroid backup, restore it(nandroid backup saves headaches ) If not you need to use Odin to flash the original firmware. What firmware are you on, mdl (4.2.2) or mk2(4.3)?
☞ Sent from here☜

baseballfanz said:
Yes if you flash the stock ROM you'll get the original unedited buildprop.
If you made a nandroid backup, restore it(nandroid backup saves headaches ) If not you need to use Odin to flash the original firmware. What firmware are you on, mdl (4.2.2) or mk2(4.3)?
☞ Sent from here☜
Click to expand...
Click to collapse
I'm on 4.3, and how would I use Odin to flash the original firmware and what version of Odin?

You can't edit build.prop because you're unrooted.... couldn't you just re-root, edit build.prop, then unroot again if you just didn't want root?

lordcheeto03 said:
You can't edit build.prop because you're unrooted.... couldn't you just re-root, edit build.prop, then unroot again if you just didn't want root?
Click to expand...
Click to collapse
When I was rooted, I tried to edit the build prop, but every time I tried to open the build prop folder to delete my adjustments, My phone would just keep on crashing, saying that the System UI has stopped working, So then I just un-rooted, hoping the problem would go away, but it didn't.

bkboss1 said:
When I was rooted, I tried to edit the build prop, but every time I tried to open the build prop folder to delete my adjustments, My phone would just keep on crashing, saying that the System UI has stopped working, So then I just un-rooted, hoping the problem would go away, but it didn't.
Click to expand...
Click to collapse
I'd think that you could use adb to pull the build.prop, edit on your computer, then push the build.prop back... I mean, doing a restore would work, but I'm thinking of how to not lose your data.

lordcheeto03 said:
I'd think that you could use adb to pull the build.prop, edit on your computer, then push the build.prop back... I mean, doing a restore would work, but I'm thinking of how to not lose your data.
Click to expand...
Click to collapse
What exactly do you mean by restore? I already factory resetted my phone. I don't really care about losing my data.

bkboss1 said:
What exactly do you mean by restore? I already factory resetted my phone. I don't really care about losing my data.
Click to expand...
Click to collapse
I meant flashing a stock firmware image via Odin. Being you don't care about data loss, that would be the route to take.

lordcheeto03 said:
I meant flashing a stock firmware image via Odin. Being you don't care about data loss, that would be the route to take.
Click to expand...
Click to collapse
Okay, So how exactly would I do that? I'm pretty new to these kind of things.

bkboss1 said:
Okay, So how exactly would I do that? I'm pretty new to these kind of things.
Click to expand...
Click to collapse
Go to sammobile.com to find the M919 UVUEMK2 firmware.
Follow this thread. It's for returning to 4.2.2, but the premise is the exact same for restoring official 4.3 as well. Just use the newest version of Odin and instead of flashing the UVUAMDL tar, use the one you just downloaded from sammobile.

lordcheeto03 said:
Go to sammobile.com to find the M919 UVUEMK2 firmware.
Follow this thread. It's for returning to 4.2.2, but the premise is the exact same for restoring official 4.3 as well. Just use the newest version of Odin and instead of flashing the UVUAMDL tar, use the one you just downloaded from sammobile.
Click to expand...
Click to collapse
Okay, I'm in the process of downloading the firmware. I also had another question. When I go to my phone's software update to check, for an update it says "Your device has been modified. Software updates are not available" and the device status is "Custom" even though I'm not rooted anymore and If I flash the original stock ROM, will this go away, and return to its normal state?

bkboss1 said:
Okay, I'm in the process of downloading the firmware. I also had another question. When I go to my phone's software update to check, for an update it says "Your device has been modified. Software updates are not available" and the device status is "Custom" even though I'm not rooted anymore and If I flash the original stock ROM, will this go away, and return to its normal state?
Click to expand...
Click to collapse
On that note, I don't know for 100% certain but I do believe that will stay. Perhaps someone else can confirm if Triangle Away will at least remove that aspect on 4.3; I know it won't touch your KNOX counter but I'm uncertain if it does anything for your flash counter.
All that device status: Custom means, aside from warranty being void is you can't update via Kies or OTA; but you can still update (when an update is released) by downloading the firmware and flashing via Odin OR using a custom recovery and a flashable zip.

bkboss1 said:
Okay, I'm in the process of downloading the firmware. I also had another question. When I go to my phone's software update to check, for an update it says "Your device has been modified. Software updates are not available" and the device status is "Custom" even though I'm not rooted anymore and If I flash the original stock ROM, will this go away, and return to its normal state?
Click to expand...
Click to collapse
Its still on modified because you altered system files.. Once you restore it should go back to normal
Sent from my SGH-M919 using Tapatalk

Thank you guys so much! I flashed the original stock ROM and everything is back to normal

[Q] AT&T Update Won't Install?

I checked my stock 4.3 rooted AT&T Samsung Galaxy S3 for an update in the settings and it said an update was available so I think it's the 4.4 KitKat update and so I downloaded the update and tried to install it but then it took me to a custom recovery mode and my friend told me I needed to get stock recovery / download mode for it to work so I flashed it on with ODIN and I checked and it worked. I then went back into the settings to check for an update and it said something like "Current software is up to date, you can check back in 23 hours and 21 minutes" and so I changed my time and date for tomorrow to bypass the wait and I downloaded the update OTA and while it was downloading I used Triangle Away to reset the binary counter back to 0 and then I tried to install it again and it seemed to be working fine and I got to an AT&T logo and a blue loading bar under it and next to that it said 5% so I went out of the room to let it load all the way and then when I came back I saw my phone rebooting and then everything was still the same when it rebooted so I checked the Current software in the settings and it still said 4.3 and I checked for an update too and it said "Install interrupted, try again in 48 hours" or something like that and so I changed my time and date to 2 days ahead and I am currently downloading it again. What should I do?

bump.

Where did you get the stock recovery? Were you unrooted before installing the update?

audit13 said:
Where did you get the stock recovery? Were you unrooted before installing the update?
Click to expand...
Click to collapse
Well, I searched on Google for stock recovery and I found it, I would link it to you in the comments but I'm pretty sure it's against the rules. I was not unrooted and have no idea how to unroot my phone..

I don't believe its against the rules to link to anything

The update needs the stock recovery. Are you able to boot into stock recovery? Can you wipe data and cache in stock recovery?

I've run into the same problem. I'm running completely stock aside from being rooted, I unrooted my phone but it still wont take the update. It gets to about 28% then reboots and says that it failed. I'll probably just go ahead and put custom recovery on and not even worry about the update at this point.

mschandler76 said:
I've run into the same problem. I'm running completely stock aside from being rooted, I unrooted my phone but it still wont take the update. It gets to about 28% then reboots and says that it failed. I'll probably just go ahead and put custom recovery on and not even worry about the update at this point.
Click to expand...
Click to collapse
I also made it only to around 27% and it reboots and fails, all this with root and stock recovery. I tried the OTA update with custom recovery from the settings and it just rebooted without even getting to the loading screen of AT&T.
audit13 said:
The update needs the stock recovery. Are you able to boot into stock recovery? Can you wipe data and cache in stock recovery?
Click to expand...
Click to collapse
Just so I wont break the rules if there is one about links like on many forums, I'll put the file here. Also, yes I did boot into stock recovery but I didn't try to wipe data and cache since, I'm not trying to delete my files.

There are no fixes for this?

internethuman said:
There are no fixes for this?
Click to expand...
Click to collapse
Did you remove any of the ATT bloatware before updating?

audit13 said:
Did you remove any of the ATT bloatware before updating?
Click to expand...
Click to collapse
I did remove Google+ but then I downloaded it back, other than that, I don't think so.

internethuman said:
I did remove Google+ but then I downloaded it back, other than that, I don't think so.
Click to expand...
Click to collapse
I asked because I noticed that my ATT Atrix HD would not take the OTA update because I had removed some of the ATT bloatware. I flashed back to a completely stock rom on my Atrix HD and it took the update.

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!

Back to 5.1.1?

Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!

Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Yes you can odin back to 5.1.1. Just make sure you flash the correct tar.

Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Better not. You can go up in version , but not down.

yes
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.

chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Viper works fine on MM. Either flash viper installation zip than the subpolicy zip from here, http://forum.xda-developers.com/showthread.php?t=3355270 .Or a permissive kernel like beastmode, from here http://forum.xda-developers.com/showthread.php?t=3284505 .

chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.

Ind3lible said:
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk

samep said:
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks brotha!

i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?

michael_0302 said:
i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?
Click to expand...
Click to collapse
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk

Thread moved to correct forums.

samep said:
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Did you get this working? I still have not flashed but am scared now lol =(

Ind3lible said:
Did you get this working? I still have not flashed but am scared now lol =(
Click to expand...
Click to collapse
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk

samep said:
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.

Ind3lible said:
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.
Click to expand...
Click to collapse
Reactivation Lock is in Settings/Security. Uncheck it before flashing.
No TWRP backup? Then I would suggest backing up what you want to keep, factory reset in TWRP and wipe internal memory and power down.
Odin OK1 stock tar in Odin and disable automatic updates in Settings/System update. Install TWRP, follow OP; make sure auto update remains disabled. If you don't disable auto updates stock enough, the update becomes persistent; you'll have to Google how to stop the persistent update notice if that happens.
One additional step I recommend after flashing custom ROM is to search your root folder for itson; delete what your search results. You may find a leftover folder at /carrier/ItsOn and a dalvik-cache belonging to an application in that folder in /data/dalvik-cache; that can cause a lot if persistent reboot demands after a factory reset despite the ROM not having ItsOn- this is a trace residue left in internal memory that gets added when you flash the stock tar in Odin. Enjoy Lollipop.
Personally, I think you'll want to come back to Marshmallow despite not seeing anything you want right now. You could make that TWRP backup and save TWRP folder to PC, just in case. To come back, all you would need to do is update the bootloader and baseband, factory reset and restore the backup.
Marshmallow is stricter but still manageable. Just takes some getting accustomed to. Once the tools and methods are achieved with proven compatibility, there may soon be custom ported ROMs for Note 4 on Marshmallow. At the moment it's thought to be a matter of when, not if. Time will tell if that thought is true.
Sent from my SM-N910P using Tapatalk

So I was rooted and had a custom recovery...

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