Hi
I am in no way a developer and I am not responsible for any damage caused to your device.
I have made some changes to the latest kernel from 43.0.A.7.99, this is from the UK-EE firmware but should work on all firmwares for the G3311. I am unable to test on any other model, so try at your own risk.
The kernel has forceencrypt and dm-verity disabled. Forceencrypt will encrypt your data partition on boot, so formatting in TWRP is pointless as the default kernel encrypts it again. dm-verity stops part of the system partition being written to, so things like init.d cannot be enabled. these are both now possible with this kernel. The kernel is NOT patched with Magisk, so this will need to be patched in the same way as when you first rooted.
Related
Currently my phone is decrypted. I am trying to install a ROM which is force encrypted.
Without wiping internal storage, how can I keep my phone decrypted?
Flash any custom kernel without encryption after you have flashed the ROM.. Didn't try this method with any custom ROM.. But tried with stock.. Worked..
Still have a backup for safety..
Joyarup said:
Flash any custom kernel without encryption after you have flashed the ROM.. Didn't try this method with any custom ROM.. But tried with stock.. Worked..
Still have a backup for safety..
Click to expand...
Click to collapse
so while flashing the ROM just install ElementalX kernel should decrypt my phone..
Thanks..
Your other option is fed_patcher_v8-signed.zip, you flash it after a ROM / kernel combo that forces encryption that forces encryption. That will disable encryption. You need to wipe everything first though to get rid of your already encrypted data though.
ForceEncrypt is a mount table option contained in the kernel (boot.img)
Encryption is done by the kernel upon first boot noticing the user partition is not encrypted.
So if you want to keep your user partition decrypted, you must never boot a kernel (boot.img) with the ForceEncrypt option in place.
There are many ways to avoid this:
One way is after you install the ROM (prior to first boot), flash a boot.img that has ForceEncrypt disabled (set to Encryptable)
Another way is to flash SuperSU (prior to first boot) and it will patch your existing boot.img to disable ForceEncrypt. If you are flashing ROMs from bootloader, eseentially this means you MUST boot into TWRP recovery to flash SuperSU PRIOR to rebooting. In the process of flashing your new ROM, if you've overwritten TWRP recovery with stock, you'll need to reflash TWRP recovery also.
What is this warning on the TWRP site regarding the S6:
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
And how does one install the above mentioned kernel without a custom recovery like TWRP?
Tyvm
spacer89 said:
What is this warning on the TWRP site regarding the S6:
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
And how does one install the above mentioned kernel without a custom recovery like TWRP?
Tyvm
Click to expand...
Click to collapse
No clue what this means, but i flashed over CPL3 the latest TWRP and it boots fine using stock kernel.
I just have the fingerprint issue... waiting for @amieldl143 to post latest bigdaddyrom build and am flashing that over CPL3 via TWRP.
What is this warning on the TWRP site regarding the S6:
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
And how does one install the above mentioned kernel without a custom recovery like TWRP?
Tyvm
I don't mean to sound like I am scolding, but this is now the third thread that you have opened regarding issues that you are having installing TWRP, which should be a relatively simple process.
I maintain a thread with step-by-step instructions here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Follow that any will have root and TWRP installed. Even if you just get up to being rooted on stock, you can use Flashify to install TWRP. Just be sure to use the right version. Again, see my thread.
Hi. Nobody could answer my Reddit thread, so I figured out I would ask here instead.
I'm using this guide: https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
My device is already rooted (on HavocOS - a big mistake because it's unstable and not fully functional), with the Big cluster disabled, TWRP 4-core recovery and the ElementalX kernel.
I want to install the latest stock, unrooted ROM because it's more secure (I suppose), stable and probably faster than any custom ROM. At the same time, I need ElementalX to underclock and 4-core TWRP in case of emergency.
I have 3 questions:
The guide tells me to install a modified boot.img that disables forced encryption. Why would I have to do it? I don't want to root it but at the same time, there's no RPMB - the bootloader locks itself with each restart. Do I need the modified boot.img anyway? Nobody explained thus far why it is needed.
As mentioned, the device locks its bootloader each time it's restarted (no RPMB). This guide https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 says that locking the bootloader when custom recovery is installed can result in a brick. I have custom recovery installed right now. Should I flash stock recovery with a boot.img before rebooting to be safe?
Can custom kernels be flashed through TWRP with a locked bootloader or should I do it through fastboot?
Oh, and by the way, I've been using my Nexus 5X with occasional restarts but no bootloop for 2 years (after replacing the motherboard with a used one that I bought, but it doesn't have RPMB). When it restarted on its own, I panicked and disabled the Big cluster using the fix but I think the restarts are caused by the unstable HavocOS ROM with an incompatible (too recent) vendor image.
My ginkgo had stock ROM V12.0.6.0.QCOMIXM (A10) and I updated to stock ROM V12.0.2.0.RCOMIXM using TWRP recovery (twrp_ginkgo-willow_3.4A9_23-12-2020_BL) However after flashing the rom zip, and after flashing magisk, my phone got into "MIUI" icon, then bootloops into recovery again with alphanumeric directory names.
I tried Disable Dm Verity Force Encrypt after flashing magisk.zip but same problem.
I have tried the following recoveries so far:
twrp_ginkgo-willow_3.4A9_23-12-2020_BL
twrp-3.5.2_10-2-ginkgo
orangefox R11.0_1 (with Disable DM-Verity, Disable Forced Encryption and Aggresive stock recovery deactivation all enabled).
But whenever I flash magisk, I still get the bootloop and alphanumeric directory names, and the only way to restore my phone without having to wipe data is to flash the recovery zip again (but without magisk).
Any suggestions on how to get around this?
bomberb17 said:
Any suggestions on how to get around this?
Click to expand...
Click to collapse
i already answered you here
use this DFE