Database Users

[REF] Nexus 9 Stock OTA URLs

This thread compiles all known OTA updates for the Nexus 9 WiFi-only and LTE variants.
Nexus 9 WiFi (flounder 0P82100) - volantis
Current firmware: Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...5f522d.signed-volantis-MRA58N-from-MRA58K.zip
------------------------------------------------------
MRA58K from LMY48T - https://android.googleapis.com/pack...83199e.signed-volantis-MRA58K-from-LMY48T.zip
------------------------------------------------------
LMY48T from LMY48M - https://android.googleapis.com/pack...26824b.signed-volantis-LMY48T-from-LMY48M.zip
------------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...gned-volantis-LMY48M-from-LMY48I.a8f87fa0.zip
------------------------------------------------------
LMY48I from LMY47X - https://android.googleapis.com/pack...olantis-LMY48I-from-LMY47X-superblock-fix.zip
------------------------------------------------------
LMY47X from LRX22L - https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
------------------------------------------------------
LRX22L from LRX22C - http://android.clients.google.com/p...gned-volantis-LRX22L-from-LRX22C.61f6bdb8.zip
LRX22L from LRX22C - https://android.googleapis.com/pack...olantis-LRX22L-from-LRX22C-fix-superblock.zip (Superblock)
------------------------------------------------------
LRX22C from LRX21R - http://android.clients.google.com/p...ned-volantis-LRX22C-from-LRX21R.3c1c62441.zip
------------------------------------------------------
LRX21R from LRX21L - http://android.clients.google.com/p...is-LRX21R-from-LRX21L-factory-recovery-ok.zip
LRX21R from LRX21Q - http://android.clients.google.com/p...is-LRX21R-from-LRX21Q-factory-recovery-ok.zip
------------------------------------------------------
LRX21Q from LRX21L - http://android.clients.google.com/p...gned-volantis-LRX21Q-from-LRX21L.e0ce5d82.zip
Nexus 9 LTE (flounder_lte 0P82200) - volantisg
Current firmware: Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...4db5d.signed-volantisg-MRA58N-from-MRA58K.zip
------------------------------------------------------
MRA58K from LMY48T - https://android.googleapis.com/pack...8ab3d.signed-volantisg-MRA58K-from-LMY48T.zip
------------------------------------------------------
LMY48T from LMY48M - https://android.googleapis.com/pack...f9311.signed-volantisg-LMY48T-from-LMY48M.zip
------------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...ned-volantisg-LMY48M-from-LMY48I.fd894caa.zip
------------------------------------------------------
LMY48I from LMY47X - http://android.googleapis.com/packa...lantisg-LMY48I-from-LMY47X-superblock-fix.zip
------------------------------------------------------
LMY47X from LRX22L - http://android.googleapis.com/packa...ned-volantisg-LMY47X-from-LRX22L.3c854210.zip
------------------------------------------------------
LRX22L from LRX22C - http://android.googleapis.com/packa...ned-volantisg-LRX22L-from-LRX22C.05a03333.zip
Special Thanks:
techiedj
EthanFirst
Dark_Eyes
JC_1
beredan
marcomsousa
Niggo372
dpjohnston
lajuoika
WineSnob
McChen147

OK guys, now that these pups are starting to ship, I need your help!
When you get your new Nexus 9 in the mail, please fire it up and DO NOT accept an OTA that comes out of the box. Please go and get the Android build #, the values of ro.build.date.utc and ro.product.name from build.prop, and the bootloader version (which you'll need to reboot into bootloader mode in order to do). Once you have that info, please post it here so we can get this thread started!
Then, after that, if there's an OTA available out of the box, please get the URL of the ZIP file from adb logcat. Once you do that, feel free to apply said OTA update and enjoy your tablet!
Thanks in advance for your help! If you need any help rebooting into bootloader mode, or grabbing OTA URLs from logcat, let me know.

The review N9 units already got their first ota from LRX16F -> LRX21L.
We need someone to connect wireshark/etherial/fiddler/<your preferred network sniffer> and grab the url for the initial ota when retail devices ship.
While they may not get that specific ota by the time it's generally out, there is very likely going to be an ota for something by then.

nexus 7 and note 3 with wifikill and dsploit so im ready

oldblue910 said:
OK guys, now that these pups are starting to ship, I need your help!
When you get your new Nexus 9 in the mail, please fire it up and DO NOT accept an OTA that comes out of the box. Please go and get the Android build #, the values of ro.build.date.utc and ro.product.name from build.prop, and the bootloader version (which you'll need to reboot into bootloader mode in order to do). Once you have that info, please post it here so we can get this thread started!
Then, after that, if there's an OTA available out of the box, please get the URL of the ZIP file from adb logcat. Once you do that, feel free to apply said OTA update and enjoy your tablet!
Thanks in advance for your help! If you need any help rebooting into bootloader mode, or grabbing OTA URLs from logcat, let me know.
Click to expand...
Click to collapse
Lollipop setup is a little different than past versions.
Step 1 - Choose language
Step 2 - Login to WiFi
Step 3 - "Downloading" updates! No choice in the matter. And it's before logging in to the device for the first time.

#3 has been explained as to why google now does this and i think its a good idea.
Ars technica interview...

cam30era said:
Lollipop setup is a little different than past versions.
Step 1 - Choose language
Step 2 - Login to WiFi
Step 3 - "Downloading" updates! No choice in the matter. And it's before logging in to the device for the first time.
Click to expand...
Click to collapse
Don't Set up Wi-Fi immediately

cam30era said:
Lollipop setup is a little different than past versions.
Step 1 - Choose language
Step 2 - Login to WiFi
Step 3 - "Downloading" updates! No choice in the matter. And it's before logging in to the device for the first time.
Click to expand...
Click to collapse
Just unplug your router from the Internet

Hindsight really is 20/20, isn't it? Of course, when I set mine up at 10:30 this morning I didn't know this would happen.... Better luck to the next guy.?

So once the forced OTA happened, what build number abd bootloader version are you on now?
Sent from my Galaxy Note 4 using Tapatalk

oldblue910 said:
So once the forced OTA happened, what build number abd bootloader version are you on now?
Sent from my Galaxy Note 4 using Tapatalk
Click to expand...
Click to collapse
Turns out my update came already downloaded
cry sorry
Will give the info you need after I unlock it

Code:
bootloader=3.43.0.0114
Ref. https://android.googlesource.com/device/htc/flounder/+/lollipop-release/board-info.txt

EthanFirst said:
Code:
bootloader=3.43.0.0114
Ref. https://android.googlesource.com/device/htc/flounder/+/lollipop-release/board-info.txt
Click to expand...
Click to collapse
Are we sure that's what's actually on the device though?
Sent from my Galaxy Tab S 8.4 using Tapatalk

