Develop Bugs

MHC19J & Data En/Decryption

Hello all,
Seeing MHC19J being the latest update to 6.0.1, I'm tempted to flash factory images like I've done for previous monthly updates (system, vendor, cache, bootloader, radio). Giving all the discussion on MHC19J & twrp v3 related to data encryption, I just want a few clarifications before I go ahead and get myself into trouble.
Here's my current setup:
-Data/Storage Decrypted (formatted userdata using twrp v2.x after unlocking bootloader when I first got 5X)
-MMB29Q - Feb 1 2016 security patch level
-Stock Rooted with Systemless v2.67 beta
-Xposed installed
Here's clarifications I'm looking for:
- will flashing MHC19J automatically RE-encrypt data/storage?
- if so, is there any way to De-crypt it without wiping data/storage? This is important to me because I'd rather keep my phone decrypted for superior performance gains and I don't really have time to reinstall my apps and restore data via Titanium backup at the moment.
If there's no way to decrypt again without completely wiping data, I think I'd rather go with V version or stay on Feb update for now.

mickey4mice said:
Hello all,
Seeing MHC19J being the latest update to 6.0.1, I'm tempted to flash factory images like I've done for previous monthly updates (system, vendor, cache, bootloader, radio). Giving all the discussion on MHC19J & twrp v3 related to data encryption, I just want a few clarifications before I go ahead and get myself into trouble.
Here's my current setup:
-Data/Storage Decrypted (formatted userdata using twrp v2.x after unlocking bootloader when I first got 5X)
-MMB29Q - Feb 1 2016 security patch level
-Stock Rooted with Systemless v2.67 beta
-Xposed installed
Here's clarifications I'm looking for:
- will flashing MHC19J automatically RE-encrypt data/storage?
- if so, is there any way to De-crypt it without wiping data/storage? This is important to me because I'd rather keep my phone decrypted for superior performance gains and I don't really have time to reinstall my apps and restore data via Titanium backup at the moment.
If there's no way to decrypt again without completely wiping data, I think I'd rather go with V version or stay on Feb update for now.
Click to expand...
Click to collapse
Flashing any factory image will encrypt your phone as soon as you boot into the rom. Make sure that after flashing factory images, you boot straight into TWRP and flash Super. I flashed every partition as the bootloader and radio are newer. I maintained my decrypt status on TWRP 3.0 after upgrading to MHC19J. Basically, do what you have done every month to maintain decrypt status and you will be fine.
Just do not boot into your system until you have flashed SuperSU.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Flashing any factory image will encrypt your phone as soon as you boot into the rom. Make sure that after flashing factory images, you boot straight into TWRP and flash Super. I flashed every partition as the bootloader and radio are newer. I maintained my decrypt status on TWRP 3.0 after upgrading to MHC19J. Basically, do what you have done every month to maintain decrypt status and you will be fine.
Just do not boot into your system until you have flashed SuperSU.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Did you use officially released TWRP v3 or the test version posted today?
Did you have to flash Su from OTG or the data partition was okay?

mickey4mice said:
Thanks. Did you use officially released TWRP v3 or the test version posted today?
Did twrp(the version you used to flash J) ask for password for data/storage upon reboot from bootloader after flashing?
Click to expand...
Click to collapse
I always follow the above post without an issue. I flash the boot.ing also as supersu will patch the kernel when flashed. I used TWRP 3.0.0 and did not have a password prompt and retained unencrypted status. Biggest key is not to boot into the ROM. If you do... It's already too late. Data is encrypted at first boot

mickey4mice said:
Thanks. Did you use officially released TWRP v3 or the test version posted today?
Did you have to flash Su from OTG or the data partition was okay?
Click to expand...
Click to collapse
I used the official TWRP 3.0 from awhile ago. Being that I was decrypted already, official TWRP 3.0 has no issues finding internal storage when moving to MHC19J. No OTG necessary.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Flashing any factory image will encrypt your phone as soon as you boot into the rom. Make sure that after flashing factory images, you boot straight into TWRP and flash Super. I flashed every partition as the bootloader and radio are newer. I maintained my decrypt status on TWRP 3.0 after upgrading to MHC19J. Basically, do what you have done every month to maintain decrypt status and you will be fine.
Just do not boot into your system until you have flashed SuperSU.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Is it enough to just flash SuperSU before boot into rom? I read something like
> You need a custom kernel that doesn’t enforce encryption on boot up. So install custom kernel via TWRP. Erase data partition. Boot up.
> via: www<dot>reddit<dot>com/r/nexus5x/comments/3zctaw/need_help_decrypting/cylsdle
That is, do I need to flash a "custom kernel" besides that flashing SuperSU before boot into rom?

KANGOD said:
That is, do I need to flash a "custom kernel" besides that flashing SuperSU before boot into rom?
Click to expand...
Click to collapse
Nope. You can flash SuperSU 2.6x only or flash a custom kernel that has disabled "force encrypt." SuperSU also patches the stock boot.img and turns off "force encrypt." Doing either will keep you decrypted.
Sent from my Nexus 5X using Tapatalk

