Does this partition = DTBO?
Can't really find anything on Google, but I know that Huawei like to rename their partitions (like Boot became ramdisk and kernel, Pixel still has boot.)
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?
Hi,
before I brick my smartphone: is the internal storage a real GPT partitioned thing which can be changed by gdisk, parted and friends? I'll change only the things starting with cache - and only sizes & partitions, not the overall layout. I would like to squeeze the unused cache-partition to a few MBs and reduce the cdrom-partition, move the system-partition at top and increase the userdata partition.
Best regards,
mifritscher
Any infos on this one? Could I recover from a completely broken flash via fastboot, qdload or sdboot?
Ok, I tried - and failed *g*
I partitioned with parted - and the kernel accepted the new partition table as well. But it seems that the phone either blocks write access to the GPT, or has its own internal version. Because after a reboot, I got the old partition table again.
Luckily I had a backup (with I needed for repartitioning anyway), and both fastboot and recovery worked. TWRP was only a bit refused regarding the broken partitions, but it could both reformat the partition and fire the backup (with I did with dd and gzip) before).
So the big question is: How can I unlock the emmc to write to the GPT?
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 ?
Hi everyone. My phone (redmi 6 cereus) has realtively small system partition, so I decided to try to manually alter the partition table. I did that one time without any problems so I thought it would go smoothly this time. Boy was I wrong Like the last time, I resized my data partition, deleted system partition and created a new one to use all the space left available after shrinking data partition. After that I rebooted my device to twrp but this time I forgot to name that new partition as system (now its label is something like "Microsoft basic data partition") and now my device bootloops. I cannot even boot to recovery, fastboot is the only thing that boots.
I've tried booting twrp using fastboot boot twrp.img but that also resulted in bootloop. My theory is that my device is trying to mount system partition during early stages of booting, but it cannot find one so it crashes and reboots. So I thought that maybe I could extract boot.img and modify it so fstab would not have any references to system partition, but my boot.img has empty ramdisk. I've tried to to the same thing with twrp image, but there I could not find fstab file.
Maybe my thinking is wrong and there is another solution to this problem. Maybe it is possible to name partition from fastboot? I don't know, I'm pretty familiar with linux, but not so much with android. Any help would be appreciated
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?