I'll wait for @USBhost to do verify his bootloader version and build number from his device.
Sent from my Galaxy Tab S 8.4 using Tapatalk

oldblue910 said:
I'll wait for @USBhost to do verify his bootloader version and build number from his device.
Sent from my Galaxy Tab S 8.4 using Tapatalk
Click to expand...
Click to collapse
After update
Build LRX21L
Bootloader
HBOOT-3.43.0.0114
OS-n/a
emmc - boot 2048

USBhost said:
After update
Build LRX21L
Bootloader
HBOOT-3.43.0.0114
OS-n/a
emmc - boot 2048
Click to expand...
Click to collapse
Thank you, sir! If anyone can find a way to get the bootloader and build number of the original shipping firmware prior to the forced OTA, please post that info as well. Until then, I'm going to start the thread at LRX21L. :good:
Sent from my Galaxy Tab S 8.4 using Tapatalk

anyone get the stock recovery.img yet? was thinking about trying to port chainfires autoroot.. but with no recovery.img or boot.img
we get no luck lol

No way for me to get past WiFi without selecting a WiFi spot. Skip is grayed out.

datdirtyscrew said:
No way for me to get past WiFi without selecting a WiFi spot. Skip is grayed out.
Click to expand...
Click to collapse
Unplug the Internet from your wifi router, that way you can connect to wifi workout being in the Internet.
Sent from my Galaxy Note 4 using Tapatalk

#nexus9

[Official Lollipop 5.1.1] Galaxy Note 10.1 (2014 Edition) SM-P607T Firmware Update

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
T-Mobile has just released the first official Android 5.1.1 Lollipop for the Samsung Galaxy Note 10.1 2014 Edition (SM-P607T). The update is currently Available Over-the-air (OTA) and via KIES in the United States. (screenshots attached)
Galaxy Note 10.1 Lollipop Firmware Details:
- Model Name: Samsung Galaxy Note 10.1 2014 Edition
- Model: SM-P607T
- Country: T-Mobile US (TMB)
- Firmware Version: P607TUVUBOI2
- OS: Android Lollipop
- OS Version: 5.0.2
- Build Date: September 09, 2015
- Changelist: 5777857
- PDA: P607TUVUBOI2
- CSC: P607TTMB1BOI2
Click to expand...
Click to collapse
Firmware Download: http://forum.youmobile.org/downloads/?sa=view&down=6351
Source: http://www.youmobile.org/blogs/entr...fficial-Android-5-1-1-Lollipop-is-Rolling-out
Regards,

Anyone know how to flash Twrp and have it stick?

*Note 10.1 2014 LTESM-P605NEEP605XXU1EOI5 5.1.1 19.09.2015 5849447

Anyone got a mirror that's faster than Sammobile or the youmobile link? I'm on the road and have to do this over my mobile network

md1008 said:
Anyone know how to flash Twrp and have it stick?
Click to expand...
Click to collapse
I flashed TWRP 2.8.7.0_4.4 with ODIN and had no issues getting it to stick. When the device reboots after the ODIN flash, make sure you are immediately holding the home button and volume up button. As long as you can get it to boot into TWRP immediately after the flash, it will stick.
However, flashing SuperSU resulted in a bootloop immediately after. Guess we need a new root for this firmware. If you care, http://forum.xda-developers.com/galaxy-note-10-2014/help/twrp-4-4-build-5-1-1-rom-t3216561 is a thread I started for this. Post there and subscribe, maybe some experts will come along to help us...

Any feedback on whether it includes the new snote and new spen features like smart clip from Note 4 or Note 5

In p605 now is possibile write a note in lockscreen

arbit12 said:
Any feedback on whether it includes the new snote and new spen features like smart clip from Note 4 or Note 5
Click to expand...
Click to collapse
The pen window has these commands now:
Air Command (no change)
Smart Select (where old Scrap Booker was)
Image Clip (where old Screen Write was)
Screen Write (where old S-Finder was)
Pen Window (no change)
So I think the answer is "Yes" depending on what you mean by "Smart Clip"

Root!
karthikrr said:
I flashed TWRP 2.8.7.0_4.4 with ODIN and had no issues getting it to stick. When the device reboots after the ODIN flash, make sure you are immediately holding the home button and volume up button. As long as you can get it to boot into TWRP immediately after the flash, it will stick.
However, flashing SuperSU resulted in a bootloop immediately after. Guess we need a new root for this firmware. If you care, http://forum.xda-developers.com/galaxy-note-10-2014/help/twrp-4-4-build-5-1-1-rom-t3216561 is a thread I started for this. Post there and subscribe, maybe some experts will come along to help us...
Click to expand...
Click to collapse
I tried the instructions on Post 144 here: http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3215876/page15
It works without doing Step 1 (i.e. on the Stock Tmobile ROM)! All credit goes to @bluecat for doing the work and @M3r71n0 for the English translation!

sandibhatt said:
I tried the instructions on Post 144 here: http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3215876/page15
It works without doing Step 1 (i.e. on the Stock Tmobile ROM)! All credit goes to @bluecat for doing the work and @M3r71n0 for the English translation!
Click to expand...
Click to collapse
Were you able to install the SuperSU beta via TWRP? I just get that the file is corrupt and can't go any further. I was able to flash the new ROM and TWRP using the first few steps.

Yes. I am not sure if a final version has been released.

Has anyone here observed that ever since updating to lollipop that it won't store Wi-Fi credentials through reboots? It seems every time I reboot my tablet I have to reconnect to my Wi-Fi...
Edit... it seems that it's not just reboots that causes the WiFi to forget the saved networks. Turning WiFi off and then back on again will also cause it to forget all saved networks. Not sure what to do to fix this this time...
Just tried a factory reset to see if maybe I just had a dirty flash or something... Didn't help. Is anyone else having this problem?

