So I bought the A1 version a couple of days ago and thought it was considered the Retail, not the Google Fi one, so I flashed the stock rom for Retail. The phone worked perfectly fine, although seemed more bloated with software than it was originally. I found out it is actually the Fi version, so I went and flashed that stock rom.
Comparing the files, I noticed that the NON-HOS.bin (modem) files were not the same. They were the same size, but had different md5sums. Do they not support the same networks? I was under the assumption they both supported all US carriers, nothing was special from one version to the other.
The Android One NON-HLOS.bin was from
PAYTON_FI_8.1.0_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And the Retail NON-HLOS.bin was from
XT1900-1_PAYTON_RETAIL_8.1.0_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Any ideas why these were different? When I flashed Android One version, I had latest version. When I flashed stock, I had one ~80mb update.
The Android One baseband version is
M660_7042.27.01.74R PAYTON_NA_CUST
I did not check the Retail when I had that installed, wish I did.
Knuxyl said:
The Android One NON-HLOS.bin was from
PAYTON_FI_8.1.0_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And the Retail NON-HLOS.bin was from
XT1900-1_PAYTON_RETAIL_8.1.0_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Any ideas why these were different? When I flashed Android One version, I had latest version. When I flashed stock, I had one ~80mb update.
Click to expand...
Click to collapse
A1 FW contains september 2018 security patch.
Retail FW contains august 2018 security patch, ~80mb update is retail OTA with september 2018 security patch.
Comby_sk said:
A1 FW contains september 2018 security patch.
Retail FW contains august 2018 security patch, ~80mb update is retail OTA with september 2018 security patch.
Click to expand...
Click to collapse
I know the versions are different, but I don't think security patches have anything to do with the modem firmware. Security patches typically address kernel issues. I could be wrong though. Im just curious if anyone knows if there is a difference between the 2 variants of the phone's modem firmware, if there is one (assuming the security patch did not update the firmware). I would know for sure if I knew if OTA was compressed when downloaded because if not, then they definitely are different modem firmwares because the modem is 90+mb and I can get that compressed to ~45mb.
Knuxyl said:
I know the versions are different, but I don't think security patches have anything to do with the modem firmware. Security patches typically address kernel issues. I could be wrong though. Im just curious if anyone knows if there is a difference between the 2 variants of the phone's modem firmware, if there is one (assuming the security patch did not update the firmware). I would know for sure if I knew if OTA was compressed when downloaded because if not, then they definitely are different modem firmwares because the modem is 90+mb and I can get that compressed to ~45mb.
Click to expand...
Click to collapse
The OTA may or may not be compressed, but it is a block level patch. It's not the new files, but just the atomic blocks that are different between the old and new images. If only a few files change in the modem, then the patch is just the blocks that are different for those files. The ROM does a block level hash to make sure it is bit-wise identical to the image, otherwise, it will throw errors or not boot at all, depending on what level of dm-verity is enforced. The modem files could be exactly the same, but only difference could be that the version string could be October instead of September, and the OS will have a different hash and consider the two different.
It's certainly not line in the good ol' days
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
You could blow up the modem images and compare the individual files to see what is different. You can certainly detect the differences at the file level, but you may not be able to know what the differences does.
Related
Did anyone else get an update to QC1 recently? I can't notice anything too different, except for the latest security patch.
Yes, it's just a normal security patch. No major changes unfortunately
woooh77 said:
Yes, it's just a normal security patch. No major changes unfortunately
Click to expand...
Click to collapse
There is updated Bootloader to V6 too. So you can't downgrade anymore to privies firmware.
New S5DPK5-to-S6DQC1-UP ADB sideload update. This update is official
If you update you not going to be able to go back unless someone post ODIN files of this firmware. Also i have Nougat files U5EQB8 to U6EQC9 with Version 6 bootloader is anybody want to try PM me. I will not post here for now since this contain version 6 bootloader and is not official yet so you can go back if other build will become official.
norbarb said:
There is updated Bootloader to V6 too. So you can't downgrade anymore to privies firmware.
New S5DPK5-to-S6DQC1-UP ADB sideload update. This update is official
If you update you not going to be able to go back unless someone post ODIN files of this firmware. Also i have Nougat files U5EQB8 to U6EQC9 with Version 6 bootloader is anybody want to try PM me. I will not post here for now since this contain version 6 bootloader and is not official yet so you can go back if other build will become official.
Click to expand...
Click to collapse
Any major changes from QA8 to QC9?
troyboytn said:
Any major changes from QA8 to QC9?
Click to expand...
Click to collapse
I can't tell. I don't own S6E model.
Clicking from Edge of Galaxy
Just curious if anyone with the US model 1806 gotten a patch update recently within the last couple months. Im still running with the the June 2017 patch.
Ive seen some people saying they have an October or January or February patch, so just wanting to see what others may have if its different
My build number is NPS26.116-26 no updates available to download from the phone
Retgb; still on October patch
The January 1, 2018 security update landed on my phone about a week ago. It's number NPSS26.116-45-9. You have to have October you can get this one, though. I am using a retus model. Probably too late to find my zip though. You might wanna check Reddit.
pswiifanwmi said:
The January 1, 2018 security update landed on my phone about a week ago. It's number NPSS26.116-45-9. You have to have October you can get this one, though. I am using a retus model. Probably too late to find my zip though. You might wanna check Reddit.
Click to expand...
Click to collapse
may i ask which version you have 3g/32gb or 4g/64gb
Yeah, I have the 3/32GB version. Interesting idea.
I got the 4/64 and i flash the lastest firmware already and i got the the January patch i am in US....
I have a copy if it helps, Jan update
drive.google.com/file/d/1DN5OEu6FkymCKJWjOgukzfI3yOKZM59t/view?usp=sharing
i wonder why my retus model didnt get an update stuck on july 1 2017.. And i got it midway through december so i would think that I would have gotten a software update out of the box over wifi for it? then again right now its bootloader is unlock and the bootloader says the software is modified?
xSpartacusx said:
i wonder why my retus model didnt get an update stuck on july 1 2017.. And i got it midway through december so i would think that I would have gotten a software update out of the box over wifi for it? then again right now its bootloader is unlock and the bootloader says the software is modified?
Click to expand...
Click to collapse
I just got the message for the January Security update for XT1806 (retus sanders). Trying to figure out a way to patch and keep root... Or patch then re-root.
DKaine said:
I just got the message for the January Security update for XT1806 (retus sanders). Trying to figure out a way to patch and keep root... Or patch then re-root.
Click to expand...
Click to collapse
Remove root, load factory recovery, update, load recovery of choice, root
Phazmos said:
Remove root, load factory recovery, update, load recovery of choice, root
Click to expand...
Click to collapse
Doing just that, I was being cheeky when I said "figuring out ..." I was hoping that flashfire or RSDLite was still an option... but your steps above are still the easiest thing to do.
Patch security update
xSpartacusx said:
Just curious if anyone with the US model 1806 gotten a patch update recently within the last couple months. Im still running with the the June 2017 patch.
Ive seen some people saying they have an October or January or February patch, so just wanting to see what others may have if its different
My build number is NPS26.116-26 no updates available to download from the phone
Click to expand...
Click to collapse
Yesterday I received the update with security patch 1 January and I have the model XT1806 us ...... So I waiting for the Oreo update....
cubano2031 said:
I got the 4/64 and i flash the lastest firmware already and i got the the January patch i am in US....
Click to expand...
Click to collapse
do you mean OTA or do you have the actual firmware so i can start from scratch?
File?
cubano2031 said:
I got the 4/64 and i flash the lastest firmware already and i got the the January patch i am in US....
Click to expand...
Click to collapse
Do you have the firmware file to share for the 4/64?
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
VarunAgw said:
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
Click to expand...
Click to collapse
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Mr. Nerd_ said:
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Click to expand...
Click to collapse
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
VarunAgw said:
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
Click to expand...
Click to collapse
You probably need to use "mfastboot" instead of "fastboot" command. Download this: https://androidfilehost.com/?fid=962187416754477464
Unpack it and place the boot.img in same directory. Open Command Prompt in that directory. Correct command is: mfastboot flash boot bootimagename.img
Here you can also find the correct patched boot.img: https://forum.xda-developers.com/moto-g6/how-to/guide-magisk-patched-boot-image-opw27-t3794977
Got the S too
Hi,
I bought my new Motorola G6+ Evert last week here in Mexico. (where I live)
It's fully unblocked
Version PVT1, SKU XT1926-6
Running Oreo 8.0
But I wondered me about that Build Number.
While every tutorial is saying that I can just flash TWRP with that Build-Number : OPW27.113-45-4
Because I have: " OPWS27.113-25-4 "
I've upgradet OTA and it still says, that I have the latest security patch (1. June 2018) and so on....
So I wonder if I can unlock the bootloader, flash OPW27.113-45-4 or OPWS27.113-45-4 to be able to install TWRP Recovery from
https://forum.xda-developers.com/showpost.php?p=76501832&postcount=3
Purpose:
I can't wait to get my new babe rooted to install the real hot Stuff on it.
But it's still confusing why I got that different Build Number.... Maybe it's because of my location.
But i'am not shure if it is safe to root it and to flash SuperSU and TWRP. With my B-Number.
So may some one got the right Firmware for me ?
Sunny Greetings
B2DR
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Junior Passos said:
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Click to expand...
Click to collapse
And what about the "-25" vs "-45"? I have the same firmware here (Argentina): OPW27.113-25
Thanks!
Also what about this version OPW27.113-89 with security patch level 1 July 2018 for Australia.
I've got an AT&T branded Note 9 stuck at the Augist security patch. I've tried a few things (clearing cache on software update, setting date forward, safe mode, Smart Switch) and none have worked, so I'd like to give ODIN a try.
Based on the version I'm at now, can anyone recommend the specific files/versions I'll need to use in order to get my phone up to date but NOT wipe my data? I'd be fine with whatever the latest AT&T release is if it means that I might again begin receiving OTA updates.
My current info is in the attached screenshot. Any help would be appreciated. I'm not technically inept, but it's been a while since I flashed an update via unofficial means and never on a Samsung device.
Thanks,
-Brett.
Just download the most recent version of the firmware with SamFirm tool, then flash it with ODIN. Use HOME_CSC and you shouldn't have to wipe.
After checking sammobile, only 1 firmware available for n960u at&t which is that august firmware.
try here
https://updato.com/firmware-archive-select-model?exact=1&q=SM-N960U
nusaf said:
After checking sammobile, only 1 firmware available for n960u at&t which is that august firmware.
Click to expand...
Click to collapse
I wonder if they're missing some updates? According to AT&T, this should be the current version:
https://www.att.com/devicehowto/tut...?make=Samsung&model=SamsungN960U&gsi=Tdi5sXtc
Release date: January 15, 2019
Android version: 8.1.0
Security patch level (SPL): December 1, 2018
Baseband version: N960USQS1ARL2
Build number: M1AJQ.N960USQS1ARJA
Previous update required: N960USQS1ARJA
File size: 83MB
Mr. Orange 645 said:
Just download the most recent version of the firmware with SamFirm tool, then flash it with ODIN. Use HOME_CSC and you shouldn't have to wipe.
Click to expand...
Click to collapse
Pardon my ignorance, but would that put me on a path to no longer get updates from AT&T directly? Meaning, if I applied the latest updates that's not AT&T specific, would that cause me to no longer get updates from AT&T (not that I've been getting even those...) in the future?
Thanks,
-Brett.
zzoinks said:
I wonder if they're missing some updates? According to AT&T, this should be the current version:
https://www.att.com/devicehowto/tut...?make=Samsung&model=SamsungN960U&gsi=Tdi5sXtc
Release date: January 15, 2019
Android version: 8.1.0
Security patch level (SPL): December 1, 2018
Baseband version: N960USQS1ARL2
Build number: M1AJQ.N960USQS1ARJA
Previous update required: N960USQS1ARJA
File size: 83MB
Click to expand...
Click to collapse
Latest Stock Official ATT_ODIN_N960USQS1ARL2 Note9 December Patch, Flash N960USQS1ARL2 and you will be on Latest Official Firmware AT&T and will recieve OTA'S as well.
https://forum.xda-developers.com/galaxy-note-9/how-to/stock-official-attodinn960usqs1arl2-t3891044
Venom0642 said:
Latest Stock Official ATT_ODIN_N960USQS1ARL2 Note9 December Patch, Flash N960USQS1ARL2 and you will be on Latest Official Firmware AT&T and will recieve OTA'S as well.
https://forum.xda-developers.com/galaxy-note-9/how-to/stock-official-attodinn960usqs1arl2-t3891044
Click to expand...
Click to collapse
Thanks!
So I can go right from my current August version straight to this latest without incrementally doing each patch in between?
zzoinks said:
Thanks!
So I can go right from my current August version straight to this latest without incrementally doing each patch in between?
Click to expand...
Click to collapse
Yes just flash away, do a data backup before you flash, cause AT&T will wipe your phone.
Sent from my SM-N960U using XDA Labs
nusaf said:
After checking sammobile, only 1 firmware available for n960u at&t which is that august firmware.
Click to expand...
Click to collapse
In my experience, Sammobile never has the current ATT firmware. They have all the other carriers, just not ATT. Plus it's slow AF to download from them.
That's why I said to use the SamFirm tool to download it. It always pulls the most recent firmware and does it directly from Samsung servers, so it's super fast and reliable.
---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------
zzoinks said:
I wonder if they're missing some updates? According to AT&T, this should be the current version:
Pardon my ignorance, but would that put me on a path to no longer get updates from AT&T directly? Meaning, if I applied the latest updates that's not AT&T specific, would that cause me to no longer get updates from AT&T (not that I've been getting even those...) in the future?
Thanks,
-Brett.
Click to expand...
Click to collapse
Why would that take you off the ATT update path? I never suggested using firmware that wasn't specific to ATT. You download the most recent firmware from ATT with the SamFirm tool and flash it in ODIN.
In model you put SM-N960U and for region, you use ATT. As long as you're on an official ATT build, you stay on the ATT update path.
The SamFirm tool just pulls the updates directly from the Samsung servers, rather than going through slow-ass sammobile or updato.
Mr. Orange 645 said:
...
Why would that take you off the ATT update path?
Click to expand...
Click to collapse
That's totally my own ignorance/caution showing. It's been quite a while since I did any sort of ROM flashing and I'm really out of the loop. I was just double checking that what you were suggesting was the latest for AT&T and not a global update of some sort.
Thanks for clarifying. I'll give the SamFirm/ODIN combo a try when I get home from work. I'll be sure to back up first (assuming Safe Switch is a good way to do so?) and hope things don't get wiped in the process. Seems to be conflicting advice between you and Venom0642, but even if it gets wiped it's not a huge deal as long as I'm backed up.
Thanks again for your time!
zzoinks said:
That's totally my own ignorance/caution showing. It's been quite a while since I did any sort of ROM flashing and I'm really out of the loop. I was just double checking that what you were suggesting was the latest for AT&T and not a global update of some sort.
Thanks for clarifying. I'll give the SamFirm/ODIN combo a try when I get home from work. I'll be sure to back up first (assuming Safe Switch is a good way to do so?) and hope things don't get wiped in the process. Seems to be conflicting advice between you and Venom0642, but even if it gets wiped it's not a huge deal as long as I'm backed up.
Thanks again for your time!
Click to expand...
Click to collapse
Yup, just back up with Smart Switch and Samsung Cloud.
When you flash with ODIN, just skip the USERDATA file and use HOME_CSC instead if CSC_OYN. That SHOULD avoid wiping your phone. But ATT is weird, so I can't promise that.
Mr. Orange 645 said:
When you flash with ODIN, just skip the USERDATA file and use HOME_CSC instead if CSC_OYN. That SHOULD avoid wiping your phone. But ATT is weird, so I can't promise that.
Click to expand...
Click to collapse
EDIT - I decided to just give it a try. I flashed the AP, BL, CP, and CSC from Venom0642's post above and skipped Userdata. It worked, without wiping the phone!
Current version info attached. Thanks all for your help!
zzoinks said:
EDIT - I decided to just give it a try. I flashed the AP, BL, CP, and CSC from Venom0642's post above and skipped Userdata. It worked, without wiping the phone!
Current version info attached. Thanks all for your help!
Click to expand...
Click to collapse
Glad you got it all figured out!!
Will this work on a Note 9 that was originally on Sprint converted to AT&T? I bought this phone on Ebay to use for ATT and the software shows as ATT/ATT/SPR. I am still on October update and want to try to flash the update to at least December.
Hello guys.
So I recently got a phone that's stuck with the August 2021 security patch. I wanna flash the latest software so had 2 questions:
1. Should I flash the most recent software update or considering I've never actually updated my phone, should I flash all the previous updates from August first before I flash the latest one.
2. I wanted to know if anyone has experience flashing SM-G998U1 firmware on a SM-G998U phone. I heard you can flash "U1" or carrier unlocked firmware on a "U" or carrier locked phone. Just that you'd lose all your data. I have an SM-G998U locked to Verizon and since I'm not in the US Verizon says they can't unlock it for me. So my only option is to flash new firmware updates. But I can't for the life of me find any Verizon SM-G998U firmware from after August 2021 (that's my latest security patch) online. So wanted to hear from anyone with experience that's flashed "U1" firmware on a "U" phone.
Flashing FW is no solution to unlock phones.
OnnoJ said:
Flashing FW is no solution to unlock phones.
Click to expand...
Click to collapse
I'm not trying to unlock my phone. It's usable cause it doesn't reject simcards. Just denies me OTA updates. All I want is new software.
Is there another option apart from flashing new firmware if I want to update it? I'd love to unlock the phone but all the websites keep talking about generating codes. My phone doesn't request a code. And I can still use it. If there isn't another option for unlocking, can you assist with the questions I've asked?
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
OnnoJ said:
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
Click to expand...
Click to collapse
Thanks so much for all the help Yeah I've seen that thread before. But only firmware available until November 2021. Nothing after. So think I'll try the U1 to U option for now.