I was just wondering what would happen if I'm using F2FS on my data partition when the custom kernel I'm using doesn't support it? Would my device still boot properly or be stuck on boot?
This happened to me. It was stuck on the bootloop
Related
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.
Guys my custom ROMs (find this issue in RR and AEX) automatically reset itself after booting into recovery!
Why is that happening?
wajeeh.ihi said:
Guys my custom ROMs (find this issue in RR and AEX) automatically reset itself after booting into recovery!
Why is that happening?
Click to expand...
Click to collapse
Use twrp to format the internal storage (you can choose f2fs or ext4) and all will be fine
Hi everybody, I've encountered a strange problem and i come to see if anybody can help me.
Symptom: can't boot into primary ROM. Fine booting into secondary.
I'm using OnePlus 3 with H2OS 3.0 stable v2 as my primary ROM, and official Resurrection Remix as my secondary (installed to data partition).
Today I wanted to update my RR to the newest version so I downloaded the zip and by the way updated Dual Boot Patcher to 9.2.0_r106.
When I turned to ROM tab, it asked me to set kernel (which i did not know why), I didn't care much and pressed 'Yes' (in my Resurrection Remix), then i rebooted to recovery in order to install the patched zip file.
Somehow it failed to install, so I decided to boot into primary and flash with Dual Boot Patcher in primary ROM. But here it happened...It turned black out after I've chosen to boot into primary in the boot screen.
I tried flashing the boot-before-updating-ramdisk.img but it only led to boot loop in boot animation of primary ROM.
ps. Today I found my magisk root in RR is lost. Are these things related?
Can anybody help me with this......
is it because I set kernel while not in primary rom? How do i solve it?
And I'd also like to know what exactly does 'set kernel' do? What files does it modify?
Hi I have unlocked my bootloader on my Moto G5 and flashed TWRP. I then tried a wipe on TWRP as it asked for decrypt password and now my phone keeps saying your device has been unlocked and can't be trusted and is stuck on this page. Can someone explain how to fix this please as i'm new to flashing this phone and not done this stuff for at least 5 years.
Smonic said:
Hi I have unlocked my bootloader on my Moto G5 and flashed TWRP. I then tried a wipe on TWRP as it asked for decrypt password and now my phone keeps saying your device has been unlocked and can't be trusted and is stuck on this page. Can someone explain how to fix this please as i'm new to flashing this phone and not done this stuff for at least 5 years.
Click to expand...
Click to collapse
The answer to your question is on my twrp faqs but I'll explain as you are new to this
If you flash twrp and are using stock rom if you modify system your phone will not boot.
This is because dm-verity will fail
To get around this you can do one of two things
1 - Flash supersu/magisk zip to root your phone - This will automatically disable dm-verity
2 - Flash a custom rom as their kernel will have been modified to disable dm-verity
You can get rid of the bootloader unlock warning by flashing a modified image
If you have gone to the trouble of unlocking your bootloader & flashing twrp I suggest you just do a full data wipe - format data if you have encryption & flash lineageos 15 & nano gapps
TheFixItMan said:
The answer to your question is on my twrp faqs but I'll explain as you are new to this
If you flash twrp and are using stock rom if you modify system your phone will not boot.
This is because dm-verity will fail
To get around this you can do one of two things
1 - Flash supersu/magisk zip to root your phone - This will automatically disable dm-verity
2 - Flash a custom rom as their kernel will have been modified to disable dm-verity
You can get rid of the bootloader unlock warning by flashing a modified image
If you have gone to the trouble of unlocking your bootloader & flashing twrp I suggest you just do a full data wipe - format data if you have encryption & flash lineageos 15 & nano gapps
Click to expand...
Click to collapse
I'm also new to the device and using a encrypted data... I ended up using a encrypted data in Lineage too
Sent from my XT1672 using Tapatalk
felipeap said:
I'm also new to the device and using a encrypted data... I ended up using a encrypted data in Lineage too
Sent from my XT1672 using Tapatalk
Click to expand...
Click to collapse
That's not a problem
If you are going from lineageos 14.1 to lineageos 15 you need to format data to remove encryption before flashing lineageos
Once you have booted lineageos 15 you can encrypt the phone again if you want
TheFixItMan said:
That's not a problem
If you are going from lineageos 14.1 to lineageos 15 you need to format data to remove encryption before flashing lineageos
Once you have booted lineageos 15 you can encrypt the phone again if you want
Click to expand...
Click to collapse
Yeah... I made the switch today and realized the worst way I wasn't able to decrypt the data on the 64Bit TWRP. It all went good eventually after a few flashes and reboots, and the ROM is great.
Sent from my Moto G5 using Tapatalk
felipeap said:
Yeah... I made the switch today and realized the worst way I wasn't able to decrypt the data on the 64Bit TWRP. It all went good eventually after a few flashes and reboots, and the ROM is great.
Sent from my Moto G5 using Tapatalk
Click to expand...
Click to collapse
I didn't compile the 64bit version of TWRP & haven't tested it so don't know about encryption of that
I know my 32bit version of TWRP can decrypt data on all 32bit roms
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.