Should have asked first, are you on stock, or did you try to root using the P605 guide? If you are rooted, then open up /system/build.prop and change ro.securestore.support from true to false to fix the wifi issue... If you are on stock, read on for some suggestions...
I do not have this problem. Based on other people discussing something similar on OTHER devices, few things you may want to try are below ... Please note that I am NOT an expert and there is a good chance I am citing discussions that have NOTHING to do with your problem. 1 and 2 should be safe and not do any damage to your device, but 3 might be risky. So, please try solutions at your own risk ...
1) Forget/Delete the connection once and connect to it again from scratch by entering the password. Right now you reenter the password when the device forgets it, but some people seemed to be discussing how deleting a working connection and reentering password manually seems to fix it. No idea why this would work!
2) Since you already did a factory reboot, one suggestion I saw elsewhere was to flash the new ROM with ODIN, then reflash it again right away. Again, absolutely no idea if or why this might ever work!
3) Are you sure you updated to the RIGHT LL ROM for your device? The most frequent reason I see for this is if you flashed the wrong device/region ... For example, if you are on the P607T (T-Mobile) and flashed the Nordic (NEE) ROM that is listed in the root guides on this site, that might mess up your wi-fi. Some discussion I saw on this suggested flashing the correct MODEM file manually.
If you ever figure it out, please come back and share your solution!
dharvey4651 said:
Has anyone here observed that ever since updating to lollipop that it won't store Wi-Fi credentials through reboots? It seems every time I reboot my tablet I have to reconnect to my Wi-Fi...
Edit... it seems that it's not just reboots that causes the WiFi to forget the saved networks. Turning WiFi off and then back on again will also cause it to forget all saved networks. Not sure what to do to fix this this time...
Just tried a factory reset to see if maybe I just had a dirty flash or something... Didn't help. Is anyone else having this problem?
Click to expand...
Click to collapse

karthikrr said:
Should have asked first, are you on stock, or did you try to root using the P605 guide? If you are rooted, then open up /system/build.prop and change ro.securestore.support from true to false to fix the wifi issue...
Click to expand...
Click to collapse
I actually have the SM-P607T and I downloaded the stock ROM from Youmobile and flashed with Odin because Kies and Smart Switch kept locking up on me. I started fresh and only restored apps after flashing an unsecured boot and rerooting.
This suggestion worked perfectly. Stored WiFi passwords now survive reboots and turning WiFi on and off.
I would have quite literally found that. Thank you SO much! That little problem was wildly inconvenient but it's fixed now.
Thanks again.

dharvey4651 said:
I actually have the SM-P607T and I downloaded the stock ROM from Youmobile and flashed with Odin because Kies and Smart Switch kept locking up on me. I started fresh and only restored apps after flashing an unsecured boot and rerooting.
This suggestion worked perfectly. Stored WiFi passwords now survive reboots and turning WiFi on and off.
I would have quite literally found that. Thank you SO much! That little problem was wildly inconvenient but it's fixed now.
Thanks again.
Click to expand...
Click to collapse
No problem! This is apparently quite a common issue and you would have bumped into a discussion sooner or later... I noticed that even the thread with the unsecured boot image has now been updated with this information
Thanks for that link btw ... Does everything else work alright with that kernel on the P607T? The P605 is AT&T, if I am not mistaken and I am unsure what changes exist between that and the T-Mo version. Its strange that Samsung has released so much on its opensource portal for the 605, but literally just one source for the 607T. Perhaps because the base code is the same? No idea, but if you are happy with your performance out of this kernel, let us know...

karthikrr said:
No problem! This is apparently quite a common issue and you would have bumped into a discussion sooner or later... I noticed that even the thread with the unsecured boot image has now been updated with this information
Thanks for that link btw ... Does everything else work alright with that kernel on the P607T? The P605 is AT&T, if I am not mistaken and I am unsure what changes exist between that and the T-Mo version. Its strange that Samsung has released so much on its opensource portal for the 605, but literally just one source for the 607T. Perhaps because the base code is the same? No idea, but if you are happy with your performance out of this kernel, let us know...
Click to expand...
Click to collapse
I'm actually quite pleased with performance and usability of my P607T with the stock 5.1.1 ROM installed. Everything works as expected except for that wifi issue and that's now fixed thanks to your info a few posts up.
I can't speak to whether or not the base code is the same or not I would imagine that the code is likely very similar if not the same because I had "[ROM][P605][5.0.2] Besonderes; a Touchwiz Lollipop ROM for Galaxy Note 10.1 2014 LTE" which is made for the P605 installed on my P607T and everything worked except wifi direct which is actually very important to me because my work program requires it.
Now I can't keep my tablet rooted because the program I use for work won't load with the tablet rooted. This has been the case since 4.4.4 too so no big deal..
What I have to do is go into supersu and turn root on and off as needed. A bit inconvenient but it works...

dharvey4651 said:
I'm actually quite pleased with performance and usability of my P607T with the stock 5.1.1 ROM installed. Everything works as expected except for that wifi issue and that's now fixed thanks to your info a few posts up.
I can't speak to whether or not the base code is the same or not I would imagine that the code is likely very similar if not the same because I had "[ROM][P605][5.0.2] Besonderes; a Touchwiz Lollipop ROM for Galaxy Note 10.1 2014 LTE" which is made for the P605 installed on my P607T and everything worked except wifi direct which is actually very important to me because my work program requires it.
Now I can't keep my tablet rooted because the program I use for work won't load with the tablet rooted. This has been the case since 4.4.4 too so no big deal..
What I have to do is go into supersu and turn root on and off as needed. A bit inconvenient but it works...
Click to expand...
Click to collapse
Good to know everything works well ...
Blue Cat has been sharing his source files and config and suggested some ways to compare P605 with P607T to figure out if they are the same or how similar they are. Its been a while since I tinkered with linux, but as and when I learn something, will update.

dharvey4651 said:
I'm actually quite pleased with performance and usability of my P607T with the stock 5.1.1 ROM installed. Everything works as expected except for that wifi issue and that's now fixed thanks to your info a few posts up.
I can't speak to whether or not the base code is the same or not I would imagine that the code is likely very similar if not the same because I had "[ROM][P605][5.0.2] Besonderes; a Touchwiz Lollipop ROM for Galaxy Note 10.1 2014 LTE" which is made for the P605 installed on my P607T and everything worked except wifi direct which is actually very important to me because my work program requires it.
Now I can't keep my tablet rooted because the program I use for work won't load with the tablet rooted. This has been the case since 4.4.4 too so no big deal..
What I have to do is go into supersu and turn root on and off as needed. A bit inconvenient but it works...
Click to expand...
Click to collapse
What process did you use to root p607t with 5.1.1?

