Disable encryption on 7.1.1 - Nexus 6 Q&A, Help & Troubleshooting

Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!

Mephisto_POA said:
Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!
Click to expand...
Click to collapse
It's no different. If your bootloader is not unlocked, unlocking it will wipe the user data partition. If the bootloader is already unlocked, you'll need to wipe the user data partition.
*IN EITHER CASE YOU WILL LOSE YOUR DATA. DO A BACKUP FIRST
Then flash a ROM with an included kernel that doesn't force encrypt. Or, just flash a kernel that doesn't force encrypt.
Now that I've answered your question, IMHO, it's not worth the effort. If your phone is crawling, do a factory reset. On a stock ROM, go to Settings > Backup & Reset and make sure you have your Google backup settings enabled. Use the Factory Data Reset button to actually reset. READ through the information and confirm. This will cause your phone to reboot with a wiped system partition.
If your on a custom ROM I'm going to assume you know how to wipe through recovery.

ktmom said:
...., IMHO, it's not worth the effort. If your phone is crawling, do a factory reset.....
Click to expand...
Click to collapse
My 7.1.1 uses the lite stock rom of Danvdh.
I think you're right about the hassle. Only decrypting is not enough. But debloating and removing unused stuff and decrypting the data partition did raise performance on my N6.

Yeah, I know it is a bit of a hassle, but considering there will be no more updates after 7.1.1 it should be a once only process right? Is possible to disable encryption on 7.1.1. without rooting?
I'm happy to unlock the bootloader and wipe the phone, not a problem.

Mephisto_POA said:
Yeah, I know it is a bit of a hassle, but considering there will be no more updates....
Click to expand...
Click to collapse
Don;t forget the monthly security updates.
I am using the lite stock room of Danvdh. It's a pre-rooted stock room.
But I think updates can be dirty flashed because the system, radio and bootloader will not change anymore.
So root and install TWRP to flash the updates

the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption

Mephisto_POA said:
the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption
Click to expand...
Click to collapse
In that case the post of @ktmom is applicable.

I am on 7.1.1 and have used the fed patcher mentioned on this site and it has worked nicely on custom and stock ROMs. But u have to be rooted.

NLBeev said:
In that case the post of @ktmom is applicable.
Click to expand...
Click to collapse
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused

Mephisto_POA said:
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused
Click to expand...
Click to collapse
Plain vanilla unencrypted would be google factory image plus a non forced enforcing kernel. B14CKB1RD, Franco there are others.
Custom ROM that is close to vanilla but comes with a non forced encrypting kernel would be Pure Nexus.

Mephisto_POA said:
I would really appreciate if you could give me some directions?
Click to expand...
Click to collapse
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/

NLBeev said:
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/
Click to expand...
Click to collapse
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?

saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
That was an answer to a different question.
The ROM you installed I believe has a non-force encrypting kernel. But just installing a non-force encrypting kernel isn't enough. You need to wipe user data and install a kernel that doesn't force encrypt.
Please read back a page to two for the whole recent conversation that has more details, like the fact that you'll lose all of your data in this process.

saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
Got it working, just followed this:
Just because forced encryption is disabled doesn't mean it decrypts you. You have to do that yourself by formatting data either through TWRP (TWRP > Wipe > Format Data button) or through fastboot (fastboot format userdata), which will wipe out your app data and your internal storage partition so make the appropriate backups.

saltyzip said:
Got it working, just followed this:
Click to expand...
Click to collapse
You going to take credit, you should at least use your own words ?

I've gone with your guys suggestion with stock lite, working like a charm, very snappy. The phone feels indeed light, and multitasking is way smoother now, thanks!!!
just on a side note, after you install the rom you need to wipe the data partition to get rid of the encryption

Installed twrp on bn Nexus 6 os 5.1 OTA for 7.1.1 encrypted it
No clue how to fix this I'm a noob unlocked bootloader unencrypted Android 5 then it OTA updated to 7.1.1 and now can't get to twrp to wipe encryption how can I get this going again phones working just can't use cable to computer have the SD card reader micro SD any help would be appreciated

kudabee61 said:
...just can't use cable to computer...
Click to expand...
Click to collapse
Get your phone's USB port fixed, then you can fix the ROM issue.

Related

Lollipop 5.1.1 stock image is up !

