Database Users

[Q] Any downside to rooting other than warranty/knox?

I am considering rooting my Canadian (Rogers) Note 3 (SM-N900W8) in order to defeat the ludicrous SD-Card crippling brought by the latest Kitkat 4.4.2 software update. I'm aware that by doing so the Knox 0x1 counter will void the warranty. What I'd like to know is whether there are any additional negative results besides this well-known one.
For example I've seen inconsistent reports of the Screen Mirroring function being disabled as soon as the device is rooted. Some claim it is more related to the presence of a custom kernel, recovery or ROM, while others insist that merely rooting with everything stock was enough to disable screen mirroring.
If I do nothing more than use CF-Autoroot as described here:
http://forum.xda-developers.com/showthread.php?t=2466423
...no custom recovery, kernel or ROM, do I risk any undesirable repercussions other than the warranty and Knox issue? Will screen mirroring or any other functions work worse than they did before?
Thanks for any help...

Rooting won't break any functionality of the phone except the security it was meant for i.e the secure container ( and of course, depending on who you ask, warranty ). Problems you mentioned are probably related to custom roms themselves.
Sent from my SM-N900W8 using xda app-developers app

hey_joe said:
Rooting won't break any functionality of the phone except the security it was meant for i.e the secure container ( and of course, depending on who you ask, warranty ). Problems you mentioned are probably related to custom roms themselves.
Click to expand...
Click to collapse
Thanks for your reply... and will it also not interfere with any potential future over-the-air updates that might come along, be it a 4.4.3 update or a more trivial software patch to fix an issue that gets released? I realize that a major enough OTA update might un-root the phone which is fine.. I just wouldn't want to brick or lose access to updates because of root. Would they continue to be accessible, or would I likely have to first un-root manually to enable them?
Thanks again...

Yes you can not OTA update on the rooted phone.
You can unroot and apply the OTA update.
Or use the fake system status option in the Wanam.

vndnguyen said:
Yes you can not OTA update on the rooted phone.
You can unroot and apply the OTA update.
Or use the fake system status option in the Wanam.
Click to expand...
Click to collapse
Thanks... if memory serves (been a while for me since last rooted device) all that is necessary to unroot is to run the administrative option from within the Superuser app itself, to remove the SU binary completely.. correct? And then to re-root just repeat the previous CF-Autoroot steps and regain SU?

paleozord said:
Thanks for your reply... and will it also not interfere with any potential future over-the-air updates that might come along, be it a 4.4.3 update or a more trivial software patch to fix an issue that gets released? I realize that a major enough OTA update might un-root the phone which is fine.. I just wouldn't want to brick or lose access to updates because of root. Would they continue to be accessible, or would I likely have to first un-root manually to enable them?
Thanks again...
Click to expand...
Click to collapse
You don`t need OTA`s mate, just download the new updated rom from Sammobile and flash it with Mobile Odin Pro and you`ll even keep root

gee2012 said:
You don`t need OTA`s mate, just download the new updated rom from Sammobile and flash it with Mobile Odin Pro and you`ll even keep root
Click to expand...
Click to collapse
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?

paleozord said:
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
Click to expand...
Click to collapse
Within a day usualy you can download the full rom from here www.sammobile.com/firmwares/2/ and flash it with Odin or better yet Mobile Odin.

paleozord said:
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
Click to expand...
Click to collapse
Or you can open the app Phone INFO ★Samsung★, select menu 'Firmware Browser...' to see a list of available stock firmwares for your phone.
Tap to view firmware's details, there is also a download link. You can download it and then flash by Kies or Odin.
(screenshots are attached)

Nk4 update

Update coming thru..
G900PVPU1ANK4
OTA file size: 366.65MB
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g900p
http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy

Finally about time!
Sent from my SM-G900P using XDA Free mobile app

The update has been released downloading now

I'm downloading right now too
Sent from my SM-G900P using XDA Free mobile app

Insert obvious follow-up question about towel root
Sent from my SM-G900P using Tapatalk

There is already an RDF discussion thread here with announcements and links.
Please refer to this thread to prevent multiple cross posting.
RDF Discussion Thread for Sprint Galaxy S5 (SM-G900P)

This is about the update itself and specific discussions about the update. This is not about the RDF itself.
Why would you want to fill that thread with stuff not immediately about the RDF discussion?
tdunham said:
There is already an RDF discussion thread here with announcements and links.
Please refer to this thread to prevent multiple cross posting.
RDF Discussion Thread for Sprint Galaxy S5 (SM-G900P)
Click to expand...
Click to collapse

