Database Develop

since i'm rooted and can't get OTA's???

I understand that by being BL unlocked and rooted, I won't be able to get OTA's, and that I will have to flash any updates I want myself. I'm ok with that. What I don't know since I'm new to the Nexus world (I was a rom flashing madman with my Galaxy Note 2), is how to tell when there's a new update to flash, and where to find it. For example, Google's "factory images" web site currently showsLRX210, which is the build on my unlocked and rooted N6.
Does that mean there are no updates available yet?
Or will updates come in small pieces that do not alter the build number?
And where will we find factory updates? Over at Google's factory images site?
-Peter

pcrussell50 said:
I understand that by being BL unlocked and rooted, I won't be able to get OTA's, and that I will have to flash any updates I want myself. I'm ok with that. What I don't know since I'm new to the Nexus world (I was a rom flashing madman with my Galaxy Note 2), is how to tell when there's a new update to flash, and where to find it. For example, Google's "factory images" web site currently showsLRX210, which is the build on my unlocked and rooted N6.
Does that mean there are no updates available yet?
Or will updates come in small pieces that do not alter the build number?
And where will we find factory updates? Over at Google's factory images site?
-Peter
Click to expand...
Click to collapse
Yes you're on the latest updated firmware. As far as taking otas it's my understanding you may be able to take them as long as you put the stock recovery back on your phone instead of Twrp. Not sure myself, haven't tried it.
You can still check for updates using the System Update feature so you can keep track that way.
Devs may also create flashable zips of Ota's as well, so that may be another option in the future. This is also my first Nexus and this is my understanding of how things will be progressing.

pcrussell50 said:
how to tell when there's a new update to flash, and where to find it.
Does that mean there are no updates available yet?
Or will updates come in small pieces that do not alter the build number?
And where will we find factory updates? Over at Google's factory images site?
Click to expand...
Click to collapse
You'll be prompted if there's an update unless you disable the prompts.
If the build number on your phone matches an image they're the same.
Images released by Google will be on their factory image page.
Sometimes factory images that have not been posted by Google are posted by other parties.

[Q] OTA Requires Carrier Approval ?

My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
As for who handles updates, it all comes from Google, no matter what. However, Google will withhold updates based on SIM card pending carrier approval. AT&T has not approved Android 5.1 yet, and therefore, anyone with an AT&T SIM card in their Nexus 6, no matter where it was purchased, will not be offered the OTA until AT&T approves it. So far, the only US carriers to approve Android 5.1 are T-Mobile and Sprint.
Click to expand...
Click to collapse
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...

clairez said:
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Yeah this is a new thing. Ridiculous. Its never been tied to SIM provision before.

clairez said:
My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Based on recollection, a few. But not many. And yes, AT&T is definately trying to control updates. I suspect Verizon will, too.
Based on the following article, I doubt that you will ever get a Verizon specific OTA on your device > http://www.androidpolice.com/2015/0...te-one-that-wasnt-purchased-from-the-carrier/

No mine would only update to 5.01. GPS N64.

Maybe pull Sim card reboot and check via only WiFi?

dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
You might get D this way, but not E.

dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
That didn't work for me - I had to also perform a factory reset to get the "D" OTA (tried this yesterday). I'm on Verizon with a Nexus 6 bought directly from Motorola.
At least this thread sort of answers my question posed in the linked post above. However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
I've been thinking of staying stock for awhile, due to expectations of quick-from-Google OTAs . . . but, this is driving me to consider custom ROMs and not looking back.
- ooofest

ooofest said:
However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
Click to expand...
Click to collapse
I'm not sure about this, but when you pull your SIM, I think Google sees it as a generic N6 via WiFi. So if you do generate an OTA download, it's the general one.

I wonder if you have to put another SIM card in. I know in Play, my device shows as a carrier, even though its a play store device. I imagine you'd have to use another sim in it to allow that sim to be "registered" with Google, to "overwrite" the previous one. I doubt there is anything you can clear to do that.

Pulling The String !
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...

@clairez,
Very good post, and summarized very concisely.

I got mine thru VZ, this is most likely the only time I'll ever say this about them - At least they released it, though being late to the party, with 5.1 already installed.
(I feel so bad for those who may have bricked trying the OTA or image and running into issues ...)
As to how they will affect us moving forward, I'm crossing my fingers, but while I hate it, let me play devil's advocate here, they didn't place a boot animation, sounds, or other oem crap on it, there are the small system services, but that's the same amongst all of the N6's. and the tramp stamp was easily removed aka ATT's.
So far, it could have been way worse as far as getting one from VZ, but I feel for you guys that had it early and are now waiting on them to get an OTA, or even have the unit register correctly on their systems.
But the overall answer to the overall thing, is that if they did hold up updates down the road, we do what any crackflasher would, flash the image when released, right? Why we got the thing in the first place

