Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
do you have access to the bootloader/recovery?
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
[email protected] said:
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
Click to expand...
Click to collapse
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
noutsos said:
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
Click to expand...
Click to collapse
are you on S-ON?
post your bootloader details
rzr86 said:
are you on S-ON?
post your bootloader details
Click to expand...
Click to collapse
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
noutsos said:
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
Click to expand...
Click to collapse
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
rzr86 said:
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
Click to expand...
Click to collapse
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
noutsos said:
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
Click to expand...
Click to collapse
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
rzr86 said:
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
Click to expand...
Click to collapse
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
noutsos said:
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
Click to expand...
Click to collapse
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
rzr86 said:
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
Click to expand...
Click to collapse
tried ruu exe but nth happened,cant find the device,and cant fastboot
How does fastboot not work? Does usb not connect at all?
Hey guys, any news about fixing bug in TWRP which caused corrupting partitions and bricking phones?
Hi guys,
I have the same issue as OP, however only the /data won't get mounted. My phone got stuck while doing wipe of the data partition in TWRP 2.6.3.0 (it didn't freeze, but it was taking over 40 minutes already), so I had to take the battery out and put it back in.
First, I tried using TWRP 2.6.3.0 to perform the wipe again, but I got
Code:
E:Unable to mount '/data'
I got the same error when I tried to install any ROM, so the installation got aborted.
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'.
Here is my bootloader info:
S-OFF
Firmware 3.33
HBOOT 1.27.1100
Radio 11.24A.3504.31_M
I am pretty much desperate at this point. Is there any way or chance of fixing my partitions? I haven't tried fixing it using parted, because I was unable to find a good howto for Sensation. I would be happy for any advice.
MatesCZ said:
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'..
Click to expand...
Click to collapse
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
rzr86 said:
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
Click to expand...
Click to collapse
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
MatesCZ said:
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
Click to expand...
Click to collapse
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
rzr86 said:
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
Click to expand...
Click to collapse
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
...
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Click to expand...
Click to collapse
MatesCZ said:
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Click to expand...
Click to collapse
yeah you are right
some partitions are broken probably from TWRP because a lot of users faced issues similar with yours
someone posted a solution few days ago how to boot a rom from sdcard
he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
he created two partitions
one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
but i can't find that post
if i find it i will come with edit
Hi everyone
Been flashing ROM for a while now, on many different devices so I am not a total noob!
But this morning I tried to fastboot flash the new 5.0 preview. I was running the previous L preview build before.
I did all the correct steps, and fastboot reported success but the phone won't boot. Just stuck in a bootloop. I ended up flashing back to 4.4 and flashing TWRP. TWRP Boots, but it won't recognize any other partitions. No /cache, no /data etc. It just gives a mounting errror. I definitely dowloaded the correct version and the hashs matched, so I am not sure why this is happening.
I followed this guide to repair partition: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
But when I run 'e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata' I get:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Is there a way to repair this?
In general this phone is messed up, and my replacement comes in on Monday. Currently GPS doesn't work, and the battery can't hold a charge. So I guess it's OK that this happened, but I would still like to fix it if there is anything I can do.
BTW Doing 'fdisk -l' reports nothing.
geoldr said:
Hi everyone
Been flashing ROM for a while now, on many different devices so I am not a total noob!
But this morning I tried to fastboot flash the new 5.0 preview. I was running the previous L preview build before.
I did all the correct steps, and fastboot reported success but the phone won't boot. Just stuck in a bootloop. I ended up flashing back to 4.4 and flashing TWRP. TWRP Boots, but it won't recognize any other partitions. No /cache, no /data etc. It just gives a mounting errror. I definitely dowloaded the correct version and the hashs matched, so I am not sure why this is happening.
I followed this guide to repair partition: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
But when I run 'e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata' I get:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Is there a way to repair this?
In general this phone is messed up, and my replacement comes in on Monday. Currently GPS doesn't work, and the battery can't hold a charge. So I guess it's OK that this happened, but I would still like to fix it if there is anything I can do.
BTW Doing 'fdisk -l' reports nothing.
Click to expand...
Click to collapse
I'm no expert but have corrupted enough filesystems and been through these errors before.
Taking a look at the man page for e2fsck I see that you can use an alternative superblock if the primary is corrupted using the -b superblock . Using mke2fs -n will print out where all the superblocks were created. Pop that number after the -b.
Have you already run e2fsck -p?
I'm guessing you have already been to the man page, but for anyone else out there:
http://http://linux.die.net/man/8/e2fsck
Today I got the same error than you when I executed the e2fsck command.
I though the partition was damaged but not, the partition was only disspeared.
So I found other therad that said that if the previous command generate error, just try this command:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
It will regenerate the partition, then you can run the e3fsck command and ensure your partitions are recovered and fixed.
hi, I'm on a Moto g xt1032.
I was on GPE 5.1, and decided to try cm12.1.
Unfortunately I keep getting the error executing updater binary in zip...
Anyone have any ideas on how to help?
I've been searching the forums for ages now :/
Thanks.
r97smith said:
hi, I'm on a Moto g xt1032.
I was on GPE 5.1, and decided to try cm12.1.
Unfortunately I keep getting the error executing updater binary in zip...
Anyone have any ideas on how to help?
I've been searching the forums for ages now :/
Thanks.
Click to expand...
Click to collapse
Which recovery are you using
sjandroiddeveloper said:
Which recovery are you using
Click to expand...
Click to collapse
Im using TWRP recovery 2.8.5.0
r97smith said:
Im using TWRP recovery 2.8.5.0
Click to expand...
Click to collapse
Try doing a clean install and you can also try a Philz 6.58.7 recovery
sjandroiddeveloper said:
Try doing a clean install and you can also try a Philz 6.58.7 recovery
Click to expand...
Click to collapse
I have tried a clean install, and wiping everything. But I still get the same problem no matter what I try to flash now.
The file system was EXT4 in GPE, but I have tried formatting to F2FS in twrp recovery, I still have the same problem.
r97smith said:
I have tried a clean install, and wiping everything. But I still get the same problem no matter what I try to flash now.
The file system was EXT4 in GPE, but I have tried formatting to F2FS in twrp recovery, I still have the same problem.
Click to expand...
Click to collapse
Can you post the exact error ???
sjandroiddeveloper said:
Can you post the exact error ???
Click to expand...
Click to collapse
All it says at the error is this:
symlink: no of symlinks failed = 1
Error executing updater binary in zip"....."
Error flashing zip"...."
Updating partition details...
Unable to mount '/system'
After that, I can see the system has changed back to EXT4
Please can anyone help?
r97smith said:
All it says at the error is this:
symlink: no of symlinks failed = 1
Error executing updater binary in zip"....."
Error flashing zip"...."
Updating partition details...
Unable to mount '/system'
After that, I can see the system has changed back to EXT4
Click to expand...
Click to collapse
I'm getting this ; trying to flash cm-12.1-20150419-NIGHTLY-falcon.zip onto my falcon which had been running GPE. I think it's due to /system not being large enough:
From dmesg:
Code:
<4>[ 693.015497,0] EXT4-fs (mmcblk0p35): bad geometry: block count 249856 exceeds size of device (215040 blocks)
Partition table reads:
Code:
34 262144 1409023 560M 0700 cache
35 1409024 3129343 840M 0700 system
36 3129344 3145727 8192K 0700 kpan
37 3145728 15204095 5887M 0700 userdata
And right enough - not enough blocks.
Code:
~ # cat /etc/fstab
/dev/block/mmcblk0p37 /data ext4 rw
/dev/block/mmcblk0p34 /cache ext4 rw
/dev/block/mmcblk0p35 /system ext4 rw
/usb-otg vfat rw
~ # make_ext4fs /dev/block/mmcblk0p35
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
~ #
I guess I've got a screwed up partition table?
---------- Post added at 11:56 PM ---------- Previous post was at 11:29 PM ----------
westwallpoma said:
I guess I've got a screwed up partition table?
Click to expand...
Click to collapse
Answering my own question here.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
Much better partition table here ; I'll flash this then have another go. Not sure what state my /data partition is in ATM
---------- Post added 20th April 2015 at 12:07 AM ---------- Previous post was 19th April 2015 at 11:56 PM ----------
Yep. That worked, just upzip, then fastboot flash the gpt from the thread I linked to:
Code:
cat /etc/fstab
/dev/block/mmcblk0p36 /data f2fs rw
/dev/block/mmcblk0p33 /cache ext4 rw
/dev/block/mmcblk0p34 /system ext4 rw
The system partition is now partition 34 instead of 35.
Just for giggles, I made sure that everything was hunky-doray:
Code:
umount /sdcard
umount /data
mkfs.f2fs /dev/block/mmcblk0p36
make_ext4 /dev/block/mmcblk0p34
mount /dev/block/mmcblk0p36 /data
mount /dev/block/mmcblk0p36 /sdcard
Then adb push CM12.zip and gapps to /sdcard and install the normal way.
what exactly does adb shell mount do?
Edit: When I input
mount -t ext4 /dev/block/mmcblk0p25 /data
I get the output
mount: Invalid argument
Edit: I made a new ext2 filesystem in mmcblk0p25, how can I mount it?
Syreth said:
what exactly does adb shell mount do?
Click to expand...
Click to collapse
It allows you to mount partions on your phone such as /system so you can edit stuff in that partion (that's why I read)
A_Bunny said:
It allows you to mount partions on your phone such as /system so you can edit stuff in that partion (that's why I read)
Click to expand...
Click to collapse
I tried to mount -t ext4 dev/block/mmcblk0p25 /data and I got mount: Invalid arguement...
probably you should check your filesystem mmcblk0p25
>if it doesnt exist, create one using mkfs
>if it is corrupted, check & repair it using fsck
samsungrockz said:
probably you should check your filesystem mmcblk0p25
>if it doesnt exist, create one using mkfs
>if it is corrupted, check & repair it using fsck
Click to expand...
Click to collapse
I don't have those commands..
Nevermind, I have e2fsck, but e2fsck -pcfv /dev/block/mmcblk0p25 gives the output
e2fsck -pcfv /dev/block/mmcblk0p25
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
25
/dev/block/mmcblk0p25:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>.
EDIT
All praise and All thanks to God
Sometimes you are not able to install gapps or other zips from TWRP due to small size of system image.
Here are the steps to increase/decrease the system image size
1. Boot to TWRP and connect your phone through usb cable.
2. unmount system from TWRP
3. commands to execute:
adb shell
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system 4G (Increasing size of system image size to 4gb, you can use any number you want, for example 2500M for 2500mb)
4. Mount the system in TWRP , now you have 4gb system image. check it by:
df system
5. Try installing the gapps or zip again. Done
Refer: https://linux.die.net/man/8/resize2fs
Dont work on Motorola One Power
chef:/ # resize2fs /dev/block/by-name/system_a 3500M
resize2fs 1.43.3 (04-Sep-2016)
The containing partition (or device) is only 655360 (4k) blocks.
You requested a new size of 896000 blocks.
Click to expand...
Click to collapse
matibu06 said:
Dont work on Motorola One Power
Click to expand...
Click to collapse
try a lower value ,maybe 2500M
Thanks! Confirmed working on a SM-G610M (a friend's Samsung J7 Prime/On NXT)
What is the exactly meaning of "unmount system from TWRP" sorry i'm french and this is not clear for me. Where i can go in TWRP to unmount the system.
i get this error
rosemary:/ # e2fsck -f /dev/block/by-name/system
e2fsck 1.45.4 (23-Sep-2019)
e2fsck: No such file or directory while trying to open /dev/block/by-name/system
Possibly non-existent device?
8|rosemary:/ #
I noticed, my rom has no system.img, which file I have to modify in this case ? I am on a Redmi Note 10s with this rom https://xiaomifirmwareupdater.com/miui/rosemary/stable/V12.5.15.0.RKLMIXM/ (the redmi note 10s have dynamic partition)
Sorry for my noob questions and responses but i'm noob in "Developement" lmao
Yanaoul said:
I noticed, my rom has no system.img, which file I have to modify in this case ? I am on a Redmi Note 10s with this rom https://xiaomifirmwareupdater.com/miui/rosemary/stable/V12.5.15.0.RKLMIXM/ (the redmi note 10s have dynamic partition)
Click to expand...
Click to collapse
you will need to resize it in fastbootd from the stock recovery.
flash the stock rec then "fastboot reboot fastboot" from bootloader.
then fastboot resize-logical-partition <partition> <size>
PS C:\Users\MohammedMehdiTBER> adb shell
prague:/ # e2fsck -f /dev/block/by-name/system
e2fsck 1.43.3 (04-Sep-2016)
e2fsck: No such file or directory while trying to open /dev/block/by-name/system
Possibly non-existent device?