tdunham said:
There is already an RDF discussion thread here with announcements and links.
Please refer to this thread to prevent multiple cross posting.
RDF Discussion Thread for Sprint Galaxy S5 (SM-G900P)
Click to expand...
Click to collapse
Nope
Sent from my SM-G900P using XDA Free mobile app

Can anyone confirm whether or not NK4 can be rooted freely at the moment? And if so, your method of choice? I've been hearing rumors about root-killing updates(especially in regards to Lollipop) and am hesitant to do any updating. I don't want to lose superuser access just so I can get an HD Voice icon.

Jay5583 said:
Update coming thru..
G900PVPU1ANK4
OTA file size: 366.65MB
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g900p
http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy
Click to expand...
Click to collapse
Can someone grab and post the ota from your cache/fota folder.

Yes new update can be rooted

The official 4.4.4 and unofficial 5.0 can both be rooted with CF auto root
Sent from my SM-G900P using Tapatalk

banccalif said:
The official 4.4.4 and unofficial 5.0 can both be rooted with CF auto root
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I wouldn't use that unless you care to trip KNOX and give up warranty. If all you want is root to remove bloat and tweak you can without tripping.
I can say I am now on the official 4.4.4 update, rooted without knox flagged (IE still full warranty).
Runs great.
The only change I don't like is before I had WiFi calling always set to on and it would be on when I turned my WiFi on and not when Wifi was off.
Now if I have it on and my WiFi off, it turns my Wifi on randomly or on reboots, even if it was prior off.
Oh well.
Anyway. For those that want to root and keep Knox 0x0 (not tripped) it's simple.
I used Kies to update to the latest release (OTA kept giving an error that many others on sprint forum are getting).
After this I installed towelroot (don't run yet). Next I used Odin to flash the NE5 stock kernel. Ran towelroot, ran Odin to flash NK4 kernel back, after installed SU and now all is well. Full root, good performance and not knox tripped. One thing to note is that while on the NE5 kernel you will get tons of errors, just ignore them, the original kernel will fix when all done.
I don't care for custom recovery and the stock kernel honestly runs great and I can manually do any tweaks I want but have the piece of mind of not having tripped knox.
Just wanted to share though that this work around works on sprint. I know other forums mention how to do on other providers etc.
**update**
I posed the files I used in another thread (as seems we have duplicate topics). So if anyone needs the kernels I got em already converted to tar and ready to go.
http://forum.xda-developers.com/showpost.php?p=57139088&postcount=76

Nice work. I'm sure some would find this helpful! I tripped knox within the fist 20mins of owning my device ?

banccalif said:
Nice work. I'm sure some would find this helpful! I tripped knox within the fist 20mins of owning my device ?
Click to expand...
Click to collapse
Yea, I've been fighting hard to avoid tripping it for the moment. I mean I guess when all said and done I don't care TOO much, but for now if I can root without tripping I will do it. (resale value also higher if not tripped so might get new phone in March).
I imagine this work-around won't work when 5.0 comes out as the kernel is changing too much so unless someone finds a new exploit to root without knox trip I will probably end up tripping it upon official 5.0 lol but until that time I have some piece of mind if anything stops working.
I'm actually fine with stock I just hate all the damn bloat they put on it so have to root to ditch it all. I don't know why they don't just make it so we can uninstall whatever we want...

Is there any reason to update to this? I might just skip and wait for Lollipop.

slickdealers said:
Is there any reason to update to this? I might just skip and wait for Lollipop.
Click to expand...
Click to collapse
Performance, bug fixes etc. etc.
Remember this is already a skipped update. Sprint skipped 4.4.3.
It also includes new modem firmware among other things.
The wait game could be a bit. I don't expect Sprint to get 5.0 until around the time the S6 is releasing. Samsung is almost done with it but it takes months before Sprint will pump it out. Do you think they would have bothered with 4.4.4 if this was going to be out in a month?
I see no reason why one would wait? Nothing is lost, root is still possible. It may also be a prep for 5.0. Maybe they are using it as a firmware stepping stone. Who knows. I wouldn't bother waiting.

bryanu said:
Performance, bug fixes etc. etc.
Remember this is already a skipped update. Sprint skipped 4.4.3.
It also includes new modem firmware among other things.
The wait game could be a bit. I don't expect Sprint to get 5.0 until around the time the S6 is releasing. Samsung is almost done with it but it takes months before Sprint will pump it out. Do you think they would have bothered with 4.4.4 if this was going to be out in a month?
I see no reason why one would wait? Nothing is lost, root is still possible. It may also be a prep for 5.0. Maybe they are using it as a firmware stepping stone. Who knows. I wouldn't bother waiting.
Click to expand...
Click to collapse
So you think we won't get Lollipop until April when we already have a leaked (pretty damn stable) build?? I'm sorry but that is straight up idiotic. We will have Lollipop by the end of Dec-Jan.

As of now there is no towelroot for 5.0 so you might have to. Xposed also doesn't work and might be a while before its able to run on the new platform.
I'm running the 5.0 leak now, we will definitely have Lollipop by Jan at the latest, I think more like late Dec
Sent from my SM-G900P using Tapatalk

JoeFCaputo113 said:
So you think we won't get Lollipop until April when we already have a leaked (pretty damn stable) build?? I'm sorry but that is straight up idiotic. We will have Lollipop by the end of Dec-Jan.
Click to expand...
Click to collapse
Might not be April but it won't be by February or probably March even.
The key word you said is "Leaked"...
Sprint had 4.4.4 builds in testing for months also, they just don't always leak out.
Just because you have a non-production version doesn't make it magically release sooner.
If you look around you will notice Sprint is generally a tad slower on some releases at times. This is because they like to wait and see what other providers do and also avoid having to do more releases.
Take Verizon S5 for example. It got 4.4.4 a lot sooner vs. we did, but the downfall was it had issues and security holes that they had to go back and patch again with more OTA's.
Sprint waited longer, didn't have to turn around and do all of this.
Waiting longer can often mean a more stable product as it allows other things to mature.
Sprint also generally doesn't like to update an phone right away if a newer model is about to come out with the new stuff also as it could cut into sales.
S5 will get 5.0 but based on how Sprint operates and historical events I don't see them doing it before a new flagship model comes out in which some people may feel they can now hold off longer. The leak FWIW is kind of like a marketing toy. It shows that they are committed to upgrading the OS so people don't do the whole "I'll never use sprint/samsung on sprint again cause they stopped updates". They are doing the updates, just doing it slower.
At the end of the day we are all speculating. You don't know for 100% just as I don't. I'm just saying (in my head at least) my thought makes more "sense".
FWIW I hope I am wrong because like you I own this phone too and want to have the new fancy stuff

NK1 (US version) is here

Just hooked up my 8.4 with Kies 3 and got this:
-----update-----
reroot: OK
Make sure you don't disable KNOX (hit cancel when you're prompted)
Wi-Fi seems to be faster
Touch looks OK.

