N900TUVSFPH3 is now available on sammobile.
Model SM-N900T
Model name GALAXY Note3
Country USA (T-Mobile)
Version Android 5.0
Changelist 6005498
Build date Fri, 26 Aug 2016 12:38:40 +0000
Security Patch Level 2016-09-01
Product code TMB
PDA N900TUVSFPH3
CSC N900TTMBFPH3
Click to expand...
Click to collapse
Here's the changelog from t-mobile:
August/September Security Updates
Click to expand...
Click to collapse
At least they are providing security updates.
Sent from my SM-P600 using Tapatalk
Can you please share the baseband and modem?
The question is, will we be able to revert back to FOL1 after this update is flashed?
megaforcer said:
The question is, will we be able to revert back to FOL1 after this update is flashed?
Click to expand...
Click to collapse
I believe so.
I was pleasantly surprised yesterday when I saw the update notification. Nice to still see love for our Note 3.
I wanted to flash this using FlashFire and retain Root from FOL1. I made an attempt leaving the defaults checked (Boot, Recovery, System, Cache).
It completed successfully however, it caused my phone to no longer recognize the sim card. I simply re-flashed FOL1 with FlashFire and it was fixed.
I assume I need to maybe also check the protected partitions (Modem Firmware, Firmware, TrustZone, DBI/SDI). At least the Modem Firmware anyways....
Does anyone know if this (checking all, or one of the protected paritions) will trip Knox, or maybe require me to lose data? I have no reason to trip knox, so I'd like to avoid it if possible.
Thanks
--------
Edit: Went ahead and tried all the protected partitions. Checked every available flash option, besides the obvious disabled bootloader ones. Clicked "Yes" when it asked to do the protected partitions seperate, then proceeded to leave the rest stuff default. Flash was successful, root kept, knox 0x0.
Little note for people who may up doing this... I disabled xposed modules and uninstalled it before flashing the updated firmware.
billowusu47 said:
Can you please share the baseband and modem?
Click to expand...
Click to collapse
everything says FPH3 after flashing, weather or not there are any differences beyond the build number is above my capability of descernemnt
NSA updates?
I'm seeing an update for this phone and I don't know if I should. I know that since my bootloader is unlocked I can flash if need be but I'm not sure once I update this I will lose the ability for custom ROMs that require an earlier firmware.
It shouldn't be an issue. This update is pretty much just an upstream on the September security patch
I'm new to XDA and to ROMs, so let me begin by saying hello and thank you to the regular posters. Many of my initial questions were answered by browsing and searching here.
My Nextbit Robin is still on the factory ROM: 7.1.1, security patch level April 1 2017. That's already too long to go without security updates in my opinion, hence my interest in moving to a maintained ROM that gets regular security fixes. My questions are:
Are there ROMs for Nextbit that are especially good on security updates? Or alternatively ROMs that aren't?
How are security updates usually handled by ROMs? Are they rolled into regular OTA updates? Are they separate and have to be manually applied? Something else?
Those ROMs I've looked most closely at (OmniROM and LineageOS) are at 7.1.2, just one minor release beyond the factory's 7.1.1. Does this imply that OmniROM and LineageOS's security releases haven't proceeded beyond when 7.1.2 was released quite some time ago?
I did search this forum, the sites of OmniROM and LineageOS, and the web, but if the answers are out there I didn't find them. Telling me to RTFM is fine; just point me to the FM.
Although I would not reject other things that ROMs can bring (improved performance vs. factory ROM, non-security bugfixes, new features, etc.), my chief interest is in keeping the phone up to date with all future security fixes via automatic OTA that I don't have to think about. Anything else that comes along with that would be great but would not be part of my decision making.
Feel free to go beyond my questions and point out things that I haven't mentioned but ought to know. I'm don't mind admitting that I'm new at this and there's a lot I don't yet know.
wpost said:
Are there ROMs for Nextbit that are especially good on security updates? Or alternatively ROMs that aren't?
How are security updates usually handled by ROMs? Are they rolled into regular OTA updates? Are they separate and have to be manually applied? Something else?
Those ROMs I've looked most closely at (OmniROM and LineageOS) are at 7.1.2, just one minor release beyond the factory's 7.1.1. Does this imply that OmniROM and LineageOS's security releases haven't proceeded beyond when 7.1.2 was released quite some time ago?
Click to expand...
Click to collapse
1. I recommend LineageOS. It's good on security updates. (Currently on March 5, 2018 security patch level.)
2. Yes, They are rolled into regular OTA. They usually include security updates within one or two weeks after they are released.
3. I may not have understood the third quesion correctly. 7.1.2 is the latest version of Android 7.x.x. After That It's 8.x. I don't think that affects the security updates.
OTA updates are checked automatically and you will be notified once an update available. But they won't be downloaded automatically. You have to press download button and then install it.
If you are planning to use encryption, you should use TWRP from LineageOS. I had problems with decrypting using TWRP from their official site.
And there are Oreo roms for robin. I think they also have latest security patches. I can't tell you much about them because I haven't tried all of them. However I've used AICP 13.1 and unofficial LineageOS 15.1 (OREO) releases (Read the last few pages of this thread and you can download them from here). Both are very usable. AICP is more customizable.
Thank you for the clear and complete answer. This will be my project for next weekend then.
KA5UN said:
1. I recommend LineageOS. It's good on security updates. (Currently on March 5, 2018 security patch level.)
2. Yes, They are rolled into regular OTA. They usually include security updates within one or two weeks after they are released.
3. I may not have understood the third quesion correctly. 7.1.2 is the latest version of Android 7.x.x. After That It's 8.x. I don't think that affects the security updates.
OTA updates are checked automatically and you will be notified once an update available. But they won't be downloaded automatically. You have to press download button and then install it.
If you are planning to use encryption, you should use TWRP from LineageOS. I had problems with decrypting using TWRP from their official site.
And there are Oreo roms for robin. I think they also have latest security patches. I can't tell you much about them because I haven't tried all of them. However I've used AICP 13.1 and unofficial LineageOS 15.1 (OREO) releases (Read the last few pages of this thread and you can download them from here). Both are very usable. AICP is more customizable.
Click to expand...
Click to collapse
Interesting that you brought up TWRP from Lineage OS.
I had used TWRP from TWRP site which I need to Format Data at first use which will decrypt me. So if I want to stay encrypted I should use TWRP from Lineage OS not normal TWRP?
iluvatrix said:
Interesting that you brought up TWRP from Lineage OS.
I had used TWRP from TWRP site which I need to Format Data at first use which will decrypt me. So if I want to stay encrypted I should use TWRP from Lineage OS not normal TWRP?
Click to expand...
Click to collapse
Yeah.
I had the same problem while using official version. I couldn't install OTA updates while using encryption because twrp can't decrypt data partition.
Also I think I read somewhere to remove any screen locks before encrypting (set them after). But I'm not sure if it's necessary.
KA5UN said:
Yeah.
I had the same problem while using official version. I couldn't install OTA updates while using encryption because twrp can't decrypt data partition.
Also I think I read somewhere to remove any screen locks before encrypting (set them after). But I'm not sure if it's necessary.
Click to expand...
Click to collapse
I'm confused now.
I want to be encrypted while on Lineage.
So if I rolled back to last stock ROM which is encrypted I should then flash the Lineage twrp you linked?
Thereafter on Lineage with Lineage twrp remaining encrypted I would be able to receive Lineage ota updates?
iluvatrix said:
I'm confused now.
I want to be encrypted while on Lineage.
So if I rolled back to last stock ROM which is encrypted I should then flash the Lineage twrp you linked?
Thereafter on Lineage with Lineage twrp remaining encrypted I would be able to receive Lineage ota updates?
Click to expand...
Click to collapse
TWRP can't decrypt stock encryption. If you're coming from stock you have to Format Data before installing lineage. After flashing lineage, you can encrypt the phone again. Then twrp (from lineage) can decrypt it.
If you are already on lineage and not encrypted, just flash that TWRP from lineage and encrypt the phone from settings.
If you're on lineage and encrypted, you can try flashing that TWRP. but I don't know if it'll be able to decrypt since I haven't tried to do that.
And yes, you would be able to install OTA updates.
KA5UN said:
TWRP can't decrypt stock encryption. If you're coming from stock you have to Format Data before installing lineage. After flashing lineage, you can encrypt the phone again. Then twrp (from lineage) can decrypt it.
If you are already on lineage and not encrypted, just flash that TWRP from lineage and encrypt the phone from settings.
If you're on lineage and encrypted, you can try flashing that TWRP. but I don't know if it'll be able to decrypt since I haven't tried to do that.
And yes, you would be able to install OTA updates.
Click to expand...
Click to collapse
Thanks for the detailed response. I'm concerned about encrypting under Lineage & getting bricked.
Is there a way to go from Stock encrypted > Lineage encrypted directly?
iluvatrix said:
Thanks for the detailed response. I'm concerned about encrypting under Lineage & getting bricked.
Is there a way to go from Stock encrypted > Lineage encrypted directly?
Click to expand...
Click to collapse
I don't think that's possible
KA5UN said:
I don't think that's possible
Click to expand...
Click to collapse
Yeah no prob
I'll just run unencrypted
December firmware updates are starting to roll out now with a couple for our device:
11.0.0 (RQ1A.201205.010, Dec 2020, AT&T)
11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
These updates can be found here as usual: Factory Images | Full OTA Images
I updated my device using the RQ1A.201205.010 image since my device's carrier is Cricket Wireless which is owned and operated by AT&T. This is should be an important note for anyone who has Cricket Wireless and this phone to use the AT&T specific firmware. After flashing via fastboot after removing the '-w' flag in the 'flash-all' script, I was able to re-root my device using the latest Magisk Canary build and after re-enabling all my modules including the Build Props module my device is successfully rooted and also passing all SafetyNet checks.
So far everything is running stable and nicely. I was using Proton Kernel on the device after I received it and previous to this update but for now I'm gonna let it run stock and see how it's overall performance is before possibly changing the kernel again. Just wanted to report my findings after applying this month's firmware update.
A few hiccups but installed and rooted here too. Still cant flash my vendor.img with a usb c to c cable. Theres a new fastbootd screen as well.
I used the Magisk Props config to spoof the Safetynet check and it stayed intact after the update flash.
the title says it all.
Nope...
You would need to completely wipe the phone like in the factory then install the older OS with the older version of security updates.