This emerging situation where carriers apparently delay our Nexus 6 OTA timings is leading me to stay on the flashing path.
Running stock and locked 5.1 E for now, might just run unlocked and accept potential decrease in local security to minimize danger in future flashes. I like stock so far, but being unlocked will probably tempt me to root and try custom ROMs, I expect.
If Verizon wanted us to stay on the pure OTA path with this phone, they don't appear to be showing that intent.
- ooofest

clairez said:
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...
Click to expand...
Click to collapse
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?

gunit34328 said:
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?
Click to expand...
Click to collapse
You don't need to re-lock your bootloader. Otherwise, yes on the others.

Evolution_Freak said:
You don't need to re-lock your bootloader. Otherwise, yes on the others.
Click to expand...
Click to collapse
thank you for your reply!

gunit34328 said:
thank you for your reply!
Click to expand...
Click to collapse
No problem at all.

just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on

dansan382 said:
just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on
Click to expand...
Click to collapse
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.

Evolution_Freak said:
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.
Click to expand...
Click to collapse
im sorry, you're right.. it was 5.0.1 because it was LRX22C.. my bad.

New Nexus 6 with no available updates (stuck on old 5.1)

Hello guys. Just bought 2 days a go a new Nexus 6. Blue with 32Gb, unlocked.
Tottaly sealed, broke the seal myself, straight from Google.
But the phone says it is updated, and finds no new update. Im on LMY47D with Android 5.1 and I dont even receive 5.1.1
Tried factory reset without SIM Card, cleaning Framework and reboot without card, everything. To no avail.
Any idea what is going on? Shouldnt I get at least Android 5.1.1?
PS: I know I can sideload it, but still, something is clearly wrong, and I would like very much to sort it out.
Thank you very much.

Same issue here. Only I'm on 5.0 and can't find any update and I would prefer to not sideload already.

if you want your phone to check for an update, you have to be on WiFi. if in youre on network instead, itll always say up to date.

I'm on wifi. It still shows no update.

Same situation, on Wifi offcourse.

tryklon said:
Same situation, on Wifi offcourse.
Click to expand...
Click to collapse
Try a factory reset, then remove your carrier SIM and power up on WiFi. My bet is that your N6 will start churning through OTAs in sequence. Not sure that you will get all the way to Marshmallow 6.0, because that last OTA is still being rolled out.

Already did it... waste of time, no updates

If your not willing to simply download and flash the images from googles website, that is your choice... but there is nothing to do but wait.

Hi Guys I am in the same boat, brand new n6 on 5.0.1 and saying up todate . In uk and carrier is Virgin if that helps.
Mal

Something strange is definately happening with Google update servers...

same dilemma and same version as op..

Personally I was like you all. I got my nice shiny new n6 from verizon (free upgrade...) Got it home kept pressing check for updates. Tried all the clearing app data from frameworks and all that.
But in the end I sideloaded it. I documented it over on the OTA url post. It is not that hard, just need some time. If you don't want to wait it might be your only option.
Total time invested was probably 1.5 hours. Downloaded all the files to my laptop and started using WUGFresh.

Stop waiting and update manually? It's not difficult, you can even save your userdata by not flashing it. There are different (and possibly easier) ways to install an update other than sideloading. especially when you can skip all the OTAs and flash directly to 6.0.
No need for a tool kit and it won't take much longer than the time it takes for you to download the factory image and extract the files.

The point is that there might be something wrong with Google's OTA servers.
Or maybe something is wrong about these phones ?
Sent from my VS985 4G using Tapatalk

Thats my point exactly. What if theres something wrong with the phone?
Google should clarify why old updates are not being delivered... not even questioning 6.0, but 5.1.1

same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0

europeanpaul said:
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
Click to expand...
Click to collapse
Why not sideload 6.0

jdice said:
Why not sideload 6.0
Click to expand...
Click to collapse
Why is Google not delivering OTA updates to these N6 owners ?
Sent from my VS985 4G using Tapatalk

Because there were a couple of security updates between 5.1.1 and 6.0 (as far AS I remember on my N6) and because I want to be sure OTA works!

