I flashed stock firmware successfully.the after few days unlocked the bootloader and flashed TWRP and installed Magisk 21.4 .after installing Viper4X and after the driver installation the phone didn't boot clearly.
When it asked for password during boot in stock Android I entered it , then it said "Decryption successfully . Unable to check data integrity " and showed a button "reset phone".
If this is the scenario.
Q1: Is it unwise to install Magisk in Encrypted phone ?
Q2: Or I should not install Magisk modules in Encrypted phone.
Ways to disable forced encryption in Nexus 6p 8.1 is appreciated..
And I tried format data and flashing Magisk.it did nothing and also no encryption zip file befor first boot..
Can I install nethunter on my stock encrypted Android with latest Magisk and twrp 3.1 fde?
Related
Heya,
I decided to nuke my beloved OP2 and start anew, this time including encryption. As I read in the encryption Q&A, the device should not be rooted when doing the encryption, as this can cause havoc.
If you want, you can skip the Italic part. Lets just say, all went well until I rebooted into recovery after setting my encryption password.
- I wiped everything, installed Oxygen OS 3.0.1, flashed the TWRP recovery image (which was recommended in the "how to install oxy 3 on OP2" guide. So it should be a compatible version).
- I boot up my phone and go to the android security settings. I put my phone on the charger and let it encrypt my system with the on-board encryption function. Everything goes well, device reboots fine, now encrypted.
- I went to the security settings again to set my password. I check "ask this password before booting". Now that the encryption is dealt with, I want to have my device rooted. I boot up into TWRP and, as expected, TWRP asks for the password that I just configured.
BUT TWRP won't accept my password, telling me it was wrong. I tried several times, checked that I didn't mess it up because of a foreign language (english) keyboard. When I rebooted the device, it accepted my password on the first try, booting normally afterwards.
I went into the security settings and chose a pattern instead of a password, to make sure the keyboard wasn't the cause of the failure. When booting into TWRP, it asks about my pattern now. But it doesn't accept it.
So I went back into the security settings and unchecked the "ask pattern before boot" part, hoping that TWRP might not need the pattern anymore. When I boot into TWRP now, it asks for a password again, although I have enabled a pattern only.
I rooted my devices several times already, without any problems. This is the first time that I use encryption, so I have no Idea what could be the cause of this problem. It just seems that TWRP has problems decrypting the OxyOs. Please keep in mind that I used the TWRP image that was recommended for OxyOS 3.0.1 in the official Oneplus Forum install guide, so it should be compatible with all the Software and Hardware.
Now that I can't access anything with my TWRP, I haven't installed my SuperSU yet. I can't see how I can gain root access without using TWRP. If I rooted the device first and then encrypted it, the TWRP problem would not matter, but that's exactly the thing that causes HAVOC.
Looking forward to ideas
Fennec
Edit: My progress:
- tried adb sideload the supersu.zip over the stock recovery (update from usb). Protocol error. Installation failed.
- tried all kinds of TWRP versions, starting at the newest 3.0.2. TWRP 3.0.2 claims to have solved the encryption issue, but when flashed I get a bootloop whenever I try to enter the recovery.
- I realized that my adb sideload failed because I used an old version of adb which I found on my laptop. The newest version managed to sideload the supersu and the xposed framework, giving me root rights. TWRP still does not work but at least I got root now :/
same: TWRP can not decrypt system partition on One Plus One, CM-13 and TWRP 3.0.2-0
I remember TWRP said: installation was not successful although it can boot into recovery...
Try fastboot official twrp-3.0.2-2 for me is working fine.
Remember to boot in recovery after flash
Sent from my ONE A2005 using Tapatalk
Hi,
I'd like to have root and xposed installed and keep the encryption enabled, I don't care about backing up the data partition or creating nandroid backups, so having a custom recovery is not important.
I've followed these steps:
- Flashed stock Oreo firmware using Odin 3.13
- Flashed TWRP 3.2.1.1, then boot to it.
- Flashed no-verity-opt-encrypt-6.0 and Magisk v16.0 from TWRP then rebooted.
but I still get Verification failed.
I've also tried to patch the boot image using Magisk Manager and flash it with Odin, but got the same results.
Can anyone tell me what else do I need to do?
Phone is Exynos (SM-G935F) edition.
Thanks.
Any luck
Hi
Just wondering if you had any luck with this?
Im actually trying to get the OREO stock ROM to allow internal storage to be accessed in TWRP so I can do a Nandroid backup but I can never seem to get it to work.
Everytime I come back it cant mount data.
Ive tried flashing ROM then TWRP immediately after.
Boot into TWRP install Magisk and no verity then reboot to system.
Once i come back data is gone. Are you able to access data in Recovery?
This custom ROM is as close to stock as possible less the unnecessary bloat. As far as I am aware, this is the only Oreo ROM that you can encrypt. Make sure you follow the instructions and then you'll have an encrypted rooted phone running Oreo:
[ROM][G935F/FD][ALEXNDR] * U2ERF4 (Oreo) * DevBase v5.8 * Encryption support [Jul-03]
https://forum.xda-developers.com/s7-edge/development/rom-dqd1-devbase-v4-1-multi-csc-safe-t3591647
Hi guys,
So I tried to upgrade to 9.0.10 using TWRP method (Full ROM zip, TWRP installer, reboot recovery, magisk) and the phone keeps rebooting to recovery.
I can see the system lockscreen for a few seconds, with the "Shutting Down" message, then it reboots to recovery.
Can somebody help me?
Thank you!
The same happened to me. I think it was a problem with the encryption because TWRP didn't ask for the pin so the files were encrypted.
I just wiped all and flashed the rom again, then flashed magisk as always, and everything went fine.
Fixed it, some Magisk module was the culprit...
Mount magisk in twrp, delete modules and reboot. I was able to boot into the system, then install the modules again.
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
coder111 said:
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
Click to expand...
Click to collapse
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
zgfg said:
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Click to expand...
Click to collapse
coder111 said:
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
Click to expand...
Click to collapse
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP: https://mega.nz/#F!hllnSIpA!amAG8moMYW_tG8r731Tzgg
Thanks for your help.
I tried the thing with Magisk Manager & boot image file, and it worked. I can live with stock recovery for now. I just needed root.
You saved me quite a bit of hassle. Thanks again.
zgfg said:
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP:
Click to expand...
Click to collapse
Hi Guys,
i lately got on old Samsung Tab 9.7 with an official Android 7 Nougar running on it.
I decided to flash twrp_3.1.0-1_sm-t550_13317 with Odin3_v3.10.7. I followed the steps ashyx described in his thread. So far so good..
Afterwards I installed SR5-SuperSU-v2.82-SR5-20171001224502 from SDCard and it prompted to reboot... now there is the problem.. It won't reboot. It says "Check failed" and I have to factory reset it. When pressing the button it boots into twrp and I can only spot red lines until it reboots with kernel binary and I'm back at the same point.
Any ideas what to do?
btw. are there any new version of twrp , SuperSu or Magisk I can use? Couldn't find any newer versions. I also search for any ROM which has the most up-to-date status (if there are any xD)
Thanks guys
Not my type of tablet but when the SM-T585 had those issues it was a wrong version of TWRP, so maybe look into that.
And SuperSU, really? That's been dead for years, use Magisk instead. It has a whole subforum here on XDA.
/edit: I managed somehow to install latest twrp and lineageOS.. but on first boot it brings up an encryption error.
"encryption was interrupted and can't complete..."
I need to factory reset the tablet... but with that i run again into a bootloop. I can't wipe "data" via twrp Error 8 was it, i think at least ^^
/edit2: I'd go with magisk... but I only find the .apk .. what do I have to flash in twrp?
/edit3:
Managed to reinstall twrp with latest verion twrp-3.5.2_9-0-gt510wifi.img. wiped all data ... Installed Magisk-v23.0 afterwards lineage-18.1-20211108-UNOFFICIAL-gt510wifi . But again.. encryption error on Lineage boot.
Problem solved.
reverted to complete stock, afterwards flashed twrp, installed magisk + lineage 18.1 + OGapps 11.0.
Now it's running.