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.

Recover data from galaxy s plus with broken screen

Hello, I have a samsung galxy s plus with cm11 and a broken screen and i want to recover data from internal storage
when the phone is on i cannot access adb
in recovery i can use adb shell but don't know how to mount the internal storage.
I've tried several ways to mount but didn't work
here is my fstab
Code:
/dev/block/mmcblk0p16 /cache ext4 rw
/dev/block/mmcblk0p17 /data ext4 rw
/dev/block/mmcblk0p15 /system ext4 rw
and recovery.fstab
Code:
# 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 recoveryonly
/dev/block/mmcblk0p13 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p15 /system ext4 ro,errors=panic wait
/dev/block/mmcblk0p16 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p17 /data ext4 nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/devices/platform/msm_sdcc.2/mmc_host/mmc1 /storage/sdcard0 vfat defaults voldmanaged=sdcard0:28,nonremovable
/devices/platform/msm_sdcc.4/mmc_host/mmc2 /storage/sdcard1 vfat defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host.0 /storage/usbdisk auto defaults voldmanaged=usbdisk:auto
can anyone help?

Google Android commander. Turn your phone on and use that to get all your files.
Sent from my SM-N900T using Tapatalk

the problem is i've modified build.prop to try to enable MTP instead of UMS but now i have boot loop (it vibrates) and even after pushing the backup of build.prop on the phone, the phone still doesn't boot. I can only use the recovery.

anyone?, Im sure there is a way but I just can't find one

[RECOVERY] Unofficial TWRP 2.8.5.2 by Syhost (for 4G)

As we all know our device does not get official TWRP builds yet. Hopefully now that the sources have been released, it's just a matter of time before this happens, but meanwhile an unofficial TWRP 2.8.5.2 build has just been released by Syhost. More information is available on his blog (in Chinese). To install:
Download the file from Baidu
The password (posted publicly on Syhost's blog) is sa89.
The download is an .exe file. It appears to be just an installation script but I did not run it. Instead, I just unpacked it with WinRAR (right-click on the file).
Inside there is the file recovery.img, which can be flashed with standard methods. The way I do it:
Code:
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery recovery.img
Alternatively, if you just want to test it without replacing your current recovery:
Code:
adb reboot bootloader
fastboot boot recovery.img
The interface is all in Chinese. If you're comfortable with that language, you can stop here. However, what I did was:
Keep the kernel from Syhost's version.
Replace the RAM Disk image with files from the stock TWRP for another device: I used openrecovery-twrp-2.8.5.2-mako.img, as I already had the file.
Integrate the TWRP Materialised Play theme in the appropriate resolution (720x1280). The file is 2850_v1_720_play.zip and you'll also want to replace the curtain.jpg file with one of the splash screens from here: splashes_720.zip.
Delete the following files:
Code:
/fstab.mako
/ueventd.mako.rc
Copy over the following files from Syhost's RAM Disk image:
Code:
/default.prop
/file_contexts
/init.rc
/init.recovery.qcom.rc
/property_contexts
/seapp_contexts
/selinux_version
/sepolicy
/service_contexts
/ueventd.rc
Replace /etc/recovery.fstab with the following contents:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:radio_efs_file:s0 wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /radio emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/mmcblk1p1 /external_sd vfat rw,noatime,nodev,noexec,nosuid,uid=1000,gid=1015,fmask=0002,dmask=0002,utf8 defaults
/dev/block/sda1 /usbdisk vfat rw,noatime,nodev,noexec,nosuid,uid=1000,gid=1015,fmask=0002,dmask=0002,utf8 defaults
Replace /etc/twrp.fstab with the following contents:
Code:
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/external_sd vfat /dev/block/mmcblk1p1 flags=display="SD Card";storage;wipeingui;removable
/usbdisk vfat /dev/block/sda1 flags=display="USB Disk";storage;removable
.
I don't think I can post the resulting image file, as none of this is my work and I don't have the original authors' permission but if you follow the above instructions, you'll end up with a working TWRP 2.8.5.2 recovery image with the English interface that also looks great thanks to the excellent TWRP Materialised theme. Haven't had the chance to test it extensively yet but everything appears to work just great at this point. Screenshots - before and after:

That's really great find. And helpful tip. Cool.
Btw, I do think you can share the resulting TWRP, in English and themed, by simply crediting the original dev/page for the find. Without credit, it won't be cool for sure, but with credit, it's good.

MTP Status
MTP does not appear to work in the modified version but neither does it work for me in the original, unmodified one, even if the description on Syhost's blog seems to suggest it should. I don't really use this function so I'll leave it like that at the moment, as it's not immediately obvious what's going on. If someone wants to take over from here, the following might be useful:
Logcat:
Code:
MtpServer::run fd: 16
E:request read returned -1, errno: 22, exiting MtpServer::run loop
TWRP Source, mtp/mtp_MtpServer.cpp:55
Code:
int fd = open(mtp_device, O_RDWR);
TWRP Source, mtp/mtp_MtpServer.cpp:47
Code:
#ifdef USB_MTP_DEVICE
#define STRINGIFY(x) #x
#define EXPAND(x) STRINGIFY(x)
const char* mtp_device = EXPAND(USB_MTP_DEVICE);
MTPI("Using '%s' for MTP device.\n", EXPAND(USB_MTP_DEVICE));
#else
const char* mtp_device = "/dev/mtp_usb";
#endif
Android Source, include/errno.h:55
Code:
#define EINVAL 22 /* Invalid argument */

itskapil said:
That's really great find. And helpful tip. Cool.
Btw, I do think you can share the resulting TWRP, in English and themed, by simply crediting the original dev/page for the find. Without credit, it won't be cool for sure, but with credit, it's good.
Click to expand...
Click to collapse
Thanks! I've PMed Syhost and will upload the image if he's OK with it.

Aqq123 said:
Thanks! I've PMed Syhost and will upload the image if he's OK with it.
Click to expand...
Click to collapse
:good:

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.