This issue is becoming more and more coomon. Lot's of people complaining on several forums about this issue.
At least its easy to see something is clearly wrong with the OTA's, since no one is getting any. There is people stuck on 5.0, 5.0.1, 5.1, etc whichever came preinstalled stays without updates.

Need explanation of locked bootloader on SM-G890A

I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer

roveer said:
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
Click to expand...
Click to collapse
hi
yes it's not possible to downgrade your rom or your bootloader because of the locked bootloader that prevents any try to modify the device...

is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.

roveer said:
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
Click to expand...
Click to collapse
Locked bootloaders are often the case for phones provided by carriers. While a phone purchased directly from the manufacturer is usually able to have its bootloader unlocked, carrier phones are locked by the carrier themselves, preventing any tampering by the end user. A custom ROM is any modified version of Android not developed by the company that made your phone. Think of it like a third party system. To get these custom ROMs onto your phone you must "flash" (simply, install) the ROM from your computer to your phone. However, a locked bootloader prevents this. While in some cases there are ways to get around carrier locked bootloaders, it is generally futile. If you purchased the S6 Active in hopes of tinkering around with custom ROMs, I'm afraid you have picked the wrong phone. The S6 Active, as of currently, is permanently locked to Samsung's and AT&T's "stock ROM"
EDIT: as for going back to Lollipop, the reason this is generally not possible is due to the fact that the Marshmallow update also updated critical parts related to the bootloader. It is impossible to roll back these changes once they have been made as they are strictly one way.

Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer

