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?
Related
Hello everyone,
i bricked my a511 because i had the stupid idea to set go back factory defaults with the old cwm.
so, i know that the problem is the damaged data partition, is it possible to recreate this partition ?
I had the same Problem. I flashed a data.img. This works. you can even mount the system partition? and the cache?
The Fastboot commands are "fastboot flash userdata C:\[your path to the data.img]" and "fastboot flash system C:\[your path to the data.img]"
and "fastboot flash cache C:\[your path to the data.img]"
Webitu
No, it's not the partition that's damaged, but the NAND chip itself.
Hello there.
I have a zenfone 2 laser that came with the CN rom.
Due to lack of communication with google I'm trying to install the WW rom.
I'm aware that the WW system partition is larger than the CN system partition.
So I started my long journey to enlarge the system partition and install the WW rom.
To do such, I've done the following:
1. Gain root with king root.
2. Installed ADB on my PC.
3. Unlocked my phone's Bootloader.
4. I installed parted in my phone.
5. I flashed the Z00T custom TWRP recovery to my phone, which worked.
6. I used parted to delete both system and userdata partitions, which were next to one another.
7. I used parted to create two new system and userdata partitions so I could have more space for the ww system.
8. I formated system with ext4.
9. I tried to format userdata with ext4, but wasn't able. So I went to fastboot mode in order to see what could I do from there.
10. I was able to format the userdata partition with ext4.
11. I was able to flash the ww system to the system partition. I was so happy
12. I tried to go back to recovery but got a boot loop.
13. I flashed Z00T custom TWRP recovery again, cleared the cache and rebooted to recovery... same boot loop.
14. I flashed numerous boot and recovery images in order to try to get to recovery mode with no luck what so ever.
I'm kind of lost and I've been wandering the web for a while in search for an answer. Any help would be much appreciated. :fingers-crossed:
Hi there,
Did you manage to resolve your problem?
I'm with the same problem (CN rom) and i'm tired looking for a solution to flash ww rom. Which program did you use to delete and create new partitions?
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.
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?