[News] OxygenOS 3.2.0 update cancelled

[Xeleth]

It seems like OnePlus has temporarily stopped rolling out the OxygenOS 3.2.0 update because of issues while upgrading.
There is currently no ETA available but they are working on resuming the rollout as soon as possible.

Due to some reports of issues while upgrading, we are temporarily stopping the rollout to investigate. We will start back up as soon as possible.

Source: https://forums.oneplus.net/threads/oxygenos-3-2-0-ota-update-will-start-soon-on-oneplus-3.453875/

Here are some issues with the 3.2.0 update that people have reported.
Keep in mind that these are unconfirmed at this point:

• Upgrading with a configured SIP-account leads to SIM-card not being recognized. (More information)
• Problems with notifications
• OTA uses HTTP to communicate the device IMEI. (More information)
• Other minor bugs reported by people. (Thanks to runboy93)

Since the update was already available for some time, the firmware is already available online and can be installed with caution.
You can comment below if you received the update and tell us which country you are from.

EDIT - 7/7/2016
It seems like 3.2.0 update got cancelled and they are now rolling out 3.2.1 instead:

Rather than continuing that rollout, we’re skipping right ahead to 3.2.1.

Source: https://forums.oneplus.net/threads/...s-starting-on-oneplus-3.454469/#post-15056543

 

[Prozart]

I was on a custom ROM so I didn't receive the OTA but I've installed it from the firmware download and haven't had any issues.

 

[k.s.deviate]

Canada, I was running 3.1.3 out of the box. I ADB pushed the 3.2.0 008-->010 OTA file posted on XDA and have no issues at all.

 

[crysen]

Germany, flashed full ROM via TWRP, no issues here

 

[_MartyMan_]

I have the 3.2 update, but i have IMEI for both SIM, and my phone booted, even root and xposed is working fine, Alert Slider is working like before. I feel sorry for those whos phone can't boot/IMEI missing :/

 

[hasenbein1966]

3.2.0 working just fine here also... (Germany)

 

[B1nny]

Here are some issues with the 3.2.0 update that people have reported.
Keep in mind that these are unconfirmed at this point:

• OTA uses HTTP to communicate device IMEI.

I'd like to use this mention to tell all of you that you can confirm for yourself that your IMEI is being sent over HTTP to the OPPO/OP servers.

As I've posted on the OnePlus forums:

You can check it for yourself by using a tool such as mitmproxy and telling your device to proxy all its traffic through mitmproxy. Every time you press the button you'll see the post request appear and you can see what they're sending.

I'm not going to explain how to install mitmproxy, since they have some pretty good documentation on how to do this on their wiki. By all means, have a look and try it for yourself. It's not too hard to install, and this way you can see and confirm the issue with your own eyes. Either way, it should look something like this:

