Database Develop

unable to apply Android 5.1 OTA (not rooted)

Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?

carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?

Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.

carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.

Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan

carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.

Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan

carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.

OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.

Why is my Nexus 6 not receiving updates?

I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!

Aniket Sarkar said:
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Click to expand...
Click to collapse
seriously?? your regretting it ??
you need patience...
patience....
patience....

I think I've mentioned that I'm not even getting 5.1, okay not even 5.0.1
Can someone please understand the level of problem I'm facing?
I've already mentioned while others are at 6.0, I'm not going anywhere ahead of 5.0
Please help!

Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.

im on my 3rd day on my nexus.. but im not losing hope.. im still waiting for the ota.. its on 5.1 lmy47d...

So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps

Same, stuck on 5.1 LMY47D

google gives us factory images for a reason. if you arent patient enough to wait for an ota, just flash a factory image yourself, instead of starting threads about how you arent getting an ota. whats the point of a thread about you not getting an ota?

snoprosledneck88 said:
....I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING.
Click to expand...
Click to collapse
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file

jj14 said:
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
Click to expand...
Click to collapse
Your right, I'm sorry. That's what I meant to say.
Sent from my Nexus 6 using Tapatalk

I got mine today and its on android 5 Doesn't want to update either, keeps saying its up to date. Haven't done anything yet with the phone. Looking now how ADB Sideload works.

jj14 said:
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
Click to expand...
Click to collapse
I've bought it from an online retailer Flipkart in India.
I'm sure there's no changes made in phone and it's original and is as a new nexus 6 should be. Just this software update is causing me problems

snoprosledneck88 said:
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Click to expand...
Click to collapse
Well I'm damn impatient, if I'd 5.1.1 and waited for 6.0 I'd have definitely had some patience, but waiting from 5.0 doesn't make sense.
Anyways to the point, after listening to your story, I tried same thing, clearing cache and reset from recovery mode, but still it didn't help
Hope there's some other resolution to this now.

I suspect it was your post that I responded to, at another forum - but you have two options really
1. Unlock bootloader (wipes data), and flash latest image
2. ADB Sideload OTAs one after the other in the right sequence (see http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 for OTA URLs) - check your current build and choose a path to get to the build you want

I am having the same problem.
I am having the same problem. Have you tried resetting the phone and starting it without the sim?

Nexus 6 not updating

I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?

entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk

If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.

Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.

entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.

The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.

Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app

When Will I get Android 7.0 OTA?

Hello all, I have a Nexus 6 and I'm using it on Verizon's network. I have yet to receive the Android 7.0 OTA update. Should I have gotten this already or is there something possibly wrong with my situation? I've searched online and it seems like I should have gotten the update already. I appreciate any help.

You should have had it by now (unless you have modified your phone in any way that might interfere with the OTA process)
Your best bet would be to sideload the OTA from https://developers.google.com/android/ota

Yeah, it's a bone stock Nexus 6. I got it from Amazon around this time last year, and I received the 6.0.1 OTA update and I receive the android security patch updates. Just no update to 7.0.

When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.

I think that there are a lot of N6 (mine is on T-mobile) out there that have not seen an OTA. I got the 6.01 November secuity patch last week. Was expecting 7.0.

I went ahead and did a sideload of the OTA 7.0. This won't break any future OTA updates, will it?

xdatastic said:
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
Click to expand...
Click to collapse
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.

russ4h said:
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
Click to expand...
Click to collapse
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/

xdatastic said:
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
Click to expand...
Click to collapse
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?

russ4h said:
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
Click to expand...
Click to collapse
Nope, the sideload doesn't break future OTA updates (however it theoretically could if you flashed a build not intended for your carrier, however usually Google just send a 'Full OTA' which a large download to your device to get it back on the correct build).
Enjoy.

I was offered 7.0 and it took rooted
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.

tbared said:
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
Click to expand...
Click to collapse
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.

I joined (then left) the Beta program so i can get a stable release of 7.0 Nougat a little over a month ago. Good so far but what I'm concerned about is security patches. Ever since I got on Nougat, my N6 no longer gets OTA security patches. I'm still on the October security patch. Anyone know what's going on?

Regardless, even with a mod'd phone, I got the 7.0 nag 2 weeks ago - which spurred me to wipe everything and flash it with NRT.

alryder said:
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
Click to expand...
Click to collapse
Thanks as soon as i have some time i will reinstall and flas..

T-Mobile Galaxy Note 9 will begin getting Android Pie update today

