Database Develop

Fix I/O Problem- Please need your help

This post will interest many. a few days ago my internal memory is physically dead, the memory (16GB) is partitioned into two, /data (~ 2GB) and /sdcard (~ 14GB). Not having these partitions the phone can not save settings or user data.
Symptoms:
* Internal sd corrupt (http://forum.xda-developers.com/showthread.php?t=845708)
* (I/O) error in factory reset
* mmcblk0p1 y mmcblk0p2 does not appear in /dev/block/
* Boot loop
* E: can not mount /dev/block/mmcblk0p1 in recovery, or updating rom
* You can't install applications, since /data does not exist
Please I need your help to move the partition /data to external sd memory (/dev/block/mmcblk1p2).
I Create two partitions fat32 (/dev/block/mmcblk1p1) and ext4 (/dev/block/mmcblk1p2) and edit the fstab file and vold.fstab. the system now recognizes the FAT32 partition of the external memory as internal memory but the partition /data does not mount the second partition of external SD.
original:
---
/dev/block/stl11 /cache auto llw,check=no,nosuid,nodev
/dev/block/mmcblk0p2 /data auto llw,check=no,nosuid,nodev
/dev/block/stl10 /dbdata auto llw,check=no,nosuid,nodev
/dev/block/stl9 /system auto llw,check=no
/dev/block/mmcblk0p1 /mnt/sdcard vfat rw
(null) /sd-ext auto rw
---
edited:
---
/dev/block/stl11 /cache auto llw,check=no,nosuid,nodev
/dev/block/mmcblk1p2 /data auto llw,check=no,nosuid,nodev
/dev/block/stl10 /dbdata auto llw,check=no,nosuid,nodev
/dev/block/stl9 /system auto llw,check=no
/dev/block/mmcblk0p1 /sd-ext vfat rw
(null) /mnt/sdcard auto rw
---
The busybox df-h command shows that the first partition is mounted, but the second partition is not listed .
I've tried everything, and what I see is that it requires more knowledge. Not whether to build or edit the kernel or some file.
I appreciate your help, since many users have a higher Know-how on this topic.
* My English is very bad, I'm using the google translator.

I tried to edit the initramfs folder to edit files lpm.rc init.rc and fota.rc, i download many kernels to remove zImage and edit images and package them again, but does not work, not that I'm doing wrong.
Someone who has worked with the edition of the kernel can help me build or rebuild a file with the new changes.

Unheard of Semi-Brick situation!!! HELP!

I was previously on Gingerbread 2.3 with CF-Root kernel. I flashed Ultimate XXLSC JB ROM v5.1 from here This ROM flashed fine from CWM as far as I know. It had a few issues since i forgot to wipe the data. I rebooted into recovery to do that. After which i lost root (im not sure if i had it before wiping the data though). The su binary was corrupted in some way (ES File explorer could not get its properties) and SuperSU said 'Installation failed'. I tried installing a simple rooting zip from CWM. This got stuck at 'Unmounting system' and did no effect to the su and busybox binaries. CWM was also causing problems. It refused to boot into system normally and could not unmount /system. I could not make a backup of this system since it would crash on backing up 'busybox'. I could not reflash the zip as it would not go further than the intial text logo. Here is the normal boot into recovery log:
Starting recovery on Sat Jan 26 17:22:13 2013
framebuffer: fd 4 (800 x 1280)
E:unknown volume for path [/system]
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /modem emmc /dev/block/mmcblk0p8 (null) 0
9 /emmc vfat /dev/block/mmcblk0p11 (null) 0
10 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
PhilZ Touch 3
CWM Base version: 6.0.1.9
Command: "recovery"
ro.sec_debug.enable=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
init.svc.ueventd=running
ro.crypto.keyfile.userdata=/efs/metadata
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
IS THE RED PART THE ISSUE? HOW DO I FIX THIS? CAN I GO BACK TO A CWM BACKUP OF MY OLD GB SYSTEM SAFELY? The OS functions fine for now though.

You forgot to wipe when installing the JB CR. So the beginning gave you an unstable system.
And that's why you should install a fresh stock Rom with Odin.
After everything is working you might restore your GB backup (using a safe kernel like Philz 3.99).
I have to admit that I have difficulties to follow your steps.

[Q] What is STE_boot1.img? And where modem.bin?

Hi!
a few questions about the Parts of the I8190.
# Mount point fs device
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25
/efs ext4 /dev/block/mmcblk0p11
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
Where ist the MODEM points?????
And
In Stock ROM is included:
STE_boot1.img
STE_boot2.img
what is this??

Darkman said:
Hi!
a few questions about the Parts of the I8190.
# Mount point fs device
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25
/efs ext4 /dev/block/mmcblk0p11
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
Where ist the MODEM points?????
And
In Stock ROM is included:
STE_boot1.img
STE_boot2.img
what is this??
Click to expand...
Click to collapse
Hi Darkman
In this post HERE I have a Mobileodin.txt made by MobileOdin whit some data very interesting about S3 Mini partitions.
We see on it the modem is on partition 12.
ValenteL

Can't use sdcard0 with cwm-6.0.4.7 on mini2

Hi,
i'm a new user and I can't add post to correct thread so I try to begin a new thread here.
I installed cwm 6.0.4.7-jena on my phone and all install process is been completed correctly but on reboot from cwn shell / menu I can't mount sdcard0.
This error from recovery.log file:
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Volume /storage/sdcard0 is not idle, current state is 2
Error mounting /storage/sdcard0!
File recovery.fstab it seems correct:
Code:
# cat /etc//recovery.fstab
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p8 /boot emmc defaults defaults
/dev/block/mmcblk0p12 /recovery emmc defaults defaults
/dev/block/mmcblk0p16 /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p18 /data ext4 nosuid,nodev,noauto_da_alloc,barrier=1 wait,check,encryptable=footer,length=-16384
/dev/block/mmcblk0p17 /cache ext4 nosuid,nodev,barrier=1 wait,check
# vold managed volumes
/devices/platform/msm_sdcc.3/mmc_host auto vfat defaults voldmanaged=sdcard0:23,noemulatedsd,nonremovable
/devices/platform/msm_sdcc.1/mmc_host auto auto defaults voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/msm_hsusb_host.0 auto auto defaults voldmanaged=usbdisk:auto
# zRam (zramsize = 64 megabytes)
/dev/block/zram0 none swap defaults zramsize=67108864
If I use last OmniROM I see that sdcard0 is not usable and this confirm like for cwn that cwn-6.0.4.7 that there is a problem with sdcard0 (internal)
But If I use last cm-10.1 sdcard0 is correctly usable sdcard yet if on cwn it isn't possible mount it.
So probably is there a bug on cwm-6.0.4.7 and omni-4.4.2-20140202-jenad-HOMEMADE.
Could be relative to a wrong partition data ? I try to format it from cwm but I receive error and I can't donwgrade to previous cwm-6.0.3.2 (that it works with sdcard0) because there is a check on status of the sdcard0.
Any suggestions ?
Thanks in advance

Cannot format /data using TWRP 3.0.2[Solved]

I have a problem ... i'm trying to install Android MM using TWRP 3.0.2 but i can't because i can't format.
When i'm trying to format it shows this error: E:Unable to wipe '/data' -- unknown file system 'auto'
Unable to format to remove encrytion
Do i need to use another recovery?
Can someone tell me how to solve this?

I had the same problem, for some reason TWRP is unable to format encrypted partitions.
It can be solved using adb shell or using the terminal in TWRP (it's under the advanced tab).
To format the partition you have to know which device it is, to find out type this inside the terminal:
Code:
cat /etc/fstab
In my case the output is:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
Which means that my /data is on device /dev/block/mmcblk0p15 and uses the f2fs filesystem. If you're on f2fs then you can format the partition using
Code:
mkfs.f2fs /dev/block/mmcblkXXXX
if you're on ext4 then use
Code:
make_ext4fs /dev/block/mmcblkXXXX
Where XXXX is whatever is in your fstab. After this TWRP should be able to mount /data.

It worked,thank you!

Ok, now i have another problem ... every time i'm trying to install(flash) a zip with TWRP it's rebooting again in TWRP and can't install anything ... I had this problem in the past and i solved it but i forgot how i did that .. anyone knows?
Solved: i had to format my sd card.

penn.gwyn said:
I had the same problem, for some reason TWRP is unable to format encrypted partitions.
It can be solved using adb shell or using the terminal in TWRP (it's under the advanced tab).
To format the partition you have to know which device it is, to find out type this inside the terminal:
Code:
cat /etc/fstab
In my case the output is:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
Which means that my /data is on device /dev/block/mmcblk0p15 and uses the f2fs filesystem. If you're on f2fs then you can format the partition using
Code:
mkfs.f2fs /dev/block/mmcblkXXXX
if you're on ext4 then use
Code:
make_ext4fs /dev/block/mmcblkXXXX
Where XXXX is whatever is in your fstab. After this TWRP should be able to mount /data.
Click to expand...
Click to collapse
I did that but I am getting only this
/3rdmodem ext4 rw 0 0
/cache ext4 rw 0 0
/data f2fs rw 0 0
and so on
/dev/block/mmcblkXXXX is missing My TWRP version is 3.1.1-1-frd any help would be greatly appreciated.

penn.gwyn said:
I had the same problem, for some reason TWRP is unable to format encrypted partitions.
It can be solved using adb shell or using the terminal in TWRP (it's under the advanced tab).
To format the partition you have to know which device it is, to find out type this inside the terminal:
Code:
cat /etc/fstab
In my case the output is:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
Which means that my /data is on device /dev/block/mmcblk0p15 and uses the f2fs filesystem. If you're on f2fs then you can format the partition using
Code:
mkfs.f2fs /dev/block/mmcblkXXXX
if you're on ext4 then use
Code:
make_ext4fs /dev/block/mmcblkXXXX
Where XXXX is whatever is in your fstab. After this TWRP should be able to mount /data.
Click to expand...
Click to collapse
I tried this but now i cant fully install roms correctly. However i did this to more than just data

Hi, I tried this, but it's telling me : "need size of filesystem"
Do you have an idea of what's going wrong ? thanks
BTW : i have : /dev/block/dm-0 /data ext rw 0 0

hi I need help. Tell me "need size of filesystem"
Please help me.

help me /sbin/e2fsck -fp /dev/block/sda18 process ended with ERROR: 8
Cannot format /data using TWRP
and
make_ext4fs /dev/block/mmcblkXXXX
tell me "need size of filesystem"
help me please

dont know how i got into this. perhaps its the twrp 3.5.2_9 issue.
my parition names are long. ../soc.0/f9824900.sdhci/by-name/userdata
there is no data partition.
any way to get out of this? i dont have anything on the phone so i just want to get back to clean start.