Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
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.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me
thekool11 said:
Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
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.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me
Click to expand...
Click to collapse
Have you checked md5sum?
glevitan said:
Have you checked md5sum?
Click to expand...
Click to collapse
Did you really need to quote all of that just to say that?
Sent from a dream.
I believe you're trying to flash a Saga ROM.
bananagranola said:
I believe you're trying to flash a Saga ROM.
Click to expand...
Click to collapse
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded
thekool11 said:
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded
Click to expand...
Click to collapse
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?
A ROM for a different device: the Desire S, codenamed Saga. We are the forum for the Desire HD/Inspire 4G, codenamed Ace.
williamrazmy said:
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?
Click to expand...
Click to collapse
here is a noob fiendly way to solve it
http://forum.xda-developers.com/showthread.php?t=2302599
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, 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.
Hi
I've cm-11-20150607-NIGHTLY-i9100 on my Samsung Galaxy SII i9100
It has gapps-kk-20140105-signed (as far as I remember).
I do have cwm 6.0.5.1
Two days ago, there was some update (haven't seen what exactly).
Now, while booting the phone hangs on the boot screen.
When I lunch into cwm-recovery I do see:
CWM-based Revocery v6.0.5.1
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
The show log says:
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p7 (File exist)
E:Can't mount /cache/recovery/log
(and more like this)
...
I do have MTP enabled, and debugging USB disabled- this is a big problem since i can not access adb...
I would like to backup data, but how can I enable adb from cwm?
I did try to wipe dalvik (I think it did work) /format cache - It does not work - it hangs.
I did try to "reboot to receovery (or reboot to bootloader): from the cwm- it hangs
I did try to mount /storage/sdcard0 - it hangs
I did try to create a backup from phone memory to scracd1 - it hangs
I can boot into fastboot.
It looks like some error on partition, or problem with internal phone memory.
Anything that try to access internal sdcard0 hangs
How can I backup the phone (or at lest photo - not all were synced yet).
What would be the next step?
Any idea howto enable USB debugging?
I've seen this tutorial
(can add a link so google "enable usb debbuging through clockworkmod with adb")
but it is for the Nexus, not for the i9100...
I do have Ubuntu, with
adb version 1.0.31
I can switch to Windows if it would help...
Ok,
For the moment, I made the wrong assumption.
I can access adb.
The solution was to install latest android SDK (cm11 is some like Android 4.4.4) to get newest adb
(developer.android com/sdk/installing/index.html?pkg=studio )
To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot. - quote from stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-command
Click to expand...
Click to collapse
stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-commands
and
having Enabled ADB Integration via Tools > Android > Enable ADB Integration
stackoverflow com/questions/26079838/android-studio-adb-error-device-unauthorized-please-check-the-confirmat
Now I can access
adb shell (while booting into cwm recovery - Power+volUp+Home)
Code:
# parted /dev/block/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 159MB 105MB CACHE
8 159MB 176MB 16.8MB MODEM
9 176MB 713MB 537MB FACTORYFS
10 713MB 2861MB 2147MB DATAFS
11 2861MB 15.2GB 12.4GB UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
~ # cat /etc/fstab
/dev/block/mmcblk0p7 /cache ext4 rw
/dev/block/mmcblk0p10 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
~ # mount -o ro -t ext4 /dev/block/mmcblk0p10 /data
mount: mounting /dev/block/mmcblk0p10 on /data failed: Invalid argument
The problem is - I can not backup the data nor mount the /data partition
Sir,
This forum is for helping new users to help members navigate the site, not for support.
I see you've found your device section and already know how things work on XDA.
So please note the sticky from the top of the Assist section and ask directly in this thread for I9100:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck