I'd like to have the flexibility of choice - I want to be able to prevent my carrier, US Cellular, or Samsung from disabling our crippling the Note should I choose not to return it.
UPDATE: Answered here.
http://forum.xda-developers.com/showpost.php?p=69377632&postcount=42
Package disabler pro
Sent from my SM-N930F using Tapatalk
And then what?
how do you know it's gonna work? I would think OS updates would have been taken care outside of standard packages.
You can go to settings and set to manual updates. It won't "disable but it won't update unless you tell it to
Sent from my SM-G935T using Tapatalk
Well on my first note mine was set to manual and it pushed the update through regardless a few hours after the notification arrived. IMO anybody able to root has nothing to lose by rooting if they're intending to keep it at this point.
Package disabler. Disable System update SDM's. Don't touch anything to do with Knox though.
Disable these:
Security policy updates
Software update
System update 1
System update 2
I've had those frozen on both my original Note 7 and my replacement Note 7 and get no OTA's at all. Don't think they can push them to you with these disabled.
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!
flanky79 said:
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!
Click to expand...
Click to collapse
I think you have to edit the build-prop (which means you need to be rooted) to get the Gear VR to work.
As far as the 2 system sdm updates - they are on both my Note 7's, but then I haven't ever taken an OTA or any update as I disabled all of that first thing I got the phones (one was my OG N7, the other the replacement N7). So I can't help you if you have already taken an update, but those system SDMs should be there unless they removed them in an update somehow, which I doubt.
teegunn said:
I think you have to edit the build-prop (which means you need to be rooted) to get the Gear VR to work.
As far as the 2 system sdm updates - they are on both my Note 7's, but then I haven't ever taken an OTA or any update as I disabled all of that first thing I got the phones (one was my OG N7, the other the replacement N7). So I can't help you if you have already taken an update, but those system SDMs should be there unless they removed them in an update somehow, which I doubt.
Click to expand...
Click to collapse
Ya, after I received the replacement on 16/9/16 (Singapore), I received an OTA update within the next couple of days that give the green battery.
That is the only update I received.
If it helps, my version is 6.0.1,
Baseband: N960FXXU2BPI5
Build number: MMB29K.N930FXXU2BPI9
So strange...
Does that mean the only choice I have is to root the phone?
(I haven't rooted before)
What is the best "stock" rooted package now?
I'm fine with the default Samsung apps generally, and does not need to have much default functions disabled.
flanky79 said:
Ya, after I received the replacement on 16/9/16 (Singapore), I received an OTA update within the next couple of days that give the green battery.
That is the only update I received.
If it helps, my version is 6.0.1,
Baseband: N960FXXU2BPI5
Build number: MMB29K.N930FXXU2BPI9
So strange...
Does that mean the only choice I have is to root the phone?
(I haven't rooted before)
What is the best "stock" rooted package now?
I'm fine with the default Samsung apps generally, and does not need to have much default functions disabled.
Click to expand...
Click to collapse
This is the first Android phone I have not rooted. Ever. So honestly, I cannot guide you on the root process, as I never did it on either of my Note 7's. I was eventually going to root, but then the recalls hit and I figured there was no point since I will be giving it up soon. But if you took the green battery update, my understanding is that you cannot root and cannot go back to the previous firmware. I do not know if the update you took got rid of the two system update SDM's, someone else will have to help you with that. I would bet that you can still prevent further OTA's with package disabler pro - however, I do not know that for sure. Hopefully others will see this thread and these posts and chime in with info that clears this up for you.
I rooted my replacement note 7 (with green battery update) a few days ago with no problem in anticipation of a crippling update pushed by Samsung: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047. But by doing so you trigger knox and lose access to secure folder and shealth. I solved the shealth problem by disabling encryption on my device with Hydra Kernel http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433 while keeping stock ROM. I am considering changing to HydraRom http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 just in case.
Hope this helped!
Considering the fact that the phone automatically runs an update at its first boot is there a way to easily shield the device from the mobile network (so that it won't update)?
Cr4z33 said:
Considering the fact that the phone automatically runs an update at its first boot is there a way to easily shield the device from the mobile network (so that it won't update)?
Click to expand...
Click to collapse
Not sure... but you could try removing the sim card
LightningJay said:
Not sure... but you could try removing the sim card
Click to expand...
Click to collapse
OK then it needs a mobile data subscription?
I thought OTAs would be running 'for free' if they are from the same carrier you are connected to?
Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware
LightningJay said:
I rooted my replacement note 7 (with green battery update) a few days ago with no problem in anticipation of a crippling update pushed by Samsung: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047. But by doing so you trigger knox and lose access to secure folder and shealth. I solved the shealth problem by disabling encryption on my device with Hydra Kernel http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433 while keeping stock ROM. I am considering changing to HydraRom http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 just in case.
Hope this helped!
Click to expand...
Click to collapse
What is your replacement baseband Version that you rooted? By any chance was it PI4?
shellie03 said:
What is your replacement baseband Version that you rooted? By any chance was it PI4?
Click to expand...
Click to collapse
My baseband version is PI5
Nice! Can you paste a link of the root method you did, please?
Sent from my SM-N930T using XDA Premium HD app
shellie03 said:
Nice! Can you paste a link of the root method you did, please?
Sent from my SM-N930T using XDA Premium HD app
Click to expand...
Click to collapse
I followed this method http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047
Cr4z33 said:
OK then it needs a mobile data subscription?
I thought OTAs would be running 'for free' if they are from the same carrier you are connected to?
Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware
Click to expand...
Click to collapse
My replacement N7 DL'd the update first thing. I did remove the sim and also shut off WIFI, but it had already DL'd the update. But I did not let it install the update. I rebooted and skipped activating the phone. I didn't do any of the first boot setup stuff - skipped all of that, then went to the play store, logged in with my gmail and first thing I installed as package disabler pro. I immediately disabled all the System updates (4 packages). After that I quit getting the notice to install the already DL'd update. Once you disable the System update SDM's, you can't even get into the phone update OTA selection in settings, it kicks you right out. So even though it had DL'd the update, I was able to prevent it from installing.
I do think the phone is trying to look for an update constantly now though. When I look at my GSM battery monitor, system updates is right near the top of what android system is using all the time. I still have excellent battery life, but I think disabling OTA system updates will make the phone constantly try to look for updates that it simply can't run because the SDM's are disabled. I can live with that as gimping the phone with a crappy OTA that limits the battery or might add other possible things I didn't want was the main goal. Phone runs great and battery life is great. That's all I need.
Related
So I'm rooted, running the Rogers kernel and the AT&T rom. I've removed the bloatware myself. Today I was notified of an AT&T update. My phone will download it, but it fails to install.
Anybody else experiencing this?
Sent from my SAMSUNG-SGH-I927 using XDA App
Probably failing a check sum. I'm avoiding updates in case they update something that prevents me from rooting.
I am rooted as well, and don't want the update.
Is there a way to disable the update checking?
I am getting this prompt also, and I wish to disable it (until I know what the update will do)
EDIT: For now I just leave my WiFi disabled (as it will only update over WiFi)
I still want to disable the checking though
i just got the update and it now says android 2.3.6
boricuaboy2005pr said:
i just got the update and it now says android 2.3.6
Click to expand...
Click to collapse
Are you rooted?
im rooted too, and im just avoiding the update at the moment
Rockwig said:
So I'm rooted, running the Rogers kernel and the AT&T rom. I've removed the bloatware myself. Today I was notified of an AT&T update. My phone will download it, but it fails to install.
Anybody else experiencing this?
Click to expand...
Click to collapse
I know that before updates install they check can check your phone and if packages have been removed, like you did, it can block the update. You may have to restore the packages that you removed before it will install.
This is the first phone I have rooted. I would like to know what the update changes, specifically if it fixes the Android OS high battery usage. Also if the update causes you to lose root or can be rooted after.
Ed
Sent from my SAMSUNG-SGH-I927 using XDA App
Got the update, and it is stuck at 74%. Has been for about 20 minutes. I'm not rooted. Think I should wait or pull the batt?
I've got the update downloaded and I'm rooted. Haven't installed the update yet, because I'm wondering if this will unroot my phone and bring back our friends from Carrier IQ…
Looking at the 2.3.6 changelog for a Galaxy S2 their update actually removed CarrierIQ
Sent from my SAMSUNG-SGH-I927 using XDA App
Same here. Rooted with Rogers kernel, AT&T ROM. Still failed the update even with the default launcher, USB Debugging set to off, and default packages (bloatware) intact. Is there a method to "unrooting" and restoring the default unrooted kernel/ROM? Would someone have had to backed up or dumped their ROM first somehow? (ODIN?)
Rockwig said:
Are you rooted?
Click to expand...
Click to collapse
No I'm not rooted,
Same thing. Rooted, was able to download update but will not install.
Update: Rooted, downloaded update, can't install.
The_Bizzel said:
Update: Rooted, downloaded update, can't install.
Click to expand...
Click to collapse
Same here. Boots into software update mode. Fails. Restarts.
Girlfriends phone tried to update, I turned off Wifi, then went to Running Services, stopped "Device Management" from running, installed Autostarts, disable Device Management from starting, turned on Wifi, hasn't seemed to come back as of yet.
Rooted AT&T rom FYI
geek_riot said:
Got the update, and it is stuck at 74%. Has been for about 20 minutes. I'm not rooted. Think I should wait or pull the batt?
Click to expand...
Click to collapse
Exact same problem on my wife's phone...she got the update today....she is NOT rooted, and also got stuck at 74% during the update. Not sure whether to pull the battery or just wait longer?
Well, since nobody has been answering my questions about this update I figured no one knows so I went ahead and installed it. I'll take my turn at Guinea pig.
I rooted the phone previously with the guide here: http://www.theandroidsoul.com/root-captivate-glide-rogers-and-att/ , not the one on XDA. I have also removed the tetheringmanager package.
The update installed fine and I still have root. Version says 2.3.6. Don't know what it did.
Lookout labs Carrier IQ detector says I do not have CIQ
I installed this update it
Did work, I still have root it also did remove carrier IQ as mentioned, it did not hang for me. I checked to see if carrier IQ was removed with titanium backup, Android is now 2.3.6, and kernel is now 2.6.36.3 not sure what it was
Before base band is now i927uckl1 not sure if that changed either.
Hope this was of help
Sent from my SAMSUNG-SGH-I927 using XDA Premium App
To the Community:
I just today received a note from T-Mobile Update Service that there's an update available. Of course being rooted it's not available to me OTA.
I plugged in my phone to Kies and the update that's available is from
Current firmware version: PDA:LK8 / PHONE:LK8 / CSC:LK8 (TMB)
to
Latest firmware version: PDA:LL4 / PHONE:LL4 / CSC:LL4 (TMB)
When I clicked on UPGRADE FIRMWARE I got a caution that read, "Devices that have been rooted or modified with customized software may experience a failure during the upgrade process."
So I have a couple of questions:
1. is this upgrade worth it?
2. should I unroot / Triangle Away / etc. and go through that rigamarole or should I risk proceeding with Kies? (As long as I don't brick my phone I have no problem recovering / restoring / etc.)
4. if I don't do anything, how can I get rid of the reminder-to-update icon in the notification bar?
Thanks in advance.
actually its not worth upgrading so consider carefully before you want to do so
Latest OTA update patches the exynous exploit. I would say yes it is worth updating.
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
Latest OTA update patches the exynous exploit. I would say yes it is worth updating.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yeah I think I agree. I thought about the upgrade, then let it go ahead. That being said, have you seen what Verizon have been up to? Really screwing with rooted users IMHO. That's why I am not too quick to update, just in case it can be a negative upgrade.
If you are already rooted and are using SuperSu, then there is a setting called "survivor mode" which will attempt to retain root even after an update. I checked this box, updated and still have root. Yet another option is ti use an app from the android market called OTA Rootkeeper which essentially does the same thing.
I don't think the update is worth it. ExynosAbuse also fixes the security flaw. So I have root and a secure phone. Also I don't care much for multi window. I will however updated whenever LTE is enabled. Well, I might wait till LTE is rolled into Cyanogen first then upgrade to that.
Supermighty said:
I don't think the update is worth it. ExynosAbuse also fixes the security flaw. So I have root and a secure phone. Also I don't care much for multi window. I will however updated whenever LTE is enabled. Well, I might wait till LTE is rolled into Cyanogen first then upgrade to that.
Click to expand...
Click to collapse
But doesn't the ExynosAbuse mess up the camera when it is disabled in the app? And if you don't disable it then you only have root without the protection. I was in this situation and just did the update with OTA rootkeeper. I maintained root and my device status is still normal. See this thread http://forum.xda-developers.com/showthread.php?t=2111188
GMAN1722 said:
But doesn't the ExynosAbuse mess up the camera when it is disabled in the app? And if you don't disable it then you only have root without the protection. I was in this situation and just did the update with OTA rootkeeper. I maintained root and my device status is still normal. See this thread http://forum.xda-developers.com/showthread.php?t=2111188
Click to expand...
Click to collapse
messing up the camera as far as I know is only on the Galaxy SIII. the note II's camera has no problems with the fix- there's no reason at all not to use it.
theoilman said:
messing up the camera as far as I know is only on the Galaxy SIII. the note II's camera has no problems with the fix- there's no reason at all not to use it.
Click to expand...
Click to collapse
From reading this thread http://forum.xda-developers.com/showthread.php?t=2052656 there were a few reports of the camera not working correctly when the exploit was disabled
Supermighty said:
I don't think the update is worth it. ExynosAbuse also fixes the security flaw.
Click to expand...
Click to collapse
Chainfire did a really good job providing a temporary solution to take care of this exploit via exynos abuse application but this vulnerability was within the kernel and this had to be fixed via kernel update. The new update patches this vulnerability at kernel level making sure no other functions are affected by it.
Sent from my SGH-T889 using xda app-developers app
[Qwaswas windingwasUOTE=whatllitbenext;37061997]To the Community:
I just today received a note from T-Mobile Update Service that there's an update available. Of course being rooted it's not available to me OTA.
I plugged in my phone to Kies and the update that's available is from
Current firmware version: PDA:LK8 / PHONE:LK8 / CSC:LK8 (TMB)
to
Latest firmware version: PDA:LL4 / PHONE:LL4 / CSC:LL4 (TMB)
When I clicked on UPGRADE FIRMWARE I got a caution that read, "Devices that have been rooted or modified with customized software may experience a failure during the upgrade process."
So I have a couple of questions:
1. is this upgrade worth it?
2. should I unroot / Triangle Away / etc. and go through that rigamarole or should I risk proceeding with Kies? (As long as I don't brick my phone I have no problem recovering / restoring / etc.)
4. if I don't do anything, how can I get rid of the reminder-to-update icon in the notification bar?
Thanks in advance.[/QUOTE]
I was wondering the same thing. I am stock/rooted. I wanted to keep root but be up to date. I found over on the q&a forum to use Voodoo OTA Root Keeper. And do the update OTA instead of using KIES. This worked like charm and made me extremely happy. Quick and easy.
ExynosAbuse messed up my camera at any rate. YMMV. The update worked fine for me. OTA Rootkeeper and restored root just fine after.
Hastily spouted for your befuddlement
There's a new OTA update available for the Galaxy S4 SGH-M919V variant from Wind Mobile, Eastlink, Videotron in Canada.
This is the update that finally brings the much awaited Apps2SD feature to our phones. It also includes the following enhancements:
- Some new icons in the settings
- Additional 'Smart Pause' button in quick settings
- Stability improvements
- Upgrades the camera firmware.
- Storage shown as 16GB now, but 6.38 GB is occupied by System memory under 'Misc'.
Firmware version: M919VVLUAMG1
So its official. TMo is the last carrier on Earth to get this update.
stevessvt said:
So its official. TMo is the last carrier on Earth to get this update.
Click to expand...
Click to collapse
Unfortunately, it appears to be the case as of now. I really can't imagine it being that far off now. Since, these versions are identical!
Will the update kill ROOT?
macaumen said:
Will the update kill ROOT?
Click to expand...
Click to collapse
The OTA will fail to update if you're rooted.
I had to Odin back to stock and then apply the OTA update.
So yes, the update will break root.
I haven't tried to root it since, so I can't report any progress there.
Sent from my SGH-M919V using Tapatalk 4 Beta
dj_aj said:
The OTA will fail to update if you're rooted.
I had to Odin back to stock and then apply the OTA update.
So yes, the update will break root.
I haven't tried to root it since, so I can't report any progress there.
Sent from my SGH-M919V using Tapatalk 4 Beta
Click to expand...
Click to collapse
It failed because it said your device is modified and prevent you from updating or it failed in the middle of updating?
tmobile needs to speed up this apps to sd update.....
I love how they are trying to hide the space the system uses under miscellaneous. This might trick people into not complaining about having more available disk space. I've heard good things about this update... Just want it already.
Still lovin' Tmo more than Sprint!!! 15-26mb beats 100k all day long. And I enjoy being able turn the camera sound off without rooting.
Sent from my SGH-M919 using xda premium
man, i got excited for a minute when i read new firmware update.
T-Mobile is usually quick to send out updates, I wonder why it's taking them long to release this one? The S3 got the JB update pretty quick if I'm not mistaken.
Burner2K0 said:
T-Mobile is usually quick to send out updates, I wonder why it's taking them long to release this one? The S3 got the JB update pretty quick if I'm not mistaken.
Click to expand...
Click to collapse
you can blame me for the update not being released and it wont be released for months, according to my sources. I talked to t mobile about all the bugs they have, so they said fine, we will do everything never to give bugs again, hence a long update period...It was probably my phone calls that lead to this wait
Luthien1 said:
you can blame me for the update not being released and it wont be released for months, according to my sources. I talked to t mobile about all the bugs they have, so they said fine, we will do everything never to give bugs again, hence a long update period...It was probably my phone calls that lead to this wait
Click to expand...
Click to collapse
You son of a ..... ;__; :crying:
I realize it's always an agonizing wait to get your hands on the newest firmware. However, there's a bright side to it. You all are still able to root and tinker with your devices.
I haven't been able to root the newest firmware using motochopper and am hesitant to try CF-Autoroot because in the case it does trip the flash counter and I loose root, I won't be able to reset it.
So, by the time tmobile sends out the update, there hopefully is a way to root.
dj_aj said:
I realize it's always an agonizing wait to get your hands on the newest firmware. However, there's a bright side to it. You all are still able to root and tinker with your devices.
I haven't been able to root the newest firmware using motochopper and am hesitant to try CF-Autoroot because in the case it does trip the flash counter and I loose root, I won't be able to reset it.
So, by the time tmobile sends out the update, there hopefully is a way to root.
Click to expand...
Click to collapse
Next time if your already rooted you can grab the app voodoo OTA Rootkeeper, which should be able to protect and reapply root after an update.
stevessvt said:
Next time if your already rooted you can grab the app voodoo OTA Rootkeeper, which should be able to protect and reapply root after an update.
Click to expand...
Click to collapse
Thanks for that tip. However, I doubt it would've worked because since I was rooted, the update failed to complete installing around 25%. So, I had to odin back to stock and then apply the OTA. Probably something to do with a locked bootloader.
Under About Phone/Status, where you 'Official'?
stevessvt said:
Under About Phone/Status, where you 'Official'?
Click to expand...
Click to collapse
Yeah, the phone status was 'Official'. You'd have to be in order to get OTA updates/notifications.
Initially upon rooting, the status changed to 'Custom', But I followed the guide below to revert it to 'Official' while retaining root.
http://forum.xda-developers.com/showthread.php?t=2296014
Nothing against Canada but can't believe they got an update before the U.S. model.
Sent from my SGH-M919 using Tapatalk 2
Can someone make a flashable rom with these update fir T-Mobile?
Sent from my SGH-M919 using Tapatalk 4 Beta
epsix said:
Can someone make a flashable rom with these update fir T-Mobile?
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
you already can get this update, but you will loose wifi calling and other tmobile features
Model SM-N900T
Model name GALAXY Note 3
Country USA (T-Mobile)
Version Android 5.0
Changelist 6005498
Build date Sat, 05 Dec 2015 10:46:19 +0000
Product code TMB
PDA N900TUVUFOL1
CSC N900TTMBFOL1
After downloading this update by OTA, I noticed no significant changes.
LTE-X said:
Model SM-N900T
Model name GALAXY Note 3
Country USA (T-Mobile)
Version Android 5.0
Changelist 6005498
Build date Sat, 05 Dec 2015 10:46:19 +0000
Product code TMB
PDA N900TUVUFOL1
CSC N900TTMBFOL1
After downloading this update by OTA, I noticed no significant changes.
Click to expand...
Click to collapse
Looks like it is related to this: https://support.t-mobile.com/docs/DOC-9050
New Features
N/A
Improvements
E911 update
Android text message security updates (Stagefright)
Dizmatic said:
Looks like it is related to this: https://support.t-mobile.com/docs/DOC-9050
New Features
N/A
Improvements
E911 update
Android text message security updates (Stagefright)
Click to expand...
Click to collapse
You beat me to it! Nice to see security fixes coming even if versions are left behind.
Does it break the root?
abaysal said:
Does it break the root?
Click to expand...
Click to collapse
I'm not sure what you mean. To get the OTA you can't be rooted in the first place. It's only a security fix, so if you have a 100% stock phone, you can root like the last version since it doesn't change anything in regards to root.
bobbyphoenix said:
I'm not sure what you mean. To get the OTA you can't be rooted in the first place. It's only a security fix, so if you have a 100% stock phone, you can root like the last version since it doesn't change anything in regards to root.
Click to expand...
Click to collapse
I use Kies or Odin for updates not OTA.
My phone is rooted with Knox 0 x 0 and is working fine.
I would not touch to anything if I will have to root again after this update.
Sometimes small updates do not change the root status.
Just wanted to know if this one will take the root away.
Got you. I've never tried updating while rooted, so I don't know what will happen. Sorry.
Sent from my SM-N900T
I'm glad they threw us a bone, but it took them 5 months to fix stagefright in an update that basically only fixed that? Surely they could have done it sooner, or did a proper 5.1 update in that timeframe...
magnafides said:
I'm glad they threw us a bone, but it took them 5 months to fix stagefright in an update that basically only fixed that? Surely they could have done it sooner, or did a proper 5.1 update in that timeframe...
Click to expand...
Click to collapse
From what I read they are working on 5.1.1 for the Note 3 (I know 6.0 is out). It takes a long time (yes months) to make sure everything is compatible with TouchWiz. Personally I don't need it as 5.0 works flawlessly for me. I'm not one to need the latest OS. If my phone does what I need/want I'm happy. The only thing I worry about is security, and now that they fixed it, I'm really happy.
Sent from my SM-N900T
bobbyphoenix said:
From what I read they are working on 5.1.1 for the Note 3 (I know 6.0 is out).
Click to expand...
Click to collapse
Where did you read that? There used to be a 5.1.1 update listed on the updates page but it was pulled months ago. T-Mobile would not even confirm whether or not anything at all is/was being worked on, or if the phone was abandoned. I highly doubt we ever get anything past 5.0 at this point.
I do agree on your other point, the Note 3 still holds up extremely well against current gen phones. I bought and returned a 6P because it just wasn't a $500 upgrade and the battery life was worse than my 2 year old N3 (original battery).
magnafides said:
Where did you read that? There used to be a 5.1.1 update listed on the updates page but it was pulled months ago. T-Mobile would not even confirm whether or not anything at all is/was being worked on, or if the phone was abandoned. I highly doubt we ever get anything past 5.0 at this point.
I do agree on your other point, the Note 3 still holds up extremely well against current gen phones. I bought and returned a 6P because it just wasn't a $500 upgrade and the battery life was worse than my 2 year old N3 (original battery).
Click to expand...
Click to collapse
My bad. It was the Note 3 Neo, not ours. Yes I agree this phone is still awesome. I have an Anker 6400 battery, and it lasts two days easy. With all the features the Note 5 removed I'll be sticking with the Note 3 for a while, or at least until it breaks, or the next Note adds back the SD, removable battery, and IR. Those are the three things I love the most. Very power user friendly those are.
bobbyphoenix said:
Got you. I've never tried updating while rooted, so I don't know what will happen. Sorry.
Sent from my SM-N900T
Click to expand...
Click to collapse
Thanks a lot in any case.
As is I will not touch to anything.
The upside does seem to worth it.
abaysal said:
Does it break the root?
Click to expand...
Click to collapse
Yes it breaks the root but you csm root again same way you did with previous version.
senozlu1 said:
Yes it breaks the root but you csm root again same way you did with previous version.
Click to expand...
Click to collapse
Is there a way to root it without triggering knox 0x0 after update?
I think he cares about keeping root after update without triggering knox count.
abaysal said:
I use Kies or Odin for updates not OTA.
My phone is rooted with Knox 0 x 0 and is working fine.
I would not touch to anything if I will have to root again after this update.
Sometimes small updates do not change the root status.
Just wanted to know if this one will take the root away.
Click to expand...
Click to collapse
Hey, just got this phone and T-Mobile will not allow for an OTA update. When I try Kies it doesn't like the S/N (I used IMEI). Is Odin the only way? If so, is there a completely (I don't even require root) STOCK version of most recent rom or just the one prior to this? I'm currently only 4.4
kingkea said:
Hey, just got this phone and T-Mobile will not allow for an OTA update. When I try Kies it doesn't like the S/N (I used IMEI). Is Odin the only way? If so, is there a completely (I don't even require root) STOCK version of most recent rom or just the one prior to this? I'm currently only 4.4
Click to expand...
Click to collapse
Just download the current ROM (FOL1) from here http://www.sammobile.com/firmwares/database/SM-N900T/, and use ODIN to install. When you click the Kies download button you get instructions, and a link to ODIN http://dl.sammobile.com/Odin3_v3.10.7.zip. Just follow the instructions, and you'll have it updated in no time.
bobbyphoenix said:
Just download the current ROM (FOL1) from here http://www.sammobile.com/firmwares/database/SM-N900T/, and use ODIN to install. When you click the Kies download button you get instructions, and a link to ODIN http://dl.sammobile.com/Odin3_v3.10.7.zip. Just follow the instructions, and you'll have it updated in no time.
Click to expand...
Click to collapse
Thank You!
Anyone tried to update with flashfire to keep root and knox 0x0?
i agree on the point they could have done a 5.1.1 update at least.
Dizmatic said:
Looks like it is related to this: https://support.t-mobile.com/docs/DOC-9050
New Features
N/A
Improvements
E911 update
Android text message security updates (Stagefright)
Click to expand...
Click to collapse
450 MB, and no significant differences?
I just got an S9 and have not been able to get it to apply all of the available updates. When I check for updates, it says that I have the latest one already. I tried the Smart Switch software and that says I am also up to date. I cleared the cache partition and then set the date to one day ahead and checked for updates. It took a few minutes checking but then it finished and said I was up to date.
My previous phone was an S8 and that phone had issues updating too. I had to go to ubreakifix to have them update the phone when Android 8 became available. After that update, my S8 never got an OTA again.
I fear that this S9 is having the same problem. I even activated the new S9 with a new sim card. I also verified that AT&T sees that I have an S9.
Anyone know what is going on? Anything else I can do to get it to update? I am currently on the previous version with baseband G960USQS3ARG8.
dominican2589 said:
I just got an S9 and have not been able to get it to apply all of the available updates. When I check for updates, it says that I have the latest one already. I tried the Smart Switch software and that says I am also up to date. I cleared the cache partition and then set the date to one day ahead and checked for updates. It took a few minutes checking but then it finished and said I was up to date.
My previous phone was an S8 and that phone had issues updating too. I had to go to ubreakifix to have them update the phone when Android 8 became available. After that update, my S8 never got an OTA again.
I fear that this S9 is having the same problem. I even activated the new S9 with a new sim card. I also verified that AT&T sees that I have an S9.
Anyone know what is going on? Anything else I can do to get it to update? I am currently on the previous version with baseband G960USQS3ARG8.
Click to expand...
Click to collapse
If you just got it, give it a week or so.
There was an S9+ that was added on another line within my account at the same time and it got all the updates right away. Hopefully time will fix mine but right now I doubt it.
Sent from my SM-G960U using Tapatalk
It's been over a week and still no update. Anyone have ideas as to what is going on?
Sent from my SM-G960U using Tapatalk
dominican2589 said:
It's been over a week and still no update. Anyone have ideas as to what is going on?
Sent from my SM-G960U using Tapatalk
Click to expand...
Click to collapse
Did you ever flash this to U1 Firmware? I had a similar issue when i decided to go back to U firmware. Ended up having to to revert back to an old version of U and then proceed with side loading updates from firmware science until the BR firmware (side note, the firmware i found on here to revert back to stock U did not have a direct upgrade path on Firmware science) then AT&T started updating as normal.
I have not flashed anything. This is new out of the box.
Sent from my SM-G960U using Tapatalk
I would take it back to AT&T.
My previous phone did the same thing which is odd. I can't see why two consecutive new phones would not update for me. Is there a way I can download the update from AT&T and sideload it without having to reinstall everything?
Sent from my SM-G960U using Tapatalk
Go to samsung.firmware.science and check.
911jason said:
Go to samsung.firmware.science and check.
Click to expand...
Click to collapse
I applied the next update from there and while it updated, it wiped my phone. now to spend a few hours again resetting everything up. i thought this wasn't supposed to wipe my phone?
Don't bother setting up your phone until you're all caught up with updates. I learned that the hard way. Just skip all the setup stuff after connecting to WiFi, then check for updates. Go back to the firmware science site if there are none available. I'm on 3BRJ6 with a November 1st security patch. This one was an OTA update after manually installing 3 or 4 from the firmware science site.
P.S. Under settings-about phone-software information do you show ATT/ATT/ATT at the bottom of the Service Provider SW ver.?
911jason said:
Don't bother setting up your phone until you're all caught up with updates. I learned that the hard way. Just skip all the setup stuff after connecting to WiFi, then check for updates. Go back to the firmware science site if there are none available. I'm on 3BRJ6 with a November 1st security patch. This one was an OTA update after manually installing 3 or 4 from the firmware science site.
P.S. Under settings-about phone-software information do you show ATT/ATT/ATT at the bottom of the Service Provider SW ver.?
Click to expand...
Click to collapse
The problem with it resetting my phone is that if still continue to not receive ota updates directly, I'll never update again since I wouldn't want to reset again. As for the fw, I do see Att/att/att.
I updated up to the October security patch to see if it would offer the Nov security patch and my phone still won't offer ota updates.
Sent from my SM-G960U using Tapatalk
Does your phone show the blue AT&T logo during boot up? Does it have all the AT&T bloatware?
Yup, it's an Att branded phone. I bought from Best buy. Came in Att box, has all the bloatware too.
Sent from my SM-G960U using Tapatalk
Then I go back to my initial recommendation that you return it. I would also consider asking AT&T if there is some way to wipe your account data clean before activating a new phone and make sure you get a new sim card.