Finally ! Straight from Google DEVS
"nakasi" for Nexus 7 (Wi-Fi) 5.1.1 (LMY47V)
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
fortissimo said:
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
Click to expand...
Click to collapse
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
iBolski said:
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
Click to expand...
Click to collapse
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
gsmyth said:
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Click to expand...
Click to collapse
thats for the Nexus 5 though, I havent seen anything for the N7 yet.
2 of mine are bricked (one APX mode, the other corrupted emmc but seems to "work" - sort of - with all F2FS rom), I bought a board for $40 to replace one of them but the digitizer clamp and pins flaked off on contact when trying to reassemble it so Im reluctant to do anything with it without touch capability. its just going to sit there with my blutooth mouse for kitchen-netflix for now. Im thinking of selling them all "as is" but Im curious if this update pans out, I might keep the touchless one.
There's a lollipop rom for F2FS??
Varnak said:
There's a lollipop rom for F2FS??
Click to expand...
Click to collapse
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
JerryPi said:
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
Click to expand...
Click to collapse
ok thanks. But i need to format system with normal partition?
Varnak said:
ok thanks. But i need to format system with normal partition?
Click to expand...
Click to collapse
You leave system partition on default ext4.
JerryPi said:
You leave system partition on default ext4.
Click to expand...
Click to collapse
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Varnak said:
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Click to expand...
Click to collapse
With the newer versions of twrp that zip is really not necessary to convert your partitions to a different file system.
To check and change format of your partitions go in your twrp recovery under wipe -advanced wipe - choose your partition - then repair or change your file system - there it says wich file system you are using and you can change it accordingly.
in twrp when you are changing the filesystem, it tells you which is the current.
Edit: just saw JerryPi's post
Two days in, 5.1.1 clearly better than 5.1 on my 32gb n7 2012 wifi.
Stock load/kernel/ext4 filesystems maintained, factory reset, full device restore/reinstall from cloud backup, rooted via TWRP, updated with SuperSU.
Nova Launcher, I just prefer it, no functional reason over stock Launcher.
Kindle app runs noticeably better, heck the Zinio reader app seems to work well too.
Google sheets/docs/presentation seems good.
TapaTalk Pro works well, as does Feedly. Notably less latency on network i/o and page transitions.
Facebook app doesn't seem to bring it down, even without any services disabled.
Haven't tried Chrome yet, and need to reload my music/video content to see how Rocket Player does.
disclaimer: I've taken to running "Trimmer (fstrim)" on an automatic schedule, daily, to keep nand free block lists healthy. That probably helps. I was doing that on 5.1 though.
If this keeps up I'd consider it a completely reasonable upgrade from KK.
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Marcovanbasten said:
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Click to expand...
Click to collapse
You need to flash via fastboot.

MRA58R build?

Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6
Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?
H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root
scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6
Any word on the changes between this and previous build yet?
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.
Pushed out by big red.... I think that's something I'll definitely wait on.
jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.
I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.
R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.

Device Encryption Question/Issue with Unlocking

I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.
Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.
TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.
ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.
Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."​Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???

Finally :Stock Android 9 Pie, Oxygen OS 9.0.2 for OP 3/3T

