Hello, I am trying to switch from CM10 to CleanRom, but am having issues installing the ROM itself. When selecting the last next before the install process in the Aroma installer, it simply goes to the install complete screen.
I pulled the install logs off the device which I have pasted below.
Code:
AROMA INSTALLER version 2.51
(c) 2012 by amarullz xda-developers
ROM Name : CleanROM
ROM Version : 5.0
ROM Author : Scott
Device : HTC One X
Start at : Thu Nov 8 13:04:13 2012
CleanROM V
//snip//
Formatting and Optimizing File System...
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Creating filesystem with parameters:
Size: 1744829440
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6656
Label:
Blocks: 425983
Block groups: 13
Reserved block group size: 103
Created filesystem with 11/106496 inodes and 13971/425983 blocks
error: file_write: write: I/O error
Installer Error (Status 1)
End at : Thu Nov 8 13:04:13 2012
I can reload CM10 happily via recovery, just not CleanRom. (I also tried Viper which failed too.)
Info:
Bootloader Unlocked
HBOOT-01.09.0000
I feel I am missing something stupid here, any ideas?
Thanks,
koj1n said:
Hello, I am trying to switch from CM10 to CleanRom, but am having issues installing the ROM itself. When selecting the last next before the install process in the Aroma installer, it simply goes to the install complete screen.
I pulled the install logs off the device which I have pasted below.
Code:
AROMA INSTALLER version 2.51
(c) 2012 by amarullz xda-developers
ROM Name : CleanROM
ROM Version : 5.0
ROM Author : Scott
Device : HTC One X
Start at : Thu Nov 8 13:04:13 2012
CleanROM V
//snip//
Formatting and Optimizing File System...
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Creating filesystem with parameters:
Size: 1744829440
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6656
Label:
Blocks: 425983
Block groups: 13
Reserved block group size: 103
Created filesystem with 11/106496 inodes and 13971/425983 blocks
error: file_write: write: I/O error
Installer Error (Status 1)
End at : Thu Nov 8 13:04:13 2012
I can reload CM10 happily via recovery, just not CleanRom. (I also tried Viper which failed too.)
Info:
Bootloader Unlocked
HBOOT-01.09.0000
I feel I am missing something stupid here, any ideas?
Thanks,
Click to expand...
Click to collapse
Have you tried wiping everything (data, cache, dalvik, system) before running the installer?
Yep, I have wiped everything. Even tried flashing the CleanRom boot.img via fastboot, non-CM10 ROMs just seem fail to load.
Unzip on a computer and flash the cleanroms boot.IMG then flash.
Sent from my HTC One X using xda premium
curly9 said:
Unzip on a computer and flash the cleanroms boot.IMG then flash.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
He's on hboot 1.09 he doesnt need to do that
Figured it out. CleanRom 5 is incompatible with TWRP 2.3+, just downgraded and it works again.
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
Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Device not rooted.
ashishk2 said:
Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Click to expand...
Click to collapse
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/
LaNsLyDe said:
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/
Click to expand...
Click to collapse
Hope it works bud ! So need the phone back and running.
Keep me posted
Will do, do you know where the thread went for the 38R flashable zip?
also when you download the fastboot zip extract it into where you have fastbooto n your pc and do these commands. will most likely wipe data and you can replace the recovery it flashed with a custom one:
Start the fastboot tool and run the following in the command line (that means, windows+r, type cmd, press enter), in sequence:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
ashishk2 said:
Hope it works bud ! So need the phone back and running.
Keep me posted
Click to expand...
Click to collapse
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.
LaNsLyDe said:
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
[/COLOR]
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.
Click to expand...
Click to collapse
I'm not rooted or custom recovery ! What do I do ?
Thread closed ! "corrupt persist.img"
Thank you
@justinblaine23 for posting the link.
@markbencze for proving detailed instruction for the fix.
@other who posted solutions.
The issues for caused bcoz of corrupt persist.img. If anyone faces the same issue reboot after boot animation or 0Mb in recovery kindly following the instruction on this link
Caution: Dont press and hold the power button to rest the phone, this caused the error on my OPO.