SuperSu 2.68
I have flashed the new 19J ROM (radio, new boot loader, system, cache & vendor partitions) I left the userdata partition as is, it was decrypted.
I have installed the latest SuperSu 2.68 Beta zip immediately through TWRP (3.0.0-1), Than I have rebooted the system.
After the first boot up, the system is ENCRYPTED! There is no option to decrypt the system in TWRP. It can see all partitions just fine.
Where did I mess it up? How can I decrypt the system without to format the data partition?
I always install monthly updates on the same way, I never had any issues..
thank you
----------------------------------
Update 1:
when I boot into Recovery and I push the "Mount" option I can see the following note
" Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details.,..
... done
Successfully decrypted with default password"
When I reboot the system it still shows: The device is encrypted.
Something wrong with the latest SuperSu?
---------------------
Update 2:
I did the exact same thing with my wife's 5X. Her phone is still decrypted after the exact same manual installation. I'm confused. ...

rooting guide for OnePlus 3 on oos 4.0+

Hi,
Can someone please start new thread for oos 4.0+ on OnePlus 3 detailing up to date guides for rooting/installing exposed mods etc.?
Sent from XDA labs

mit2nil said:
Hi,
Can someone please start new thread for oos 4.0+ on OnePlus 3 detailing up to date guides for rooting/installing exposed mods etc.?
Sent from XDA labs
Click to expand...
Click to collapse
NO Xposed Mod For Android N yet
for Rooting Follow The Steps
1) Install Stock 7.0 Oxygen OS 4
2) Unlockbootloader Flash TWRP recovery
3)bootup to recovery Hit Cancle for the Decrypt Go to Wipe and Factory reset
4)copy SuperSU.zip To Device via TWRP MTP Support
5)flash The zip and boot systems

Scronix said:
NO Xposed Mod For Android N yet
for Rooting Follow The Steps
1) Install Stock 7.0 Oxygen OS 4
2) Unlockbootloader Flash TWRP recovery
3)bootup to recovery Hit Cancle for the Decrypt Go to Wipe and Factory reset
4)copy SuperSU.zip To Device via TWRP MTP Support
5)flash The zip and boot systems
Click to expand...
Click to collapse
if I wanted to save my data partition & update it to f2fs, would an adb backup before the format & restore after do the trick?

Id recommend to use magisk and phh's systemless su.

vivanshah said:
if I wanted to save my data partition & update it to f2fs, would an adb backup before the format & restore after do the trick?
Click to expand...
Click to collapse
for data partition, just do backup using Titanium and restore afterwards,
for internal storage, use adb pull /sdcard (or /storage/emulated/0 ) to pull the files to your PC and just push it later
you also can use TWRP backup for data and restoring by choosing "rm-rf" method in the setting

Scronix said:
NO Xposed Mod For Android N yet
for Rooting Follow The Steps
1) Install Stock 7.0 Oxygen OS 4
2) Unlockbootloader Flash TWRP recovery
3)bootup to recovery Hit Cancle for the Decrypt Go to Wipe and Factory reset
4)copy SuperSU.zip To Device via TWRP MTP Support
5)flash The zip and boot systems
Click to expand...
Click to collapse
Hi @Scronix,
I did wipe "Data partition" but did not do factory reset. Do I need to wipe cache & dalvik as well to get rid of encryption issue?
Also, I can first restore my backup from google account and take nandroid backup before processing to flashing su right? So, only extra step in original instructions posted in pinned OP3 thread is to do factory reset after installing twrp.
My issue description @ https://forum.xda-developers.com/showpost.php?p=70509349&postcount=464
Sorry for noob comments. This is first time I am experimenting with my device and want to proceed cautiously.

xkhen0017 said:
Id recommend to use magisk and phh's systemless su.
Click to expand...
Click to collapse
What the magisk does and can i use it in any other way with rooted device?

Ok so I flashed the SR1 joint. It was working for a couple days but now it says "theres no su binary installed". Can anyone tell me why this is happing??

mit2nil said:
Hi @Scronix,
I did wipe "Data partition" but did not do factory reset. Do I need to wipe cache & dalvik as well to get rid of encryption issue?
Also, I can first restore my backup from google account and take nandroid backup before processing to flashing su right? So, only extra step in original instructions posted in pinned OP3 thread is to do factory reset after installing twrp.
My issue description @ https://forum.xda-developers.com/showpost.php?p=70509349&postcount=464
Sorry for noob comments. This is first time I am experimenting with my device and want to proceed cautiously.
Click to expand...
Click to collapse
i strongly recommend A factory reset, also do not restore google backup for best result Also the factory reset s to be done by TWRP not stock and install SuperSU Before Booting into system

Thanks everyone for help. I was able to root after updating TWRP to official 3.0.3 and following guides.
I am still new to tinkering with my device. I will try magisk and system less su soon.
Sent from my OnePlus 3 using XDA Labs

