Hi everyone,
We appreciate everyone’s feedback from the OxygenOS 3.5.1 community build. With your help, we have optimized the build and improved several key areas. This update includes:
Added “kill all background processes” button in recents menu
Added long press options in messages application
Enhanced incoming call notification UI
Added manual “check for update” button
Added additional directions for first fingerprint configuration
Battery Saver mode optimizations and enhancements
Added back contacts widget in launcher
Improved dialer speed
New modes added in control panel (night mode and battery saver)
Added support for PIN codes up to 6 digits
Visit the download page here:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.5.2_community_build/
If you’ve already flashed a previous community build, you will recieve this update via OTA. If you haven’t, you will need to flash this build by ADB sideload. Your data my transfer, but there is always a possibility of losing personal data, so be sure to backup all of your important data before flashing this build. As stated before, once you flash the community build, you’ll continue getting community OTAs.
Please follow the links below for the experience survey and bug reporting sheet. We’d really appreciate a few minutes of your time, as it will help us make OxygenOS even better. One last thing: this is a limited program, so we may disable this download link once we receive enough feedback.
https://goo.gl/forms/xBXWi6ksNsvrxiB12 - Feedback on UI/UX
https://goo.gl/forms/HM3v1zU134oGh05R2 - Bug reporting sheet
Note: If you flash this community build, you’ll receive community OTAs (but not official OTAs). You’ll need to manually (clean) flash back to our official builds to continue receiving official OTAs. Rolling back to official OxygenOS versions require wiping data and cache.
Thank you for helping us build a better OxygenOS.
Never settle.
Nice work. Question, there is no mention if this process will wipe my internal memory. Will it?
Nice!!!!
No mention as to whether this build fixes some of the major bugs reported from the 3.5.1 build. Such as random reboots and limited to no LTE connections for some.
Mirror https://drive.google.com/file/d/0B9m3hH0v4dbcT2NDRmtwMWIxZEE/view?usp=sharing
I am having strange problem. The update showed its 171 MB, so I downloaded it and hit update and reboot. After that, the phone automatically booted to twrp recovery and nothing happened. So I restarted the device. After booting there was a notification " update failed, click here to enter repair mode". Now the update shows 1364MB. Now I am pretty sure this happened in the last update too, which was 52 MB initially and went straight to 1.3GB.
Can anyone tell me whats happening there?
Another build and another "Cannot Read" error in ADB
What is this ><
EDIT: huh a reboot fixed the issue....
abhish3kkk said:
I am having strange problem. The update showed its 171 MB, so I downloaded it and hit update and reboot. After that, the phone automatically booted to twrp recovery and nothing happened. So I restarted the device. After booting there was a notification " update failed, click here to enter repair mode". Now the update shows 1364MB. Now I am pretty sure this happened in the last update too, which was 52 MB initially and went straight to 1.3GB.
Can anyone tell me whats happening there?
Click to expand...
Click to collapse
are you rooted? just download the whole file and update via TWRP.
abhish3kkk said:
I am having strange problem. The update showed its 171 MB, so I downloaded it and hit update and reboot. After that, the phone automatically booted to twrp recovery and nothing happened. So I restarted the device. After booting there was a notification " update failed, click here to enter repair mode". Now the update shows 1364MB. Now I am pretty sure this happened in the last update too, which was 52 MB initially and went straight to 1.3GB.
Can anyone tell me whats happening there?
Click to expand...
Click to collapse
If your phone is rooted and unlocked you can't update it by OTA.
you have to download the full ZIP then flash it via TWRP
I cant flash the full version with TWRP, someone have the same problem?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
@k.s.deviate, @innocentwoolf Oh I see. Downloading the whole file from the link. Thanks
I can not update gives me Error 7 Help please.
Did they update to the September patch level?
ajnexus5 said:
I can not update gives me Error 7 Help please.
Click to expand...
Click to collapse
I´ll try to modify the update script in the zip file. (notepad++!
I remove the first line where the error came from. it cant read your device model.
i´ll try it now to flash
seems to flash it now without error.
oh no... flashed stock rom without supersu. ok the device is encrypted again. (multirom)
so i have to wipe everything again. i will test it later :c but you can modify the update script to flash it
darkjedi said:
Did they update to the September patch level?
Click to expand...
Click to collapse
Yes they does.
panther124 said:
I´ll try to modify the update script in the zip file. (notepad++!
I remove the first line where the error came from. it cant read your device model.
i´ll try it now to flash
seems to flash it now without error.
i will look now.
i will update this post
Click to expand...
Click to collapse
What is the file who I need to modify with Notepad++?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
riki_corrales.10 said:
What is the file who I need to modify with Notepad++?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
open the zip-meta inf-com-google-android-updater-script (use winrar)
copy it on your desktop and open it with notepad++.
the line should look like this:
getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + "".");
remove this and then save the file and put it back into the zip. (it can take one minute to put it back in it (winrar))
and dont forget to mount system read-only when you flash the rom! otherwhise it can gives an another error
1+ 3
Can anyone try this? I think o discovered a bug, don't know if it is only me or is it there in all Oxygen OS builds.
1- open a music track in any music player, take the stock OOS music player or the Google Play Music app.
2- seek the bar till you reach the last couple of seconds of the song
3- confirm if the song returns back to the beginning while it still displays the seek bar where you dropped it.
This bug is inevitable with any music player. Also it happens if you seek forward past 1/2 or 2/3 of the bar
Thanks!
panther124 said:
open the zip-meta inf-com-google-android-updater-script (use winrar)
copy it on your desktop and open it with notepad++.
the line should look like this:
getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + "".");
remove this and then save the file and put it back into the zip. (it can take one minute to put it back in it (winrar))
and dont forget to mount system read-only when you flash the rom! otherwhise it can gives an another error
Click to expand...
Click to collapse
You are the best men, thanks
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Related
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
Hi all, I see there is an update listed on this page link V12.0.2.0.QFAEUXM.
Can someone confirm if this has been released as stable already? And if you received it, how is this an improvement over V12.0.1? I am holding on to V11 as I heard V12s initial release was not that well polished and strains the battery.
Thanks!
it's only security update for August
Sent from my MI 9 using Tapatalk
LubbeSGS said:
Hi all, I see there is an update listed on this page link V12.0.2.0.QFAEUXM.
Can someone confirm if this has been released as stable already? And if you received it, how is this an improvement over V12.0.1? I am holding on to V11 as I heard V12s initial release was not that well polished and strains the battery.
Thanks!
Click to expand...
Click to collapse
- I have received this OTA update and it's stable.
- Everything work's more or less stable, at least I didn't find any issue until now.
- What I have noticed is that Weather app is replaced with G version in his name and now one can update this app manually without previous notorious "authorisation" issue.
- Mi Global Browser is still there and still can't be uninstalled ( Failed [-1000] error in adb shell during uninstall).
- In Indian Forbes site I have seen that they will release update which will allow uninstalling MiBrowser and few other apps because Indian government have banned all of these apps.
- Battery life is a little better from previous ROM.
- There is no more stuttering in Chrome browser.
- That's my humble experience so far.
Thanks @Jehonan I think I may give it a shot then.
Cannot flash the update
I am on miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM.
I did not get the OTA yet and my battery life is very poor so I am eager to upgrade, I tried to update manually from the updater to either files:
- miui_CEPHEUSEEAGlobal_V12.0.2.0.QFAEUXM
- miui-blockota-cepheus_eea_global-V12.0.1.0.QFAEUXM-V12.0.2.0.QFAEUXM
but I always get the "Sorry, flash to this stable version is not allowed".
Any ideas what is the problem?
meroupow said:
I am on miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM.
I did not get the OTA yet and my battery life is very poor so I am eager to upgrade, I tried to update manually from the updater to either files:
- miui_CEPHEUSEEAGlobal_V12.0.2.0.QFAEUXM
- miui-blockota-cepheus_eea_global-V12.0.1.0.QFAEUXM-V12.0.2.0.QFAEUXM
but I always get the "Sorry, flash to this stable version is not allowed".
Any ideas what is the problem?
Click to expand...
Click to collapse
Which update procedure did You follow?
Did You make folder on root of the internal drive, copied appropriate downloaded ROM inside this folder and start upgrade from there?
I went to the Rom version in settings. Cliqued on the 3 dots. Select rom to install. Then tried to import the files from download, root, dowloaded_roms folders. Same result: "flash to this stable version is not allowed".
With the same procedure I am able te reflash miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM as much as I want. But no way to upgrade.
I also tried from recovery. But there is no option to flash update.zip.
meroupow said:
I went to the Rom version in settings. Cliqued on the 3 dots. Select rom to install. Then tried to import the files from download, root, dowloaded_roms folders. Same result: "flash to this stable version is not allowed".
With the same procedure I am able te reflash miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM as much as I want. But no way to upgrade.
I also tried from recovery. But there is no option to flash update.zip.
Click to expand...
Click to collapse
Did You tried with OTA version of this update?
Same procedure, in root of the drive in downloaded_rom folder copy OTA update and start update from there.
Here is a link to ROM's.
P.S.
I believe that You must first go with OTA version of the firmware because of the downloaded ROM decrypting procedure. After that You can go with recovery type of ROM (full ROM upgrade).
Yes, I tried the update file as well.
Both files give the same error ("Sorry, flash to this stable version is not allowed"):
- miui_CEPHEUSEEAGlobal_V12.0.2.0.QFAEUXM_44dcb66933_10.0.zip
- miui-blockota-cepheus_eea_global-V12.0.1.0.QFAEUXM-V12.0.2.0.QFAEUXM-789914bb83-10.0.zip
I am able to flash V12.0.1 from the same site so I am sure to be on the right ROM:
- miui_CEPHEUSEEAGlobal_V12.0.1.0.QFAEUXM_4d28c84f58_10.0
Something else is preventing the upgrade.
Well, I found out that I needed to change the region settings from France to Belgium... now it updates.
How stupid!
Hi all, I'm having a strange behaviour after the update: the quick charge ( using a wireless charger ) isn't working anymore.
Does anyone have the same issue?
stocaprimo said:
Hi all, I'm having a strange behaviour after the update: the quick charge ( using a wireless charger ) isn't working anymore.
Does anyone have the same issue?
Click to expand...
Click to collapse
Nope!
Mine is working as it should, without any issue what so ever.
Strange!
Did You check wireless charger itself?!
---------- Post added at 11:19 AM ---------- Previous post was at 11:13 AM ----------
meroupow said:
Well, I found out that I needed to change the region settings from France to Belgium... now it updates.
How stupid!
Click to expand...
Click to collapse
Excellent!
I'm glad it worked for You!
Good luck in the future!
P.S.
There is nothing stupid about this so don't blame yourself!
I would rather call this Xiaomi's stupidity and theirs mumbo jumbo with all of these "special" update procedures !
What is yhe exact solution to this problem
I already tried to change my region it didn't work for me im using redmi note 8 pro Indonesia rom
New beta Oxygen OS update for the OnePlus 7 pro
Details
• Type: beta
Changelog
System
• Improved system stability and fixed general issues
• Updated Android Security Patch to 2020.10
Camera
• Fixed the flashback issue when switched to the front camera in particular cases
Links
• ROM: -Global | OP7P -
https://otafsg1.h2os.com/patch/amaz...gen_13.W.45_OTA_045_all_2010191035_181a6b.zip
This update has my phone clunky. Everything I do is on a delay (typing or keyboard appearing or texts loading/screens loading) or gets stuck (volume up it sometimes goes all the way up and so on). Never had a similar issue. Done multiple restarts, even switched slots, boosted ram. Not sure what else to do.
Suggestions?
Porquiplane said:
This update has my phone clunky. Everything I do is on a delay (typing or keyboard appearing or texts loading/screens loading) or gets stuck (volume up it sometimes goes all the way up and so on). Never had a similar issue. Done multiple restarts, even switched slots, boosted ram. Not sure what else to do.
Suggestions?
Click to expand...
Click to collapse
Ye I believe this update has issue, I'm having wifi issue I'm been disconnecting for no reason. Keyboard delay is also there .
Lol these betas are pretty irrelevant, no meaningful changes. And Android11 roms are solid so.
farhan20 said:
Ye I believe this update has issue, I'm having wifi issue I'm been disconnecting for no reason. Keyboard delay is also there .
Click to expand...
Click to collapse
No problema here, everything works flawlessly
Sent from my OnePlus7Pro using XDA Labs
No problems here too. Everything working fine, fast and smooth.
Anyone on open beta 19 having trouble removing the india.img file, where in the settings it states to login to Oneplus? I've tried using the India Fake Partition Deleter from mauronofrio, attempting to manually delete india.img in TRWP or a root file explorer, and the Overlay Mount Fix by Zackptg5. Any help would be greatly appreciated.
Porquiplane said:
This update has my phone clunky. Everything I do is on a delay (typing or keyboard appearing or texts loading/screens loading) or gets stuck (volume up it sometimes goes all the way up and so on). Never had a similar issue. Done multiple restarts, even switched slots, boosted ram. Not sure what else to do.
Suggestions?
Click to expand...
Click to collapse
Try to wipe cache (boot into recovery and wipe cache).
How do you update this and keep twrp
Is it just flash twrp retention script then flash rom
gap30 said:
How do you update this and keep twrp
Is it just flash twrp retention script then flash rom
Click to expand...
Click to collapse
Flash Full rom zip and Twrp zip file.
Solved. I showed hidden files.
Where is the downloaded firmware update saved? I would like to move it to a prepared folder and do an update via twrp.
unavix said:
Solved. I showed hidden files.
Where is the downloaded firmware update saved? I would like to move it to a prepared folder and do an update via twrp.
Click to expand...
Click to collapse
In the root directory of your internal storage (i.e. not in any folder).
The firmware update beta 19 was downloaded in a hidden folder called .ota. So not right at the root of the repository.
a63548 said:
Anyone on open beta 19 having trouble removing the india.img file, where in the settings it states to login to Oneplus? I've tried using the India Fake Partition Deleter from mauronofrio, attempting to manually delete india.img in TRWP or a root file explorer, and the Overlay Mount Fix by Zackptg5. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Having this issue as well and have tried as you have to fix. Wiping cache does not help as well.
Anyone know how to get rid of this nag?
will this beta update to android 11 beta?
klemen241 said:
will this beta update to android 11 beta?
Click to expand...
Click to collapse
No, update to 11 will come end of 2020, beginning 2021
Update to Oos 11 is supposed to be out in December
vegetaleb said:
Update to Oos 11 is supposed to be out in December
Click to expand...
Click to collapse
I really hope it comes soon. Any source for it coming in December?
Exciting to see android 11 come to our OP7 series!
Can someone who doesn't mind being a guinea pig test the update out? I am currently on a third party ROM (i do prefer OEM) however i had to go that route since my usb to audio splitter didn't work after 10.X.X.X update here since November. Was wondering if someone who doesn't mind could update to this latest, and test it out. https://www.xda-developers.com/oneplus-7-7-pro-7t-7t-pro-stable-oxygenos-11-android-11/
Regards,
Travis
i would love to do it but no file for the 7 pro yet
There aren't files for 7 series, only for 7T and 7T Pro.
I've read something about problems with Camera app, so they turned off distributing update. Still waiting
Global version is on Oxygen Updater now.
Nothing for EU yet.
Official Global Link : https://otafsg1.h2os.com/patch/amaz...1.P.35_OTA_0350_all_2103221240_0ebe9c8a78.zip
Android File Host Mirror : https://www.androidfilehost.com/?fid=2188818919693770547 (MD5 : 3ec7940e9e50032b540ceaf2a3364f85 )
Pack with rooted boot image and instructions for Global : https://www.androidfilehost.com/?fid=2188818919693770594 ( MD5 : b24c7463ef9a78ab0ae7ae708dc46c37 )
I've extracted all the image files but AFH is still being a pile of crap, FTP uploads won't work and web uploads keep stopping or not completing, uploaded mirror to Dropbox for now, will try to get it uploaded to AFH asap.
Pack with all extracted images for Global version : (TEMP Dropbox Link) https://www.dropbox.com/s/nwfo6433wdkkkk3/Default-OxygenOS11-Final-Images_Global.zip?dl=0
Is it true AOD is missing??
I will keep Beta 4 if this is true
vegetaleb said:
Is it true AOD is missing??
I will keep Beta 4 if this is true
Click to expand...
Click to collapse
AOD was in the labs, labs is not included in the stable release ring (probably never will be) as it's supposed to be test software.
djsubterrain said:
AOD was in the labs, labs is not included in the stable release ring (probably never will be) as it's supposed to be test software.
Click to expand...
Click to collapse
Can someone try this trick to enable AOD on stable OOS 11?
[ROOT/Magisk] Enable Always on Ambient Display on Oxygen OS 11 Beta 1
Contrary to what OnePlus have said, the code for the Always on Ambient Display is in the first beta of Oxygen OS 11. All you have to do is enable the feature, which is disabled in the "OPFeatures" framework. This is very simple, and can be done...
forum.xda-developers.com
Installed and working stable for me. No problems observed with camera, messaging etc. AOD is irrelevant to me - won't miss it. Battery seems to be stable too - no indication of excessive power usage. Will update if I see anything. BTW, I am stock non-rooted.
Can we return nanroid if 11 is buggy ?
zelenko said:
Can we return nanroid if 11 is buggy ?
Click to expand...
Click to collapse
There will possibly be a rollback link provided if OnePlus ever make an actual thread for the release, there isn't one at the moment.
OK, I'm mistaken, there is actually a thread now :
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
No rollback link though so you'd likely need to do a full flash which would probably wipe the phone.
Has anyone rooted yet? And if so, which version of majisk did you use?
Hi, I tried rooting with the patched boot.img linked above but it fails to boot twice then enters recovery. Also tried patching the img myself using the latest magisk 22.0 app but it gave the same behavior. I use the command: fastboot flash boot magisk_patched.img to flash.
Anyone know what's up ?
EDIT: after the failed boot I have a "BOOT REASON" menu in recovery giving this message:
Code:
--------------------------------
Boot Reason : RescueParty
--------------------------------
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
Trying the adb command in recovery tells me it's unauthorized and I had to give access from the phone (which isn't possible it seems). Doing the adb pull with the system booted gives:
Code:
adb: error: failed to stat remote object '/mnt/vendor/op2/rbr_log': Permission denied
EDIT 2: After a backup and clean wiping the userdata magisk seems to work now.
From OxygenOS 11 Open Beta 4
to OxygenOS 11
without losing your data.
1.) Download and install OxygenOS 11
2.) Download keep_data.apk
You need to install it after the update was installed but before you restart.
After the apk is installed, run the application, click "KEEP DATA".
You should now be able to restart the phone without losing your data
P.S.
All your applications
and data remain intact
vegetaleb said:
Can someone try this trick to enable AOD on stable OOS 11?
[ROOT/Magisk] Enable Always on Ambient Display on Oxygen OS 11 Beta 1
Contrary to what OnePlus have said, the code for the Always on Ambient Display is in the first beta of Oxygen OS 11. All you have to do is enable the feature, which is disabled in the "OPFeatures" framework. This is very simple, and can be done...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, that does put the option back into the display settings, but just like before it gets lost in reboot unless you add that sh file
btvolta said:
Has anyone rooted yet? And if so, which version of majisk did you use?
Click to expand...
Click to collapse
Coming from ob4, I reflashed magisk to the inactive slot in the app after the upgrade was complete but before I rebooted the phone. After the reboot, I tapped on the magisk app and it said it needed additional files. After it downloaded and installed the additional files the phone rebooted and my root works fine. I started with magisk 22.
I am on 10.3.7 rooted with magisk. Before starting, a few questions. Is it possible to upgrade to 11 without losing data and retaining root? If not, is there a magisk for 11. What is the safest way to upgrade? Also, is there twrp for 11? Any help would be greatly appreciated.
Fresh install from factory reset. Screen still wigs out on FHD. Unlocking causes everything to be gigantic and have to hard reset. So no change for me from beta 4 to stable 11.
djsubterrain said:
Global version is on Oxygen Updater now.
Nothing for EU yet.
Official Global Link : https://otafsg1.h2os.com/patch/amaz...1.P.35_OTA_0350_all_2103221240_0ebe9c8a78.zip
Android File Host Mirror : https://www.androidfilehost.com/?fid=2188818919693770547 (MD5 : 3ec7940e9e50032b540ceaf2a3364f85 )
Pack with rooted boot image and instructions for Global : https://www.androidfilehost.com/?fid=2188818919693770594 ( MD5 : b24c7463ef9a78ab0ae7ae708dc46c37 )
I've extracted all the image files but AFH is still being a pile of crap, FTP uploads won't work and web uploads keep stopping or not completing, uploaded mirror to Dropbox for now, will try to get it uploaded to AFH asap.
Pack with all extracted images for Global version : (TEMP Dropbox Link) https://www.dropbox.com/s/nwfo6433wdkkkk3/Default-OxygenOS11-Final-Images_Global.zip?dl=0
Click to expand...
Click to collapse
I read the instructions in the zip file. My question is do we install the magisk and boot image before or after we install the update?
So I'm stuck in a boot loop after taking the OTA.
There is a Eu version of Android 11, I woke up with notification )
I couldn't find an answer and nobody would answer me on the Telegram group so I have to ask here.
My current build is:
PixelExperience_Plus_rosemary-13.0-20230125-2021-OFFICIAL
I need to update to build:
PixelExperience_Plus_rosemary-13.0-20230219-1738-OFFICIAL
But, using the System Update I can only download the update file and when I tap install it says something like I'll be notified when it's done, or something along those lines, but nothing happens. No progress bar, no notification, no nothing.
Can I just adb-sideload the file from my PC and apply it? Do I need to wipe anything? Will I lose my data?
MentalCombo said:
I couldn't find an answer and nobody would answer me on the Telegram group so I have to ask here.
My current build is:
PixelExperience_Plus_rosemary-13.0-20230125-2021-OFFICIAL
I need to update to build:
PixelExperience_Plus_rosemary-13.0-20230219-1738-OFFICIAL
But, using the System Update I can only download the update file and when I tap install it says something like I'll be notified when it's done, or something along those lines, but nothing happens. No progress bar, no notification, no nothing.
Can I just adb-sideload the file from my PC and apply it? Do I need to wipe anything? Will I lose my data?
Click to expand...
Click to collapse
ask the dev or the gruop for the resptive guide to update the rom
tutibreaker said:
ask the dev or the gruop for the resptive guide to update the rom
Click to expand...
Click to collapse
Okay, thank you.
This bug is known for January patch and your only choice is to dirty flash the ROM to update. You would've known this if you followed the device-specific Telegram group at @/PixelExperienceRosemaryChat at the time.
I tried dirty flashing but something goes wrong.
I'm using Pixel Recovery and what I did was clicked "Enable ADB", then went to "Apply update" and adb sideloaded the update file from my PC, but this is what happens:
BTW, I do have plenty of space on my phone.
MentalCombo said:
I tried dirty flashing but something goes wrong.
I'm using Pixel Recovery and what I did was clicked "Enable ADB", then went to "Apply update" and adb sideloaded the update file from my PC, but this is what happens:
BTW, I do have plenty of space on my phone.
Click to expand...
Click to collapse
go to rom telegram group