https://www.tmonews.com/2019/03/t-mobile-galaxy-note-9-android-pie-update/
From the source :good:
Good News for those who have waited, according to t-Mobile news
""Following the T-Mobile Galaxy S9 and S9+ getting Android Pie a couple of weeks ago, it’s now the Galaxy Note 9’s turn to get a piece of Pie.
T-Mobile has updated its Galaxy Note 9 support page to show that the Android 9.0 Pie update will begin rolling out today, March 1st. The update is version N960U1UEU1CSB3 and is 1671.6MB in size.
In addition to Android 9.0 Pie, Galaxy Note 9 customers can expect Samsung’s new One UI user interface. It includes an updated look that moves interactive elements toward the bottom of the screen so they’re easier to reach, which should be especially useful on the Note 9 and its 6.4-inch screen. Samsung has added a night mode to its One UI as well.
Also included in this update is a new e911 call flow, says T-Mobile, along with a compass calibration fix and a BYOD update.
T-Mo does say on its Note 9 support page that the update “will not be available to all customers right away”, so it may take a few days to make its way to your phone. If you’d like, you can manually check for the update by going into Settings > Software update > Download updates manually. Be sure to let us know when your T-Mobile Galaxy Note 9 gets its Android Pie update!""

Does anyone know what the "BOYD update" means?

microbespecialty said:
Does anyone know what the "BOYD update" means?
Click to expand...
Click to collapse
"BYOD" Bring your own device.

rsfinsrq said:
"BYOD" Bring your own device.
Click to expand...
Click to collapse
Sorry. I should be more specific. I know what BYOD means. The question I am trying to ask is what exactly does this update do with regards to "BYOD update"?

microbespecialty said:
Sorry. I should be more specific. I know what BYOD means. The question I am trying to ask is what exactly does this update do with regards to "BYOD update"?
Click to expand...
Click to collapse
Hopefully this will answer your question;
https://www.samsung.com/us/support/answer/ANS00078492/

I was already updating just under 3 hours ago. I dislike the location of the time clock, how they moved it to the left side. I hope there's a fix.

rsfinsrq said:
Hopefully this will answer your question;
https://www.samsung.com/us/support/answer/ANS00078492/
Click to expand...
Click to collapse
Oh bummer. So this means there will be the pink T Mobile start up screen and all that? That's what happened when I brought a Verizon S8 over to The Mobile. Replacing Verizon's red start up screen with T Mobile's is not a huge deal, but I'd rather not get it on my unlocked Note 9.
Guess I'll have to see when the Pie update rolls out to unlocked Note 9s.

microbespecialty said:
Oh bummer. So this means there will be the pink T Mobile start up screen and all that? That's what happened when I brought a Verizon S8 over to The Mobile. Replacing Verizon's red start up screen with T Mobile's is not a huge deal, but I'd rather not get it on my unlocked Note 9.
Guess I'll have to see when the Pie update rolls out to unlocked Note 9s.
Click to expand...
Click to collapse
I believe you will get the T-Mobile boot screen and a couple T-Mobile bloat apps.

microbespecialty said:
Oh bummer. So this means there will be the pink T Mobile start up screen and all that? That's what happened when I brought a Verizon S8 over to The Mobile. Replacing Verizon's red start up screen with T Mobile's is not a huge deal, but I'd rather not get it on my unlocked Note 9.
Guess I'll have to see when the Pie update rolls out to unlocked Note 9s.
Click to expand...
Click to collapse
The BYOD features such as carrier boot screen only applies to the carrier branded models. The unlocked U1 models will remain unbranded when switching carriers.
---------- Post added at 08:04 AM ---------- Previous post was at 07:52 AM ----------
rsfinsrq said:
Hopefully this will answer your question;
https://www.samsung.com/us/support/answer/ANS00078492/
Click to expand...
Click to collapse
Sweet. Been trying to explain this to people. Didn't think to look for an official Samsung document!

I have seen reports that the update will apply carrier specific apps and boot screen based on the sim card you have inserted at the time of updating.
See this thread;
https://forum.xda-developers.com/galaxy-note-9/how-to/n960usqu1csaa-official-ota-update-pie-t3895831

rsfinsrq said:
I have seen reports that the update will apply carrier specific apps and boot screen based on the sim card you have inserted at the time of updating.
See this thread;
https://forum.xda-developers.com/galaxy-note-9/how-to/n960usqu1csaa-official-ota-update-pie-t3895831
Click to expand...
Click to collapse
Only on the carrier branded models. It will NOT apply a carrier boot screen to the unbranded models. They have a different build number.
The T-Mobile document listed the wrong build number for their release. T-Mobile pushed N960USQU1CSB3.
The unlocked, unbranded U1 model will get N960U1UEU1CSB3 (most likely).

