The below works for Nougat ROMs. I didn't have a chance to try with Oreo yet, sorry.
The ability to encrypt a device doesn’t depend on the presence of the stock recovery nor no-verity-opt-encrypt being flashed or not. It simple needs an unrooted boot.img at the moment the encryption is attempt. You do however need no-verity-opt-encrypt flashed to allow a custom ROM to boot. So the desired state to allow encryption from within a custom ROM is to have the stock boot.img with only no-verity-opt-encrypt applied to it.
The simplest sequence to archive a fully encrypted device with a custom ROM is the following:
- Flash (I recommend Dr. Ketan) ROM as always, but DISABLE ANY ROOTING in the installer
- Encrypt the device from the settings menu
- Flash the ROM one more time, this time WITH MAGISK ROOT. It will display a warning about /data not being mountable as it is now encrypted. That is ok as everything we need is already in place
If you didn’t choose fast encryption (which I recommend for security), download Trimmer (fstrim) from Play Store, tick all partitions and click Trim Now. This will free up all the sectors overwritten by the encryption process on the flash controller and makes your device work super smooth like before encryption.
This obviously only works that simple with ROMs that offer the ability to initially flash without root and if you’ve been on stock or a rootless ROM before. If that’s not the case you have the following options:
- Flash Magisk Uninstaller after initial ROM flash. You may have to reflash no-verity-opt-encrypt in TWRP again, in case it fails to boot now.
- Flash the stock book.img back in Odin and apply no-verity-opt-encrypt in TWRP. Use 7-Zip to create a tar only containing the stock BOOT.IMG and flash it in Odin using the AP slot.
- Flash back a TWRP backup taken of the boot partition before installing a root ROM, but after flashing no-verity-opt-encrypt.
Updating your ROM works no different then usual also. Just dirty flash over if it's the same ROM unless the release notes explicitly mention to factory reset. You don't need /data writable for a ROM update.
Enjoy your fully encrypted and rooted device.
Thank you, I'll try this when I'm at home. Nice recommendation with the trimmer tool, too!
Chainfire root & encryption [N950F]
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Encryption in oreo rom
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
halloweltkk said:
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
Click to expand...
Click to collapse
I haven't tried it with Oreo yet. But I'll probably give it a spin with Oreo within the next month. Sorry for that, will add a note to the guide.
little-endian said:
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Click to expand...
Click to collapse
Sorry for the late reply. I have no S7 to try, but believe using Magisk instead of SuperSu should work. Magisk has means to work with devices with forced encryption. AFAIK with an encrypted device it will put things to the cache partition first and on the next boot move things to the final location. I'm not aware of a similar mechanism in SuperSu.
I would try to unroot with Supersu, flash TWRP and give Magisk a spin. Keeping the stock ROM should be ok, however it will likely fail SafetyNet after plain Magisk Root. In that case try the universal SafetyNet fix also available as module within the Magisk app. If it fails to boot after Magisk root, try flashing the no verify opt encryption patch, but I don't think you need it.
I tried it in O5 as well and cannot get it to work. Just soft reboot as mentioned. No magisk just the ROM with stock kernel and still fails. Any advice?
will this work on s8?
Worked for me on S9 (GF-960F)! Thanks!
Had to use the Magisk Uninstaller first though, as I've alrady rooted.
Has anyone had any luck with this on Oreo? I've been trying to get my N960F simultaneously rooted and encrypted, but haven't had any luck with any method I've tried thus far. I can root it just fine, or encrypt it, but I've not found a way to do both at the same time without it resulting in "Verification failed" and a reset loop.
no-verity-opt-encrypt unable to find boot block location
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
sllorent said:
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
Click to expand...
Click to collapse
Maybe it's too late to answer to you, but this could be usefull for someone else.
I had same problem, "Unable to find boot block location", with same TWRP 3.2.3.
To solve this problem i downgrade TWRP 3.2.3 to TWRP 3.1.0-1 - Nougat that i found here https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627.
Than i followed the step to root, but i used Magisk 17.3 instaead SuperSu (Magisk 18.0 gave me some problem). Now i have root permissions with Magisk
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
sllorent said:
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
Click to expand...
Click to collapse
I don't know, sorry. How can i check that?
Inviato dal mio SM-T819 utilizzando Tapatalk
Android root + encryption possible at all ???
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Any thoughts on this? And other ideas on Android / third party encryption apps? Encrypting containers with EDS would be an alternative (recommended by Veracrypt) since full disc encryption is still not available for Android (why btw.? nobody seems to care...) - but I am not sure if one could run / move apps into the container (like contacts, sms, e-mail-apps etc.)...
Cheers!
no ideas - nobody ??
no ideas - nobody ??
Finally, rooted with Magisk and encrypted data note8 exynos
Followed these threads
https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
https://forum.xda-developers.com/note-fe/how-to/exynos-8890-sm-n935f-ds-twrp-root-t3771767
Tested with stock Nougat and TWRP-3.2.1.0-greatlte (with twrp-3.2.3-0 fail)
got these combinations working
Samsung_S7+Oreo+Magisk+Xposed+root+encryption
LG_V30+OreoAOSP+Magisk+Xposed+root+encryption(+BThandsfree)
also according to TWRP and the threads it was impossible. the TWPR might not be able to read files, i don't care as long as i have encrypted system. I can flash from the system.
Wouldn't like 3rd party solution as i want Secure Boot and type password during the boot.
Encryption and root is a must. But it's getting difficult more and more nowadays. ROM threads don't list limitations since KNOX was ever introduced, and that sucks. Instead of "knox will be tripped, warning boot screen will be showm, TWRP won't read filesystem, BT handsfree won't work, encryption won't work" you get "no limitations". Have to read full threads to discover the truth.
Hope Note9 and S10 will be ok.
No encryption working on my N960FD
I tried to install it while updating to DrKetan p09 and it doesnt work.
Is it possible for somebody to help me ?
I ve done a clean install and unrooted the no-verity-encrypt flash (The phone didn't even unlocked with pin )
xdaparanoia said:
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Cheers!
Click to expand...
Click to collapse
Is this true??
Related
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Thanks in advance guys
Fcleon said:
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Click to expand...
Click to collapse
Yes, that's the correct place to get the TWRP image file from. You've backed up so that's good. Make sure the PC you're using has USB 2.0 ports. If it only has USB 3.0 ports you'll need an external USB 2.0 hub for this to work. fastboot boot the TWRP image file and backup using TWRP. I backup system image, vendor image, boot & data. You don't need System or Vendor. Flash Magisk and install the Magisk manager apk. I use AdAway for blocking ads which requires root. You don't need to flash dm-verity, DFE or diskquota disabler. Nor do you need to worry about security.
Fcleon said:
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Thanks in advance guys
Click to expand...
Click to collapse
i am on 3.3.3-1 unofficial, the touch issues fixed in this one
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
download link
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw
- Magisk disables Dm Varity itself while flashing
- but for DFE you need to flash saperate Disable Force Encryption - Treble.zip
i replied similar question(s) and more YESTERDAY at https://forum.xda-developers.com/showpost.php?p=80170044&postcount=3
if you can manage some time, Please do read ~ its about rooting to custom rom flashing
edit: https://www.youtube.com/watch?v=BsHtfLh6azw plz see
YasuHamed said:
i am on 3.3.3-1 unofficial, the touch issues fixed in this one
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
download link
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw
- Magisk disables Dm Varity itself while flashing
- but for DFE you need to flash saperate Disable Force Encryption - Treble.zip
i replied similar question(s) and more YESTERDAY at https://forum.xda-developers.com/showpost.php?p=80170044&postcount=3
if you can manage some time, Please do read ~ its about rooting to custom rom flashing
edit: https://www.youtube.com/watch?v=BsHtfLh6azw plz see
Click to expand...
Click to collapse
Ok but in my situation and for the things that I am gonna do, do you really think I need to disable DFE and the other things?, disabling all this things are for what reason?
guhvanoh said:
Yes, that's the correct place to get the TWRP image file from. You've backed up so that's good. Make sure the PC you're using has USB 2.0 ports. If it only has USB 3.0 ports you'll need an external USB 2.0 hub for this to work. fastboot boot the TWRP image file and backup using TWRP. I backup system image, vendor image, boot & data. You don't need System or Vendor. Flash Magisk and install the Magisk manager apk. I use AdAway for blocking ads which requires root. You don't need to flash dm-verity, DFE or diskquota disabler. Nor do you need to worry about security.
Click to expand...
Click to collapse
Alright then, I have another question, I am right now on 10.3.7 when Xiaomi releases a new version how do I update it, after rooting, normal OTA or I need to do another process?
Fcleon said:
Ok but in my situation and for the things that I am gonna do, do you really think I need to disable DFE and the other things?, disabling all this things are for what reason?
Click to expand...
Click to collapse
now the question is SHOULD you be disabling DFE and if yes why? if no WHY ?
Google has been putting great efforts recently to keep users data secured !
force encryption encrypts data (internal storage) for the user . however it consumes battery and later if you are trying to flash roms , there are high chances you will be locked out! because twrp cannot READ that encryption. hence after installing rom, if you go back to twrp! and try to access internal STORAGE, twrp will give your error that unable to Mount storage!
now at the time CLEAN FLASHING if you had flashed DFE, it will DISABLE GOOGLE Encryption and twrp will able to access your data
YasuHamed said:
now the question is SHOULD you be disabling DFE and if yes why? if no WHY ?
Google has been putting great efforts recently to keep users data secured !
force encryption encrypts data (internal storage) for the user . however it consumes battery and later if you are trying to flash roms , there are high chances you will be locked out! because twrp cannot READ that encryption. hence after installing rom, if you go back to twrp! and try to access internal STORAGE, twrp will give your error that unable to Mount storage!
now at the time CLEAN FLASHING if you had flashed DFE, it will DISABLE GOOGLE Encryption and twrp will able to access your data
Click to expand...
Click to collapse
Alright so in theory is better to disable force encryption to improve battery and to have the option to install a custom ROM, although at the moment I do like MIUI. And what about disk quota disabler ? What is the reason to disable that?
And if I disable FDE I have to permanent install TWRP ? Because since I just want magisk for the moment I wanted to just use TWRP temporarily and like for making my phone kinda more secure if someone steals it from it
Fcleon said:
Alright so in theory is better to disable force encryption to improve battery and to have the option to install a custom ROM, although at the moment I do like MIUI. And what about disk quota disabler ? What is the reason to disable that?
And if I disable FDE I have to permanent install TWRP ? Because since I just want magisk for the moment I wanted to just use TWRP temporarily and like for making my phone kinda more secure if someone steals it from it
Click to expand...
Click to collapse
1. for disk quota disable or not and why please read more on this subject at https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389. (mainly to make storage stats faster, disk quota is used and to obsolete them you disable it)
2. Twrp is the flasher! and you can flash any modes, roms (designed for the device in your hand!) hence you don't have to keep it flashed! you can call the twrp from fastboot command from pc when you want to!
Thanks everyone I finally unlocked the bootloader, and then used fastboot boot TWRP, backup up everything, then flashed magisk, and then FDE, I can say that the device feels much faster, maybe is the placebo effect but anyway I like it.
The last question that I have is what happens when Pocophone releases a new stable version?, should I just use TWRP and flash the ota file? and i guess flash magisk again and fde again right?
Fcleon said:
Thanks everyone I finally unlocked the bootloader, and then used fastboot boot TWRP, backup up everything, then flashed magisk, and then FDE, I can say that the device feels much faster, maybe is the placebo effect but anyway I like it.
The last question that I have is what happens when Pocophone releases a new stable version?, should I just use TWRP and flash the ota file? and i guess flash magisk again and fde again right?
Click to expand...
Click to collapse
What I always do when updating is:
1. fastboot boot twrp
2. uninstall magisk
3. install full rom (not ota)
4. install magisk
5. reboot
6. install magisk manager
7. install modules
Hello community, so I have successfully done it as in title,
but I still have some steps which not very clear and would hope xda community could enlighten me about it.
so my steps are like this:
1. unlock bootloader with Mi unlock tool
2. flash stock MIUI10.3.8 android 9 rom
2.1 transfer 'Disable force encryption treble' and 'Magisk 19.4' to phone storage
3. fastboot, adb flash twrp 3.2.3-1, boot into twrp 3.2.3-1
4. install the 2 zip files in twrp
reboot system, and it went through..
I know I was lucky, so got some questions here:
1. TWRP mention it's necessary to do dm-verify disable. but I review seems I never did it and got no warning message or error about it. I wonder reason for this? is it because I never modify system partition anyway.
2. 'Disable force encryption treble' file has Magisk built in. I was surprised to see it in log, but nevertheless went to flash higher version 19.4 file. all went through I wonder any issue could be caused from this.
3. I review and realize didn't do the 'wipe data/cache' step before install the 2 zip files. It went through without issue surprisingly.. I wonder the reason for this.
3.1 and if I follow the guide to wipe data and cache first, the 2 zip files will still be there? kind of weird not sure how the emulated storage works..
3.2 Is this 'Disable force encryption treble' file step necessary? I read TWRP can auto settle this encryption thing in newer versions.
and I also wonder whether it means my current phone state is 'not encrypted' state. I check in settings 'encrypt with lock screen password' is off.
Thanks in advance guys
poor me no reply and magisk hide to be punched by safetynet enhance..
phileasx said:
poor me no reply and magisk hide to be punched by safetynet enhance..
Click to expand...
Click to collapse
You followed and old guide.
The latest stable for the poco is 11.0.6 (Android 10)
and the latest magisk is 20.3
Dfe is needed only if you don't want encryption. Otherwise it's not.
The question is what do you want to do.
Custom ROMs/stock ROMs, Android 9/10 there's a different procedure for each one.
sotosgolf said:
You followed and old guide.
The latest stable for the poco is 11.0.6 (Android 10)
and the latest magisk is 20.3
Dfe is needed only if you don't want encryption. Otherwise it's not.
The question is what do you want to do.
Custom ROMs/stock ROMs, Android 9/10 there's a different procedure for each one.
Click to expand...
Click to collapse
Thanks for your reply. Yep I used an older version as I needed something proven working. I'm fine with just MIUI10 android 9 and magisk 19.x.
Do you know about the Dm-verify thing, is it optional also?
phileasx said:
Thanks for your reply. Yep I used an older version as I needed something proven working. I'm fine with just MIUI10 android 9 and magisk 19.x.
Do you know about the Dm-verify thing, is it optional also?
Click to expand...
Click to collapse
Keeping dm-verity is an extra barrier for your device to not be exploited.
If you don't have any reason to turn it off, leave it as it is.
The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.
0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.
1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone, or to a type C usb stick if the device is encrypted.
2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).
3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type
Code:
fastboot flash recovery [twrp version name]
4. Type fastboot reboot and hold Vol+ to go staight into TWRP.
5. From there flash magisk, wipe caches and reboot to system.
6. Come back here and hit that thanks button. :good:
It was always the trick to survive twrp is to boot into recovery and flash magisk. Anyway, good to have a clean thread.
Mi 9T Pro ll Tapatalk
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?
It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
hoopsnake said:
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?
It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
Click to expand...
Click to collapse
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".
Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day.
Nothing changed regarding unlocking, flashing TWRP/Orangefox and rooting regarding the 9T Pro since it's release.
There is NO special method for Miui 12 and the method is overall as good as the same for all Xiaomi/Poco devices.
And the "many people" you mentioned is just 1 person who asked for it in the Questions/FAQ section so no need for unnecessary cluttering of threads.
It sometimes takes a while after flashing magisk for the phone to boot up. Make sure you double check that it was successful by using the Magisk Manager app!
trelokeeper said:
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".
Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day.
Click to expand...
Click to collapse
Yes but is it really relevant to discuss changes on other devices on this forum? No
If those people can't do some simple basic research they shouldn't be rooting in the first place it's designed to be simple and easy and if people can't get that they should have never unlocked their bootloader in the first place. Nothing but clutter here. Give one example of someone speading as you say "lies" about dfe.
Is there a way to fix the "ctsProfile: false" ?
Tried a couple modules but they didn't work.
jugul said:
Is there a way to fix the "ctsProfile: false" ?
Tried a couple modules but they didn't work.
Click to expand...
Click to collapse
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail
Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails
If so, try how it works for Mi 9T, MIUI 11:
https://forum.xda-developers.com/showpost.php?p=83035713&postcount=40681
In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.
The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model
There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
zgfg said:
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail
Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails
If so, try how it works for Mi 9T, MIUI 11:
https://forum.xda-developers.com/showpost.php?p=83035713&postcount=40681
In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.
The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model
There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
Click to expand...
Click to collapse
That worked. Thanks!
trelokeeper said:
The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.
0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.
1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone.
2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).
3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type
4. Type fastboot reboot and hold Vol+ to go staight into TWRP.
5. From there flash magisk, wipe caches and reboot to system.
6. Come back here and hit that thanks button. :good:
Click to expand...
Click to collapse
Hey there I am a completely newbie in this thing, can you please guide me through dm's or anybody else there to help me . I am from India I bought k20 pro in alpha sale and it's warranty is now over so I wanted to root my phone.
I patched the b0ot file of my ROM with magisk and then I flashed it with fastboot. My devices is rooted but I have a issue with WiFi, suggestions?
I'm install twrp on powershell. I got information, is it succesful and when i want to go to recovery i see only miui recovery,. Not twrp. Where is a problem? Bootloader unlocked
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.
Apparently everything went smoothly, but when the reboot starts again with OrangeFox.
Can someone help me?
Thank you
nigol
nigol said:
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.
Apparently everything went smoothly, but when the reboot starts again with OrangeFox.
Can someone help me?
Thank you
nigol
Click to expand...
Click to collapse
Did you Format (not Wipe) Data?
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?
what are problems with leaving encrypted partition... pls help
mustali said:
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?
what are problems with leaving encrypted partition... pls help
Click to expand...
Click to collapse
Just for rooting you don't need DFE, nor to format (neither to wipe) Data.
You need it if you go to flash custom ROM
Btw, rooting can be done without TWRP, just by patching boot.img and flashing the patched image from Fastboot
zgfg said:
Did you Format (not Wipe) Data?
Click to expand...
Click to collapse
No, I just installed the zip with OrangeFox.
How can I fix it?
Orange restarts every time you restart ...
nigol
nigol said:
No, I just installed the zip with OrangeFox.
How can I fix it?
Orange restarts every time you restart ...
nigol
Click to expand...
Click to collapse
Try to Format Data from TWRP: Wipe, Advance, Format Data
ok thanks, I'll try
nigol
---------- Post added at 10:24 AM ---------- Previous post was at 10:11 AM ----------
On OrangeFox in the Wipe directory there are only these entries:
Dalvik / ART Cache, Cache, System, Vendor, Data, Internal Sorage, USB-Storage.
Which entries should I format?
Thank you
nigol
Hello, all. This is my first time posting on XDA, so please bear with me.
I have succeeded in rooting my Samsung Galaxy Tab S6 (running Android 11) with Magisk using the System-As-Root method shown here. My primary reason for rooting my device was to get back the background clipboard access that was nerfed by Google in Android 10. I am utilizing the Magisk module Riru - ClipboardWhitelist as a workaround.
Unfortunately (and obviously), the Module only works when I boot to the Magisk in Recovery partition, through the key combos. Frankly, I have basically no use for the default boot partition since about 1/3 of the apps that I normally use rely on the clipboard access, and the other 2/3 rely on the previous group.
Is there any way to set the device to just automatically boot the the Magisk in Recovery Partition by default, so I don't have to hold down the key combo every time I start up my device? I am open to suggestions, and can follow written guides fairly well...
Otherwise, do I have to look at reflashing the firmware back to the Stock Android 9? If so, how to I get around the restriction in Samsung Download Mode that limits you to flashing the current firmware or newer?
Unless something has changed dramatically since I rooted my t860 (I think you transposed the digits) Magisk is not a recovery. For a recovery you need TWRP. Best help available is here: https://t.me/tabs6twrp
quasiperfect said:
Unless something has changed dramatically since I rooted my t860 (I think you transposed the digits) Magisk is not a recovery. For a recovery you need TWRP. Best help available is here: https://t.me/tabs6twrp
Click to expand...
Click to collapse
I used the method shown here. Magisk in Recovery refers to this.