Hello,
i Have recently upgraded to android 10. When flashing twrp i get a message failed to mount system partition. If i reformat system to ext 2 then back to ext4 i can mount system in twrp. When i re flash latest factory pixel 2 image and go back into twrp i can no longer mount system again. Is this some new thing with Android 10? Without it mounted i can not access my system partition with root explorer or other root apps. is there a way to force system to mount after flashing a new image?
After reflashing with magisk system was mounted somehow. Not sure how this happened.
Related
Help!!!!!
I chose the wrong option in TWRP and wiped system. now my data partition wont mount and TWRP says there is no os installed. how do i install a os on there and data partition shows up as 0 mb
joel_1204 said:
Help!!!!!
I chose the wrong option in TWRP and wiped system. now my data partition wont mount and TWRP says there is no os installed. how do i install a os on there
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images#hammerheadktu84m
Hi,
i want to format my /data but i can't because TWRP can not mount it.
I tried to change the filesystem to ext4 and format it but i stuck in boot.
It also says internal storage 0mb.
How can i fix that?
or is that normal with nougat atm?
yeah, I have the same problem. I think the L04 doesn't have a working version of TWRP.
TomboIa said:
Hi,
i want to format my /data but i can't because TWRP can not mount it.
I tried to change the filesystem to ext4 and format it but i stuck in boot.
It also says internal storage 0mb.
How can i fix that?
or is that normal with nougat atm?
Click to expand...
Click to collapse
same here! I tried to go back to EMUI 4.1 and use flash fire to update firmware without loosing root, it works all the way up to the EMUI 5 update then it forces me into TWRP to flash the file for whatever reason and then I loose root, and TWRP stops working properly.
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?
I tried to install a custom rom, somehow the stuck in boot up screen. I got in TWRP and found that the /data partition can not be mount. How can I get /data partition back?
Try formatting
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?