Hi all, just got my new V20 (Verizon)! Feels good to be back after my beloved G3 died last year. I know that Android 7.0 includes the new file-based encryption, but you have to enable it from developer options. Should be "convert to file encryption." However I don't have the option on my V20. Am I missing something? Does anyone else have the option?
On Verizon as well and I don't have it either.
All v20 have encryption enabled out the box as when we root and use TWRP have to wipe the whole thing
Sent from my Pixel XL using Tapatalk
nexus6r3plicant01 said:
All v20 have encryption enabled out the box as when we root and use TWRP have to wipe the whole thing
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Does that mean that after we finish installing TWRP and boot the phone for the first time it will start using the file based encryption again?
farleydwnsu said:
Does that mean that after we finish installing TWRP and boot the phone for the first time it will start using the file based encryption again?
Click to expand...
Click to collapse
No
To be able to use twrp you have to remove encryption and mot use it as it blocks twrp from backing up your data.
Therez a fix for twrp i started to port to the v20 so it wasnt a requirement to decrypt but in all honesty encryption slows your handset down a ton!
So you either use full device encyrption by defualt.
Or you formatt your phone and flash a Rom that has decryption turned off.
If you ask the dev of your model nicely that makes the rom you are gonna use i bet he would make you a boot.img with it on if you wanted. Just know that twrp backups of your data will not work.
Related
Following this thread http://forum.xda-developers.com/showthread.php?t=2447534 you'll find an app called Dual Boot Patcher.
With this app you can patch ROMs for dual booting. No need for special recovery, no need for kernel with kexec patch. You can even flash the ROMs from within the app. Only thing thats missing for now is backup and recovery, but according to the dev it will be implemented.
How To:
1. Download the app here https://snapshots.noobdev.io/ and install.
2. In the app go to ROMs. There you'll find your current ROM. press the three dots and choose "Set Kernel". Now you're ready for patching and flashing you first ROM.
3. Choose "Patch zip-file" from the main menu. There you choose which slot. On OnePlus One you have to choose Data (rom gets installed on data partition) as our system partition is to small to support multiple roms. After the Rom you can patch gapps and other files to flash (supersu, v4a, etc) the patched files end with data-slot-xx.zip e.g. cm13.zip -> cm13data-slot-01.zip
4. now you can flash the patched files either in recovery or directly in the app.
Coming from the LG G2 which had no MultiROM I'm using this app for a long time with no problem. Right now i have 3 Roms on my phone. Primary is AOSParadox 5.1.1, data slots are Sultans cm12.1 and Omni 6.0
That's very cool, thank you for sharing I will be trying it
Tried the app in s4, quite useful one also having support for app sharing... I thought it never supports one plus one... Well try..
Sent from my A0001 using Tapatalk
Thanks for sharing mate. BTW, is there any possibility of a hard-brick? Since i barely get any free time from my job and opo is my primary & only device, i really can't go through all the hassle of recovering from a hard brick.
Gave it a try. Didn't work on patching zip. Threw an error code - 15
abhibnl said:
Thanks for sharing mate. BTW, is there any possibility of a hard-brick? Since i barely get any free time from my job and opo is my primary & only device, i really can't go through all the hassle of recovering from a hard brick.
Click to expand...
Click to collapse
Honestly I don't know. I've used it a lot on my G2 and my OPO. Never bricked anything. If it happens that the patched ROM does not boot just boot into recovery and flash the boot.img of your primary ROM. You can find the boot.img at data\multiboot\primary.
wickedninjalo said:
Gave it a try. Didn't work on patching zip. Threw an error code - 15
Click to expand...
Click to collapse
Strange. Never had an error while patching zip files. Did you use the patcher app on your phone or the windows version? I never tried the windows version.
tropenfrucht said:
Strange. Never had an error while patching zip files. Did you use the patcher app on your phone or the windows version? I never tried the windows version.
Click to expand...
Click to collapse
Phone version, I'll give windows version a try and report back
can't install the utilities due to opo does not support aroma, i patched and flashed and changed to secondary and does not boot
---------- Post added at 08:02 AM ---------- Previous post was at 07:59 AM ----------
abhibnl said:
Thanks for sharing mate. BTW, is there any possibility of a hard-brick? Since i barely get any free time from my job and opo is my primary & only device, i really can't go through all the hassle of recovering from a hard brick.
Click to expand...
Click to collapse
i don't believe u will hard brick due to its flashed to the system or data, so all u have to do is make a nandroid backup 1st, and if things go wrong, like above just flash ur boot image or just restore ur nandroid.
Same here. Got an error code 15 while trying to patch
Also, does it matter what data slot ID you enter?
@ tropenfrucht This is very helpful feature and I have been using it for over a month and the best part is easy to use keep up the good work.
Great mate
Do i have uninstall multirom first or may I have both systems?
Enviado desde mi A0001 mediante Tapatalk
It just occured to me, that despite encrypting my device, I can boot into TWRP recovery and flash things to various partitions without entering a password.
Doesn't that essentially mean that the encryption key must be stored somewhere by TWRP in a clear (unencrypted) form?
If so, doesn't root basically render device encryption meaningless? Sure the average phone thief might not care to crack into it, but it would probably be trivial for anybody with a little technical knowledge and time on their hands. And police probably have a step-by-step process for cracking rooted devices.
Does root compromise encryption?
static416 said:
It just occured to me, that despite encrypting my device, I can boot into TWRP recovery and flash things to various partitions without entering a password.
Doesn't that essentially mean that the encryption key must be stored somewhere by TWRP in a clear (unencrypted) form?
If so, doesn't root basically render device encryption meaningless? Sure the average phone thief might not care to crack into it, but it would probably be trivial for anybody with a little technical knowledge and time on their hands. And police probably have a step-by-step process for cracking rooted devices.
Does root compromise encryption?
Click to expand...
Click to collapse
To answer your exact question, no, root doesn't compromise encryption. Root and TWRP are two separate things, you can have TWRP without root. However, TWRP does allow access to your data without requiring authorisation.
Doesn't "enable Password on Boot" in Settings/Security, force a password onto TWRP as well?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Doesn't "enable Password on Boot" in Settings/Security, force a password onto TWRP as well?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah that's a good point, I don't use that feature as I find it annoying so I forgot about it.
SlimSnoopOS said:
Doesn't "enable Password on Boot" in Settings/Security, force a password onto TWRP as well?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The only way your data is truly encrypted (in my opinion) is doing just that.
Agent said:
The only way your data is truly encrypted (in my opinion) is doing just that.
Click to expand...
Click to collapse
Thanks so much! This is exactly what I was looking for.
I don't know why it didn't occur to me earlier. I'm glad I don't have to choose between security and usability (root, TWRP, etc).
i was thinking about this today actually, because my phone has no encryption (both system and userdata).
However, with purenexus rom and cerberus if your phone is ON when it's stolen, you can essentially prevent someone from booting into recovery since the normal power menu is not available, and pressing and holding the power button for 10 secs just reboots the phone into OS again which is locked. Also, the USB defaults to charging, so data is inaccessible.
is there a way boot into recovery in a situation such as this?
2x4 said:
i was thinking about this today actually, because my phone has no encryption (both system and userdata).
However, with purenexus rom and cerberus if your phone is ON when it's stolen, you can essentially prevent someone from booting into recovery since the normal power menu is not available, and pressing and holding the power button for 10 secs just reboots the phone into OS again which is locked. Also, the USB defaults to charging, so data is inaccessible.
is there a way boot into recovery in a situation such as this?
Click to expand...
Click to collapse
They can hold Power and volume down to boot right into bootloader (and subsequently recovery) from lockscreen. I did this last night since restoring my TWRP 3.0 backup locked me out of my 5X lol
Edit: just want to be clear, I do not have Cerberus. idk if it blocks the above combo as well
SlimSnoopOS said:
They can hold Power and volume down to boot right into bootloader (and subsequently recovery) from lockscreen. I did this last night since restoring my TWRP 3.0 backup locked me out of my 5X lol
Edit: just want to be clear, I do not have Cerberus. idk if it blocks the above combo as well
Click to expand...
Click to collapse
You're right, that way definitely works. And I'm not sure that it it can block that tbh
2x4 said:
You're right, that way definitely works. And I'm not sure that it it can block that tbh
Click to expand...
Click to collapse
Keep in mind that when your data is encrypted and a boot password is used, they may can get into the bootloader, but they can not get inside your system. They will have to wipe it to get anything on it that will work.
Agent said:
Keep in mind that when your data is encrypted and a boot password is used, they may can get into the bootloader, but they can not get inside your system. They will have to wipe it to get anything on it that will work.
Click to expand...
Click to collapse
Thanks for the clarification. Is there any way to get the boot password feature without encrypting my data?
I flashed the no-verity-opt-encrypt-5.1.zip to disable the internal encryption, but now the phone can't boot into the OS anymore. It can still boot into TWRP, is there any way to recover it? Thanks.
awdrifter said:
I flashed the no-verity-opt-encrypt-5.1.zip to disable the internal encryption, but now the phone can't boot into the OS anymore. It can still boot into TWRP, is there any way to recover it? Thanks.
Click to expand...
Click to collapse
lol that zip doesn't 'disable encryption', it prevents the system from encrypting the storage the first time that it boots with a non-encrypted storage. Installing SuperSU or Magisk is usually enough because they have that script integrated too.
The way to fix it is to go to Wipe --> Advanced wipe --> Format data --> type 'yes'. You're gonna lose your internal storage and data.
After doing that, don't reboot. Go to Install and flash Magisk or SuperSU or that no-verity zip (only flash one of those).
Well, I tried to update TWRP last night and I think I have completely bricked it. To flash it back requires opening up the phone, which I'm not going to do. Maybe I'll make a smash the phone video later. I'm glad I only attempted this after I got a new phone, never ZTE, never again.
awdrifter said:
Well, I tried to update TWRP last night and I think I have completely bricked it. To flash it back requires opening up the phone, which I'm not going to do. Maybe I'll make a smash the phone video later. I'm glad I only attempted this after I got a new phone, never ZTE, never again.
Click to expand...
Click to collapse
Lol the one who messed up was you, not ZTE
If you knew that flashing that zip on an already-encrypted storage wouldn't do anything, it'd still work...
Also, I'm curious: What did you do to brick your phone while attempting to update TWRP? It was as simple as putting the .img on your phone and goin to Install image...
Well, if I knew why it bricked I wouldn't flash it would I? The ZTE phone had some kind of encryption in the internal storage, I was trying to disable it. It probably tripped some security measure. The phone's software was garbage the day I got it (almost 1 year ago). After I rooted it I thought I could flash some third party rom to fix it, but since it was encrypted I can't. I didn't want to mess with my only phone, so I begrudgingly used it for almost a year, but now that I have a replacement phone, I thought I would attempt to disable the encryption and flash different rom just to experiment before giving the phone away. So in a sense I already written off this POS. Never ZTE, never again.
awdrifter said:
Well, if I knew why it bricked I wouldn't flash it would I? The ZTE phone had some kind of encryption in the internal storage, I was trying to disable it. It probably tripped some security measure. The phone's software was garbage the day I got it (almost 1 year ago). After I rooted it I thought I could flash some third party rom to fix it, but since it was encrypted I can't. I didn't want to mess with my only phone, so I begrudgingly used it for almost a year, but now that I have a replacement phone, I thought I would attempt to disable the encryption and flash different rom just to experiment before giving the phone away. So in a sense I already written off this POS. Never ZTE, never again.
Click to expand...
Click to collapse
Okay. For anyone who comes next: it is NOT NECESSARY to root the phone to install a custom ROM! Simply with unlocking the bl and installing TWRP, then wiping system and formatting data, then using the universal bootloader and modem, you can install a custom ROM.
I was asking what you did to brick it while updating TWRP. Never heard about something like that
Hi so I just rooted my op6t yesterday after having it for a couple weeks and I did everything fine and installed a couple root apps. I later discovered custom kernels and wanted to flash one. I went into twrp and all the folders were weird names and the same thing shows on my computer when I plug the phone in. After looking it up my phone is encrypted. I never clicked anything that said to encrypted my phone and it wasn't encrypted before. In Android it says it's encrypted and now I have to reset it to unencrypt it? I'm ok with that but that's a little annoying. Some people said something about a bug in twrp that has to do with encryption but I'm confused why my phone just did that. I restored apps and settings with Google backup which I ran right before I rooted the phone and restored right after I rooted it. Does anyone know what caused it to encrypt itself and how I can prevent it from doing it again? Thanks.
Sounds like you need to do a lot more reading before you attempt to modify your phone. The phone comes encrypted from the factory. There are plenty of topics about this exact issue. Also, if you had read anything in this thread then you would see that decryption in TWRP was fixed a while ago. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
are you sure you had encryption disabled before? my 6t was encrypted from the beginning. I installed root with twrp by using ADB sideload and I never used the file explorer from twrp itself.
if encryption was off, this happened on my old Nexus 6 sometimes too after installing a custom kernel. it was every time really annoying that I got force encrypted even when the kernel builder stated that it does not...
OnkeIM said:
are you sure you had encryption disabled before? my 6t was encrypted from the beginning. I installed root with twrp by using ADB sideload and I never used the file explorer from twrp itself.
if encryption was off, this happened on my old Nexus 6 sometimes too after installing a custom kernel. it was every time really annoying that I got force encrypted even when the kernel builder stated that it does not...
Click to expand...
Click to collapse
Maybe it was encrypted from the factory. I could access files through my computer though. Should I reset the phone and flash twrp again then turn off encryption in Android settings? I'm a bit new to this so I'm not entirely sure. I just followed the guide on xda for rooting and unlocking the 6t bootloader.
Skyline3499 said:
Maybe it was encrypted from the factory. I could access files through my computer though. Should I reset the phone and flash twrp again then turn off encryption in Android settings? I'm a bit new to this so I'm not entirely sure. I just followed the guide on xda for rooting and unlocking the 6t bootloader.
Click to expand...
Click to collapse
You should still be able to access files from the computer.
The phone should work fine.
It's just that the version of TWRP you have does not support encryption.
tech_head said:
You should still be able to access files from the computer.
The phone should work fine.
It's just that the version of TWRP you have does not support encryption.
Click to expand...
Click to collapse
I think it does though I tried the decrypt command in twrp terminal but it failed. It wants a password and I tried my pin which didn't work.
Skyline3499 said:
I think it does though I tried the decrypt command in twrp terminal but it failed. It wants a password and I tried my pin which didn't work.
Click to expand...
Click to collapse
That version of TWRP does not support decryption.
GO back and flash the stock boot image.
Temp boot TWRP.
install Magisk and move on.
yerger said:
Sounds like you need to do a lot more reading before you attempt to modify your phone. The phone comes encrypted from the factory. There are plenty of topics about this exact issue. Also, if you had read anything in this thread then you would see that decryption in TWRP was fixed a while ago. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Click to expand...
Click to collapse
Ok, thanks, that twrp version worked with the encryption and everything if fine now.
Well, decryption actually. I would love to disable encryption entirely like on the OP6, but apparently that's not possible due to the fingerprint or something. It's so frustrating. I load OOS then Havoc (or ASOIP, maybe others) and everything seems fine until i try to flash something in TWRP only to find it won't accept my pattern, pin, fingerprint etc. Anyone seen this?
You have to clean flash an April security patch build, add your password/pin etc., then dirty flash to May and it will work
The other day it did that to me but when I skipped the pattern my files still showed up as normal. I'm using TWRP 3.3.0-2
king_david43 said:
The other day it did that to me but when I skipped the pattern my files still showed up as normal. I'm using TWRP 3.3.0-2
Click to expand...
Click to collapse
ZeroKool76 said:
You have to clean flash an April security patch build, add your password/pin etc., then dirty flash to May and it will work
Click to expand...
Click to collapse
Hmm, i swear i think i tried that a couple times. :latest release, no beta.
I'm very familiar with wiping the data partition to create a fresh decrypt one. I think i just need a no-forced encrypt zip like on OP6. Unfortunately i think that screws up login attempts because of the fingerprint being proprietary. If someone knows a way or is working on it, you'd be my hero.
jaysonic88 said:
Hmm, i swear i think i tried that a couple times. :latest release, no beta.
I'm very familiar with wiping the data partition to create a fresh decrypt one. I think i just need a no-forced encrypt zip like on OP6. Unfortunately i think that screws up login attempts because of the fingerprint being proprietary. If someone knows a way or is working on it, you'd be my hero.
Click to expand...
Click to collapse
Have you tried to format data instead of wiping? Some ROMs like treskmod require this for successful decryption.
reppi said:
Have you tried to format data instead of wiping? Some ROMs like treskmod require this for successful decryption.
Click to expand...
Click to collapse
Sorry, yes that's what i mean. I indeed do completely format the data partition where it prompts and requires "yes" to do so. The odd thing is it DOES decrypt it just sometimes encrypts again and then locks me out. I do tend to reinstall twrp and root more than is probably required (to get safetynet passed). Is there some rule i need to follow or something i need to do during each flash to prevent this?
Thanks by the way for everyone's input.
jaysonic88 said:
Sorry, yes that's what i mean. I indeed do completely format the data partition where it prompts and requires "yes" to do so. The odd thing is it DOES decrypt it just sometimes encrypts again and then locks me out. I do tend to reinstall twrp and root more than is probably required (to get safetynet passed). Is there some rule i need to follow or something i need to do during each flash to prevent this?
Thanks by the way for everyone's input.
Click to expand...
Click to collapse
Ok, i think i found the issue. According to the guy who wrote the unofffical TWRP 3.3.02 it's a bug in the code. He sent the info including the lines of code that were causing the problem to teamwin.
https://forum.xda-developers.com/showpost.php?p=79515334&postcount=2559