Great I have been waiting for the US version,
On your upgrade did root carry over from your previous install or did you re-root with TR or use the kernel swap method?

mingkee said:
Just hooked up my 8.4 with Kies 3 and got this:
-----update-----
reroot: OK
Make sure you don't disable KNOX (hit cancel when you're prompted)
Wi-Fi seems to be faster
Touch looks OK.
Click to expand...
Click to collapse
I also got the update on my tab pro 12.2 ota

otyg said:
Great I have been waiting for the US version,
On your upgrade did root carry over from your previous install or did you re-root with TR or use the kernel swap method?
Click to expand...
Click to collapse
I rerooted with CF.

What the changes for NK1? Is it still 4.4.2?

HKSpeed said:
What the changes for NK1? Is it still 4.4.2?
Click to expand...
Click to collapse
Yes, it's still 4.4.2.
It's a bit snappier and the Wi-Fi performance is better.

mingkee said:
Just hooked up my 8.4 with Kies 3 and got this:
-----update-----
reroot: OK
"
Wi-Fi seems to be faster
Touch looks OK.
Click to expand...
Click to collapse
Can you explain for a new user please.
Is this the recent update I hear people are getting yesterday and today?
:Make sure you don't disable KNOX (hit cancel when you're prompted)"
Is this something for those rooted or does it apply to stock application. Have no clue what KNOX or Kies 3 is

It is for those who are rooting. This is the notice from the SuperSu app which is used in the routing process

mingkee said:
I rerooted with CF.
Click to expand...
Click to collapse
doesn't CF trip knox, has anyone tried TR on this firmware yet?

otyg said:
doesn't CF trip knox, has anyone tried TR on this firmware yet?
Click to expand...
Click to collapse
It will trip KNOX, so you go other route if it's your concern.

GTT1 said:
Can you explain for a new user please.
Is this the recent update I hear people are getting yesterday and today?
:Make sure you don't disable KNOX (hit cancel when you're prompted)"
Is this something for those rooted or does it apply to stock application. Have no clue what KNOX or Kies 3 is
Click to expand...
Click to collapse
If you disable KNOX during root process, it will crash some services which causes system crash when waking up (see Q&A section).