roveer said:
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
Click to expand...
Click to collapse
If the software you are referring to is something provided by blackberry, perhaps they need to patch their software for compatibility with Android Marshmallow. While not all software is broken by a major Android update, there are definitely some that are. Of course enterprise level software is entirely foreign to me (I'm only 17), so getting a second opinion on this issue would definitely be a good idea.

OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer

roveer said:
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
Click to expand...
Click to collapse
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.

FevenKitsune said:
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
Click to expand...
Click to collapse
So I wiped the cache partition and factory reset within the bootloader and tried my app again. It continued to fail. I even found the MM image in the S6 Active MM thread and sideloaded it. It was only 400+ megs though. Still the app doesn't work so I'm starting to doubt that my problems are related to my particular S6 but its always a possibility. I'm trying to get Blackberry to dig up their own S6A and test on their own. They've been testing with a S6 for the past 2 days (on my BES server) and haven't seen the same problems, so it's either my device or a problem with the S6A (which as has been pointed out does use a different firmware version than the S6), but until I can get another S6 Active device to test I won't know.
Roveer

SM-N920F (Actually SM-N920A) on 3 UK - updating from 5.1.1 to MM and beyond

*Utter noob alert!*
tl;dr - can i update to MM 6+ without totally screwing my phone and entering a whole world of pain?
Proud owner of mongrel SM-N920A purchased from HK via eBay. Device has no branding on hardward / software other than Samsung.
Settings > System > About Device shows model number = SM-N920F. LIES!!!!!
Phone INFO *Samsung* apk shows it's really an SM-N920A
I've attached output from Phone INFO showing 'General', 'CSC', 'Firmware' and 'Android' info.
Having read over threads on Sammobile and here on XDA, it appears some people are losing anything from mobile reception & data to full on apocalyptic bricking. Most of these posts are from earlier in 2016 so I'm wondering, now we're further down the line and the dust has settled, whether there's any consensus on best way forward to get Marshmallow / Nougat and beyond - if at all.

Anyone out there able to offer help and guidance?

Please :crying:

Ah come onnn! Someone here must be able to help!?

dmlargo said:
Ah come onnn! Someone here must be able to help!?
Click to expand...
Click to collapse
This is commonly done to increase the value of the phone by tricking the buyer into thinking it's a non-US model.
Anyway, AT&T and T-Mobile are better than Verizon or Sprint if it comes to using them outside the US, because of better LTE band support.
Since an AT&T phone will only receive OTA updates with an AT&T SIM inserted, you have to sideload the MM update yourself through adb and then keep on sideloading every new build as it comes out.

murtaza02 said:
This is commonly done to increase the value of the phone by tricking the buyer into thinking it's a non-US model.
Anyway, AT&T and T-Mobile are better than Verizon or Sprint if it comes to using them outside the US, because of better LTE band support.
Since an AT&T phone will only receive OTA updates with an AT&T SIM inserted, you have to sideload the MM update yourself through adb and then keep on sideloading every new build as it comes out.
Click to expand...
Click to collapse
So...
If I can get my hands on a prepaid / payg at&t sim here in the UK I could theoretically just get an OTA update that way?
If not, I'll look into sideloading. Do you know of any instructions on how to do?
And, thanks for replying. Very much appreciated

dmlargo said:
So...
If I can get my hands on a prepaid / payg at&t sim here in the UK I could theoretically just get an OTA update that way?
If not, I'll look into sideloading. Do you know of any instructions on how to do?
And, thanks for replying. Very much appreciated
Click to expand...
Click to collapse
Not necessarily, since the device needs to be connected to AT&Ts network, the SIM would either not work, or start Roaming in the UK.
Sideloading means you will have to get the OTA Zip files and install them on your phone using the Android Debugging Bridge (ADB).
This is the thread HERE: http://forum.xda-developers.com/att...ow-to-manually-update-to-marshmallow-t3380624
It's a very well written guide on how to update the AT&T Note 5.
Your current build number is different from the one used in the main post of the guide, so you're going to have to browse through the thread, grab a different build of Lollipop, flash that, then sideload the Marshmallow updates, one by one, till you get to a fairly new build, then what you do is, factory reset the phone, so you have a clean install of Marshmallow on your phone.

murtaza02 said:
Not necessarily, since the device needs to be connected to AT&Ts network, the SIM would either not work, or start Roaming in the UK.
Click to expand...
Click to collapse
Of course! I'm an idiot. Doesn't bode well does it! :laugh:
murtaza02 said:
Sideloading means you will have to get the OTA Zip files and install them on your phone using the Android Debugging Bridge (ADB).
This is the thread HERE: http://forum.xda-developers.com/att...ow-to-manually-update-to-marshmallow-t3380624
It's a very well written guide on how to update the AT&T Note 5.
Your current build number is different from the one used in the main post of the guide, so you're going to have to browse through the thread, grab a different build of Lollipop, flash that, then sideload the Marshmallow updates, one by one, till you get to a fairly new build, then what you do is, factory reset the phone, so you have a clean install of Marshmallow on your phone.
Click to expand...
Click to collapse
Build number being LMY4X.N920AUCU1AOGG
Doesn't matter that bootloader, PDA,CSC and baseband versions are mostly all different?
You're a great help. Thank you! +1

dmlargo said:
Of course! I'm an idiot. Doesn't bode well does it! :laugh:
Build number being LMY4X.N920AUCU1AOGG
Doesn't matter that bootloader, PDA,CSC and baseband versions are mostly all different?
You're a great help. Thank you! +1
Click to expand...
Click to collapse
You're on AOJ1 According to your screenshot.
You need to downgrade to UPB2 Or something and then flash the OTAs from Marshmallow to your phone from PB2.
I'm out of the house at the moment, will be home very soon, and try to find a link for you.

murtaza02 said:
You're on AOJ1 According to your screenshot.
You need to downgrade to UPB2 Or something and then flash the OTAs from Marshmallow to your phone from PB2.
I'm out of the house at the moment, will be home very soon, and try to find a link for you.
Click to expand...
Click to collapse
Thanks man.
For that version AOJ1 - that's bootloader version right? Just so I can differentiate what to look for.
Take it easy

dmlargo said:
Thanks man.
For that version AOJ1 - that's bootloader version right? Just so I can differentiate what to look for.
Take it easy
Click to expand...
Click to collapse
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.

murtaza02 said:
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
Click to expand...
Click to collapse
Epic. If I take it back to 2BPE6 successfully, I'm guessing it's then just the same process to push up to 6.0.1 and beyond?

dmlargo said:
Epic. If I take it back to 2BPE6 successfully, I'm guessing it's then just the same process to push up to 6.0.1 and beyond?
Click to expand...
Click to collapse
Nope, that was the process I described initially that required you to flash 2BP2 First and then onwards to Marshmallow.
The file I've linked (2BPE6) isn't an OTA. It's the entire full ROM file for the 6.0.1 update for the N920A. Once you flash this and the phone reboots, it'll go directly to Marshmallow.

murtaza02 said:
Nope, that was the process I described initially that required you to flash 2BP2 First and then onwards to Marshmallow.
The file I've linked (2BPE6) isn't an OTA. It's the entire full ROM file for the 6.0.1 update for the N920A. Once you flash this and the phone reboots, it'll go directly to Marshmallow.
Click to expand...
Click to collapse
And, more importantly, I'll hopefully have a standardised stack across csc, PDA and what not.
Like I said in op - there's unsurprisingly a lot of talk out there about note 5 on at&t when it comes to updates. I'd hoped because mine was already rooted and had a CHN / TGY csc that it kind of showed if someone in China had done stuff to it, and it still worked, then there was a possibility of moving it to 6.0.1
I'll get all files together along with your notes and have a go after getting a nandroid back up. Might be a while given time of year though.
Nice one

dmlargo said:
And, more importantly, I'll hopefully have a standardised stack across csc, PDA and what not.
Like I said in op - there's unsurprisingly a lot of talk out there about note 5 on at&t when it comes to updates. I'd hoped because mine was already rooted and had a CHN / TGY csc that it kind of showed if someone in China had done stuff to it, and it still worked, then there was a possibility of moving it to 6.0.1
I'll get all files together along with your notes and have a go after getting a nandroid back up. Might be a while given time of year though.
Nice one
Click to expand...
Click to collapse
The CSC and everything will go back to the default ATT one and it'll have no trace of ever being a fake N920F.
Everything will show N920A and you may also have a bit of AT&T bloat ware, most of which can be disabled.
But the main point is that the phone will no longer be modified in any way and will be completely stock.

murtaza02 said:
The CSC and everything will go back to the default ATT one and it'll have no trace of ever being a fake N920F.
Everything will show N920A and you may also have a bit of AT&T bloat ware, most of which can be disabled.
But the main point is that the phone will no longer be modified in any way and will be completely stock.
Click to expand...
Click to collapse
But doesn't that mean it'll be region locked / potentially losing network connection?

dmlargo said:
But doesn't that mean it'll be region locked / potentially losing network connection?
Click to expand...
Click to collapse
Nope. Once it's unlocked, it's always unlocked.
I live in Pakistan, American carrier phones are very common here. AT&T, Verizon, T-Mobile and Sprint, all the variants of Note 5 are available here and I've flashed updates on a friends AT&T Note 5 and it didn't get re-locked. I've flashed a T-Mobile Note 4 and 5, neither got re-locked.
Point being, that re-locking crap only used to happen on phones that were unlocked using a glitch or a software based unlock.

murtaza02 said:
Nope. Once it's unlocked, it's always unlocked.
I live in Pakistan, American carrier phones are very common here. AT&T, Verizon, T-Mobile and Sprint, all the variants of Note 5 are available here and I've flashed updates on a friends AT&T Note 5 and it didn't get re-locked. I've flashed a T-Mobile Note 4 and 5, neither got re-locked.
Point being, that re-locking crap only used to happen on phones that were unlocked using a glitch or a software based unlock.
Click to expand...
Click to collapse
Cool. I'll have a look this weekend. Fingers crossed.
After that I'll have a go a re-rooting using something similar to: https://www.search4roots.com/how-to-easily-root-samsung-galaxy-note-5-sm-n920a-marshmallow-6-0-1/

murtaza02 said:
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
Click to expand...
Click to collapse
I had a very similar situation ( AT&T re-custom Note5 ) , followed the procedure and everything went straight
so thanks to both of you for this thread and pretty straight guide
really
the only "issue" is that quite many thing ( graphically speaking ) changed from Lollipop , not in a "good" way , and I'm not sure wheter they're supposed to change for Marshmallow or for the AT&T bloatware/customization ..what is sure is that the phone was running bit cleaner before . ( i.e. no extra icons , no recording or "AT&T video call " icon available on phonecall screen when calling ..just an example among some things i noticed besides some at&t apps in the home screen )
is there a way to know it and to remove any of it , besides rooting the phone ? - which I'm not sure can be done on a n920a

boodi said:
I had a very similar situation ( AT&T re-custom Note5 ) , followed the procedure and everything went straight
so thanks to both of you for this thread and guide
the only thing is that quite many thing ( graphically speaking ) changed from Lollipop , not in a "good" way , and I'm not sure wheter they're supposed to change for Marshmallow or for the AT&T bloatware/customization
is there a way to know it and to remove any of it , besides rooting the phone ? - which I'm not sure can be done on a n920a
Click to expand...
Click to collapse
Package Disabler Pro. It's a paid app. You can use it to disable (not remove) some bloatware that's preinstalled by Samsung and AT&T.
No root possible, so you can't remove the apps.
Sent from my SM-G935F