Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
System
1.Optimized network connection
2.Optimized stability for wi-fi connection
3.Fixed screen flickering issue in day light
4.General bug fixes and improvements
5.confirm pin without tapping
Camera
Improved HDR mode
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
I also get that update.
If i download it.. can i just not update right away?
because i want to manually update from twrp and re root with magisk.
Thanks in advance
Sent from my ONEPLUS A6000 using Tapatalk
ossy1337 said:
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
Click to expand...
Click to collapse
I have no photos with older firmware.i think now the photos taken are more brighter
Root users beware: issues with newer TWRP version!
This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
So since twrp latest works fine on my device with encryption included, I can just start the update?
Sent from my ONEPLUS A6003 using Tapatalk
Neurom67 said:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
Click to expand...
Click to collapse
Can you link 3.2.1-1 version? https://eu.dl.twrp.me/enchilada/ There is only 3.2.1-0 or 3.2.2-0
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
No problem with blue twrp.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Fails for everyone atm. Was working fine for me until two days ago before Google updated the api
Sent from my ONEPLUS A6003 using Tapatalk
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Here is why; https://mobile.twitter.com/topjohnwu/status/1029239685338419200
3.2.1.0 installed 5.1.11 fine on my OP6.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
SpectraFun said:
No problem with blue twrp.
Click to expand...
Click to collapse
Batfink33 said:
3.2.1.0 installed 5.1.11 fine on my OP6.
Click to expand...
Click to collapse
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Have TWRP 3.2.3 and installed 5.1.11 just fine.
SMS786 said:
Have TWRP 3.2.3 and installed 5.1.11 just fine.
Click to expand...
Click to collapse
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Vuska said:
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Didn't disable my pattern lock..worked just fine.
I downloaded the zip online and installed through TWRP. Just make sure to reinstall your TWRP installer after installing the full rom OTA (wipe cache/dalvik first), then reboot back into TWRP and install Magisk..then boot into system.
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Chinaroad said:
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Click to expand...
Click to collapse
People seem to be saying this for every release
giebeka said:
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Click to expand...
Click to collapse
Used Oxygen updater to download zip. Rebooted to bootloader. Went Install and selected ZIP. then added TWRP zip as well. Installed both. Rebooted to bootloader again. Flashed elementalx kernel(you can skip it) and magisk. All works fine.
kakkooran said:
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
...
5.confirm pin without tapping
Click to expand...
Click to collapse
I can't find where to enable this. Anyone found it?
Related
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Horgar said:
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Click to expand...
Click to collapse
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Horgar said:
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Click to expand...
Click to collapse
I'm not bothered with twrp recovery so did not flash the zip, but like I said I booted into twrp.img, flashed supersu and suhide and that's it. All working for me including SafetyNet. I used USB OTG for this process.
I did the same as the poster above.
just curious;
but how is Android 8.1? ?
I've found 8.0 to not be as good on battery life as 7.x.x, although I think I have mostly worked that out on my custom kernel...
any other notable goodies?
(ps: I don't care for the pixel launcher or the ambient services stuff..)
mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
I flashed factory image and I have error.
Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
Move the entire folder to a drive other than C drive. I think that might fix it.
NoobInToto said:
Move the entire folder to a drive other than C drive. I think that might fix it.
Click to expand...
Click to collapse
I did. But the error exit
Myo Thu Htet said:
I did. But the error exit
Click to expand...
Click to collapse
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
NoobInToto said:
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
Click to expand...
Click to collapse
I did all u did ?
Yes I checked G+
Only few can install.
Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
mannunikhil said:
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
Click to expand...
Click to collapse
Nope. It looks like Google's fault this time.
NoobInToto said:
Nope. It looks like Google's fault this time.
Click to expand...
Click to collapse
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
mannunikhil said:
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
Click to expand...
Click to collapse
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
NoobInToto said:
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
Click to expand...
Click to collapse
Mine was the fair test just to check if OTA zips are corrupt or not. I provided suggestions for factory image not for OTA, no point in extracting the OTA anyway. And if you had gone through all the threads you would see I mentioned I had similar issue sideload'ing OTA over 8.0.0, so that means we are sailing in same boat. OTAs had compatibility issue with 8.0.0, glad google listened and taken them off.
I still have little lag in app drawer hoping that would be fixed too in republished OTA.
Just signed up for Android beta program and got the 8.1 update for my project fi carrier unlocked Google pixel XL. The update seems to be running smoothly and everything is working so far on my device... I didn't have any issues with installation it installed just fine... Can't wait for Nov security patch supposed to be a good network feature in there in Dev settings.
I am not sure if this may help anyone trying to look at why the issues are present when trying to install:
Android 8.1 beta OTA upgrade on OG Pixel
I, just like many of you, have been experiencing OTA "installation problem" when trying to upgrade to the 8.1 beta. After reviewing comments and what worked for who, I decided to give this a shot and it worked. I am not sure if this will work for other devices (nexus or XLs) and keep in mind that you WILL lose all your data stored on the device, so back up prior to this method.
1. Be sure you are enrolled in the beta program.
2. Wait for the OTA to notify you that it's available.
3. Select "Download and Install".
4. After it has done its duty, DO NOT select "Restart and Install"
5. Go to "Factory Reset" and pull the trigger.
6. Your phone will factory reset, stating it's wiping everything, then it will install the update successfully.
NOTE: this is what worked for me. I'm unsure if it will solve all the "Installation problem" reports which have been made.
It's weird cause when I tried to factory reset, then download and install, it didn't work. Yet, downloading but NOT installing, then factory resetting worked.
After doing this I posted it here: https://plus.google.com/+ChristopherLeeMurray/posts/KDCZXbfAxLJ
You don’t need to sign up to the beta program. Just go to the Google website and download the latest 8.1 factory image. That's what I did and had no problem with flashing it. You can also delete the - w and keep your data. It's getting past the TWRP password to decrypt that I cant do. So can't flash root or recovery. Anyone managed this?
I'd prefer to be in the beta program since I'm a Android apps beta tester. I beta test everything and when it was installing it said on the screen that it's a beta version of the original software version of 8.1 which is what I believe is on Googles page and mine may have errors and defects.. the beta program gets different software than what Google usually posts. Different features and such which isn't in the official version which makes it a beta version.
need small help which would benefit others too.
anybody who are ready to format device or has a good backup
try to flash latest magisk 15.0 on u'r device- Ohh, don't flash directly 15.0- i already tried it and it wouldn't work or change device to generic
our device was working perfectly with magisk upto 14.5 but it lost support later
An user in magisk forum with huawei device claimed that- u need to check 2 options which are under safety net check
tick these options
Preserve force encryption
Preserve AVB 2.0
(Check attached pic)
flash 14.5 magisk- then update magisk to 15.0 within the magisk manager checking the above mentioned options
I invested lot of time this morning to troubleshoot this but couldn't get it right but above mentioned method seems reasonable- so anyone who has backup of entire device or going to format device soon- just try whether this method works and report back.
sreekantt said:
try to flash latest magisk 15.0 on u'r device- Ohh, don't flash directly 15.0- i already tried it and it wouldn't work or change device to generic
our device was working perfectly with magisk upto 14.5 but it lost support later
Click to expand...
Click to collapse
Damn, i was updating to my latest build last week and immediately after i flashed TWRP, Magisk V14.6, i was on V14.5 before the update and since that only after this i went to check phone info, noticing the model changed to generic_a15, i thought that i made something bad. It was Magisk's fault so instead! I restored a previously took backup made before updating and now i have to doing again the update. This time i won't flash nothing above V14.5.
RedSkull23 said:
Damn, i was updating to my latest build last week and immediately after i flashed TWRP, Magisk V14.6, i was on V14.5 before the update and since that only after this i went to check phone info, noticing the model changed to generic_a15, i thought that i made something bad. It was Magisk's fault so instead! I restored a previously took backup made before updating and now i have to doing again the update. This time i won't flash nothing above V14.5.
Click to expand...
Click to collapse
Yes exactly- 14.6 and 15.0 are changing vendor partition .....few claim that preserving force encryption and dm verity does the trick
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
looks like this method is working on huawei p9
sreekantt said:
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
looks like this method is working on huawei p9
Click to expand...
Click to collapse
Thanks for sharing. I'm taking a nandroid backup, testing it in 5 minutes...
RedSkull23 said:
Thanks for sharing. I'm taking a nandroid backup, testing it in 5 minutes...
Click to expand...
Click to collapse
good lord ! waiting for results :fingers-crossed:
sreekantt said:
good lord ! waiting for results :fingers-crossed:
Click to expand...
Click to collapse
It worked
RedSkull23 said:
It worked
Click to expand...
Click to collapse
Ooo !!! yeah--- finally :highfive:
sreekantt said:
Ooo !!! yeah--- finally :highfive:
Click to expand...
Click to collapse
After some tests, personally i don't advice to update it to V15.0 yet. Most is working fine by what i've saw, but i've noticed that on MiX it's not possible to modify some system files after updating. I presume that some error is still under-the-hood and even if the update went fine, there must be some lil' issue. In fact i restored the backup took before upgrading Magisk. I'll wait a bit before update it again
RedSkull23 said:
After some tests, personally i don't advice to update it to V15.0 yet. Most is working fine by what i've saw, but i've noticed that on MiX it's not possible to modify some system files after updating. I presume that some error is still under-the-hood and even if the update went fine, there must be some lil' issue. In fact i restored the backup took before upgrading Magisk. I'll wait a bit before update it again
Click to expand...
Click to collapse
Yeah ...may be regular early stage bugs...that explains viper npt working on many phones after v15...lets wait
I've a nice update for you and every EMUI user man; latest Magisk update, V15.1, solved the vendor issue and now it's everything good. I tested it, look here... no need to keep AVB2.0 ticked before updating, just direct install it through Magisk Manager and you're ready to go
RedSkull23 said:
I've a nice update for you and every EMUI user man; latest Magisk update, V15.1, solved the vendor issue and now it's everything good. I tested it, look here... no need to keep AVB2.0 ticked before updating, just direct install it through Magisk Manager and you're ready to go
Click to expand...
Click to collapse
TFS
did u update from v15 ??
btw- Hide u'r IMEI in 2nd pic
Edit - Updated from v15 to 15.1 successfully with AVB 2.0 unchecked and everything is intact as of now
Update- seems like updating from faulty v15 caused issues- Play store was not able to detect apps, not able to change boot animation etc
So i planned to clean install with Magisk 15.1 - uninstalled every trace and rebooted which caused NRD test keys build
Could be the issue caused by magisk modifying vendor partition and couldn't restore properly
Luckily, i had a complete TWRP backup - wiped everything(including cust, vendor, product) except internal storage > restored(including vendor, product)
flashed magisk 15.1 and everything working perfectly without any issue of modified vendor.
Update 2 - Damn EMUI- No sound
flash stock firmware > locked bootloader > unlock again > restore TWRP backup(only data, system, boot)- Vendor restore never worked for me
sreekantt said:
TFS
did u update from v15 ??
btw- Hide u'r IMEI in 2nd pic
Edit - Updated from v15 to 15.1 successfully with AVB 2.0 unchecked and everything is intact as of now ??
Click to expand...
Click to collapse
Whoops, didn't noticed the visible IMEI usually i remove it... thanks for the heads-up. I've updated by V14.5 anyway
I have trouble when update magisk to v15!
no sound at all!!
no mic...no camera, no call, no audio playing,no video playing!
I had a backup but when restored it...problem persist
what can I do!
plz help
GR5 2017 BLL-L21
Med Benarfa55 said:
I have trouble when update magisk to v15!
no sound at all!!
no mic...no camera, no call, no audio playing,no video playing!
I had a backup but when restored it...problem persist
what can I do!
plz help
GR5 2017 BLL-L21
Click to expand...
Click to collapse
Completely uninstall Magisk through Magisk Manager and reboot. Then flash your original boot.img from your build, reboot, reinstall Magisk Manager again and this time directly flash Magisk V15.1. It should work
RedSkull23 said:
Completely uninstall Magisk through Magisk Manager and reboot. Then flash your original boot.img from your build, reboot, reinstall Magisk Manager again and this time directly flash Magisk V15.1. It should work
Click to expand...
Click to collapse
how can i get the boot.img and how can i flash it???
Med Benarfa55 said:
how can i get the boot.img and how can i flash it???
Click to expand...
Click to collapse
The boot.img is backed up (I don't know the exact folder), then flash it using TWRP
Med Benarfa55 said:
how can i get the boot.img and how can i flash it???
Click to expand...
Click to collapse
To get and flash a clean boot.img, you need to:
1 read your build number from phone info
2 download the update.zip matching your build (BLL-L21C432Bxxx, for example) from Hwmt.ru site
3 extract the update.app from the zip file
4 using Huawei Update Extractor program on PC, open the update.app and extract from it the boot.img
5 flash the boot.img by fastboot typing "fastboot flash boot boot.img" (remember to completely uninstall Magisk before doing this, if not you'll face issues)
and that's all. After that, you can reflash Magisk V15.1 back through TWRP
PalakMi said:
The boot.img is backed up (I don't know the exact folder), then flash it using TWRP
Click to expand...
Click to collapse
Yeah it's backed up, but if it's backed up with a supersu app active on system, the su binary files would be already "dirty"... I flash a clean boot.img before every update because if not, the update verification on boot before update will fail, even if stock recovery is clean
So when backing up superSU or magisk, the boot.img is modified! Good to know
PalakMi said:
So when backing up superSU or magisk, the boot.img is modified! Good to know
Click to expand...
Click to collapse
Exactly! Discovered it by myself during updates :cyclops:
Latest TWRP doesn't support Android Pie 9.0 for OnePlus 6, or at least for me it didn't.
So, I've made a Magisk patched boot image for Android P that we can flash it in fastboot bootloader.
Note: This is not Oxygen OS ROM, this is just a patched boot img for Oxygen OS to make root work. You need to unlock the bootloader before proceeding with anything.
Note 2: Please disable Magisk modules in the Magisk Manager before flashing the patched boot, because some modules might not support the latest OOS and your device will bootloop. If the modules has been updated by the devs to support the latest OOS you can install the modules after that.
Note 3: Sorry guys, I haven't tested the Android Q Developer Previews. Even though Magisk is supported on Q, please flash it at your own risk.
For older versions download from here: Google Drive
Folder updated with Stock boot images as well.
OOS 10 Open Beta 5 Patched Boot
OOS 10 Open Beta 5 Stock Boot
OOS 10.3.1 Patched Boot
OOS 10.3.1 Stock Boot
Flashing instructions:
Code:
fastboot boot (patched_boot_filename_here).img
or
fastboot flash boot (patched_boot_filename_here).img
Thanks @vlaf
reboot to system (if you make another reboot the root won't stick, so continue with the following steps)
Open Magisk (in settings select beta channel) and click install and install Magisk again with Direct Install (recommended)
reboot again and the root will stick even after the reboot.
The thread I followed for the instructions is here. Thanks for @b1czu
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Even easier way to root without TWRP:
1. Install OTA update (Don't reboot).
2. Open Magisk Manager, install Magisk and choose "Install to Inactive Slot (After OTA)" (Now reboot).
3. Now you are rooted without TWRP and without any boot img hassles as well.
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Not work here. Bootloop, only see Bootanimation not more.
SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
If you are I can give you the stock boot image for reverting it.
ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
Yes lol.
It works for me. That's a great help. Thank you.
SpectraFun said:
Yes lol.
Click to expand...
Click to collapse
I've updated the Google drive folder with the stock boot image for DP3.
Download and flash it to revert the bootloop.
I'm not really sure why it didn't work for you. Sorry about that.
Raymond.William said:
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Click to expand...
Click to collapse
Yeah TiBu is the main reason for me as well.
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
geoff5093 said:
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
Click to expand...
Click to collapse
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Yeah I did, but I rebooted an additional time and everything works now!
ManikandanGuru said:
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
geoff5093 said:
Yeah I did, but I rebooted an additional time and everything works now!
Click to expand...
Click to collapse
That's great.
What about safety net?
G0dofWar said:
What about safety net?
Click to expand...
Click to collapse
The first one, ctsProfile, fails. But the second one basicintegrity passes. I believe the only app I use that checks safetynet is PokemonGo and that works for me.
SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
toastyp said:
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
Click to expand...
Click to collapse
Lol sure is unlock.
MrSteelX said:
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
Click to expand...
Click to collapse
Yes. This worked. A simple workaround to get twrp working with encrypted Android P
Download link updated with Beta 1 patched image.
I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
double post
skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to
ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..
WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?
Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??
I've managed to solve all problem by rooting and installing magisk
1. Some apps may not work properly
I have tried every app I used in oreo and each app works fine (I know this is not a solution )
2. Google pay not works
Solution-Google pay works by using a magisk module called
*tezhider4magisk*
https://androidfilehost.com/?fid=5862345805528042557
3. Google play shows device not certified
Solution - Google play shows device is certified using magisk module called
*ClearPlayStoreWithServiesData4Magisk*
https://androidfilehost.com/?fid=890278863836289937
4. Safety net not passed in magisk on open beta 1/2/3
Solution - for safety net to pass in magisk we need to edit a line in build.prop (have to some file explore like es file explorer or root explorer to edit build.prop)
Replace
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
Click to expand...
Click to collapse
With
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Click to expand...
Click to collapse
5. For rooting oxgyen os open beta 1/2/3
Follow guide from developer [Manikandanguru] (all thanks to him?)
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Is there a fix yet for aod/ambient display yet?
Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Doesn't work, crashes display settings.
sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
For me aod/ambient display works perfectly
Have you dirty flashed new beta
Try doing a factory reset I hope that will fix it
BossNexusS said:
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
Click to expand...
Click to collapse
Try clearing cache from recovery that solves a lot of issues
Gmos24 said:
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Click to expand...
Click to collapse
Woah! Sorry about that, I guess I should have tested it first on P. I'll flash OOS Open Beta 2 today and then try this mod. Will update if it works.
And status bar issue is a strange one, no idea about that!
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
droid-devz,
Flash Oos ob02, then twrp blu spark.
Reboot to twrp to check if it's working. Flash Magisk 17.1.
Reboot to system.
Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Yess i just updated from beta 1 to beta 2 no problem
You'll just lose root everytime you update and have to install just magisk again
Don't install custom recovery that causes problems I guess use the above method (in the thread)
droid-devz said:
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
Click to expand...
Click to collapse
Official twrp doesn't work only blue star twrp works
Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Probably not..magisk root rewrites the boot image..safest bet would be to use update manager to flash whole rom updates, then reinstall magisk.
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
JRevenge said:
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
Click to expand...
Click to collapse
does not happen with me !!!
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
digidude512 said:
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
Click to expand...
Click to collapse
safety net passes with current canary build of magisk
plug this into the custom section in the magisk settings under update channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
sorry, hit send before it finished uploading