dmunjal said:
What process did you use to root p607t with 5.1.1?
Click to expand...
Click to collapse
I followed the instructions from this linked thread, substitute p607t firmware for the p605 in step 1.
Key is to not let it auto reboot after Odin flashes twrp, if you miss that step then you have to reflash it as it will be overwritten.
Once you are in twrp then you flash supersu and boot up.
sandibhatt said:
I tried the instructions on Post 144 here: http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3215876/page15
It works without doing Step 1 (i.e. on the Stock Tmobile ROM)! All credit goes to @bluecat for doing the work and @M3r71n0 for the English translation!
Click to expand...
Click to collapse
I was never able to get Knox disabled from supersu and was constantly getting the security check notification(I had frozen parts of it in the past and now it won't thaw no matter what I have tried, FULL wipe and reflash, check w tibu and still frozen... No idea). I used titanium backup to freeze "securitylogagent" and everything has been fine since, including WiFi credentials sticking
Sent from my SM-P607T using Tapatalk

jayman350 said:
I was never able to get Knox disabled from supersu and was constantly getting the security check notification(I had frozen parts of it in the past and now it won't thaw no matter what I have tried, FULL wipe and reflash, check w tibu and still frozen... No idea). I used titanium backup to freeze "securitylogagent" and everything has been fine since, including WiFi credentials sticking
Sent from my SM-P607T using Tapatalk
Click to expand...
Click to collapse
Same here. Disabled the log agent.

6.0 Rolling Out For Canadian [Wind] XT1527!

Just got the notification now. Anybody interested? If so, a quick link, or a step by step on what's needed to pull this in for distro to all!?!? I have not dl'd yet, as I'm sure that's the first section to start with! :fingers-crossed:

I insteresa this update but unfortunately I have no knowledge to make a master eso.Espero help us forgiveness for my English so bad

I would like to try but my computer its broken

DSchwarz47 said:
I would like to try but my computer its broken
Click to expand...
Click to collapse
You would like to try what? What I was stating was my Moto E has an update available to 6.0 MM. I have not downloaded it as of yet, cause I am aware there's something you need to do first in order to capture the download for redistribution. From what I understand you cannot use an already downloaded and installed OEM~OTA update for redistribution...
A little guidance from the seniors would be EXTREMELY appreciated, as this is my first thread ever... I'm looking at you squid2 lolz

i am waiting for the 7th when Telus said they would roll it out.
Not sure how they make the uploaded Firmware archives either..
No matter how many time i asked i either got ignored or hammered with some weird advice (English issue?)
And i meant the one that we all use uploaded to Mega etc.
Who is making them and with what?
Apparently no one knows and what concerns me even more is a little thing called security.
I asked so uhhh why are we not using hashes to verify the firmware ?
It's complete insanity to check hashes on some dumb app and not your OS ..that just blows me away LOL

I'm interested in putting this on my Sprint phone (XT1526). CM13 won't detect my Canadian SIM.

24.51.39.en.CA
That's the fsent. Will upload in a few hrs.
Does anyone know if I'll be able /aloud to post a AFH link here on this thread I started?

Marshmallow v6.0 24.65.39 Telus XT1527 downloading now..
someone already ripped it into a standard package.
So OP you are in luck someone did the work for you :good:
I am downloading this one but there is one for Rogers too..
XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
http://www.filefactory.com/file/10v...0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
Source + Rogers version etc:
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2

lenigma1too said:
24.51.39.en.CA
That's the fsent. Will upload in a few hrs.
Does anyone know if I'll be able /aloud to post a AFH link here on this thread I started?
Click to expand...
Click to collapse
You were right
BUILD REQUEST INFO:
SW Version: surnia_retca-user 6.0 MPI24.65-39 25 release-keysM8916_2020629.41.03.21.51R
MBM Version: 80.20
Modem Version: M8916_2020629.41.03.21.51R
FSG Version: FSG-8916-02.61
Build Fingerprint: motorola/surnia_retca/surnia_umts:6.0/MPI24.65-39/25:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.51.39.surnia_retca.retca.en.CA
Model number: Moto E
Android Version: 6.0
Baseband Version: M8916_2020629.41.03.21.51R
Build Number: MPI24.65-39
Build Date: Thu Jan 28 14:25:13 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_telus_v1.1.nvm
Blur Version: Blur_Version.24.51.39.surnia_retca.retca.en.CA
Version when read from CPV: surnia_retca-user 6.0 MPI24.65-39 25 release-keys

I tried installing the Rogers firmware but stuck on boot animation. Help?
EDIT: I think I fixed it. Installed squid kernel r16.

xpmule said:
You were right
BUILD REQUEST INFO:
SW Version: surnia_retca-user 6.0 MPI24.65-39 25 release-keysM8916_2020629.41.03.21.51R
MBM Version: 80.20
Modem Version: M8916_2020629.41.03.21.51R
FSG Version: FSG-8916-02.61
Build Fingerprint: motorola/surnia_retca/surnia_umts:6.0/MPI24.65-39/25:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.51.39.surnia_retca.retca.en.CA
Model number: Moto E
Android Version: 6.0
Baseband Version: M8916_2020629.41.03.21.51R
Build Number: MPI24.65-39
Build Date: Thu Jan 28 14:25:13 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_telus_v1.1.nvm
Blur Version: Blur_Version.24.51.39.surnia_retca.retca.en.CA
Version when read from CPV: surnia_retca-user 6.0 MPI24.65-39 25 release-keys
Click to expand...
Click to collapse
Could you please lend a fellow Ontarian brother a hand, and tell me where the OTA file actually is? I've had the damn thing for a week now, and I can't seem to find it anywhere to capture it! I would love to actually install this OTA...
I do appreciate your help in finding somebody who had done the work already. However the OTA that I have waiting on this phone is a slightly different one. the numbers are different 24.51.39.... my educated guess is going to be it is slightly smaller because it contains no Rogers or Telus bloatware. Wind Mobile does not have a single app installed on this phone right outta the box, So I would like to capture it before I send it off to be installed.
I have read many of your posts across multiple threads, and you are obviously quite knowledgeable -> especially in the coding Department!

Are you sure it's going to install?
Once you Root it or various other custom changes the updates will not install.
It checks if you were tampering with the phone and will deny the update.. even if you can download it.
Thanks for the kind words but i am not sure off hand unless i search around.
One thing you try doing is search online etc with the words Blur, Update, Zip, Location
Or if you have a file manager with root you can search for it.
The benefit of the full packages available is they just install on any phone with no checks.
It's also not an update but the full installer.
So i think it's possible you may download an update with patches.
So it will see what you had before and patch those files.
Which could make saving & using the update again later problematic
..especially if you root !
If you upload it publicly we can check and see if it's a full install or a patch by looking at updater-script probably.
If i were you i would keep tabs on the Firmware repositories to see if the Wind package gets uploaded.
Then you will have a full install you can use coming from most others and with the security checks removed.
If you have something that can search your system files installed you can try searching for something that
will probably have Blur in the file name and be a flashable zip file.
If you have TWRP installed i think you can just load that and look around with the Built-In File Manager.
I am eating lunch so i might look on the web soon and check back here.. good luck.
Sorry i have not done it before so maybe someone who has can speak up or you can find one of their topics here.

The OTA update file is in the device main memory in data/data/com.motorola.ccc.ota/app_download

Thanks hedimahf i will save that for future reference.
Also lenigma1too i am pretty sure if you rooted your phone then you can not install that update.
Those type of updates are risky for us that customize our phones.. be careful.. make plans to fix it ahead of time
Unless my phone was stock (not rooted) with the default recovery and an original factory locked bootloader
i myself would not even attempt to install the update.
Google it and see the many people talking about BootLoop problems
I bet there is also little difference between Wind, Rogers or Telus aside from a couple small APK's and the Modem data stuff.
If all three have the same radio band support then i wouldn't worry too much about which one to use.
Although you may end up struggling to get your phone calls and text's etc working again if you switch like that.
The Telus one i tried just had 1 extra APK the "My Telus" app and a shortcut to it on the phone.. i uninstalled it with ease.
Other than that i did not see ANY other app's installed that were not standard on the USA/EU retail versions etc
EDIT:
Oh and the BootLogo was like on Lollipop but slightly more blue.
And the Boot animation was new too.. Marshmallow Telus has "Stitches World" video.
The default wallpapers and the collection of them were like on Lollipop too.
EDIT:
My point was the Telus firmware only had "branding" with that one app.
Otherwise the word Telus does not show up anywhere really.
Also i tend to compare packages so i am keeping my eye out so i can see what is different.
If you want i can PM you if i run across Wind version.

Can this be insstalled on a stock 5.1 xt1528? if so how? thanks

abispac said:
Can this be insstalled on a stock 5.1 xt1528? if so how? thanks
Click to expand...
Click to collapse
I don't think you understood what this topic was about.
He was asking how to capture an OTA update.
Didi you read what was said?

The needed flashing method?
xpmule said:
Marshmallow v6.0 24.65.39 Telus XT1527 downloading now..
someone already ripped it into a standard package.
So OP you are in luck someone did the work for you :good:
I am downloading this one but there is one for Rogers too..
XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
/file/10vpb6d09x43/XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
Source + Rogers version etc:
/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
Can those compiled zip files in filefactory website be installed using TWRP recovery or are they created to be installed using desktop ADB software only?
Click to expand...
Click to collapse

hedimahf said:
xpmule said:
Marshmallow v6.0 24.65.39 Telus XT1527 downloading now..
someone already ripped it into a standard package.
So OP you are in luck someone did the work for you :good:
I am downloading this one but there is one for Rogers too..
XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
/file/10vpb6d09x43/XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
Source + Rogers version etc:
/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
Can those compiled zip files in filefactory website be installed using TWRP recovery or are they created to be installed using desktop ADB software only?
Click to expand...
Click to collapse
They are intended to used with RSDLite or ADB.
They are found on the big Firmware topic(s) here. (first post over there for links)
You should check out the discussion going on for help with that on those topics for best information.
Putting Firmware from on model onto another may break your ability to make phone calls
and then you would have to try and fix it somehow and it starts to get complicated.
Which is why those other topics are so valuable.. good luck.
I repeat the 2 zip's mentioned are NOT flashable-zip's. (they are just a normal zip file for storage)
Click to expand...
Click to collapse

A new OTA rolled out for many users.
I found it in root /cache
I am working on restoring my phone to stock and applying it.
I don't see anyone making a non-sign firmware package so..
EDIT:
I got it installed now.. it says Patch Level DEC 1st 2016 (instead of February)
System version version 24.71.4
I guess i have to re-apply a ton of changes now

No Firmware available for S8 ATT

I have an unlocked S8 from ATT currently on T-Mobile with Android Version 7, i would like to upgrade to 9 but the CSC version for ATT doesn't seem to be available in updato or SamMobile, for some reason the ATT CSC its only available in samsung version SM-G950U1 but my device apparently its SM-G950U. Not sure what to do I'm new at this and don't want to brick my phone any further assistance its gladly appreciate it ! happy V-DAY ~~

zephirop said:
I have an unlocked S8 from ATT currently on T-Mobile with Android Version 7, i would like to upgrade to 9 but the CSC version for ATT doesn't seem to be available in updato or SamMobile, for some reason the ATT CSC its only available in samsung version SM-G950U1 but my device apparently its SM-G950U. Not sure what to do I'm new at this and don't want to brick my phone any further assistance its gladly appreciate it ! happy V-DAY ~~
Click to expand...
Click to collapse
You're stuck in AT&T's hellish 2017 view of the world in which its altered Android Nougat would not update automatically unless the phone had an AT&T SIM card on an active account. But no fear, all you have to do is upgrade to Oreo, by which time AT&T wasn't such an ass.
Go here https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817 for links to Samsung drivers and Standard Odin program and read the Prerequisites section and Flashing Standard Firmware. Thanks, Mike15678
Go here https://forum.xda-developers.com/att-galaxy-s8/how-to/g950u-stock-g950usqs2brb1-odin-files-t3757490 for link to BRB firmware (last version of Nougat). Thanks, bboii86
And go here https://forum.xda-developers.com/att-galaxy-s8/how-to/g950u-att-stock-odin-files-firmware-t3769147 for link to CRB firmware (first version of Oreo). Thanks again, bboii86
Download and update the Samsung drivers on your PC. Unpack the BRB and CRB packages in separate folders. Unpack Odin and fire it up. Follow Flashing directions in first link for BRB, then for CRB. If BRB stalls at 32% choose Wipe Cache Partition and then Reboot
Once you have CRB installed, you might have to manually update to the next step but it will be over-the-air from T-Mobile. T-Mo will shuffle you along to Pie after that, about a dozen firmware upgrades but easier than finding them on the interweb.

Similar - Already have Oreo and want to get to Pie
So my situation is a bit different, but not by much.
I have an unlocked S8 Active (SM-G892A) from AT&T. I am not on T-Mobile. BUT, I live overseas here in Germany now so its T-Mobile here. I am not sure if that matters.
I already have Android 8.0.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which I got last January (2019) before I moved here to Germany, but that was on AT&T. I still have my account with AT&T and the accompanying SIM (I switch SIMs when I travel back home to the States). But everytime I do, even if its for 2 or 3 weeks, no matter what I do to try and update it, it never does the OTA. The AT&T stores (when I am there) tell me something along the lines of 'it will come' or restart and wait, etc. So they are no use when I am there. And they certainly won't help me when I am here in Germany.
T-Mobile here tells me that I have to get it from AT&T and AT&T tells me to get bent. Your message above seemed to imply that I might be able to get it to "marry-up" with T-Mobile's networks so that I can get OTAs from them. DO you think that's possible for here in Germany too?
Update OTA doesn't work, but I am EXTREMELY new to this and do not want to brick my phone. I just want to get updates and Android 9 Pie. So I don't think I need all of the links/steps that you provided, but I have no clue.
Thanks!

SigEpMan said:
So my situation is a bit different, but not by much.
I have an unlocked S8 Active (SM-G892A) from AT&T. I am not on T-Mobile. BUT, I live overseas here in Germany now so its T-Mobile here. I am not sure if that matters.
I already have Android 8.0.0
which I got last January (2019) before I moved here to Germany, but that was on AT&T. I still have my account with AT&T and the accompanying SIM (I switch SIMs when I travel back home to the States). But everytime I do, even if its for 2 or 3 weeks, no matter what I do to try and update it, it never does the OTA. The AT&T stores (when I am there) tell me something along the lines of 'it will come' or restart and wait, etc. So they are no use when I am there. And they certainly won't help me when I am here in Germany.
T-Mobile here tells me that I have to get it from AT&T and AT&T tells me to get bent. Your message above seemed to imply that I might be able to get it to "marry-up" with T-Mobile's networks so that I can get OTAs from them. DO you think that's possible for here in Germany too?
Update OTA doesn't work, but I am EXTREMELY new to this and do not want to brick my phone. I just want to get updates and Android 9 Pie. So I don't think I need all of the links/steps that you provided, but I have no clue.
Thanks!
Click to expand...
Click to collapse
My roadmap is for a Galaxy S8 which is totally different software from the S8 Active. But the gist is the same. Search the forum for "G892A" to find the firmware updates.
I don't know which update package releases the S8 Active to cooperate with T-Mobile. Check the list of Previous Updates at the ATT website to figure out where your phone is and where it needs to go (add this to URL>>) devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1223303?make=Samsung&model=SamsungG892A
As I understand it, you won't brick your phone by upgrading firmware as long as you use non-beta firmware you find via XDA. After you update the baseband version you still might not get OTA in Germany, but perhaps it could work next time you're in the States. Good luck!

Similar - Already have Oreo and want to get to Pie
This is what it AT&T says I can UPGRADE to:
* Release date: March 10, 2020
* Android version: 9.0
* Security patch level (SPL): January 1, 2020
* Baseband version: G892AUCU5CTA2
* Build number: PPR1.180610.011.G892AUCU5CTA2
This is what I HAVE now:
* Android version: 8.0.0
* Security patch level (SPL): January 1, 2019
* Baseband version: G892AUCS3BSA1
* Build number: R16NW.G892AUCS3BSA1
**BUT** That baseband does NOT exist on that link (I already had it, that's how I found out that there was, somewhere on the planet, a patch to make it upgrade). The baseband I have is not in the previous listed ones. Its newer that about half and older than the other half.
I did a search for G892A and there was nothing that I could find. There was stuff for G892U, but that's not my case as that's a (US?) T-Mobile version of an S8 Active and mine is an AT&T version. From what I could tell, doing something for a "U" wont work for a "A".
Does that help you in any way to get me to the right place?
THanks!!!!

SigEpMan said:
This is what it AT&T says I can UPGRADE to:
* Release date: March 10, 2020
* Android version: 9.0
* Security patch level (SPL): January 1, 2020
* Baseband version: G892AUCU5CTA2
* Build number: PPR1.180610.011.G892AUCU5CTA2
This is what I HAVE now:
* Android version: 8.0.0
* Security patch level (SPL): January 1, 2019
* Baseband version: G892AUCS3BSA1
* Build number: R16NW.G892AUCS3BSA1
**BUT** That baseband does NOT exist on that link (I already had it, that's how I found out that there was, somewhere on the planet, a patch to make it upgrade). The baseband I have is not in the previous listed ones. Its newer that about half and older than the other half.
I did a search for G892A and there was nothing that I could find. There was stuff for G892U, but that's not my case as that's a (US?) T-Mobile version of an S8 Active and mine is an AT&T version. From what I could tell, doing something for a "U" wont work for a "A".
Does that help you in any way to get me to the right place?
THanks!!!!
Click to expand...
Click to collapse
Go to this thread >> // SM-G892A \\ Galaxy S8 ACTIVE **Stock Odin Firmware G892AUCU1AQG4**
But skip to post #187 on page 19 for the link to Baseband version G892AUCU5CSJ3. It's not the most current version but it will get you Pie and hopefully OTA updates after that. It takes a looong time to download the package. When you start up Odin, you don't need to fill in the userdata box; just load the BL, AP, CP and CSC files. I neglected to say, like everything on this site, I'm not responsible if something bad happens etc. Just extrapolating from my own experience. Happy updating!

Got a newer version from halabtech - the one AT&T is pushing
plunk99 said:
Go to this thread >> // SM-G892A \\ Galaxy S8 ACTIVE **Stock Odin Firmware G892AUCU1AQG4**
But skip to post #187 on page 19 for the link to Baseband version G892AUCU5CSJ3. It's not the most current version but it will get you Pie and hopefully OTA updates after that. It takes a looong time to download the package. When you start up Odin, you don't need to fill in the userdata box; just load the BL, AP, CP and CSC files. I neglected to say, like everything on this site, I'm not responsible if something bad happens etc. Just extrapolating from my own experience. Happy updating!
Click to expand...
Click to collapse
First off, THANKS! Secondly, I saw you post and I will do that based on your responses to these 2 questions:
1) Do I have to update in the order that AT&T put them out, or can I go straight to the one to be the final?
2) In another post, I was directed to the halabtech site. They did indeed have the most current baseband that AT&T just announced on their website. Are you recommending baseband above because it will get me to something that T-Mobile here in Germany might start pushing OTA updates, or would the halabtech one (which I already downloaded) do the same thing - basically, was your baseband meant to break the AT&T link to get other updates elsewhere?
The only reason I ask is because the never sold the Active here in Europe, so I don't know if the OTAs will be for just this region, or that updates are updates, globally. I am not a cell guy, so I have no way of knowing.
But again, THANKS!!!!!

SigEpMan said:
First off, THANKS! Secondly, I saw you post and I will do that based on your responses to these 2 questions:
1) Do I have to update in the order that AT&T put them out, or can I go straight to the one to be the final?
2) In another post, I was directed to the halabtech site. They did indeed have the most current baseband that AT&T just announced on their website. Are you recommending baseband above because it will get me to something that T-Mobile here in Germany might start pushing OTA updates, or would the halabtech one (which I already downloaded) do the same thing - basically, was your baseband meant to break the AT&T link to get other updates elsewhere?
The only reason I ask is because the never sold the Active here in Europe, so I don't know if the OTAs will be for just this region, or that updates are updates, globally. I am not a cell guy, so I have no way of knowing.
But again, THANKS!!!!!
Click to expand...
Click to collapse
1) I'm not sure whether you can skip versions. For my AT&T S8 (regular not active) a post told me to first install the BRB package (last Android Nougat) then the CRB (first Oreo). Then T-Mobile started pushing a bunch of OTA updates (and actually skipped a few versions on its own).
But you are already on Oreo, so I don't know which baseband version gets you past the AT&T block on carrier switching. I pointed you to the CSJ package hoping it would work but don't know for sure if it will. If it fails to update your phone, you'll have to find and download a version maybe halfway between your current version and CSJ and keep your fingers crossed. And even if CSJ does work, I don't know that T-Mobile will OTA it from there. But if it doesn't, the next time you are in the U.S. hopefully AT&T or T-Mobile would update it automatically.
2) I don't know anything about halabtech, but just a quick glance shows me it's in Egypt and has lots of stuff for Mideast phones. Another reason I suggested the CSJ package is because it's on XDA, which I trust because it helped me solve my problem. There's really not much difference between CSJ and CTA, just a couple of month's worth of security patches, as opposed to the huge difference between CSJ and what's on your phone now.

Similar - I have Oreo but I can't get Pie.
I have an unlocked Galaxy S8 (SM-G950U) and I'm using it on an Indian carrier. I can't get OTA updates since I don't have an AT&T sim. I checked SamMobile for firmware updates but couldn't find one for SM-G950U. I want to update to Pie and get One UI features but I couldn't. What should I do?
What I have is:
- Android 8
- Security Patch Level: January 1, 2019.
- Baseband Version: G950USQU5CSA4.

[OneUI 4.0 Beta] [Now Rolling Out!!] Galaxy S20/+/Ultra Beta Thread, Update.zip files.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Galaxy S20 series OneUI 4.0 Android 12 Beta Thread.
The beta program has now started in the UK, India, The US and Korea
UPDATE:
As of 23rd of November:
[Beta 2 is now rolling out in the UK!]
Always check post #2 to see the latest update.zip links when available.
-This thread will be for sharing tips and help and update.zip/.bin files (when/if available) for the OneUI 4.0 Android 12 Beta for the Galaxy S20 series (Unlocked/Exynos-Snapdragon)
Eligible models:
Exynos:
-Galaxy S20 (SM-G980F)
-Galaxy S20 5G (SM-G981B)
-Galaxy S20+ (SM-G985F)
-Galaxy S20+ 5G (SM-G986B)
-Galaxy S20 Ultra LTE/5G (SM-G988B)
Snapdragon:
USA VARIANT:
-Galaxy S20 5G (SM-G981U1)
-Galaxy S20+ 5G (SM-G986U1)
-Galaxy S20 Ultra 5G (SM-G988U1)
KOREAN VARIANT:
-Galaxy S20 5G (SM-G981N)
-Galaxy S20+ 5G (SM-G986N)
-Galaxy S20 Ultra 5G (SM-G988N)
Installation Methods:
ADB-method:
1. Download SDK platform tools https://developer.android.com/studio/releases/platform-tools
2. Extract the file in your desktop.
3. Inside the extracted folder, put the update.zip file you downloaded.
4. Inside this folder, holding left shift, do a right click with the mouse and select "open command prompt here", The command prompt will open.
5. Shutdown your phone and connect it to your pc with an original cable
6. Holding power and volume up buttons, enter into recovery mode.
7. Select "update via ADB". (scroll down using the volume buttons and select using the power button).
8. Connect the phone to a PC using an original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options on your pc you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Connect any USB device to your device, AKG earphones could work, then press Power+volume up buttons to get into recovery mode.
5. Using your volume keys navigate to "update via sdcard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes installing. It will take some time.
8. Phone will reboot by itself and load android.
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
There are two methods that you can use to get into recovery mode:
Method 1:
1. Connect your phone to your PC (Make sure USB debugging is on).
2. Using ADB, enter the command ./adb reboot recovery
3. Wait a little and you should be in recovery mode.
Method 2:
1. Power off your device
2. Connect your device to a PC or connect the AKG earphones.
3. Hold down Power+VolumeUp buttons and keep pressing them until you enter recovery mode.
How to capture the update.bin file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Leave the app and go to the settings and Start the software update in settings by pressing "download" and don't pause it
4. Go back to canary app and start it by pressing the little circle at the bottom right, and it will grab the link for you
5. Copy the link and post it here if you wish.
This will not trip knox if done by the methods above
Don't install a beta unless you are fully aware what you are going into.
Don't install the beta if you want your phone to be stable, IT'S a BETA.
It's recommended to make a backup of your data before updating to the Android 12 Beta.
Important Notes:
-Rename the .bin file to update.zip in order to be able to flash it from recovery.
-A common mistake done by some people is that they see the file named update while its a WinRAR.zip file already, then they add another .zip making the name of the file update.zip.zip which will not be flashed successfully, So make sure you do it right.
-Updating to the beta is AT YOUR RISK, No one is responsible if anything goes wrong.
You will not receive OTAs again UNTIL you are on a firmware that gets released later for your original CSC, thats most likely not happening before the BETA is over.
Small note:
My Galaxy S20 Ultra isn't from a country that has a beta program, I manually changed the CSC to DBT, that makes me receive DBT OTA Updates but participating in the beta in the past years, needed a sim card from the country of your CSC, Meaning i need a german SIM to be able to participate, so sadly i will not be able to pull the update.zip file unfortunately, But i will try my BEST to keep the thread updated with the latest beta update.zip file (If/when someone pulls it)

