Database Info

[Q] I want to update the TWRP.. it's possibly whitout a pc/adb ??

The question it's simply and i'ts on title:
On My OPO i have flashed the TWRP 2.7.1.1 successfully about one month ago........ now i advice it's been released the 2.8.0.0 and i want try to update it:
- I have downloaded the http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.8.0.0-bacon.img it's no possibly to flash it or upgrade it directly from recovery right ?
On Official page i have looked there is a APP called TWRP Manager. I have installed this APP but when i launch it i obtain a warning that APP force me to install the "Busybox stericson". WTF it's that this busybox ??? It's a addons for my phone ??? I can install it... but i don't know if this APP make some problems whit CM11S and/or make unstable the stock rom......
Exist another method instead using a PC and ADB ??

DjDiabolik said:
The question it's simply and i'ts on title:
On My OPO i have flashed the TWRP 2.7.1.1 successfully about one month ago........ now i advice it's been released the 2.8.0.0 and i want try to update it:
- I have downloaded the http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.8.0.0-bacon.img it's no possibly to flash it or upgrade it directly from recovery right ?
On Official page i have looked there is a APP called TWRP Manager. I have installed this APP but when i launch it i obtain a warning that APP force me to install the "Busybox stericson". WTF it's that this busybox ??? It's a addons for my phone ??? I can install it... but i don't know if this APP make some problems whit CM11S and/or make unstable the stock rom......
Exist another method instead using a PC and ADB ??
Click to expand...
Click to collapse
Normally busybox is free on the playstore. Not sure how to explain but it adds the possibility to do some commands, in this case TWRP Manager.
But I read posts from 2 people that they had issues with installing CM11s from scratch so I would wait to see if it is ok to do so or wait for an update.
2.7.1.1 works do there is no rush to update.