After a long long wait its finally here. The oneplus 3T gets android pie. Install it and share your experience here
https://9to5google.com/2019/05/22/oneplus-3-android-pie/
I'm downloading using oxygen updater app
Anything to share? Any issues?
ptoner said:
Anything to share? Any issues?
Click to expand...
Click to collapse
Using this since past 2 days. I am completely stock with locked bootloader, unrooted and stock recovery.
No issues till now. Feels good to be back to stock oxygen OS for a change from all these custom roms.
affection788 said:
Using this since past 2 days. I am completely stock with locked bootloader, unrooted and stock recovery.
No issues till now. Feels good to be back to stock oxygen OS for a change from all these custom roms.
Click to expand...
Click to collapse
You installed it on a locked bootloader. So you factory reset the phone before updating. Or did you just flash and lose no data
Sent from my ONEPLUS A6003 using Tapatalk
ptoner said:
You installed it on a locked bootloader. So you factory reset the phone before updating. Or did you just flash and lose no data
Click to expand...
Click to collapse
I installed it on a unlocked bootloader. I was previously on Skydragon. Flashed stock OS in twrp. Lost all data in internal storage after reset.
Sounds good have been avoiding on my work phone for fear that it'll become unstable or slow. Seems thats not the issue
affection788 said:
I installed it on a unlocked bootloader. I was previously on Skydragon. Flashed stock OS in twrp. Lost all data in internal storage after reset.
Click to expand...
Click to collapse
I'm running rooted Skydragon OS with twrp and unlocked bootloader. Can I directly flash oos via twrp? Will there be any issues?
Does the stock recovery replace twrp after flashing oos?
Darkweb_182 said:
I'm running rooted Skydragon OS with twrp and unlocked bootloader. Can I directly flash oos via twrp? Will there be any issues?
Does the stock recovery replace twrp after flashing oos?
Click to expand...
Click to collapse
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
affection788 said:
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
Click to expand...
Click to collapse
Do you know if it will be the same if you are not encrypted, and want to stay not encrypted? Is there a way to do that without formatting (maybe using the patched firmware or theone3os)?
groshnack said:
Do you know if it will be the same if you are not encrypted, and want to stay not encrypted? Is there a way to do that without formatting (maybe using the patched firmware or theone3os)?
Click to expand...
Click to collapse
mine is decrypted and installed fine and is still decrypted,sorry wrong thread
Just installed it, the initial look seems good. The phone spent some time optimizing the apps but after that it seems smoother and much cooler looking.
Ok so if i still on android n 7.1.1 and rooted and magisk installed ohh and twrp is there too, is it going to be safe to install android pie oos 9.0.2 and to keep the root and magisk and the twrp without loosing my data?
If its safe pleas do till.
ml700 said:
Ok so if i still on android n 7.1.1 and rooted and magisk installed ohh and twrp is there too, is it going to be safe to install android pie oos 9.0.2 and to keep the root and magisk and the twrp without loosing my data?
If its safe pleas do till.
Click to expand...
Click to collapse
It is not. You will have to factory reset/format data for getting OOS Pie. That is going to delete your data, Magisk and in the process, you may have to reflash TWRP also.
I'm on open beta 39 OnePlus 3 with twrp bluspark.
So can I download the update or the full ROM? I'm a little confused as to where it is on the forums.
Then do I just flash it in twrp (wipe first I know but should I wipe data as well?) While flashing does it tell you to wipe, format or do I do that all myself?
What are the s steps?
I'm happy to wipe everything as I want to clean up my device anyway.
Thank you so much for the help.
affection788 said:
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
Click to expand...
Click to collapse
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Darkweb_182 said:
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Click to expand...
Click to collapse
Performance is good and smooth. Good battery life as well. I haven't rooted it yet, wanna keep it stock for the time being but I am sure it can be rooted. Yes Gcam works. I am using one of the stable Arnova based Gcam.
affection788 said:
Performance is good and smooth. Good battery life as well. I haven't rooted it yet, wanna keep it stock for the time being but I am sure it can be rooted. Yes Gcam works. I am using one of the stable Arnova based Gcam.
Click to expand...
Click to collapse
I wasn't able to root Oxygen OS oreo firmware that's why I was asking
Darkweb_182 said:
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Click to expand...
Click to collapse
Battery life is not as good as Oreo OOS. I have disabled OnePlus's advanced battery optimizations, you should know.
Performance on stock kernel is mostly fine with stutters in phone app mainly. But i think that's phone app's fault. Performance with the custom kernel I am using right now is great and the ROM feels smooth.
Yes, I am running it rooted with a custom kernel.
I haven't used Google camera as I hardly use my phone's camera. Maybe once a week.
abhibnl said:
Battery life is not as good as Oreo OOS. I have disabled OnePlus's advanced battery optimizations, you should know.
Performance on stock kernel is mostly fine with stutters in phone app mainly. But i think that's phone app's fault. Performance with the custom kernel I am using right now is great and the ROM feels smooth.
Yes, I am running it rooted with a custom kernel.
I haven't used Google camera as I hardly use my phone's camera. Maybe once a week.
Click to expand...
Click to collapse
How did you root it?
Which custom kernel are you on?
Also does the bootloader get locked after flashing oos?
Darkweb_182 said:
How did you root it?
Which custom kernel are you on?
Also does the bootloader get locked after flashing oos?
Click to expand...
Click to collapse
Those are pretty basic questions actually. I assume you haven't rooted your phone in recent time?
I just flashed the magisk zip before first boot into system to keep twrp and one restart settled things and magisk is now working fine.
I am using mcd kernel build r27 but it has broken Hotspot functionality, which I don't care much about.
Why would the bootloader get locked after flashing OOS? You need to manually go into fastboot mode and manually enter some commands to lock/unlock bootloader. It can't be done via recovery afaik.

How do I upgrade from an rooted and unencrypted OOS 5.0.4 to OOS 9.0.5?

So recently I've been thinking of upgrading my phone from Oreo to Pie now that it is available and has had a few updates.
Now I haven't updated my phone in a while. The last time was around the summer of 2018. The OxygenOS version my 3T currently is running is 5.0.4 and my TWRP is on version 3.2.3-0.
A while back I was using the custom ROM 'FreedomOS' (for anyone that still remembers) but that ROM hit it's EOL point last year.
After FreedomOS went EOL I switched to stock ROM following this guide to stay decrypted: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Since I switched back to stock I haven't touched the system or recovery at all besides updating Magisk now and then.
Now the question I'm having is how do I update my phone to the latest Pie version of OxygenOS? Which is version 9.0.5 as of writing this post.
Preferably I would like to upgrade with a dirty flash to keep my data (if I run into issues after I'll clean flash) and I also want to stay dencrypted and have Magisk as root.
For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)
it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
First of all, both of you thanks for the replies.
wojtek007pl said:
For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)
Click to expand...
Click to collapse
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
BrahmaGandhi said:
it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324
allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
Click to expand...
Click to collapse
In simple words phone is slower and hotter. Battery isn't better too (battery life for me was decreased from 5 to 3, 3.5 hours screen on time). You can find more on Oneplus forums.
allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324
Click to expand...
Click to collapse
i personally would suggest you to stay on oreo or jump to pie custom roms, just skip the oos 9.0.5..
the only thing that really fast and smooth just the face unlock feature :laugh:
as far as i know when you flashed stock oos your data will always be (re)encrypted, unless you do the firmware's patch things like you did before.
jumping (upgrade) from diff. android version it's better to do a clean flash (4 wipes, exclude int. storage will be saved)...and it's mandatory required (from stock to any custom roms). except when you forced to format data you'll lost all data in your phone, for sure.
and if you want to stay unencrypted and disable dm verity for good, it's better to do all that stuffs while on stock oos before you jump onto custom roms.
for more details and assistance i suggest you post on the main thread.

Categories

Resources