[OFFICIAL] OxygenOS 10.0.1 (Android Q 10.0) OTA for OnePlus 5 (cheeseburger)
- Thread starter Funk Wizard
- Start date
Always after. Right order: ROM>Magisk>Kernel(optional)>No Verity V3. If Magisk V18 don't survive the first boot, flash it once again after initial setup.
P. S. Personally i prefer still MagV17-2
P. S. Personally i prefer still MagV17-2
Why do you prefer Magisk 17.2 over 18.0? Just curious...Always after. Right order: ROM>Magisk>Kernel(optional)>No Verity V3. If Magisk V18 don't survive the first boot, flash it once again after initial setup.
P. S. Personally i prefer still MagV17-2
I think it's depend of the no-verity.zip
1. Before magisk here: https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389
2. after magisk here: https://xdaforums.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
1. Before magisk here: https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389
2. after magisk here: https://xdaforums.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Fortunately, I haven't had any trouble with Magisk in a very long time. Cool. :good:
hello guys, I have a big problem I installed the rom Pie9 above 5.1.7 according to instructions and everything ok but when restarted when it asks for the password tells me it is wrong, I also tried to formatted via twwrp and make a clean flash but always the same problem, is there a solution? thank you
Did you removed the pin/pattern as suggested before flashing the update? Is your device storage encrypted or decrypted? You enter that password in twrp or after booting up the rom?
I just dirty flashed the OS. Sorry, if this has been covered, but...
Magisk won't ask for root permissions for the apps, just automatically denies them access, whereas before, I always got a prompt asking if access should be gained or not.
Frustrating, as some of the apps I used rooted, now stopped working, Magisk Manager inbuilt update being one of them, hehe.
Tried with both, Magisk 17.3. and 18.0.
Manager says it's installed, and passes the SafetyNet. What to do?
Not really sure if this should be here or in the Magisk thread, but it happened while migrating the OS, so it's got something to do with the update. Hope someone is able to help quickly. Thanks.
Magisk won't ask for root permissions for the apps, just automatically denies them access, whereas before, I always got a prompt asking if access should be gained or not.
Frustrating, as some of the apps I used rooted, now stopped working, Magisk Manager inbuilt update being one of them, hehe.
Tried with both, Magisk 17.3. and 18.0.
Manager says it's installed, and passes the SafetyNet. What to do?
Not really sure if this should be here or in the Magisk thread, but it happened while migrating the OS, so it's got something to do with the update. Hope someone is able to help quickly. Thanks.
I removed pin / patten before flash, the password I enter after starting the rom and my device is decrypted.Weird thing that even if I restore the nandroidbackup done before the flash tells me that the password is wrong, no I know more what try I find myself with the phone blocked. help
That includes also the flash of a no verity file to stay decrypted? Did you changed your twrp too prior or in relation to the rom update? Please give details steps what(file names) you've flashed in which order and what you have before(twrp).
Every information might be helpful
That includes also the flash of a no verity file to stay decrypted? Did you changed your twrp too prior or in relation to the rom update? Please give details steps what(file names) you've flashed in which order and what you have before(twrp).
Every information might be helpful
I used these steps:
Download the full ROM zip from the downloads section above
Reboot to TWRP recovery (please make sure that it's the latest one from one of the links above, unless you're on OxygenOS Oreo, in the case of which stick to the existing recovery that you have and update your recovery only after you've upgraded to OxygenOS Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
From the TWRP menu, Install > Select full ROM zip > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
If you were decrypted earlier, flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
but if I wanted to start from 0 what procedure should I do? it does not matter if I lose all the data I have made a backup of the internal memory
I asked you about the files you used and twrp version you installed too. There are so many people who flash wrong files, so it's absolutely important to make this transparent if you want help to solve your issue.
The clean flash instructions are also in the first post after the ones you've quoted for updating.
Thanks for the info but in the meantime I started making a clean pie install as I couldn't find another solution.
I had a recent titanium backup of my sms, so I decided to start fresh with only that.
I've already spent a few hours setting up some some apps on pie..
Now I think it's too much of a hassle to go back to oreo and then reflash... :/
If only I had that info earlier..
I'll see how it goes
Thanks for the help nonetheless!!!
Clean flashing a new Android version is always better than dirty flashing over the older one although some people have had some success doing it. Why take the risk?
I agree.
It's just that I hadn't kept a titanium backup before attempting the update. (apart from my sms messages that is)
I thought the nandroid backup would be enough in case something goes wrong..:/
Now I have to spend too much time re-creating my setup
I have to spend literally days to reach the same setup..
I tried restoring apps from the nandroid through titanium, but for some reason I have no success
I see no new apps after the operation, although it has that ability theoretically
The reason I'm considering going back is to take a titanium backup and batch restore my setup/apps, after a clean install...
But I'm fearing that won't work too for some reason, maybe I will still have trouble restoring the nandroid and lose more time flashing clean again
I'm a typical unlucky guy
Now all is just a mess.. Not sure what is worth doing from here.
I installed in this order:
TWRP_3.2.3-Pie_siankatabg_OP5.zip
Magisk-uninstaller-20181208.zip
OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988b.zip (without compatibily zip)
Magisk-v18.0 (18000) .zip
Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble) .zip
I always backup user apps, SMS and wifi settings with titanium backup and that can safely be restored on every os generation. Every other restore within titanium backup is risky. I did this from Oreo to pie as well as nougat to oreo or vice versa, doesn't matter.
Similar threads
- Sticky
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
225Hey everyone,
ANNOUNCEMENT
We are starting to push the incremental roll-out of OxygenOS version 10.0.1 for the OnePlus 5/T devices.
Changelog:
Explore what's new on Android 10 here.Code:[B]System:[/B] • Fixed the abnormal call recording issue • Fixed the de-activated alarm issue when the phone was powered off • Updated Android Security Patch to 2020.09 • Updated GMS package to 2020.08 [B]Full Screen Gestures:[/B] • Back gesture from the bottom of the screen is available (OP5T only) [B]Camera:[/B] • Electronic Image Stabilization has been added, bringing you the more stable shooting experience
Notes:
• If you don't have the Community app installed on your device, feel free to download it from here. You can check here for more information on the integrated Feedback tool. Make sure to let us know how you feel about the build here in the thread too, we look forward to reading your feedback.
• Click here to find out how to take logs on OxygenOS.
Warning: Please remove your existing screen lock/pin/pattern/password and set it to swipe before starting the update process.
DOWNLOADS
Full ROM Zips:
• OxygenOS 10.0.1: Official Link | AndroidFileHost Mirror | Google Drive Mirror
• MD5: 8f41d1cca57e8a91879f4b09088103b4
Custom Recoveries:
• TWRP by mauronofrio: Official Link
• TWRP by poad42: Official Link
• blu_spark TWRP by eng.stk: Official Link
• Official TWRP by Dees_Troy: Official Link
Root:
• Magisk: Official Link
Warning: Do not flash partial update OTAs (under 1 GB) on a modified/rooted device! If you want to use partial OTAs, you must first flash the full OxygenOS zip that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing a full zip in recovery.
FLASHING INSTRUCTIONS
Download the necessary files from the section above and follow the steps below:
Note: Dirty flashing is fine if you are running an old OxygenOS version or a ROM based on OxygenOS. If you are, however, coming from a Custom ROM, you must clean flash.
For Non-Rooted Users with a Locked Bootloader and Stock Recovery:
- Download the full zip/incremental OTA from the downloads section above and place it in the root of your internal memory
- Reboot to stock recovery > Shutdown device > Press Volume Down + Power buttons together
- Select language > Install menu > Install from internal > Select the full zip > Flash
- After a successful flash > Wipe cache
- Reboot
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from H2OS/OOS:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are using a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- If you were decrypted earlier, flash xXx No Verity 4.0.zip from here
- Reboot
Warning: Dirty flashing (update) can be risky! Remember that if you face issues after dirty flashing, you will have to clean flash.
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are using a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash xXx No Verity 4.0.zip from here
- Reboot
Never Settle.
XDA:DevDB Information
[OFFICIAL] OxygenOS Stable for the OnePlus 5, ROM for the OnePlus 5
Contributors
Funk Wizard, shadowstep, Some_Random_Username
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2018-09-28
Last Updated 2020-11-20128Download Section Moved to OP and is now maintained by the Official Maintainers !!
Thread Contributors:
@shadowstep
@CamoGeko
@Funk Wizard85Flashing Instructions moved to OP and now maintained by official Maintainers !
Thread Contributors:
@shadowstep
@CamoGeko
@Funk Wizard28Normally I don't comment on stuff like this but the amount of complaining in this thread has caused me to unsubscribe. I'm sorry but how did you guys not expect this coming into the device? You could see OnePlus' track record with the OP3/T (before the past month or so). You're expecting Google-level updates out of a company with probably a tenth of the amount of developers. Would I love to see more timely updates? Absolutely. OnePlus could greatly improve their release schedule by keeping their own development separate from security updates so they can release those updates within a few days of release without introducing regressions but who knows what they plan to do. Yeah, they hyped the camera up and yeah, it has fallen a little flat but I am sure the complaints on their own forum are rolling in hard, where they are actually listening. Plus you all act like Funk Wizard is an official OnePlus employee, expecting him to comment on issues he has no insight on. I'm not directing this as one person, I've been subscribed to this thread since I got the device a month and a half ago and it's been many people so don't think I'm personally attacking you (famous last words).27[How To] Take Log's on OOS/H2OS | Oneplus Logkit | Bug Reports
Hi All
To begin with let me Thank You All for your Active Participation and Feedback on Cheeseburger OOS Updates. We are trying to introduce new features, optimize the software and eliminate the bugs for a better user experience, making OOS/H2OS the Best Optimized OEM Rom :highfive:
In order to do this we would appreciate regular feedback/bug reports/logs from our users to diagnose issues and rectify them :good:
I see that although users are able to reproduce various issues, however very few actually go ahead and submit the logs. Without the logs/bug report its very difficult for the ROM Team to reproduce the same issue and hence takes longer time to identify and kill these issues
Thus to make it simpler, let me introduce you to the OnePlus Logkit which is an OOS in-built feature to capture logs and does not require root access or any special permissions. If you follow the below you can easily take logs and submit for further testing and it does not matter if you are a stock or rooted user :wink:
Before we begin :fingers-crossed:
* Please make a clean flash to check whether the issue still persists before taking the log, most of the times a clean flash will solve your issue so we would appreciate if you do a clean flash before reporting any issue.
* We would appreciate logs without any mods like SuperSU/Magisk/Magisk Modules, Custom Kernels or any other Visual or SystemUI Mods/Substratum.
* This method should work on all OOS/H2OS Versions Stable & Beta as and when it comes for OP5 :fingers-crossed:
* Install the latest User Feedback App and use the same to submit logs/upload and share the link with me so i can forward them to the ROM Team :good:
Follow the below steps to take logs on OOS/H2OS using Oneplus Logkit and before you start, clear/close all recent apps:
1. Go to phone dialer app and dial *#800# :good:
2. Select the first option which says “oneplus Logkit” > Delete history log :good:
3. Click "advanced" > "save log type", select all these options (Kernel, Main, System, Radio, Event, Tcpdump), then click OK :good:
3. Go back & select the first option "save log", it would give you a prompt to reboot (reboot if the issue reoccurs easily, otherwise, click “cancel” :good:
4. Now make the issue reproduce and take a screenshot of the issue wherever possible :fingers-crossed:
6. Enter Oneplus Logkit, choose “other log info”, click “get bugreport info” once > Wait for 2-3 mins and let the Logs get saved till it shows a toast with "get info done" :good:
7. Go back, choose save log again to stop the log reporting :good:
7. Finally, Enter Files > Internal Storage > oem_log, find the folder, zip it to compress and send it to us along with the screenshot :highfive:
As mentioned above use the User Feedback App to submit the logs or upload and share the link the ROM Team on bughunters@oneplus.net and also share the upload link with me :good:
I will try my best to follow it up with the team directly :highfive:
Many Thanks for your support and consideration :highfive:
PS: Screenshots attached for the entire process for easy understanding :fingers-crossed:
