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.

[Q] Can't mount /dev/block/mmcblk0p1

Ok, so my basic problem is my Verizon Tablet suddenly wouldn't get past the samsung screen on bootup. This happened suddenly without me changing anything at all. Just turned it on one day and BAM.
First guess was to boot into recovery and do a wipe data/factory reset.
When I do this it just goes to the first line "formatting /data..." and hangs for a long time. Eventually it prints this out
Code:
--Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard.android_secure!
Skipping format...
Data wipe complete.
I currently do NOT have my SD card inserted as I didn't want to to hurt it during all my messing about fixing this. FYI
I tried giving it its kernel again, and then tried other kernels i'v found around the forum with no change.
I used the Heimdall One-Click found here: http://forum.xda-developers.com/showthread.php?t=1323527 with still no change. But now that I'm running a stock kernel I get this error message as soon as I get into recovery
Code:
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
When I try a wipe data/factory reset I get this error
Code:
update application, please wait
E:Can't mount /dev/block/mmcblk0p2
(Invalid argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet, please use UI menu for format a
nd reboot actions.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
After doing a bunch of searching I found this page:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partition-on-internal-storage
Post number 7 is where the good info is. I have to upgrade my kernel to one that is rooted (like clockworkmod 5.0.2.7) so I can push the files to the correct spots. From the shell using ADB I type
Code:
parted /dev/block/mmcblk0
If I type print I get this:
Code:
Number Start End Size Type File system Flags
1 32.8kB 220MB 220MB primary ext4
2 220MB 1539MB 1319MB primary ext4
3 1539MB 1959MB 419MB primary fat16
when I type mkfs ext2 I get this error message
Error: File System was not cleanly unmounted! you should run e2fsck.
When I try to run e2fsck /dev/block/mmcblk0 It says this
The superblock could not be read or does not describe a correct ext filesystem.
So Im thinking these programs cannot edit a ext4 filesystem. Since the plan is to format them anyway, I'll delete and recreate them. I did see this on a page somewhere but I cant find that one for the life of me... sorry.
parted /dev/block/mmcblk0
rm 1
rm 2
None of that gives any error messages, but when I print it still shows the same file system, both partitions I just deleted are still there.
So maybe i'm just using parted wrong or it is bugging out? So i try fdisk
Code:
fdisk /dev/block/mmcblk0
p
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 26880 215008 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26881 187904 1288192 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
Partition 3 does not end on cylinder boundary
d (to delete partition)
Partition Number (1-4): 1
d
Partition Number (1-4): 2
p (to print partition table)
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
w (to write and exit)
So that seemed to work right, I I deleted partition 1 and 2 then looked at the table and they are gone and I wrote it. Now I go back into it and BAH, nothing has changed!
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 26880 215008 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26881 187904 1288192 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
Partition 3 does not end on cylinder boundary
I'v used many diffrent Kernels and tried a few different roms (not like its loading that far anyway)
The best I'v gotten it to do is when using Heimdall One-Click it will go past the samsung screen to the Verizon screen. I'v waited at that screen for a very long time with no change...
At this point, i'm stumped. I have no idea where to go next or if I'm even on the right track.
Any help would be greatly appreciated.
Thanks!

I was getting this exact same error on my AT&T Tab. I fixed it by flashing JJ7 from samfirmware.com. Here's what I did:
http://forum.xda-developers.com/showthread.php?t=1388470
check my post there. Obviously you'll have to use a firmware compatible with your VZW Tab, but it might work for ya.
Good Luck.

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.

Data recovery, how to mount messed up /data - Internal SD - sda25 in Recovery/ADB

Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.

白い熊 said:
Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
Click to expand...
Click to collapse
cant you simply wipe the affected partitions(except data of course)? then flash a rom?
have you tried;
mount /sys/block/sda25 /mydata
or
mount /dev/block/sda25 /mydata
or
adb
mount -o rw /dev/block/sda25/data /mydata
in both cases /mydata is just the mount point so I believe it can simply be called what ever you want including just /data
have you read:
https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
edit:
by any chance when you first flashed twrp, did you forget to format data?
if yes then flash back stock AP file(original phone's firmware) in Odin AP slot only and you should be good to go.( you shouldn't loose any files in internal storage)