Update.zip Files:
Exynos:
S20 Ultra 5G (SM-G988B):
Beta 1 DUJ5->ZUK1 (Huge thanks to @LeeXDA18)!
Beta 2 ZUK1->ZUKA (Thanks to @LeeXDA18)!
S20+ 5G (SM-G986B):
Beta 1 DUJ5->ZUK1 (Thanks to @mefistos)!
Beta 2 ZUK1->ZUKA (Thanks to @mefistos)!
S20+ LTE (SM-G985F):
Beta 1 DUJ5->ZUK1 (Thanks to @corsicanu)!
Beta 2 (UK) ZUK1->ZUKA (Thanks to @corsicanu)!
Beta 2 (India) ZUK1->ZUKA (Thanks to @evil22)!
Final Build ZUKA->EUL6 (Thanks to @evil22)!
S20 5G (SM-G981B):
Beta 1 DUJ5->ZUK1 (Thanks to @LeeXDA18)!
Beta 2 ZUK1->ZUKA (Thanks to @LeeXDA18)!
S20 LTE (SM-G980F):
Beta 1 DUJ5->ZUK1 (Thanks to reddit user @adityadbz)!
Beta 2 ZUK1->ZUKA (Thanks to @adityadbz)!
Final Build ZUKA->EUL6 (Thanks to @adityadbz)!
Snapdragon:
(US Version):
S20 Ultra 5G (SM-G988U1):
Beta 1 DUJ7->ZUK7 (Thanks to @dinopeyton)!
Beta 2 ZUK7->ZUKB (Thanks to @dinopeyton)!
Beta 3 ZUKB->ZUL1 (Thanks to @dinopeyton)!
S20+ 5G (SM-G986U1):
Beta 1 DUJ7->ZUK7 (Thanks to @iHateCrapple)
Beta 2 ZUK7->ZUKB (Thanks to @iHateCrapple)!
Beta 3 ZUKB->ZUL1 (Thanks to @iHateCrapple)!
S20 5G (SM-G981U1): Not Available.
(Korean Version):
S20 Ultra 5G (SM-G988N):
Beta 1 EUI4->ZUK6 (Thanks to @3arthur6)!
Beta 2 ZUK6->ZUKC (Thanks to @3arthur6 and @zwenchao_1989)!
Beta 3 ZUKC->ZUL2 (Thanks to @zwenchao_1989)!
Final Build ZUL2->FUL9 (Thanks to @3arthur6)!
S20+ 5G (SM-G986N):
Beta 1 EUI4->ZUK6 (Thanks to @zwenchao_1989)!
Beta 2 ZUK6->ZUKC (Thanks to @zwenchao_1989)!
Beta 3 ZUKC->ZUL2 (Thanks to @zwenchao_1989)!
S20 5G (SM-G981N):
Beta 1 EUI4->ZUK6 ( Thanks to @zwenchao_1989)!
Beta 2 ZUK6->ZUKC (Thanks to @zwenchao_1989)!
Beta 3 ZUKC->ZUL2 (Thanks to @zwenchao_1989)!

