OFFICIAL OOS4.0.1 NOUGAT is out for OnePlus 3!!!
Incremental roll-out of OxygenOS 4.0.1 (N) for the OnePlus 3 is on !
Here are some highlights::
WHAT'S NEW
Upgraded to Android 7.0 Nougat
New Notifications Design
New Settings Menu Design
- Multi-Window View
Notification Direct Reply
Custom DPI Support
Added Status Bar lcon Options
Improved Shelf Customization
Updated APN Settings for select Carriers
Fixed Proximity Sensor bug during calls
Increased System Stability
***Known Issues and Fixes
Apps might not download from Play Store.
If you are trying to download via Data Roaming, it will not work. This is a known Google issue.
Please follow Google’s troubleshooting steps and see if the problem is resolved.
Try turning on Battery Saving Mode and reset Play Store app preferences.
If you have these 3 apps installed: Truecaller, AVG Antivirus and PayTm, please try to force stop or uninstall them before performing download from Play Store.
If you still experience mobile data issues caused by APN, please go to APN settings page and manually choose try all the options. In the case that mobile data is still unusable, please send me a pm along with affected career and device model.
WiFi connectivity might still fluctuate, if you experience this issue, please send me a pm
www.oneplus.net
Use server germany on oos 4.0 to get update directly
If you do not get update try clearing data of app (system update)
-Flashing (method 1) (Unlocked bootloader with custom recovery)
*Flash mod twrp via adb
*Command "fastboot flash recovery recoveryname.img"
*Reboot into recovery
*Clear system (data if u were on any other cm/aosp rom)
*Flash full zip
*Flash super su latest beta(optional)
*Reflash mod twrp
*Reboot
-Sideload (method 2)(Unlocked bootloader with stock recovery)
*Reboot into recovery sideload mode
*Type this command via adb on pc
*" adb sideload zipname.zip"
Download links
Zip ota 37mb (drive)https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
Full zip 1434mb (direct server)
http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
Twrp mod https://forum.xda-developers.com/devdb/project/dl/?id=21835
Hit the thanks button if u like
Join the WhatsApp group for discussion news and fun (no room for spammers)
https://chat.whatsapp.com/0vwWQykbwRoG1I51OhYVdB
Nishidh said:
Only some developers got this update here are some pics
36 mb
Zip files will be uploaded soon
Click to expand...
Click to collapse
No existing link though
Anything yet?
Again! Just updated to 4.0...
Nothing here yet going through Canada.
Nothing and here vpn Canada
Nishidh said:
Only some developers got this update here are
some pics
36 mb
U can update directly using VPN Canada server from oos 4.0 (Not Tested)
Zip files will be uploaded soon
Click to expand...
Click to collapse
Soon? Have you got those zip files?
This is it: https://goo.gl/MpKe7e
Do you need to be on the beta or stable branch to receive the update OTA?
Seems like stable.
Anyone got their hands on flashable zip file?
Why don't you guys just chill for a couple of days. Wouldn't that be nice
Do not need flashable zip, all you need is OTA download and do Local Upgrade
23Six said:
This is it: https://goo.gl/MpKe7e
Click to expand...
Click to collapse
did you save/capture the OTA zip before installing?
It's developer preview, and it's for the developer team I guess. Not for mass distribution.
And then why create a thread at XDA?
23Six said:
This is it: https://goo.gl/MpKe7e
Click to expand...
Click to collapse
How did u get it?
oriveradel said:
And then why create a thread at XDA?
Click to expand...
Click to collapse
Because XDA is for developers... :laugh:
Everyone knows that, but since is not for the public should be OnePlus forums only
No zip available guys, just developer preview so do not expect a zip.
This is my installation process [last post summary]
https://forum.xda-developers.com/gal...ageos-t3576865
Downloaded lineage-14.1-20170322-nightly-klte-signed.zip
flashed this ROM with TWRP
rooted with CF-Auto-Root - same problem
downloaded again addonsu-ARM-signed_14.1
flashed this ROM again with TWRP
cleaning Dalvik and cache [kind of never done it before here]
rooted with addonsu-ARM-signed_14.1
all works
PS after flashing 20170322 ROM, on the first run I almost sh*at myself as SD card was not recognized. Restarted and was OK.
CATLOG screenshot
https://dl.xda-developers.com/4/1/0....jpg?key=J9F9olpmOpltDNbjtBwaxQ&ts=1491479200
If I try to update binaries in TWRP, it stops, restarts and stops during Lineage loading screen forever. [nothing in TWRP logs about SU I can see]
So I flash ROM again, and addonsu-ARM-signed_14.1 from TWRP to fix it.
I was reading that after flashing addonsu-ARM-signed_14.1 - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
Is there a way to have it done?
Is it sometimes necessary to set permissions in Terminal for some SU files/folders before updating binary? I think ages ago I was doing something like this...?
Is it possible that
1. flash ROM
2. root fith CF root
3. dirty flashROM
4. use correct root addonsu-ARM
can have anything to do?
SM-G900F
lineage-14.1-20170329-nightly-klte-signed.zip
lineage-14.1-20170405-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
The link for your install process, gives an XDA 404 page loading error.
One question though with SuperSU settings. Do you have it set to allow SU to run during boot? Maybe that's why it seems to take forever to load after updating binaries through TWRP?
Sent from my SM-G930P using Tapatalk
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...
Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
* DELETED *
Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?
niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.
system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse
automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.
Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?
I have rooted and installed magisk in my note 10 pro and even though I see the update in the settings and can download it. The update doesn't get installed and opens the TWRP recovery which then just fails and restarts without installing the update. Is there any way that I can install the OTA update?
XDA_chron said:
I have rooted and installed magisk in my note 10 pro and even though I see the update in the settings and can download it. The update doesn't get installed and opens the TWRP recovery which then just fails and restarts without installing the update. Is there any way that I can install the OTA update?
Click to expand...
Click to collapse
Previously, updates were downloaded to the / sdcard / downloaded_rom folder (if you look at the path from the phone) in the phone's memory, check in TWRP, if there is no firmware file there, then download the update from the website, load it into the phone's memory or a flashcard and update. After updating, without booting into the system, flash the archive using magisk and then boot into the system.
Dron74 said:
Previously, updates were downloaded to the / sdcard / downloaded_rom folder (if you look at the path from the phone) in the phone's memory, check in TWRP, if there is no firmware file there, then download the update from the website, load it into the phone's memory or a flashcard and update. After updating, without booting into the system, flash the archive using magisk and then boot into the system.
Click to expand...
Click to collapse
Instead of doing all of these things I was thinking of waiting a month or two and installing the pixel experience rom