Hey guys,
has anyone succeeded in upgrading their OPO from nougat to oreo with activated encryption? So far I have tried different roms, but none of them get along with the encryption. Even when I encrypted in the custom rom after a clean flash, they didn't work.
I have tested OmniRom, DU, CandyRom and CarbonRom until now.
Unfortunately, there are no hints in the corresponding threads as to whether the encryption works. I would be happy to receive further information. Thank you!
I tried these last two weeks. In all cases I formatted data first and encrypted after flashing.
Carbon ROM works for me without bugs. It's my daily driver. One downside is battery usage.
AOSP Oreo for OnePlus One worked as well, but with bug 'camera force closing'.
[Android 8.1.0r20][OMS] TugaPower™ 12.0 worked as well but I had Bluetooth issues (wrong Mac address). Not related to encryption I guess.
What was your issue with CarbonRoM?
Good luck.
Peter.Zwegat said:
Hey guys,
has anyone succeeded in upgrading their OPO from nougat to oreo with activated encryption? So far I have tried different roms, but none of them get along with the encryption.
Even when I encrypted in the custom rom after a clean flash, they didn't work.
Click to expand...
Click to collapse
The bold part DOES work, upgrading with activated encryption is not a good way to do it. I.e. first you format data in TWRP and then clean flash.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
hartlijn said:
I tried these last two weeks. In all cases I formatted data first and encrypted after flashing.
[Android 8.1.0r20][OMS] TugaPower™ 12.0 worked as well but I had Bluetooth issues (wrong Mac address). Not related to encryption I guess.
Click to expand...
Click to collapse
I use Tugapower O13 now. However please reveal the mystery Which bloody version of TWRP actually supports Oreo encryption? I have tried three recent versions including the latest official and they all cannot decrypt /data in recovery.
PS. Also what is the best firmware for oreo roms, which one you personally use for carbon rom for instance?
hartlijn said:
I tried these last two weeks. In all cases I formatted data first and encrypted after flashing.
Carbon ROM works for me without bugs. It's my daily driver. One downside is battery usage.
AOSP Oreo for OnePlus One worked as well, but with bug 'camera force closing'.
[Android 8.1.0r20][OMS] TugaPower™ 12.0 worked as well but I had Bluetooth issues (wrong Mac address). Not related to encryption I guess.
What was your issue with CarbonRoM?
Good luck.
Click to expand...
Click to collapse
Good to know because of TugaPower and CarbonROM. With the latter I had a bootloop after a few days without my influence, so I finally switched back to LineageOS 14.1. And AFWall+ didn't work.
1plus said:
The bold part DOES work, upgrading with activated encryption is not a good way to do it. I.e. first you format data in TWRP and then clean flash.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
I use Tugapower O13 now. However please reveal the mystery Which bloody version of TWRP actually supports Oreo encryption? I have tried three recent versions including the latest official and they all cannot decrypt /data in recovery.
PS. Also what is the best firmware for oreo roms, which one you personally use for carbon rom for instance?
Click to expand...
Click to collapse
Why not upgrade from Nougat to Oreo with encryption enabled? Theoretically that should work...
I don't want to use TugaPower because I'm still looking for a custom rom with Slim recents.
1plus said:
...
I use Tugapower O13 now. However please reveal the mystery Which bloody version of TWRP actually supports Oreo encryption? I have tried three recent versions including the latest official and they all cannot decrypt /data in recovery.
PS. Also what is the best firmware for oreo roms, which one you personally use for carbon rom for instance?
Click to expand...
Click to collapse
TWRP does not support decryption. So I always backup and format data
Firmware I flashed before flashing BaconRom is for the baseband 4.0.1.c7.0011.
Peter.Zwegat said:
Why not upgrade from Nougat to Oreo with encryption enabled? Theoretically that should work...
I don't want to use TugaPower because I'm still looking for a custom rom with Slim recents.
Click to expand...
Click to collapse
No, precisely in theory that WONT work. Problem is that sometimes the encryption is changed in the AOSP source itself, so any downstream roms have the same problem.
Daniel (Tugapower builder) in another thread confirmed that no twrp currently works with oreo encryption on oneplus1 after february security patch in AOSP.
I guess our only change is to beg unofficial TWRP builders to patch twrp and build it for oneplus.
Yep, TWRP can't decrypt storage on Oreo. So you can encrypt in Oreo, it works fine, but you can't then access storage in recovery. I find this to my cost in AOSOext, had the camera problem, thought flashing an update might fix it, and found I could not.
So if you need encryption, forget Oreo for now.
While waiting for working TWRP, I've been sideloading rom updates. Thus far this has worked on encrypted Tuga Oreo.
The "famous" february patch is for File Based Encryption that is not supported on Oneplus One (due to missing encryption in ext4 kernel driver).
Oneplus One only encrypt the full data partition (Full Disk Encryption). So in my opinion a rebuild of twrp is needed but also with some other fixs.
Someone has some logs!?!
Thanks
Michele
Can we expect an update for TWRP in near future? That seems to be the biggest problem
BUMP - anyone working on TWRP for Oreo encryption? Without it I can't upgrade from Nougat.
Upgraded to Oreo with working encryption
I had upgraded from lineage 14.1 (encryption enabled) to ASOP Oreo (21/12/2017 (Beta 4) Encryption Enabled) and upgraded to further versions and currently using Resurrection Remix 6.0 (encryption enabled) using TWRP, wiped my system and data partition during each flash, while the internal storage remains untouched.
pp_1 said:
I had upgraded from lineage 14.1 (encryption enabled) to ASOP Oreo (21/12/2017 (Beta 4) Encryption Enabled) and upgraded to further versions and currently using Resurrection Remix 6.0 (encryption enabled) using TWRP, wiped my system and data partition during each flash, while the internal storage remains untouched.
Click to expand...
Click to collapse
You mean you are now using RR6.0 with encryption turn on and the encryption too works in TWRP? As of now I saw "practically all" Oreo rom and all versions or TWRP with encryption turned on will have problem to access data partition within TWRP. Or long question short, you can decrypt data partition in TWRP?
xange said:
You mean you are now using RR6.0 with encryption turn on and the encryption too works in TWRP? As of now I saw "practically all" Oreo rom and all versions or TWRP with encryption turned on will have problem to access data partition within TWRP. Or long question short, you can decrypt data partition in TWRP?
Click to expand...
Click to collapse
Yes using RR6.0 with encryption enabled and can decrypt the data partition in TWRP.
Related
I have installed the CyanogenMod 12 nightlys on my OnePlus using TWRP.
After setting my phone up how I wanted it, I encrypted my phone, not thinking it would cause any issues.
I now want to update to the latest nightly but TWRP will not install anything as it cannot mount any of the volumes.
I assume this is because I encrypted it.
There doesn't seem to be a way to decrypt my phone and there's no way to get to anything in TWRP.
So far I've tried reflashing my bootloader but still can't mount the volumes I need to wipe to reinstall the ROM.
How do I wipe them with the volume being encrypted? Where do I go from here? Thanks in advance!
TWRP / Lollipop encryption bug
See Bug #333 on TWRP's github.com site
Hello everyone,
I think I have a big issue on my hands. My OnePlus One has always been encrypted. When I upgraded to lollipop for Cyanogenmod, I had to wipe my device because the encryption from lollipop was different than kitkat. That seemed to go well and lollipop is working fantastically. I encrypted my device again after installing lollipop. Now, when I try to flash a zip with TWRP, it says my password is incorrect and I can't mount the system. I am able to decrypt my device when booting into Android, so I know my password is correct, but TWRP doesn't think it is. When I upgraded and encrypted my device, I was using TWRP version 2.8.0.1. I have since upgraded to the latest version 2.8.5.1 successfully with no change in behavior. What can I do to get TWRP working again? It is pretty much useless when I can't mount the system and install anything.
Please let me know if this thread belongs elsewhere.
Thanks,
Chris
abel408 said:
Hello everyone,
I think I have a big issue on my hands. My OnePlus One has always been encrypted. When I upgraded to lollipop for Cyanogenmod, I had to wipe my device because the encryption from lollipop was different than kitkat. That seemed to go well and lollipop is working fantastically. I encrypted my device again after installing lollipop. Now, when I try to flash a zip with TWRP, it says my password is incorrect and I can't mount the system. I am able to decrypt my device when booting into Android, so I know my password is correct, but TWRP doesn't think it is. When I upgraded and encrypted my device, I was using TWRP version 2.8.0.1. I have since upgraded to the latest version 2.8.5.1 successfully with no change in behavior. What can I do to get TWRP working again? It is pretty much useless when I can't mount the system and install anything.
Click to expand...
Click to collapse
Have you tried flashing back to 2.8.0.1 to see if it still works?
Newer versions of TWRP have encryption problems.
meekrawb said:
Have you tried flashing back to 2.8.0.1 to see if it still works?
Newer versions of TWRP have encryption problems.
Click to expand...
Click to collapse
I just tried 2.8.0.1 with no success. This appears to be a known issue (issue 333 on the TWRP GitHub repo), and people are suggesting to just upgrade nightly versions without backing up first. :S
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1:
!NEW AND THE ONLY RECOMMENDED METHOD!
You must be on Oreo. Before flashing delete all your saved fingerprints and screen locks.
1. Reboot to bootloader (Bootloader must be unlocked)
2. fastboot boot recovery-xx.img (in ADB)
-> Grab official recovery from here: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
3. Wipe System/Data/Cache/Dalvik
4. Flash Lineage & TWRP Installer zip
-> Grab TWRP installer from the link above
5. Reboot to recovery using TWRP Recovery (In TWRP go to Reboot -> recovery)
6. Flash Gapps/MicroG (opengapps.org -> platform ARM64 -> Android 8.1 + Variant [IMO pico is your best pick])
7. Flash Magisk [latest] if you want ROOT (I bet you want!)
-> Grab Magisk from here: http://tiny.cc/latestmagisk
8. Reboot to System
How to update from previous build:
If you don't have permament TWRP, just follow the method above.
If you have permament TWRP:
Delete all your previous fingerprints (just for safety)
Boot to TWRP
Wipe Data/Cache/Dalvik (wiping is optional - but clean flash is always encouraged)
Flash Lineage ROM zip file
Flash Magisk
Flash Gapps/MicroG
Reboot
KNOWN BUGS:* No bugs right now! Enjoy bug-free rom!
If you have signal stability issues, try this:
Dial *#*#4636#*#*
Go to Phone information
Set Preferred Network Type from Unknown to LTE or WCDMA only
WHAT IS WORKING:* Everything else
LINEAGE BUILD CHANGELOG:
Code:
[FONT="Arial"]
[B]Most recent build (24.03.2018):[/B]
Fixed portrait mode
Enabled hal3 camera by default
Added doze
Lineage upstream
[B](22.03.2018): [/B]
Fixed double tap to wake (should only work for focaltech panel)
Rebased kernel to latest oreo source drop
Enabled cpusets
Lineage upstreams
[B](13.03.2018): [/B]
Fixed verity issue (builds now can be flashed without magisk)
Fixed Live Display
Fixed Substratum
Fixed ril issues
Lineage Upstream changes
[B](08.03.2018): [/B]
Fixed notification light (should work in call cases now)
Fixed slow charging
Fixed deep sleep issue
Added navbar toggle
Fixed goodix fingerprint issue (should work for all and all 5 fingerprint should be registered now)
Lineage Upstream changes
[B](06.03.2018): [/B]
Fixed led light
Added fingerprint gestures
Fixed Bluetooth name
Fixed battery capacity
Lineage upstream changes[/FONT]
Have fun with LOS!
Q&A
What does NIGHTLY mean?
Nightlies are automatical builds (every few days), so it mean you will have frequent updates, recent Lineage changes will be present in a rom. Also fixes and new stuff will come faster!
How I can go back to stock?
Grab Mi A1 tool from here: https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857.
Install it in your PC, enable USB Debugging on your phone, plug phone to PC
Click Flash Stock ROM button
Click Download ROM and wait
Click FlashAll. Your phone will reboot to fastboot and it will start to flash stock
[You will loose all your data, so backup is encouraged]
Do I need to downgrade to Nougat before flashing?
Not anymore It's advised to flash from Oreo
After update my FP don't work, wat to do?!
Make a clean flash using method from OP. If clean flash won't help, try: https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
Is Dolby working on Lineage 15.1? How to install it?
Just download Magisk module and enjoy!
My mobile signal is unstable. Is there a way to fix it?
Yes, see a workaround from OP
Why Selinux is permissive, not enforcing?
In unofficial builds Selinux is permissive. If the build goes official, it will have Selinux set to enforcing. Don't worry, just wait for official version!
Is this rom stable enough to be a daily driver?
Depends what you need. Check buglist - if these bugs don't bother you - it can surely be a daily driver
When new build will be avaible?
Don't ask for ETAs. Developers are working hard (in their free time!) to fix a bugs - we just need to wait patiently.
Some users are experiencing wifi issues (myself included). How can i fetch the log?
Steps to reproduce: Turn off bluetooth. wait a moment... wifi will start dropping connection a lot. To fix, just turn on BT again.
Headphones do not work.
Headphones are working!
By the way. I found a bug. The equalizer don't work correct. Everytime when you skip a song you must tap the bass regulator again in the equalizer app. When you don't do it, it plays without bass.
konradit said:
Headphones do not work.
Click to expand...
Click to collapse
Everything fine here, try to reflash
Installed and used for 24 hrs with no apparent problems. No fingerprint bug.
All the other bugs reported in OP exists.
Returned to Stock since I found it a bit smoother.
I will wait for a more stable official build
Good work so far
still
rasputine said:
still
Click to expand...
Click to collapse
Are you using the deadman twrp? I got that using other TWRP versions.
goofball2k said:
Are you using the deadman twrp? I got that using other TWRP versions.
Click to expand...
Click to collapse
Yes I'm using deadman's twrp
rasputine said:
Yes I'm using deadman's twrp
Click to expand...
Click to collapse
Did you reboot after doing the data wipe?
Can I install LOS 15.1 without flashing magisk? I have tried this and had bootloop before any lineageos bootlogo
radogost said:
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1: There's a few working methods. First, most popular one:
....
Third, last one:
Boot to the recovery (same recovery as method above)
Wipe system and cache ( data is optional if your are on Oreo)
Check which partition you are on (A or on partiton B)
Flash the rom on one of the partitions
Flash the twrp installer zip
link: http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
Reboot back to the recovery
Switch to the second partition
Flash GAPPS/MicroG and Magisk
Reboot
Click to expand...
Click to collapse
Sorry to pick this up again but the last method implies that TWRP will be installed permanently as default recovery, right? I was successfull only with the first method however I always end up in LOS recovery when try to enter recovery with Vol-up+Power after everything is installed.
I'm sure we all agree that this whole recovery mess needs to be sorted out quickly. Even experienced users are hitting snags and flood the board with questions .
goofball2k said:
Did you reboot after doing the data wipe?
Click to expand...
Click to collapse
Yes sir
i face the same issue with any methond i am using.
in some cases i am unable to install all the zips and in another case i am unable to install only magisk(error 1)
i followed exactly the steps.
any suggestions?
I'm not sure why the issues. I followed the steps in the OP, except I didn't flash TWRP, I just boot to it temporarily.
I did the following:
Flashed 7.11.18 ROM using MiFlash.
Booted into the ROM, set it up minimally.
Rebooted to fastboot, unlocked bootloader
booted temporarily to deadman TWRP, wiped system/cache/dalvik/data (just to be sure it is completely clean)
rebooted and then booted back into deadman TWRP
flashed LOS.
rebooted and then booted back into deadman TWRP
Flashed gapps and magisk.
rebooted to OS.
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Flashed from 8.1.10 without any problems...
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
---------- Post added at 01:47 PM ---------- Previous post was at 01:47 PM ----------
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
t0per666 said:
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Click to expand...
Click to collapse
Tornado95 said:
Flashed from 8.1.10 without any problems...
Click to expand...
Click to collapse
Hmm so which one is telling the truth? ??
Sent from my Xiaomi Mi A1 using XDA Labs
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
TWRP
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
Orangefox TWRP
https://sourceforge.net/projects/or...OrangeFox-R9.0-2-whyred-MIUI-Pie.zip/download
(This version not compatible with oreo so use it for miui pie only)
https://youtu.be/1WnxULKjgdE
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
gursewak.10 said:
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
https://youtu.be/1WnxULKjgdE
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
Click to expand...
Click to collapse
So from what I've read, if you flash the rom first, then update your recovery you should be good?
Sent from my Redmi Note 5 using Tapatalk
OrangeFox
gsmyth said:
So from what I've read, if you flash the rom first, then update your recovery you should be good?
Sent from my Redmi Note 5 using Tapatalk
Click to expand...
Click to collapse
Yeah sure
gursewak.10 said:
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
Click to expand...
Click to collapse
does this version support f2fs? Thanks in advance.
sushuguru said:
does this version support f2fs? Thanks in advance.
Click to expand...
Click to collapse
Yes it supports.
Remember to backup internal storage before changing file system.
Thanks bro it works like charm
Working good but after the restart the twrp is gone, stock recovery gets replaced
I tried to flash then no-verity-opt-encrypt-6.0.zip but getting error not installing
Please tell me what to do now, twrp is replacing by stock recovery
Update - It is resolved now, I flashed magisk over it and twrp is not replaced anymore
gursewak.10 said:
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
TWRP
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
Orangefox TWRP
https://sourceforge.net/projects/or...OrangeFox-R9.0-2-whyred-MIUI-Pie.zip/download
(This version not compatible with oreo so use it for miui pie only)
https://youtu.be/1WnxULKjgdE
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
Click to expand...
Click to collapse
Thank you for sharing.
Can I install it without magisk?Will it be gone after the device restarted without installing magisk?
Just info : Link updated https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
it's a recovery so magisk is your choice if you want it or not.
ashish1989 said:
Working good but after the restart the twrp is gone, stock recovery gets replaced
I tried to flash then no-verity-opt-encrypt-6.0.zip but getting error not installing
Please tell me what to do now, twrp is replacing by stock recovery
Update - It is resolved now, I flashed magisk over it and twrp is not replaced anymore
Click to expand...
Click to collapse
I had this problem before. when you flash twrp, try to reboot to twrp again. then the twrp won't be flashed by stock recovery.
I've tired most of the top ROMs for the past 2+ years and haven't had any success getting encryption to work on anything past Android Nougat. Either boot decryption will work and TWRP fails to decrypt or vice versa or neither will be able to decrypt.
For a while (using LineageOS) you could flash Nougat, encrypt the device, then wipe AppData + System (keeping the encryption), and flash the Oreo ROM and it would work. Although I haven't had luck with that anymore.
What's causing this issue with N5 and successful encryption? Is TWRP fundamentally outdated or flawed? Is there something wrong with N5 hardware that prevents it from working with newer Android versions? And is there a successful way to get encryption working?
NOTE: I have done the Nexus5 system repartition , this was occurring before I performed that, and I've tried with both stock TWRP and partition TWRP to no success.
Everything is pretty simple. TWRP for hammerhead should be updated to support new encryption introduced since Oreo. Many other devices have updated device tree to support new encryption...