Will you also open a thread for S10+ Android 12 One Ui 4.0 beta update.zip

Marvfit213 said:
Will you also open a thread for S10+ Android 12 One Ui 4.0 beta update.zip
Click to expand...
Click to collapse
Yeah i'm planning on making one, but i'm not sure if samsung is planning on doing a beta for the s10 series, i hope they do. I"ll make a thread in the coming days in the S10+ forum just for case.

I really hope there will be someone who has DBT/BTU CSC that shares Update.zip links when the beta comes out. Would be much appreciated.
Also, Does anyone think there is a way to bypass the your sim card is not from your country service provider message that used to come up in the samsung members app in the last years?

What... No Snapdragon love??

AhmedMomen said:
Yeah i'm planning on making one, but i'm not sure if samsung is planning on doing a beta for the s10 series, i hope they do. I"ll make a thread in the coming days in the S10+ forum just for case.
Click to expand...
Click to collapse
Ok
Im sure samsung do a beta for S10 series

WuNgUn said:
What... No Snapdragon love??
Click to expand...
Click to collapse
If sb else doesn't create a thread for the SD models i might do it myself, but i don't think it's a good idea to have them both in the same thread, last year this was the case here in the S20 forum and they later divided the thread and made a new thread for the snapdragon models and kept the old one for the exynos.