Mr. Orange 645 said:
The unlocked, unbranded U1 model will get N960U1UEU1CSB3 (most likely).
Click to expand...
Click to collapse
Meanwhile, can N960USQU1CSB3 be flashed to the N960U1?

Gary02468 said:
Meanwhile, can N960USQU1CSB3 be flashed to the N960U1?
Click to expand...
Click to collapse
Yes it can. Use Patched ODIN and flash the full firmware file. Just realize you will get carrier bloat such as the carrier boot screen and preloaded apps.

Mr. Orange 645 said:
Yes it can. Use Patched ODIN and flash the full firmware file. Just realize you will get carrier bloat such as the carrier boot screen and preloaded apps.
Click to expand...
Click to collapse
Great, thanks! And if I do flash N960USQU1CSB3 to my SM-N960U1, can I keep my apps, data, and settings (similar to an OTA update) if I use CSC_HOME?

Gary02468 said:
Great, thanks! And if I do flash N960USQU1CSB3 to my SM-N960U1, can I keep my apps, data, and settings (similar to an OTA update) if I use CSC_HOME?
Click to expand...
Click to collapse
Most likely, but back up everything just in case. I recommend back up with Samsung Cloud and Smart Switch.

Mr. Orange 645 said:
Most likely, but back up everything just in case. I recommend back up with Samsung Cloud and Smart Switch.
Click to expand...
Click to collapse
Flashing my unlocked SM-N960U1 to N960USQU1CSB3 went smoothly and the new firmware shows up as Official in the Settings|Status. All my data and apps were preserved, just like an OTA update.
However, if I try now to check manually for OTA updates, then after it says "Checking for updates..." for a few seconds, instead of then telling me I'm up-to-date, it says "Your current software version isn't supported. Visit a service center."
Does that mean I'm not going to get the next OTA update? And if so, is there any way to fix it? (My model number is now listed as SM-N960U, and service provider SW ver is TMB/TMB/XAA.)

Gary02468 said:
Flashing my unlocked SM-N960U1 to N960USQU1CSB3 went smoothly and the new firmware shows up as Official in the Settings|Status. All my data and apps were preserved, just like an OTA update.
However, if I try now to check manually for OTA updates, then after it says "Checking for updates..." for a few seconds, instead of then telling me I'm up-to-date, it says "Your current software version isn't supported. Visit a service center."
Does that mean I'm not going to get the next OTA update? And if so, is there any way to fix it? (My model number is now listed as SM-N960U, and service provider SW ver is TMB/TMB/XAA.)
Click to expand...
Click to collapse
I'm on T-Mobile and mine just says I'm up to date. Not sure why it would say your software version isn't supported. You may need to factory reset since you went from U1 to U firmware.

Mr. Orange 645 said:
I'm on T-Mobile and mine just says I'm up to date. Not sure why it would say your software version isn't supported. You may need to factory reset since you went from U1 to U firmware.
Click to expand...
Click to collapse
Oh well. I was hoping to avoid that. What if I flash the CSC_OMC instead of HOME_CSC? I've read that for TMO, CSC_OMC won't cause a factory reset. Do you think it might fix the update problem?
Alternatively, if I wait for the unlocked version of CSB3 and then flash that, would that return my device to being able to receive future unlocked OTAs?

Gary02468 said:
Oh well. I was hoping to avoid that. What if I flash the CSC_OMC instead of HOME_CSC? I've read that for TMO, CSC_OMC won't cause a factory reset. Do you think it might fix the update problem?
Alternatively, if I wait for the unlocked version of CSB3 and then flash that, would that return my device to being able to receive future unlocked OTAs?
Click to expand...
Click to collapse
You can try CSC_OMC. It used to cause a factory reset, but I've also heard it doesn't anymore.
If you go back to the U1 firmware when Samsung released Pie, then it should put you back on OTA path, but again you may need to factory reset.

Mr. Orange 645 said:
You can try CSC_OMC. It used to cause a factory reset, but I've also heard it doesn't anymore.
If you go back to the U1 firmware when Samsung released Pie, then it should put you back on OTA path, but again you may need to factory reset.
Click to expand...
Click to collapse
If I try CSC_OMC now, would I flash that by itself (having already flashed the other components), or would I reflash everything over again? And would I still omit USERDATA?
Update 1: I did flash CSC_OMC by itself now, and it didn't wipe my apps or data, but it also didn't fix the OTA-check problem.
Update 2: I did a factory reset. Now the software update properly says up-to-date.