Straight to the content, new mirrors appreciated. I will update this thread as soon as a new update comes out.
Links to Odin are from sammobile, and the ADB drivers are on Github. All links are clean and untouched.
Odin 3.11.1
ADB for Windows
===========================
Untouched side loadable update zips downloaded from xdmd.sl.attcompute.com (sideload using ADB):
7.0 branch:
2017 Mar security level Android 7.0 (G920AUCU5EQB8 to G920AUCU6EQC9)
2017 Mar security level Android 7.0 (G920AUCU5DQB3 to G920AUCU6EQC9)
2017 Feb security level Android 7.0 (G920AUCU5EQA8 to G920AUCU5EQB8)
2017 Feb security level Android 7.0 (G920AUCU5DQB3 to G920AUCU5EQB8)
2017 Jan security level Android 7.0 (G920AUCS5DPK5 to G920AUCU5EQA8) | Credit goes to Mohit0144
6.0 branch:
2017 Feb security level Android 6.0.1 (G920AUCS5DPK5 to G920AUCU5DQB3)
2017 Feb secruity level Android 6.0.1 (G920AUCS5DPK3 to G920AUCU5DQB3)
2017 Jan security level Android 6.0.1 (G920AUCS5DPK3 to G920AUCS5DPK5)
2016 Dec security level Android 6.0.1 (G920AUCS5DPK1 to G920AUCS5DPK3)
2016 Nov security level Android 6.0.1 (G920AUCS5DPJ1 to G920AUCS5DPK1)
===========================
Official complete Odin images (flash using Odin):
2016 Oct security level Android 6.0.1 (G920AUCS5DPJ1)
Current update path to most current build:
G920AUCS5DPJ1 (odin flash) -> G920AUCS5DPK1 (sideload) -> G920AUCS5DPK3 (sideload) -> G920AUCS5DPK5 (sideload) -> pre-release G920AUCU5EQA8 (sideload) -> pre-release G920AUCU5EQB8 -> pre-release G920AUCU6EQC9
If you are on a version more recent than DPJ1, you can start from a later sideload update.
Disclaimer: You are responsible for what you do to your phone
How to flash using Odin (will wipe phone):
1. Extract complete firmware
2. Extract Odin software
3. Shutdown phone
4. Press BL, AP, CP, and CSC buttons in-order in Odin and load files, Odin may freeze during this, just wait it out. Don't touch other options
5. Press Volume down, home, and power together to go into download mode
6. Plug in phone to laptop, and press start to flash
How to sideload using ADB (will wipe phone):
1. Install ADB, reboot
2. Using cmd, cd into the folder of the sideload update zip
3. Shutdown phone, press Volume up, home, and power together to go into download mode
4. Select "apply update from adb", use power button to confirm
5. Using the command "adb devices", verify that the phone is detected after plugging in, if it is detected, proceed
6. Type in command "adb sideload SIDELOADZIPNAME"
7. Wait, it takes a bit for the update to work, and the phone may appear frozen during this process.
If confused, see this thread: http://forum.xda-developers.com/att...ating-to-android-6-0-1-g920aucu3cpd6-t3371884
did exactly what u said with the odin and i keep getting a fail...
Billfromnj05 said:
did exactly what u said with the odin and i keep getting a fail...
Click to expand...
Click to collapse
Well, the file is the exact same as that from this thread. And it is working for those people, so not sure why this is happening to you without more details.
Thank you for these updates.
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update
(oct)
Click to expand...
Click to collapse
I have absolutely no idea about why your phone is crashing.
Installing an update may fix it, just by virtue of clearing the /data partition and resetting it to stock in the process. But personally I doubt it (unless google fixed a denial of service bug that you were somehow triggering?).
Not really a diagnosis thread, so do you mind creating a new post with USB debugging turned on and logcat output so the community can help?
See here: http://android.wonderhowto.com/how-...ture-logcat-for-detailed-bug-reports-0167774/
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
Click to expand...
Click to collapse
Not sure as to specifics of your reboot issue, but I had an S6 that started giving me multiple random reboots per day. Luckily I was inside warranty by a couple weeks - it was a hardware issue. Ended up with a new main board, plus a new display since the tech broke the original somehow changing the board.
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
supersmilers said:
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
Click to expand...
Click to collapse
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
December update has been pushed out OTA. Is PK3.
Sent from my SAMSUNG-SM-G920A using Tapatalk
GilbertoXDA17 said:
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
Click to expand...
Click to collapse
Not sure, but probably need to flash this with Odin
worked fine, note of caution.
my att gs6 was on oj9. flashed went through fine initially then an error came up "can't open the serial(com)port" and FAIL in red above the blue part.
however, the phone progress meter kept going and eventually the flash was successful.
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
wiltaf said:
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
Click to expand...
Click to collapse
I would bet that it's because you're not on an AT&T sim. I don't think they feel responsible to update the phone if it's not on their network. Not sure if you can throw someone's sim in there to update it or if you just ODIN flash it to update it.
Edit: You can also try to use Smart Switch to see if it'll pull the update, or try a Samsung Experience at a BestBuy to see if they can push the update.
Thanks. Now my phone is up to date.
This is the only way I can apply updates. For some reason I never get the OTA updates.
Thanks my phone updated to latest.
will my unlocked galaxy s6 become locked if i update using this?
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Is this for phones already with root access?
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
Zero4 said:
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Click to expand...
Click to collapse
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
---------- Post added at 06:22 PM ---------- Previous post was at 05:42 PM ----------
mjr4281 said:
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
Click to expand...
Click to collapse
They did change it up though. Whatever you choose as your screen lock i.e., pattern, pin, password, is what will be used for unencryption at start-up. The one thing that doesn't make sense to me is that they now give you an option to use one of these methods or none at all during start-up. I don't see the point in using encryption if you can't password protect it, but I haven't fully researched all the options yet.
My Nexus 6 received 7.0 update notification and I would like to wait for 7.1 to upgrade together. But yesterday the 7.0 notification suddenly gone, I've manually check the update but the system said my phone already get the latest update. Then I've checked the version of my Nexus 6, it is MOB31H, I don't remember whether I have the November update. Now I have few questions and hope someone can help me.
1. Why the 7.0 update notification suddenly gone?
2. I've checked the Full OTA images, the Nov update contains MMB31C and MOB31K, If I would like to manually apply the update, which one should I use? (My Nexus 6 is international version XT1103)
3. If i manually apply the the Full OTA Images on Nov update by adb sideload, will all the data being erased and need to re-config and reinstall all apps?
Thanks so much in advance for your help.
1. Unknown
2. Your device model doesn't matter as the OTA zips work on both, but based on the model number you gave, you have a US device. The international unit is XT1100. Use the version with the code ending in "K" if wanting Android 6.x. Android 7.x uses codes starting with "N".
3. Flashing an OTA zip will not cause loss of data.
Strephon Alkhalikoi said:
1. Unknown
2. Your device model doesn't matter as the OTA zips work on both, but based on the model number you gave, you have a US device. The international unit is XT1100. Use the version with the code ending in "K" if wanting Android 6.x. Android 7.x uses codes starting with "N".
3. Flashing an OTA zip will not cause loss of data.
Click to expand...
Click to collapse
Thanks so much for your help, I think I mis-type the model, XT1100 international should be correct.
I've just sideloaded the version MOB31K successfully and will wait for the 7.1 fix on the speaker phone echo problem before upgrade to 7.1.
Please don't mind to ask one more question, i guess the MMB31C and MOB31K is for US and International model respectively. On version Nougat, no different on XT1103 and XT1100, one version for both model?
Thanks so much again for your help.
Or you could sideload NBD91X, which is Nougat without the speakerphone problem.
@mega23mac: MMB31C is for CDMA devices in the US, if I recall correctly. As @dahawthorne points out, you could install a 7.0 OTA, but if you don't need the speakerphone, the 7.1 OTA works just fine. Google should have it patched for next month's security update.
the latest August 2020 update
has broken LOCAL vpn on my (Brzailian) s10+
PDA G975FXXU8CTG4
CSC G975FOWO8CTG4
result : no more Adguard (nor Blokada)
for info Windscribe vpn works (but this does not resolve my AD-annoyances ...)
now, I tried to go back to an earlier ROM but of corse Samsung made that impossible (flashing via Odin I get the message on the phone-screen that the ROM is not compatible)
is there a workaround to get back to an earlier ROM ?
thanks
Bas
You can only go back to an earlier stock ROM if it's on the same bootloader you're currently on. Bootloader 4 can't go back to bootloader 3. However, bootloader 4 and roll back to an earlier bootloader 4 version.
ok, thanks for the info
in the end I rooted with magisk
now using AFWall+ (firewall) and Adaway, having much more control
Lord i was just abt to upgrade... Samsung screwed up. again. guess you gotta wait for the patch.
for those using AdGuard...
Try the latest nightly: 3.5 nightly 6
Their changelog says: * [Fixed] Fix For Device With A Restrictive Account #3299
after updating the app, use adb as described here:
https://kb.adguard.com/en/android/faq#restrictedaccount
This worked for me
Hi All,
I urgently need some help to downgrade Samsung Galaxy Note 9 phone Model No: SM-N960F/DS from currently running OS Android 10 to Android (Oreo) 8.1 or 8.0.
Following are the current versions running:
Software version: SAOMC_SM-N960F_OXM_XSA_QQ_0016
Knox Version: Knox 3.4.1, Knox API Level: 30, TIMA: 4.10.
I have downloaded the XSA version of Android 8.1 from Sammobile, followed all the instructions by running Odin3 V3.14.4, gone into the Download mode of the phone. The phone connects to Odin as I can see on Odin status of Blue Colour Com connection established, Odin then displays "Recovery", unfortunately the phone gets stuck at this status showing "Recovery". I have let the phone run for hours or even a full day but the status never changes from "Recovery"
Could anyone please assist me to complete the downgrade. Am I missing any step here?
Thanking you in advance
I don't think downgrade to oreo is possible. Pie is possible if baseband version's 5th character from the back is 4.
Rosli59564 said:
I don't think downgrade to oreo is possible. Pie is possible if baseband version's 5th character from the back is 4.
Click to expand...
Click to collapse
Thank you for the prompt reply. I just check the digit, its 6 not 4. What are my options here?
None. Your options are only firmwares with the number 6, which date to April/May, last OneUI 2.0 firmwares.
I did read that one can flash custom roms that are older, if one leaves Bootloader untouched to v6, but that is something i wouldn't encourage to do.
PlutoDelic said:
None. Your options are only firmwares with the number 6, which date to April/May, last OneUI 2.0 firmwares.
I did read that one can flash custom roms that are older, if one leaves Bootloader untouched to v6, but that is something i wouldn't encourage to do.
Click to expand...
Click to collapse
Thank you PlutoD, I am happy to read about it as well, if you want to post the link or let me know where to find the info.
CrazynWild said:
Thank you PlutoD, I am happy to read about it as well, if you want to post the link or let me know where to find the info.
Click to expand...
Click to collapse
I have no links except the Development board here, my input came as something that i've seen discussed somewhere in there.
As you can see, there are some Oreo Custom ROMs, i'm not sure if they are actively maintained (if one can say anything active about that), but if you are determined to do what you want, i would start by choosing the ROM first, put a question there or the last resort, contact the developer.
I'll be very blunt with you, i see no reason for people to revert to older roms, but i dont want to get in to that argument, but having a v6 Bootloader (and maybe Modem too) with a v1/v2 system firmware is something that could give you unpredictable issues nobody could help you with.
Could boot a pie custom rom with android10 bootloader. Not sure about oreo though
Hi, hope somebody can help me, i unlocked the bootloader in this phone because i want to root it, in the past i never really rooted phones unless necessary but never got into the magisk app
The phone is XT1900-4
android 9: PPWS29.69-40-3-1
security patch: 1 september 2019
The phone support is over and wont receive any update anymore
I understand how to install the TWRP, however when i go to the page for download the img and zip, i see this name
twrp 3.6.2_11-0-payton with the proper zip and img files
but down there is anothers ones which say
twrp 3.6.0_9-0-payton with the zip and img files
and even down there other ones without the 9 or 11
So the question is correct me if i am wrong, the ones at top are the most recent ones 3.6.2_11 than the 3.6.0_9 But those two numbers at end, 11 and 9 are because you need to have android 11 for install the 3.6.2? if i am correct then i must flash the one which says 3.6.0_9 since i am using android 9? or has nothing to do what version of android i have and just install the most recent one?
Ive been doing more digging, and just realized Magisk app and Magisk manager have been integrated
So my new questions is...how do i root this phone now? do i still need twrp? or just download the magisk 25.1 and follow instructions?
The first video i saw is this one
but since is using old files(as well any other video), i wanted to use updated files hence i dont know if this video is outdated now or still being the only way for root the phone which will force me to use those old files
Thank you
Ignore this second post in the thread, was a mistake and dont know how to delete, just focus in my question/request
Need to root Moto X4 in july 2022