Related
Check for OTA Update in your settings.
Is it Lollipop?
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Update the Software for the Samsung Galaxy Note II (i317)
Update summary
AT&T released a new software update for the Samsung Galaxy Note 2 (SGH-i317) via Firmware Over the Air (FOTA) over Wi-Fi on November 11, 2014.
Software Update Includes
Android OS Enhancements
User-Initiated Software Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
Tap Software update.
Tap Check for updates, and then follow the subsequent prompts.
Verifying the Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
The following information displays:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Kernel version: 3.0.31-1728680 [email protected] #1 Wed Oct 1 22:38:36 KST 2014
Build number: KOT49H.I317UCUCNJ1
File size: 93.2MB
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
keplenk said:
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
Click to expand...
Click to collapse
I wouldn't. I just posted this in the other thread about the OTA:
a042349 said:
Same thing happened to me. Rooted but otherwise stock GN2. Got the update, rebooted and it got stuck at the boot logo. I tried everything. Flashed CWM, then tried a couple different ROM's. Then went to TWRP recovery, and tried the Team Elektron ROM, that got a little farther, boot logo with sound, but it still hung. Tried a modem update, and even the bootloader - nothing worked.
Luckily I had just bought mine ($300 on Amazon right now) so I just sent it back as defective and ordered a new one. Gonna be real careful of the ATT update and maybe even skip it and go right to a custom ROM.
Click to expand...
Click to collapse
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
kabinoff said:
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
Click to expand...
Click to collapse
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
melvinaury said:
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
actually flashed CF with Odin and it worked.
kabinoff said:
actually flashed CF with Odin and it worked.
Click to expand...
Click to collapse
Did it really work?
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
toshik1 said:
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
Click to expand...
Click to collapse
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Zen Arcade said:
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Click to expand...
Click to collapse
Yes the SIM card has normal active service on it.
Other reasons OTA won't work:
1 - Location (if you are not in an area where OTA updates are provided, then...
)
2 - AT&T Update apk disabled on phones (seems unlikely that this would be the case on two phones but a factory reset might clear this as it is set on the data side)
3 - Identity issues (could be any number of things related to IMEI, efs partition scrambling, etc - just spitballing)
As far as suggestions go, I'd say try a factory reset and clear cache from recovery. If that doesn't work, maybe go back to AT&T and see if they can figure it out - the phones are stock and it's their OTA process. If that doesn't work, you can pursue the path I suggested previously - same firmware update, minus the script that pushes stock recovery every time you boot. You will trip the knox flag though...only an issue for warranty repair really. Others here have intentially or unitentionally received the NJ1 OTA with the knox flag tripped on their phones.
DroidTuner said:
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Click to expand...
Click to collapse
Which process did you freeze?
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
toshik1 said:
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
Click to expand...
Click to collapse
Glad to hear it. Wait a day (or disable network time and the set the time on the phone forward at least a day) and try again - you should get NJ1. (If that's what you want). Approx. 93MB security and minor enhancement update.
Just to follow-up - it took the second update with T-Mobile SIM card even without waiting for 24 hours.
I guess in order to take the updates the phone's IMEI MUST re-register on AT&T network with the valid AT&T SIM card first.
It's now I317UCUCNJ1
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 another monthly update for my AT&T Note 5 labeled N920AUCS4CPL1 with the December 1, 2016 security patch included. I can't find anything else on this update but again, it looks like another security update - - NOT Android 7.0+
@mattern1974, did you take a screenshot or something? What does the about device screen say?
itskapil said:
@mattern1974, did you take a screenshot or something? What does the about device screen say?
Click to expand...
Click to collapse
Here you go!
Second screen shot
mattern1974 said:
Second screen shot
Click to expand...
Click to collapse
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
Thanks man!
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
How did you change your background
MusicHelps said:
How did you change your background
Click to expand...
Click to collapse
Themes in the settings.
Edit: I also use Nova Launcher since I like the speed and customization over the stock Touchjizz.
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Wow---this update is KILLING my battery. Google play services is running in the background like crazy. I've lost 10% in 2 HRS with little use where as before the update I would have lost 10% by 2 PM---UGH! Anyone else having this problem?
I updated to PK1 the day I got my phone (last week Monday).
The battery life for me has been superb (since I flashed through ODIN and started setting it up from scratch).
I want to get PL1 (for peace of mind), but I don't have an AT&T SIM card, so I'm waiting for a complete file that I can flash through ODIN.
I don't want anymore updates because I'm almost out of equipment contract now and I want to hack my Note 5. I wasn't aggressive about this until recently but somehow I had auto update on. So my phone started the download but I rebooted it and stuck it in the microwave.. (panic style) Then I tried to downgrade to 5.11 using the PH4 and the PH2 firmwares in succession but PH4 soft bricked me. Then I tried flashing N920AUCS4CPK1. and I got success. Wiped it all back to November 2016 security patch. (I dunno if this works after it installs, I have a sinking feeling it will not work.. There is no firmware available with Dec 2016 security patch that I'm aware so no way to recover if I'm correct in assuming the bootloader is blocking me from downgrades)
Edit: I want stress that fact that my phone never said Dec 2016 security patch, during all this it was still Nov 2016 patch
droidvoider said:
if I'm correct in assuming the bootloader is blocking me from downgrades)
Click to expand...
Click to collapse
With AT&T bootloaders, I thought that was always the case.
You WILL take the update when Nougat arrives. I'm eager to know when that will be. I have no intention of rooting my device to trip Knox.
batuhur said:
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Click to expand...
Click to collapse
Here S4CPK1 - to- S4CPL1 -
norbarb said:
Here S4CPK1 - to- S4CPL1 -
Click to expand...
Click to collapse
Thank you very much
Updating now
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
norbarb said:
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
Click to expand...
Click to collapse
Why don't you try it and let us know?
mattern1974 said:
Why don't you try it and let us know?
Click to expand...
Click to collapse
I don't have Note 5
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Anonymously_Unknown said:
My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
With a locked bootloader, it will probably stay unrooted. I don't know of a root for it, would be nice if there was one. I think 5.01 bootlaoder got unlocked... But I keep looking...
Anonymously_Unknown said:
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
Check the file to norbarb post, and send to your phone via ADB, you can search in google how can you send ota by adb, its easy. Send OTA via adb donesnt affect knox, its install manually OTA.
This is the new updates thread. Thanks to @norbarb for the original thread. Norbarb no longer has the Note 4 and has moved on...
Note: All updates here will factory reset your phone. Back up your data!
Let your phone cool between updates, extended overheating will kill your device.
Official Aug security update Android 6.0.1 Marshmallow
SS-N910AUCS2EQG1-to-S2EQH1-UP.zip
Don't be ungrateful. If you download the file, hit "Thanks" below.
The details
Release date: Aug 28, 2017
Android version: 6.0.1
Security patch level (SPL): Aug 1, 2017
Baseband version: N910AUCS2EQH1
Kernel version: 3.10.408932341
Build number: MMB29M.N910AUCS2EQH1
Build fingerprint: 6.0.1/MMB29M/N910AUCS2EQH1
Previous version required: N910AUCS2EQG1
File size: 27MB
Image
Official security updates
S2EQG1-to-S2EQH1
S2EQF1-to-S2EQG1
S2EQE1-to-S2EQF1
S2EQD1 to S2EQE1
S2EPK5 to S2EQD1
S2EPK4 to S2EPK5
S2EPK3 to S2EPK4
S2EPK2 to S2EPK3
U2EPK1 to S2EPK2
S2EPH7 to U2EPK1
U2EPH5 to U2EPK1
Marshmellow Official At&t updates :
EPH5 to EPH7
DOI9-to-EPH5
DOI7 to EPH5
DOI6-to-EPH5
ODIN FILES to skip individual updates, if you are behind...
ODIN FILE N910AUCS2EQF1
ODIN
Installation :
Download files you need form links above.
Backup your phone data, all data will be erase.
Put all desire files on SD-CARD
Restart phone in recovery mode '"Volume UP + Home button+ Power"
Choose from menu load update from sd-card
Choose desire file and update.
Follow direction for all files you need to update to.
You don't need to reboot all the way true for every update. When phone restart just hold Volume UP plus Home button. This will get you back to recovery.
ODIN Directions: (Warning, read up on ODIN before doing this... You can seriously mess up your phone if you do things wrong.)
1: Install Samsung drivers on your computer.
2: Run Odin tool as Administrator on your PC.
3: Reboot your device into download mode. To do it, hold down the Volume down+Home+Power simultaneously for about 5 sec until Android warning sign appears on the screen. Hit Volume up to continue.
4: While in odin mode, connect your device to PC via the USB port. Make sure that your device is connected to Odin by looking at the ID:COM section.
5: Click on each of the BL, AP, CP and CSC buttons, and make sure the appropriate ODIN file is in each of those categories.
6: Do NOT change any of the check marks. Make sure Repartition is NOT checked.
7: Click START. When this process has finished, you'll be notified in Odin (succeeded 1 / failed 0) and your phone's screen will go blank.
8: Unplug your phone and reboot. At this point your phone should boot up with the new version you just installed.
Thx a lot for the August security patch.
Quick question, it's been awhile since I flashed updates from recovery. My son is using my old Note 4 without a SIM, so these updates are my path to keeping him up to date on security. If I flash from recovery the two latest security updates (he's on June), I'll wipe his phone, right? Will ODIN for these zips avoiding wiping him, or do I just have to have him backup/restore first?
stoobie-doo said:
Quick question, it's been awhile since I flashed updates from recovery. My son is using my old Note 4 without a SIM, so these updates are my path to keeping him up to date on security. If I flash from recovery the two latest security updates (he's on June), I'll wipe his phone, right? Will ODIN for these zips avoiding wiping him, or do I just have to have him backup/restore first?
Click to expand...
Click to collapse
Odin will wipe everything, so you will need to backup first. Only way to save everything is by the incremental OTA updates
My N910A is a bit behind in updates it looks like. I've unboxed it and its on Android 5.1.1 with baseband version N910AUCU2DOI3, 3.10.40-5613584 kernel, patch level 2016-02-01.
What upgrade path should I take if I want to reach marshmallow? I'm not sure what can be skipped.
vendicarsi said:
My N910A is a bit behind in updates it looks like. I've unboxed it and its on Android 5.1.1 with baseband version N910AUCU2DOI3, 3.10.40-5613584 kernel, patch level 2016-02-01.
What upgrade path should I take if I want to reach marshmallow? I'm not sure what can be skipped.
Click to expand...
Click to collapse
Use the Odin link, and that gets you within one or two updates. Let the phone cool for an hour between updates.
If we get an update it will be an I update (we're on h now), and it will have the blueborne Bluetooth bug fix.
https://www.sammobile.com/2017/09/25/samsung-rolls-security-patches-fix-blueborne-vulnerability/
Unfortunately, I'm not seeing a S2EQI1 file on the server yet...
I hope AT&T is not leaving us with a major Bluetooth bug. Note 4 is near end of life.
Links forU2EPK1 to S2EPK2 and S2EPK2 to S2EPK3 do not work anymore
Hey guys,
I'm currently on N910AUCU2EPK1 baseband version and would like to update to newer versions.
I've already dowloaded all the most recent ones except the S2EPK2 and S2EPK3 and therefore cannot install them since I would first need to download and install the S2EPK2 and S2EPK3.
The download pages are not working anymore.
would really appreciate if you could help me on this matter.
Thanks for all your support
Utmost Thanks!
From a very old (and annoying) member still clinging to his Note 4 with removable battery (on my third battery now) I thank you so much for keeping my AT&T updated here in the United Arab Emirates....
Verizon has released the latest Note 4 security patches. Hopefully att won't be too far behind. https://www.sammobile.com/2017/09/21/galaxy-note-4-blueborne-patch-released-verizon/
I still cannot find any files on the ATT server.. Verizon's update is U2CQI2. I've tried many variants to no avail. Att is generally slower with patches. This is a good sign though, that a patch should be in the works... If/when I find it, I'll post it.
We got to be hopefull. At&T has delayed September update for most phones.
just got a update from att N910AUCS2EQE1
peterson65 said:
just got a update from att N910AUCS2EQE1
Click to expand...
Click to collapse
this was May update. when did u get that!
mmaku said:
this was May update. when did u get that!
Click to expand...
Click to collapse
just got it yesterday? wtf att is way behind in pushing updates
OK today it updated to N910AUCS2EQF1
peterson65 said:
just got it yesterday? wtf att is way behind in pushing updates
OK today it updated to N910AUCS2EQF1
Click to expand...
Click to collapse
that is still way back. the latest update is QH1
The security update is a factory reset
The security update is a factory reset?!
I thought it was only a security update - wtf
my entire data partition is wiped
i want to die
Only updates given to att users, OTA (over the air), with att active service will preserve your data. Downloading and applying the update wipes your data. We've searched for a work around, to no avail. Sorry you lost your data. Without att service, we can't do anything else
Shanghai.Knight said:
Only updates given to att users, OTA (over the air), with att active service will preserve your data. Downloading and applying the update wipes your data. We've searched for a work around, to no avail. Sorry you lost your data. Without att service, we can't do anything else
Click to expand...
Click to collapse
This really needs to be more obvious in your OP.
Recommendation:
Official Aug security update Android 6.0.1 Marshmallow
SS-N910AUCS2EQG1-to-S2EQH1-UP.zip
>> THIS FILE FACTORY RESETS YOUR PHONE <<
Don't be ungrateful. If you download the file, hit "Thanks" below.
Click to expand...
Click to collapse
"Official Aug security update" gives no indication that it's going to wipe your phone. I have had to stop using this phone immediately and I'm going to end up paying a hardware engineer to remove the internal memory in a soldering oven and build a USB adapter for it so that I can recover the data that this "security update" formatted over.
Don't call something an "update" if it's a factory reset. This is bananas.
delugeofspam said:
This really needs to be more obvious in your OP. .
Click to expand...
Click to collapse
I feel terrible that you've lost important data. You'll notice the original update thread op never mentioned this either. We've probably taken this fact for granted
I've taken your suggestion and updated the op. to highlight this.
Always, always back up your data in multiple locations.
Good luck.
Shanghai.Knight said:
I feel terrible that you've lost important data. You'll notice the original update thread op never mentioned this either. We've probably taken this fact for granted
I've taken your suggestion and updated the op. to highlight this.
Always, always back up your data in multiple locations.
Good luck.
Click to expand...
Click to collapse
I just "thanked" this post and the OP. I appreciate what you're doing here. I'll figure this out, I'm resourceful!
EDIT: it is possible, and worked just fine for me
- - - - - - - - - - - - - - - - -
Hi guys.
recently got a used s9, did all the updates (for security updates) and didnt even look, just kept updating and find myself on android P.
I've played around with it and found it less intuitive and pretty lacking in some regards. (and may possibly have some issues relating to the OS too; battery and phone)
software updates says:
Code:
current version: G960FXXXXU2CRLO / G960FOXXM2CRLO / G960FXXXU2CRLI
Security patch level: 1 January 2019
SM-G960F, Phone status: Official, baseband version G960FXXU2CRLI, Kernel version: 4.9.59-15076275, build verison: ppr1.180610.011.G960FXXU2CRLO
I'm wondering if it's possible to flash back to official Android O, while retaining untripped KNOX. (having KNOX in a usable/official status)
I've read online that it should be possible to do, but talk of using the "OEM unlocking" option has me weary.
I dont want to blindy follow a guide to find i've broken KNOX or have a brick.
some of you guys are pretty cluey. so i thought it be a good first place to ask.
cheers
Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
PoochyXXX
PoochyX said:
Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
Click to expand...
Click to collapse
Hmm, thats what I'm afraid of.
The downgrade guide i mentioned was here:
https://techbeasts.com/downgrade-ga...xy_S9S9_Plus_to_Android_Oreo_from_Android_Pie
not sure how legit it is though.
I havent read anything on XDA on the forums here, hence my new topic.
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
Ohhh
PoochyXXX
*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
AP_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship_meta.tar.md5
MD5: 4ECA2C5657506ADE7B9D3B1721B0F958
SHA1: 14063F2CF282E37C2C7D59D80FFF404C400D306D
BL_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship.tar.md5
MD5: 9529200BCE0C339B04152AC27DE34F5E
SHA1: 1821D68544490355042E7BF1589F2284FEF76324
CP_G960FXXU2BRJ1_CP10881699_CL14479316_QB19997556_REV01_user_low_ship.tar.md5
MD5: 8E07784192BCAF0454AB079ECBBD150D
SHA1: E7EFC1ED9E35C7B1F235792FAF46AFCAA945FF38
CSC_OMC_OXM_G960FOXM2BRJ3_CL14479316_QB20051937_REV01_user_low_ship.tar.md5
MD5: 17932E611CB0DF71C7B91BA84186843C
SHA1: 6BEE275DCC778124CB1EBF88EFA087538D9DCBE3
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.
tim455 said:
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.
Click to expand...
Click to collapse
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October
*Detection* said:
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October
Click to expand...
Click to collapse
Thanks for all the helpful information.
Downloading again now just to check hash comparison.
AP SWAEV: B:2 K:2 S:2 -- looks good.
I'll reply back in a few hours with my results.
Many thanks.
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
To understand that you are downloading the BRJ6 firmware ?
Thx.
tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
:good:
dinamo1975 said:
To understand that you are downloading the BRJ6 firmware ?
Thx.
Click to expand...
Click to collapse
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
*Detection* said:
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
Click to expand...
Click to collapse
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.
tim455 said:
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.
Click to expand...
Click to collapse
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin
*Detection* said:
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin
Click to expand...
Click to collapse
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)
tim455 said:
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)
Click to expand...
Click to collapse
Not really, I am running DBT firmware with XEU CSC just because the DBT firmware updated first, once XEU releases the same update I`ll flash back, and so on
tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
What was the bootloader version of the Android 8 vs the version you had on Pie? Did you downgrade the bootloader as well?
can the same method be used to go down from 10 to 9? i have snapdragon 960w