AhmedMomen said:
I really hope there will be someone who has DBT/BTU CSC that shares Update.zip links when the beta comes out. Would be much appreciated.
Also, Does anyone think there is a way to bypass the your sim card is not from your country service provider message that used to come up in the samsung members app in the last years?
Click to expand...
Click to collapse
At least with root, it's possible to fake your service carrier and register to the beta.
I already done this for the S8 android 10 beta and will try again with my imported korean S20U.
Apps like Android Market Enabler does the job
Edit: service carrier has to match with csc to register

3arthur6 said:
At least with root, it's possible to fake your service carrier and register to the beta.
I already done this for the S8 android 10 beta and will try again with my imported korean S20U.
Apps like Android Market Enabler does the job
Edit: service carrier has to match with csc to register
Click to expand...
Click to collapse
Do you think I could get a esim from Germany to sign up for beta program or do I need a physical sim card?

Aussiegeek420 said:
Do you think I could get a esim from Germany to sign up for beta program or do I need a physical sim card?
Click to expand...
Click to collapse
Not sure about esim
But an old sim card without active mobile plan should do the trick too

3arthur6 said:
At least with root, it's possible to fake your service carrier and register to the beta.
I already done this for the S8 android 10 beta and will try again with my imported korean S20U.
Apps like Android Market Enabler does the job
Edit: service carrier has to match with csc to register
Click to expand...
Click to collapse
Yeah that could work but i'm not really into root sadly, And i think i cannot really get german sim cards here unfortunately. Although i really wanted to share update.zip files when the beta comes out as i already share update.zip links for the monthly DBT OTA updates, But yeah i guess i have to hope that someone with a DBT SM-G988B and a German SIM card who's willing to participate in the beta shares the links with us.

It could be literally months before we see a S20 series update. Likely will release as final...
Did Samsung run a beta program for older flagship hardware last year? Or just release final?

WuNgUn said:
It could be literally months before we see a S20 series update. Likely will release as final...
Did Samsung run a beta program for older flagship hardware last year? Or just release final?
Click to expand...
Click to collapse
S10 got first beta 11 on 25th Nov.2020
S20U got first beta 11 on 15th Oct.2020

brouwerchris said:
S10 got first beta 11 on 25th Nov.2020
Click to expand...
Click to collapse
AH yes.... I remember now.
Thanks

Hi everyone, without sim with wifi the beta does not receive it anyway if the phone has the German csc?

cosimo66 said:
Hello everyone, without sim and wifi the beta does not receive it anyway if the phone has german csc?
Click to expand...
Click to collapse
The case in the last years has been that if you don't have a SIM card that matches your CSC, (if it's BTU then you need to have a UK sim, if it's DBT you must have German sim, etc) you will not be able to enroll officially through samsung members
If somebody else catches Update.zip file though, you can install it manually.

A LOT of Galaxy and Samsung devices getting September security update tomorrow/this/last week...
Maybe this is what Samsung has been waiting on before releasing beta to S20 series....

WuNgUn said:
A LOT of Galaxy and Samsung devices getting September security update tomorrow/this/last week...
Maybe this is what Samsung has been waiting on before releasing beta to S20 series....
Click to expand...
Click to collapse
Yeah also the S21 Ultra is even getting october patch.
I can't help but notice, There hasn't been any leaks about samsung testing A12 for the S20 Series, which probably means we could be not less than 3 weeks away from a beta release which kinda sucks tbh.
I hope they surprise us and release it next week or the one after it, and maybe after all they have been testing it internally in secret for a while now and we don't know. We"ll see.

Latest test firmware of the G988N from today : G988NKSU1FUI2
Since the latest public release is G988NKSU1EUH1 and so the E goes to F, this firmware is a OneUI 4 test.
This explains why the korean S20 serie has not yet received the september firmware.