Hi guys currently im running OSS+Franco Kernel with my op3t decrypted.
If i wanna flash another custom kernel i should flash the stock boot.img so that means will crypt my phone again and that's ****.
in the next updates will crypt the op3t by default?
so is recommended let it crypted or decrypted?
what would you use?
Thank You
If you reflash boot.img and don't want your phone to encrypt, you need to redo whatever you did that you originally did to disable forced encryption (SuperSU, fed-patcher, etc.) before you reboot into Android.
Related
hey guys, so I want to encrypt my phone but I want to stay rooted with magisk and xposed. (Using SuperSU 2.78 SR3). Device: OnePlus One running SultanXDA's CM13.
Are there any special steps I need to take before I start the encryption process? do I need to completely unroot and remove all traces of all these before going back or will it just work?
I haven't seen this question addressed before and this would help others with the same questions.
Thanks for any advice!
Since there was no support from anyone, I decided to just remove everything (xposed, magisk and supersu) then encrypt, and finally re-add everything back. I did this just to avoid any complications and all works fine without issue.
@Nomelas what version of magisk did you use? and did you sideload them or just flash with the cache work around?
I've been at this all day with no luck
@GbizzleMcGrizzle what phone are you using? I had to completely remove everything before encrypting. Also reflashed stock system
@Nomelas Galaxy S7 (SM-G930F) it wont encrypt with magisk installed and magisk wont install after it has been encrypted.
@GbizzleMcGrizzle are you flashing through twrp? (are you decrypting when you boot into twrp)
i've tried flashing in twrp and sideloading. I don't think I can decrypt in twrp but magisk says it has a work around for not beiing able to boot /data and supposedly put in in cache and then moves it to data after boot so IDK
Hi there, what is easiest way to root nougat? oxygenOS 4.0?
i mean root that is working with stable nougat version. thanks.
Unlock bootloader if you haven't already (it will wipe all your data. Yes, all.), flash TWRP recovery and use that recovery to flash SuperSU flashable zip, which you can find by googling SuperSU.
I would wait a bit. I have spend quite some time on reverting. It seems there are some issues with twrp and how it handles encryption. I couldn't bypass encryption password in twrp and flash anything. I could on 3.5 but not in nougat. There are a few threads about it. A new twrp version will probably fix it.
Didn't someone make a post that you have to change the partition to f2fs to fix the encryption issue?
The Oneplus 3T comes with f2fs (you can check the partition type in twrp>wipe>tick 'data'> repair filesystem> choose 'CANCEL'). Currently the only way to fix the encryption issue in twrp is to disable encryption I think.
Sorry i didnt mean this to be Q & A, i want only ask that is it okay to root nougat or does it have some kind of problems still..
Could i install twrp on 3.5.4, root it, then flash OOS 4.0 in twrp?
Yes that's what I did. Make sure you flash the full zip (around 1.4 GB). You will lose root though.
Can't you redo root/supersu after flashing nougat? Also you can try magisk as well on nougat. I heard that works well.
Hi everyone,
I really looked many websites and I think the answer is no but I still wonder if there is a way to root MI 8 with magisk from twrp without format the phone? I am running latest global stable rom with unlocked bootloader. I just want to root and install magisk for certified play store, netflix and adaway but setting and installing all apps again will take some time... As far as I know it was possible before as I did it at a MI 6 running miui 9.
Thanks in advance.
No
magisk, Boot Image Patching
YES! I finally figured out how to get root and keep encryption with Stock Global but you have to flash an alternate kernel first. You can keep your encryption without issues. I've been using this for a few weeks without issues now. The STOCK kernel has been the issue the whole time.
For Stock MIUI Global (Beta or Stable) Already Setup & Encrypted:
1.) Boot to TWRP Recovery (i'm using twrp-3.2.3-4)
2.) Flash Sphinx kernel (i'm on v2.5) You CANNOT keep ROOT while retaining encryption on a STOCK Kernel at this time!
3.) Flash Magisk (i'm using 18.0)
4.) Flash Disable_Dm-Verity ONLY! (DO NOT FLASH DM-VERITY with Encryption REMOVER or FEC in the filename or you will screw up your encryption!)
-I use this DM-Verity remover here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
-you need to re-name the zip file with only "DM-Verity" in the filename without the ForceEncryption in the name before flashing! The filename determines/triggers what the zip disables!
DO NOT ERASE OR FORMAT ANYTHING!
Reboot and enjoy root while retaining encryption.
-You need to follow these steps on every new ROM flash!
-You can't do OTA updates, you need to flash new full ROMs!
Oh sorry I missed that he's already unlocked the bootloader
Agimax said:
YES! I finally figured out how to get root and keep encryption with Stock Global but you have to flash an alternate kernel first. You can keep your encryption without issues. I've been using this for a few weeks without issues now. The STOCK kernel has been the issue the whole time.
Click to expand...
Click to collapse
I can confirm this works, or at least in global ROM. I tried flashing Xiaomi.eu rom from global, but I couldn't boot it. I remember someone said that rom doesn't have encryption implemented.
Hey guys, do you know how to install global properly? I have installed the last one, but i can't change region it keep up on china region, and the baterry drain is bad. I used twrp recovery, but when i installed the global rom it doesn't work anymore, it started the miui recovery instead of custom. Help please
I installed magisk without a reset easily. Also im on stock kernel and my phone's encrypted ?
what is encryption for?`sry for maybe stupid question :x
Agimax said:
The filename determines/triggers what the zip disables!
Click to expand...
Click to collapse
Really...
---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------
Ferr1s said:
what is encryption for?`sry for maybe stupid question :x
Click to expand...
Click to collapse
Well your files will be encrypted so noone can access your files without the encryption password if the phone gets lost.
Agimax said:
YES! I finally figured out how to get root and keep encryption with Stock Global but you have to flash an alternate kernel first. You can keep your encryption without issues. I've been using this for a few weeks without issues now. The STOCK kernel has been the issue the whole time.
For Stock MIUI Global (Beta or Stable) Already Setup & Encrypted:
1.) Boot to TWRP Recovery (i'm using twrp-3.2.3-4)
2.) Flash Sphinx kernel (i'm on v2.5) You CANNOT keep ROOT while retaining encryption on a STOCK Kernel at this time!
3.) Flash Magisk (i'm using 18.0)
4.) Flash Disable_Dm-Verity ONLY! (DO NOT FLASH DM-VERITY with Encryption REMOVER or FEC in the filename or you will screw up your encryption!)
-I use this DM-Verity remover here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
-you need to re-name the zip file with only "DM-Verity" in the filename without the ForceEncryption in the name before flashing! The filename determines/triggers what the zip disables!
DO NOT ERASE OR FORMAT ANYTHING!
Reboot and enjoy root while retaining encryption.
-You need to follow these steps on every new ROM flash!
-You can't do OTA updates, you need to flash new full ROMs!
Click to expand...
Click to collapse
Hello, I'm running stock MIUI 10(global) on my Mi 8. It is already rooted. I was flashed DM-verify with encryption remover. Then rooted it.
Now I want to encrypt my phone without wiping data. I tried flashing Sphinx kernel then encrypt the phone but it failed. Should I reset my phone and setup again to encrypt the phone or it is possible to encrypt it without resetting?
Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.
Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
MoistPicklez said:
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
Click to expand...
Click to collapse
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Click to expand...
Click to collapse
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
So installing most ROMs seems fairly straightforward, following
the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything
from the internal storage? So at that point I'd have to copy back
all my ROMs and zips back to the phone in TWRP and flash from
this point correct?
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
MoistPicklez said:
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
Click to expand...
Click to collapse
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
MoistPicklez said:
So installing most ROMs seems fairly straightforward, following the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything from the internal storage? So at that point I'd have to copy back all my ROMs and zips back to the phone in TWRP and flash from this point correct?
Click to expand...
Click to collapse
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
Code:
adb pull /sdcard
MoistPicklez said:
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
Click to expand...
Click to collapse
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Click to expand...
Click to collapse
Awesome info, big thanks to you my good sir. Finally
on Havoc 2.9 and decrypted. Now just gotta get a feel
for this phone and keep on reading. Cheers!