updating rooted op3 without clean flash

haven't updated my phone in quite a while now, and was wondering if there is a method to update to latest OOS without having to perform a backup-->clean flash-->restore.
obviously the backup should stay, is it possible to update without clearing data?
what about oxygen updater app?
thanks

knoximator said:
haven't updated my phone in quite a while now, and was wondering if there is a method to update to latest OOS without having to perform a backup-->clean flash-->restore.
obviously the backup should stay, is it possible to update without clearing data?
what about oxygen updater app?
thanks
Click to expand...
Click to collapse
If you are changing Android version, it is better to clean flash. Clean flash involves wiping System, Data, Dalvik and Cache. Internal Storage where your photos and other files are stored need not be wiped. That said, it is prudent to have a backup of the photos and other files stored on your PC/Laptop since you never know whether ultimately you end up wiping Internal Storage also.
Obviously, you will lose root (and TWRP) which you have flash again. For root, Magisk is better than SuperSU on Oreo.
I have no experience with the Updater app.

Can I stay encrypted when making a clean upgrade to OOS 5.0.8?

I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?

msafiri said:
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
Click to expand...
Click to collapse
Since you are on OOS (though beta), flashing 5.0.8 should not affect your encryption status. Your plan is ok.
Encryption is related to security. Decrypted means lesser security though I have no idea by how much. It is your call.

Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.

abhibnl said:
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
Click to expand...
Click to collapse
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?

msafiri said:
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
Click to expand...
Click to collapse
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
Yep, i understand the difference in the operations on the data partition now. Thank you once again for the clarification.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
One small addl. info. After flashing TWRP, there is no need to reboot to recovery. Simply flash Magisk right after TWRP and then boot to system. Flashing Magisk at that stage prevents TWRP being overwritten by stock recovery.
EDIT: or you can skip flashing TWRP and boot back to recovery after flashing the ROM and then flash Magisk alone before booting into system. Either way, you save one step.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
I always download the full OTA zip and flash it manually wiping only system and cache/dalvik partitions, and I never had any issues whatsoever. Sure you will need to reflash magisk since your kernel and firmware will be flashed again.

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.

tnsmani said:
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
Click to expand...
Click to collapse
Thanks. That clears my doubts.

Pie Firmware Rom?

I just unlocked my Mix 2, but doing some looking before rooting. Is there any Roms that will work on Miui Beta Global 9.5.16? If all custom Roms are using 8.0 firmware, i guess i will wait to root this phone. If there is a Rom i can flash being on 9.0 firmware please let me know where to find it. Thank you.

Use the xiaomi.eu Roms, they are original Chinese MIUI Roms, but without any Bloatware Apps
https://xiaomi.eu/community/forums/miui-rom-releases.103/

If you browse through the forum you will find that most pie rom's have moved or are moving to pie firmware.

jkotte said:
Use the xiaomi.eu Roms, they are original Chinese MIUI Roms, but without any Bloatware Apps
https://xiaomi.eu/community/forums/miui-rom-releases.103/
Click to expand...
Click to collapse
How do I flash this rom? I never had luck with Xiaomi.eu roms but this time Imma do it again if I find someone who has working instructions.
Which recovery do I need? I'm currently on TWRP 3.2.3.0 (the official one from TWRP website)
What I do is
Wipe Data, Cache, System, Internal Storage everything. Even format data. Then copy the rom over into internal storage and flash it. Wipe cache again. Reboot system.
It always is stuck in loading.
Edit: I'm on Havoc OS-Pie currently.

dark_prince said:
How do I flash this rom? I never had luck with Xiaomi.eu roms but this time Imma do it again if I find someone who has working instructions.
Which recovery do I need? I'm currently on TWRP 3.2.3.0 (the official one from TWRP website)
What I do is
Wipe Data, Cache, System, Internal Storage everything. Even format data. Then copy the rom over into internal storage and flash it. Wipe cache again. Reboot system.
It always is stuck in loading.
Edit: I'm on Havoc OS-Pie currently.
Click to expand...
Click to collapse
Im on 9.5.23 eu, just wipe data caches system. If you are encrypted format data(im decrypted so i dont format sata) if you format sata reboot recovery and just install the zip. First boot may take longer than usual.
Sent from my Xiaomi MIX 2 using XDA Labs

dark_prince said:
How do I flash this rom? I never had luck with Xiaomi.eu roms but this time Imma do it again if I find someone who has working instructions.
Which recovery do I need? I'm currently on TWRP 3.2.3.0 (the official one from TWRP website)
What I do is
Wipe Data, Cache, System, Internal Storage everything. Even format data. Then copy the rom over into internal storage and flash it. Wipe cache again. Reboot system.
It always is stuck in loading.
Edit: I'm on Havoc OS-Pie currently.
Click to expand...
Click to collapse
Sorry for late response, i had this Problem too, bootlooping...
NEVER wipe System or Persist! Just FORMAT Data and install the Rom, i did it via ADB Sideload, worked perfectly