TR won't work anymore but you can swap kernels with AN3 (or 1) root with TR then swap back to NK1 and not trip knox.
Anyways someone (on another thread) said the ANG1 firmware have + - adjustment for auto brightness however I'm not seeing that option in this firmware did they remove it in this revision (I never tested ANG1) so just wondering.

mingkee said:
If you disable KNOX during root process, it will crash some services which causes system crash when waking up (see Q&A section).
Click to expand...
Click to collapse
I did this, then froze all the knox stuff in titanium backup. Not a single crash or reboot with knox disabled.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
---------- Post added at 07:22 PM ---------- Previous post was at 06:47 PM ----------
Just added a thread with the this FW and it's parts in odin flash-able form.. Here: http://forum.xda-developers.com/gal...320xar1ank1-extracted-stock-firmware-t2954549

I just got the OTA and installed it, I wasn't rooted though so just your basic OTA install.
Too soon to notice any changes but wondering why it isnt 4.4.4? My wife has an S4 and it was just updated to 4.4.4 and I think the S4 is older than the tab pro.

mingkee said:
I rerooted with CF.
Click to expand...
Click to collapse
Can you please tell me how you were able to root with CF? I tried using the method from android central. Everything worked like the guide stated but the tablet still don't have root access.

The day that I installed the OTA my battery life was pretty bad, on a very basic level it drained a little more than twice as fast when using the table the same way in the past.
It could just be because the new software was flashed and it needs to settle a bit and maybe a reboot or two, well that is what I am hoping at least.

Raistlin1 said:
The day that I installed the OTA my battery life was pretty bad, on a very basic level it drained a little more than twice as fast when using the table the same way in the past.
It could just be because the new software was flashed and it needs to settle a bit and maybe a reboot or two, well that is what I am hoping at least.
Click to expand...
Click to collapse
I updated yesterday and it seems the battery consumption is the same. Maybe a reboot or one cicle charging will do it.
The only difference I noted is that it seems a little bit snapier, but again, it could be the placebo effect...

I noticed you said you went from NG1 to NK1 and that it was snappier
Did you try NI1? That was already snappier than NG1, so I wonder if there's any diff for those of us on NI1

locutusx said:
I noticed you said you went from NG1 to NK1 and that it was snappier
Did you try NI1? That was already snappier than NG1, so I wonder if there's any diff for those of us on NI1
Click to expand...
Click to collapse
I didn't try the NI1. I haven't rooted my tablet yet, a bit of lazyness and lack of time.. hahahahah
But it seems the difference between the NI1 and the NK1 is the CSC (UK vs USA). I don't think they differ much if differ at all. Maybe someone with more knowledge can tell better.

how can you root nk1?

SM-T320 March 2015 Firmware Upgrade

I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.

horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
IPTV or torrent tv, normally plays through mx player ?. Was a bug, half of the screen black
http://forum.xda-developers.com/app...f-screen-black-watching-t3017829#post58842303

That firmware is just for the UK, which I believe went to NI1 last fall about a month before the U.S. went to NK1.
I don't know that I'd read a lot into it. If anything, they could be getting UK firmware better aligned with other locations for a smoother universal upgrade to 5.
Edit: Okay, looks like it's indeed out now for the U.S., too. Still hoping it's progress towards a Lollipop upgrade.

So does anyone actually know what changes this update brought? I was having some issues with my tab pro 8.4 missing touches, i 1st noticed it during gaming but was able to replicate it with display tester multitouch test.
It seems to be fine now, i thought for sure it was a hardware defect but now I'm not so sure. Anyone else in a similar position as me?

Hey there
I m downloading it, but not sure i will apply it .. does it makes root going byebye ? Wanna stay with my device rooted !
thanks

I just downloaded and installed in California. Still 4.4.2 no issues so far.
Sent from my SM-T320

+1. Got excited over nothing.
johna2u said:
I just downloaded and installed in California. Still 4.4.2 no issues so far.
Sent from my SM-T320
Click to expand...
Click to collapse

Rooted device? Able to root after update?
Thx

Just finished updating and was very disappointed that it's still 4.4.2, I didnt check this forum beforehand so was hoping for a nice surprise.
I hope we see official 5.0 for our devices...

Still. Nothing here! Will we ever get lollipop?

biroot said:
Rooted device? Able to root after update?
Thx
Click to expand...
Click to collapse
Without thinking I took the update and lost root. So, I'm searching to see if root is available for the update.

