Hi everyone, I can't install the "no verity opt encrypt 6.0" in any way, obviously the twrp is ok, the root is ok with Magisk, but trying to install the encrypt zip continues to give me error. Does anyone have the solution?
Maybe the zip is outdated...
Check this thread.
popoiuiu said:
Hi everyone, I can't install the "no verity opt encrypt 6.0" in any way, obviously the twrp is ok, the root is ok with Magisk, but trying to install the encrypt zip continues to give me error. Does anyone have the solution?
Click to expand...
Click to collapse
reboot recovery than try flashing, cheers
Their is a newer version out, prior to flashing
Related
Guys I'm looking for someway to clean flash 4.1.1 OOS and then get root with magisk and all the safetynet related stuff. Oh, also I should disable the dm-verity warning.
Only I can't find any guide to show me that, anyone who can explain in detail?
Thanks in advance
ruggyboss said:
Guys I'm looking for someway to clean flash 4.1.1 OOS and then get root with magisk and all the safetynet related stuff. Oh, also I should disable the dm-verity warning.
Only I can't find any guide to show me that, anyone who can explain in detail?
Thanks in advance
Click to expand...
Click to collapse
You'll need TWRP installed, so if you haven't got that already, unlock the bootloader and fastboot flash TWRP.
Code:
fastboot oem unlock
fastboot flash recovery <filename>.img
There's plenty of guides around on how to set up fastboot.
After that it's just a matter of flashing the full OTA in TWRP and after that the Magisk zip. Magisk will disable dm-verity.
Install the Magisk Manager, enable Magisk Hide and you're done.
Didgeridoohan said:
You'll need TWRP installed, so if you haven't got that already, unlock the bootloader and fastboot flash TWRP.
There's plenty of guides around on how to set up fastboot.
After that it's just a matter of flashing the full OTA in TWRP and after that the Magisk zip. Magisk will disable dm-verity.
Install the Magisk Manager, enable Magisk Hide and you're done.
Click to expand...
Click to collapse
So I rooted with magisk, no problem but one: I still get the dm-verity warning on boot.
Tried flashing no-verity-opt-encrypt 5.1 but nothing (actuality I don't even know how that works). Help for this? Thanks guys
ruggyboss said:
So I rooted with magisk, no problem but one: I still get the dm-verity warning on boot.
Tried flashing no-verity-opt-encrypt 5.1 but nothing (actuality I don't even know how that works). Help for this? Thanks guys
Click to expand...
Click to collapse
Is it dm-verity or unlocked bootloader warning? They're different...
Didgeridoohan said:
Is it dm-verity or unlocked bootloader warning? They're different...
Click to expand...
Click to collapse
The one that goes "the dm-verity is (or is not?) started in enforcing mode and may not work properly", and then there's red text...
here you go:
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
You can also flash a custom kernel that has dm-verity disabled.
Ok then
Done with that too
Thanks a lot! <3
Hello everyone, I've tried to search on the web about this issue since the OTA for Android O is finally out for the Oneplus 5 and couldn't get a satisfying solution. I rooted my OP5 a while ago with Magisk and now that this update is out and tried to install it, It just wouldn´t let me, searching I found that my locked swich to relock the bootloader was because I had to enable it on Magisk, so I opened magisk and couldn´t find that option, and now that I searched on how to enable the "Lock bootloader option" in the Magisk app and found nothing, I'm just out of ideas, so guys, could you help a (noob) brother out with this?
Ps.: If you could attach some screenshots about where to click or what to do, I'll apreciate it a lot (yeah, I'm that stupid when I freak out and don't find how to undo mi mess)
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the full OTA zip, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Didgeridoohan said:
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the update, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Click to expand...
Click to collapse
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Fosko Stock said:
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Click to expand...
Click to collapse
Yes.
Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.
I am also interested about update with Magisk
GeorgeKatsi said:
Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.
Click to expand...
Click to collapse
You can flash patched_boot to get the TEMP magisk working before the new twrp available for 10.0.3.0
Code:
fastboot boot patched_boot.img
The boot image can be patched via magisk by yourself or you can use mine from 20181104_mi8_10.0.3.0_patched_boot.img
Remember this TEMP solution fails after rebooting. Or you fastboot boot patched_boot.img every rebooting.
Hello ich have the Same Problem, can U Tell step by step how to do that?
Ich want to flash custom Rom
same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data
mikefallen said:
same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data
Click to expand...
Click to collapse
I flashed the patched_boot made by magisk, but I am still unable to decrypt twrp. I hope they support 10.0.3.0 soon so I can use twrp again.
Hello guys,
Yesterday I flashed my Mi 8 to get root permissions with Global V10.2.1.0 with Magisk 17.3, including Disable DM-Verity and Force Encrypt. Everything was working perfect, Magisk notified me about updating to v18, so I did, and MIUI notified me about an update (if I'm not mistaken, for 10.2.2.0).
MIUI downloaded the update and asked me to reboot to install it. It booted into TWRP and did the whole installation, apparently without issues, but then I restarted and it goes straight to TWRP.
I tried clearing cache/dalvik but nothing.
Every time I reboot and gets to TWRP, when I press the menu button to see the log, the last lines say:
Full SELinux support is present.
set_policy_failed:/datamisc
I don't know if this is relevant, but seeing a "failed" is not nice.
As an observation, the folder /data/system is full of folders, but the /system directly in root folder only has /usr/share/zoneinfo (I don't know if this is normal or not),
If the system updated to 10.2.2.0, would flashing to 10.2.1.0 set the ARB or it's safe for me to flash it again? Any ideas?
Thanks!
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
ArmedandDangerous said:
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
Click to expand...
Click to collapse
Thanks for the answer! Do I need to wipe DATA too?
EDIT: I just flashed DM-Verity and then Magisk and all good. No need to wipe data. Thanks!!
Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.
SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!