The Busybox installer by stericson is from what I gather not dangerous and is useful for many apps, such as the TWRP Manager. But if you are unsure, I believe the app Flashify does not require Busybox to be installed (don't quote me on that), and it can be used to flash the new TWRP 2.8 image file. Search for Flashify in the Google Play store and install it. Then select "recovery image" and select the TWRP .img file. That worked for me when I tried yesterday, but I can't give you any guarantees.

ok boys... tomorrow i uninstall the official twrp manager and try to use this app........... i hope this not brick my opo

DjDiabolik said:
ok boys... tomorrow i uninstall the official twrp manager and try to use this app........... i hope this not brick my opo
Click to expand...
Click to collapse
Do not use 2.8, it has issues with flashing kernels. It can cause bootloops. Just stick with 2.7.1.1, it's rock solid.

TheShoxter said:
Do not use 2.8, it has issues with flashing kernels. It can cause bootloops. Just stick with 2.7.1.1, it's rock solid.
Click to expand...
Click to collapse
I used 2.8 and flashed a ROM and flashed multiple kernels without any problems.
As mentioned before, use Flashify. https://play.google.com/store/apps/details?id=com.cgollner.flashify

Thanks for all reply.... i have correctly updated my Recovery from 2.7.1.1 to this 2.8.0.0
For now i don't need to change nothing from STOCK ROM... i have already unlock the bootloader some month ago.. i have root permission and i have a good feedback whit the stock CM11S............
Otherwise if i have some problems i thinks i can re-download and i can reflash the 2.7.1.1 over this 2.8.0.0 whitout any problems rights ?

DjDiabolik said:
Thanks for all reply.... i have correctly updated my Recovery from 2.7.1.1 to this 2.8.0.0
For now i don't need to change nothing from STOCK ROM... i have already unlock the bootloader some month ago.. i have root permission and i have a good feedback whit the stock CM11S............
Otherwise if i have some problems i thinks i can re-download and i can reflash the 2.7.1.1 over this 2.8.0.0 whitout any problems rights ?
Click to expand...
Click to collapse
Correct.
Sent from my Oneplus One

zephiK said:
I used 2.8 and flashed a ROM and flashed multiple kernels without any problems.
As mentioned before, use Flashify. https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
Hmm, I'll give Flashify a try then.

twrp manager works fine for me
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en

gyroscope/ autorotation not working after 5.1 roms flashed.

No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?

sseng587 said:
No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?
Click to expand...
Click to collapse
Revert to some other cm12.1 build nightly instead or flash latest nightly build
May be it's a problem associated with that build

I tried other 12.1 rom, same results. Cm 12.0 is fine though.

Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip

I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m

[email protected] said:
I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m
Click to expand...
Click to collapse
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1

Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m

[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Same problem here, I think the problem is located in the firmware. So it is something that CM will have to modify. Because the latest firmware (like the one in the zip) is also included in the latest nightly builds.
If rotation is something you need badly you can try the following 2 options:
- use an app to do the rotation like: playstore:rotation manager
- flash the stock CM11 and the accompaning firmware back, reflash the firmware in attachement and then reflash the CM12.1 nightly. (untested)

[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Little update ... Rotation seemed to work for a minute but has since stopped. Frustrating.

Same issue here, all sensors are shown to be off by Sensor Kinetics from Play Store.
Flashing everything from the factory restore image via fastboot did not help...

I have been troubleshooting the issue of rotation/orientation sensors seemingly not working. What I have found on my new OnePlus One, running the latest CyanogenMod 12.1 nightly builds is this:
Once I root the device using SuperSu I cannot regain use of the sensors/auto-rotate. I use the app named Phone Tester and after the phone is rooted the comps/orientation sensors show no output.
If I unroot the phone and reboot several times, the orientation subsystem functionality returns.
No matter what firmware/Cyanogen ROM combination I use the result is the same.
I wonder if anyone else can confirm that their screen rotation ceases to function when the phone is rooted.
Cg6ry79m

davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m

[email protected] said:
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m
Click to expand...
Click to collapse
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app

cantthinkofagoodname said:
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I had used the latest SuperSU. The problem persists even when I don't use SuperSU though. I feel like it is some sort of race condition as processes kick off during boot or something.
I wish I wasn't relying on voodoo to get the accelerometer/auto-rotate to work.
cg6ry79m

sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Yes! Thank you this worked. Was getting really annoyed by this issue, thought I was gonna be stuck on 5.02 forever. Tried flashing different nightlies, different modems...
Flashed everything from the 20150505 Firmware, the first 8 steps in the guide quoted above. For some reason flashing each file manually works as opposed to flashing the zip with all of them- odd, but hey whatever works...

Great thanks that worked!!
Sent from my A0001 using Tapatalk

I wanted to close out this issue as I believe it has been resolved. This problem was also a case of TWRP not correctly flashing the firmware. I "downgraded" from the X.X.0.7 TWRP to that X.X.0.6 version that others have posted links to in other threads. Frankly the GUI on this version is better.
So I downgraded TWRP, reflashed the 9 July Cyanogen nightly build. Accelerometer, compass, and proximity sensor working fine. Survived reboots. Survived new nightly.
Thanks to you folks who posted the issue about TWRP not flashing firmware correctly.
cg6ry79m

sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
i have issue with gyroscope like this video:
https://www.youtube.com/watch?v=cXsB2LG1ftM
Thanks for this method but not working for me!
could you give me more detail working firmware
i try 8 step in fastboot mode with 20150515 and 20150518 firmware but the issue still here!

Which version of twrp do you use? And did you flash the latest su?
Sent from my A0001 using Tapatalk

davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Thaks guys it worked for me
Cheers!

TWRP downgrade works but strangely.

Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?

Unnecessary screenshot attached :good: enjoy~

Tiash420 said:
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Click to expand...
Click to collapse
Did you try flashing the recovery img via TWRP itself? And are you using any theme on TWRP 3.x.x.x?

Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.

Tiash420 said:
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Click to expand...
Click to collapse
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk

Renosh said:
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I get the notification quick settings bug, I mean, I can't get quick setting toggles directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that? Meanwhile my friend on the other hand downloaded the same version from the same place and he doesn't face those bugs. :'| Why is this happening to me?

Tiash420 said:
I get the notification quick settings bug, I mean, I can't get quick settings directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that?
Click to expand...
Click to collapse
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk

Renosh said:
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|

Tiash420 said:
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Click to expand...
Click to collapse
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk

Renosh said:
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well doesn't matter, I flashed Sultan's unofficial CM13 build via Kumajaya's TWRP 3.0.0.0 and it works fabulously! jgcaap can wait, I'm sure it's not much different in features and stuff! :3

Custom Recovery

so I have the asus transformer prime TF-201 and the twrp recovery available is 2.6.6. Can i actually flash 2.8.5 ?

QuadTurbo said:
so I have the asus transformer prime TF-201 and the twrp recovery available is 2.6.6. Can i actually flash 2.8.5 ?
Click to expand...
Click to collapse
The latest official TWRP version is 2.6.3.0 and the device is no longer maintained.
Where did you find the 2.8 version?

QuadTurbo said:
so I have the asus transformer prime TF-201 and the twrp recovery available is 2.6.6. Can i actually flash 2.8.5 ?
Click to expand...
Click to collapse
Yes, you can upgrade your version of TWRP as long as there is a newer version of TWRP for your model number.
If you get it in .img format you can flash it in TWRP(TWRP can flash .img files) or with Flashify.
Or
If you get it in .zip format you can flash it in TWRP also.
Just remember, after you flash it in TWRP you need to find the reboot option at TWRP main menu and choose "reboot recovery" and it will reboot into the new TWRP, if you fail to do this step you won't keep the new version and it will revert back to the older version that you already had.
Sent from my SCH-I535 using Tapatalk

http://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Well if you look at this thread the rom is for TF-700 and TF-201 and the pre requisites require TWRP 28.0.0. While The official release for TF-201 Is 26.6.3. This Confuses me. How Do I flash it???

Droidriven said:
Yes, you can upgrade your version of TWRP as long as there is a newer version of TWRP for your model number.
If you get it in .img format you can flash it in TWRP(TWRP can flash .img files) or with Flashify.
Or
If you get it in .zip format you can flash it in TWRP also.
Just remember, after you flash it in TWRP you need to find the reboot option at TWRP main menu and choose "reboot recovery" and it will reboot into the new TWRP, if you fail to do this step you won't keep the new version and it will revert back to the older version that you already had.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395.
Can you Just explain This KANG TWRP?????

QuadTurbo said:
http://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Well if you look at this thread the rom is for TF-700 and TF-201 and the pre requisites require TWRP 28.0.0. While The official release for TF-201 Is 26.6.3. This Confuses me. How Do I flash it???
Click to expand...
Click to collapse
When you see a thread that says a ROM requires a certain version of TWRP, it means you need "at least" that version and not a version older than that. Best bet is to always use the newest, most up to date TWRP then you don't have to worry about it because newer versions of TWRP can flash older ROMs with no problem but older versions of TWRP can't flash some newer ROMs. As ROMs become newer they require newer TWRP because partitioning structure changes with each new version of android so the recovery has to be compatible with the changes made in partition structure, that's why older recovery can't flash some newer ROMs, because the older recover doesn't have the necessary changes to keep up with changes in partition structure.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 05:06 PM ---------- Previous post was at 05:02 PM ----------
QuadTurbo said:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395.
Can you Just explain This KANG TWRP?????
Click to expand...
Click to collapse
There isn't much to explain other than the fact that "KANG" means they created that recovery using work someone else did, it means they probably ported that recovery from a different device.
Sent from my SCH-I535 using Tapatalk

@QuadTurbo
Good advice: READ! As much as you can find about what you're going to do. XDA + google will help you to find nearly everything...
KANG TWRP is a unofficial TWRP, its built for a unofficial bootloader (ported from another device) (included in the Hairybean Rom Thread)
Latest TWRP 3.0.2.0 + Hairybean Bootloader 4.2.1 + instructions can be found when you click the links.
Make sure to READ and UNDERSTAND everything before you proceed flashing a modified bootloader to your device, as you can easily (hard)brick it by flashing a wrong bootloader.

So you're implying that i can actually flash an unofficial version of TWRP Recovery.

LS.xD said:
@QuadTurbo
Good advice: READ! As much as you can find about what you're going to do. XDA + google will help you to find nearly everything...
KANG TWRP is a unofficial TWRP, its built for a unofficial bootloader (ported from another device) (included in the Hairybean Rom Thread)
Latest TWRP 3.0.2.0 + Hairybean Bootloader 4.2.1 + instructions can be found when you click the links.
Make sure to READ and UNDERSTAND everything before you proceed flashing a modified bootloader to your device, as you can easily (hard)brick it by flashing a wrong bootloader.
Click to expand...
Click to collapse
Since I plan on running a NV Flash on my prime before flashing any other official or unofficial version of custom recovery. How do i Find out the number of my bootloader. Since I Unlocked The Bootloader, CPU-Z and any other app like it keeps showing me bootloader unknown.

Oxygen OS 5.1.11

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?