Rooted T320UEU1AOC1
66gt350 said:
Without thinking I took the update and lost root. So, I'm searching to see if root is available for the update.
Click to expand...
Click to collapse
I rooted with Chainfire"s CF-Auto-Root for Odin. download.chainfire.eu/383/CF-Root/CF-Auto-Root/CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip (For T320). Main web page here autoroot.chainfire.eu/. As you know To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding! So don't forget http//:

Rooted i747 said:
I rooted with Chainfire"s CF-Auto-Root for Odin. download.chainfire.eu/383/CF-Root/CF-Auto-Root/CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip (For T320). Main web page here autoroot.chainfire.eu/. As you know To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding! So don't forget http//:
Click to expand...
Click to collapse
Thanks for the quick reply. Reading on the main page, did using the Chainfire's CF-Auto-Root trip the Knox Counter and the custom firmware counter?
thanks

A little bit less lag going from TW to Magazine tiles. Tried removing them with no luck. Hopefully this update sets us up for lollipop.
Sent from my HTC One mini using XDA Free mobile app

66gt350 said:
Thanks for the quick reply. Reading on the main page, did using the Chainfire's CF-Auto-Root trip the Knox Counter and the custom firmware counter?
thanks
Click to expand...
Click to collapse
It trips knoxs
Ported Note 4 on 3

Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again

M4r10 22 said:
Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again
Click to expand...
Click to collapse
I'm in the process of trying to line up everything to do this. My update that pushed through took me to T320UEU1AOC1. I haven't located the extracted US kernel file for that and unfortunately don't know how to pull it from my current build. Sammobile has an AOC1 file noted as Cellular South and the build time is same date as mine but different timestamp. Anyone know if that would work to get me back to my current build and keep my US region?

horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
How did you do this? I have mine rooted and have TWRP but can't figure out how to get that stupid Touchwiz back. Any help would be great
---------- Post added at 02:25 AM ---------- Previous post was at 01:27 AM ----------
horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
Could you put the steps I need in order to what you did here?

I have the Romanian version of the updated ROM on a T325.
The biggest issue I have noticed is with the light sensor, with the previous ROM the auto setting worked smoothly, now with the new ROM the screen doesn't fade continuously. Whenever I turn on the screen the brightness just switches from a higher to a lower setting or inversely (without smooth fading and with lag), also the screen flickers horribly when it detects a change so I can't use the auto anymore.
The second issue is with the Samsung keyboard with learning disabled, in a Facebook floating chat window I tried to respond to someone and the keyboard would auto complete with empty words and after every word I had to delete the word before to be able to write the next word. I had to re-enable the learning to get rid of this very annoying problem.
I will try to downgrade to the previous ROM and root it with towelroot and say goodbye to any future official Samsung updates. Samsung has the ****tiest update developers, actually I had the same problem with the auto light setting (but not so serious) with the ROM which was before the good one.
By the way, if Lollipop comes DON'T UPGRADE. Lollipop on S5 sucks bigtime, the phone has major issues, android eats more battery than the screen.
Stick with the previous ROM, for me it was the most flawless one. I might try a cache wipe on the current ROM but I doubt it has anything to do with the screen flickering.

M4r10 22 said:
Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again
Click to expand...
Click to collapse
stormygal said:
I'm in the process of trying to line up everything to do this. My update that pushed through took me to T320UEU1AOC1. I haven't located the extracted US kernel file for that and unfortunately don't know how to pull it from my current build. Sammobile has an AOC1 file noted as Cellular South and the build time is same date as mine but different timestamp. Anyone know if that would work to get me back to my current build and keep my US region?
Click to expand...
Click to collapse
After losing root when I took the T320UEU1AOC1 update, I was able to flash the T320 kernel in this thread then use Towelroot again. I did have to reboot, even though it told me I wouldn't need to. I uninstalled and reinstalled SuperSU (hit cancel when I got the SuperSU notice about Knox) and verified root with Root Checker Basic. Then installed the AOC1 kernel. I still have root and Knox is not tripped. (KNOX KERNEL LOCK: 0x0; KNOX WARRANTY VOID: 0x0)

[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop

If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.

Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?

^^^I'm not sure, but I've been postponing mine since the Ota was pushed.

Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.

When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"

itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"

rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.

Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated

Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!

So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?

hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man

samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.

I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.

Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?

There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it

So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?

As of now it makes no difference.

Stupid question, but how do you turn off automatic OTA on lollipop?