Hello guys !
So here's my question: I have a modified boot.img on my mobile that deactivates forceencrypt and dm-verity, which has the consequence of not encrypting the /data partition on the 1st boot, and then makes it accessible under TWRP.
If now I flash a stock boot.img, which involves the activation of FE and DMV, will my /data partition be encrypted ? Or will I remain status quo if we start from the premise that it is only at the 1st boot that the encryption is played?
Looking forward to reading you
I found time to test stock boot flash upon modified boot through TWRP: it turns in bootloop, surely because of the data on /data partition which are not in coherence with stock boot. Going on a /data format should bypass the bootloop problem, but I did not proceed.
For now, I have my answer, so it is OK.
Related
Accidentally I deleted boot and boot1 partitions on my Mi4 while extending system partition. Could create system partitions as ext2 but I do not understand what type of filesystem boot and boot1 belong to. Could someone help in creating back the lost partitions? Thanks in advance
[update]
I think I messed up boot partition...so tried to flash rom via fastboot(since I created the system partition already). Now I can't flash recovery also. Can enter only fastboot mode.Is my mobile permanently bricked?
I have a Mi A2 lite (msm8953), and I am trying to boot on two different data mounts. I managed to do it by mounting user data partition as /preData then mounting /preData/second on /data on vendor partition init files, and I booted successfully.
But when going back to the /data as /data, my unlocking pattern doesn't work and I have to delete "/data/system/locksettings.db".
My question is, since the process of booting to a subdirectory (/data/second instead of /data) of the actual data does not touch the actual /data/ files at all, how did the lock process get messed up for the primary data?
My guess is there's a specific partition involved in the lock process that's being modified, if I am correct, which one is it ?
hello i have sm-g950f on latest update(pie) and when i flash the twrp it corrupts my data it says failed to mount data,invalid argument i tried all possible ways to fix it like form ext4 to ext2 and again to ext4 but it wont work.It shows 0mb of storage when i try to switch to otg or etc...
The phone is OEM unlocked,any suggestion?
The data partition in TWRP is not corrupted, it's encrypted. TWRP can not decrypt it so data appears to have a 0MB size.
Formatting data will remove the encryption, but it will re-encrypt on the next boot unless it's blocked from doing so. I'm not experienced with this device, but typically setting Magisk to no-encrypt or flashing a no-encrypt kernel for your device are the common ways to keep data from getting encrypted.
This is one is solid for flashing in TWRP to prevent encryption: https://zackptg5.com/android.php#disverfe
ktmom said:
The data partition in TWRP is not corrupted, it's encrypted. TWRP can not decrypt it so data appears to have a 0MB size.
Formatting data will remove the encryption, but it will re-encrypt on the next boot unless it's blocked from doing so. I'm not experienced with this device, but typically setting Magisk to no-encrypt or flashing a no-encrypt kernel for your device are the common ways to keep data from getting encrypted.
Click to expand...
Click to collapse
Thank you it didnt corrupt it but it was encrypted.Fixed by flashing a zip
HisEvilness said:
This is one is solid for flashing in TWRP to prevent encryption: https://zackptg5.com/android.php#disverfe
Click to expand...
Click to collapse
Thank you this fixed my issue!!
Hello, i have a Redmi note 9S which shipped with Android 10 out of box.. i'm using Dynamic System Updates (DSU) with unlocked bootloader to try custom roms and decided to modify some custom GSI to manually root it and customize some apps (modifications directly to system partition) but noticed that system partition can't be mounted as rw and gives error "wrong fs type, bad option,.." i can only mount it as ro.
I knew that this happens because ext4 partition formatted with EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (so called ext4 dedup) and this prevent it from being mounted as rw, trying to extend system.img with fallocate and resize ext4 file system with resize2fs and then use "e2fsck -E unshare_blocks" seems to work but the phone can't boot and trying to create a new rw system.img also fail as device doesn't boot, also i noticed that GSI versions with "vndklite" can be mounted as rw but same thing, it fail to boot when flashed with DSU and the device reboot again to the main OS..
So i have two questions here:
1) is that happens because the device refuse to boot system partition without EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS as it's already shipped with Android 10 and support this out of box or this happens because of DSU and will boot if flashed with fastboot?
2) and most importantly how can i modify system.img and then apply EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (apply shared blocks feature on the file system) like what custom roms developers do so i can boot a modded system partition?
Any help would be appreciated.. Thanks!
same question, did you find answer?
Hi all,
i have pure AOSP A.13 installed, and after installation i accidentally flashed twrp 3.7 by fastboot flash.
Now, system boot from slot A works, but seems i corrupted somehting:
- at twrp, /sdcard is always empty, have to re-adb push images
- installing i.e. magisk, get such errors
failed to mount "system_ext" (Block device required)
Unable to mount /data/media/TWRP/.twrps
etc.
Super partition seems anyway ok, since AOSP boots fine.
Also, quite strange, Nord is A/B, but i still have recovery partition.
Is there any chance to recover ?
Thanks