(for obvious reasons, I've blurred out my IMEI + imgur link, XDA keeps messing up my image inclusion for some reason)

 

[Xeleth]

I'd like to use this mention to tell all of you that you can confirm for yourself that your IMEI is being sent over HTTP to the OPPO/OP servers.

As I've posted on the OnePlus forums:
I'm not going to explain how to install mitmproxy, since they have some pretty good documentation on how to do this on their wiki. By all means, have a look and try it for yourself. It's not too hard to install, and this way you can see and confirm the issue with your own eyes. Either way, it should look something like this:
http://i.imgur.com/rFdkfVU.png
for obvious reasons, I've blurred out my IMEI)

This could turn out really bad if their OTA servers cannot force SSL without a client-side update.
I seriously hope they have identified this problem and delayed the 3.2.0 update as a result.

Thank you for bringing this to our attention!

 

[Bradl79]

That's y u just unlock the bootloader and install twrp then flash the full 3.2.0 zip and no need for OTAs, its still covered under warranty, I just don't understand why someone would buy a Oneplus 3 and ont do any of that

 

[voltiger]

I'm a German user and have it already. For me none of the posted issues apply. Even two SIM cards in the phone (Telekom and Congstar).

I just don't see any improvements. The sRGB mode is not useful as white turns into yellow which looks bad.

 

[Xeleth]

That's y u just unlock the bootloader and install twrp then flash the full 3.2.0 zip and no need for OTAs, its still covered under warranty, I just don't understand why someone would buy a Oneplus 3 and ont do any of that

Being cautious with things like unlocking the bootloader and flashing OTAs makes sense when the device is still new. There have been cases where low-level actions have lead to undocumented restrictions like degradation of camera quality. Making sure changes to the device are reversible and firmware versions safe is actually pretty clever, but usually not necessary with manufacturers like OnePlus. I still wouldn't flash an update which got cancelled in the middle of a rollout, since I feel like they wouldn't cancel a rollout unless it was something serious.

These updates could also be region restricted for reasons like radio optimization or extended carrier support.

 

[C.H.T.J.]

Flashed 3.2 over 3.1.3 no issue her. I am from Germany

 

[danyvw]

Installed 3.2.0 thru TWRP, everything is working flawlessly.

Sent from my SM-T810 using XDA-Developers mobile app

 

[Bradl79]

Being cautious with things like unlocking the bootloader and flashing OTAs makes sense when the device is still new. There have been cases where low-level actions have lead to undocumented restrictions like degradation of camera quality. Making sure changes to the device are reversible and firmware versions safe is actually pretty clever, but usually not necessary with manufacturers like OnePlus. I still wouldn't flash an update which got cancelled in the middle of a rollout, since I feel like they wouldn't cancel a rollout unless it was something serious.

These updates could also be region restricted for reasons like radio optimization or extended carrier support.

That's y with trwp u make a Nandroid backup so if things go wrong u can go back to ur old image, also there are no issues with 3.2.0, I have been running for a day and no issues, I think with degrading u r talking about cm13, yes that could be possible but by rooting or unlocking bootloader will not have any effect on that at all u r still stock

 

[hellkun]

Weird issue for me: I cannot grant permissions for some certain apps, not all, just a few in my case, it kept saying "screen overlay detected". A reply from another forum inspired me, I turned off dark mode in Settings, then permissions worked.
I've no idea why dark mode becomes an obstacle for setting permissions. I'm on OOS 3.2.0, updated manually.

 

[Aut0mat3d]

Got it yesterday (3.1.2, stock with unlocked bootloader, non-rooted) - update failed twize. - could be my fault as i booted into TWRP via Fastboot to make a Nandroid Backup and allowed access to /SYSTEM
After that i flashed TWRP and switched to FreedomOS 1.1 after a wipe (http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348) - all fine, IMEI is there - all OK

I also mentioned the yelloish tint after switching to SRGB which disappeared after the first reboot - now i am a happy camper @3.2
Coming from a Oppo Find7a I am verry impressed from the Oneplus3 - mainly the Camera and the aluminium Body

 

[s3axel]

Just for clarification: the issue was not with IMEI, but with the SIM cards not being recognized when a SIP-account in the Android phone app has been configured.

I had this as well, removal of the SIP account (I mainly use a 3rd party app anyway) solved that issue - 3.2.0. up and running very nicely here (also in Germany )

 

[cabanas1]

Updated then rooted it no problems imei working fine

 

[Sledge2013]

I'm rooted and first flashed Stock-ROM 3.1.3 and then OTA-Update to 3.2.0....no issues...in Germany

 

[sriharshaarangi]

Weird issue for me: I cannot grant permissions for some certain apps, not all, just a few in my case, it kept saying "screen overlay detected". A reply from another forum inspired me, I turned off dark mode in Settings, then permissions worked.
I've no idea why dark mode becomes an obstacle for setting permissions. I'm on OOS 3.2.0, updated manually.

This happened to me on OOS 3.1.2 as well