Database Develop

[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.

Problem updating from one CyanogenMod nightly build to another.

Hi,
I'm currently running a nightly build of CyanogenMod 9 (9-20120618-NIGHTLY-p3) on my Galaxy Tab 10.1v, and I am trying to update to a newer build.
I've downloaded '9-29120712-NIGHTLY-p3' and saved the zip on my SD card. I reboot into clockwork mod recovery and, after clearing the cache, I try to apply the update zip. I also tried installing it using the ROM Manager, but it still fails. I don't understand why it won't work. Please help!!!!
This is log:
---------------
Starting recovery on Sun Jul 14 05:39:43 2019
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) 0
3 /boot emmc /dev/block/mmcblk0p3 (null) 0
4 /system ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /data ext4 /dev/block/mmcblk0p8 (null) 0
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard 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()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.koush.20120428.005633
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sat Apr 28 00:57:05 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=GT-P7510
ro.product.brand=samsung
ro.product.name=GT-P7510
ro.product.device=p4wifi
ro.product.board=p3
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p4wifi
ro.build.description=GT-P7510-user 3.2 HTJ85B UEKMM release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.2/HTJ85B/UEKMM:user/release-keys
ro.build.characteristics=tablet,nosdcard
ro.cm.device=p4wifi
ro.opengles.version=131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttys0
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-p4wifi-UNOFFICIAL
ro.modversion=9.0.0-RC0-p4wifi-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=2884143423F4557
ro.bootmode=unknown
ro.baseband=207_DB120215
ro.carrier=unknown
ro.bootloader=P7100BUKC8
ro.hardware=p3
ro.revision=14
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=stopping
sys.usb.state=adb
service.adb.root=1
ro.cwm.prefer_tar=true
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
a684e0f33ac9a63ea2f20f2798d687fa
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.8");
ui_print("July 13, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.8
July 13, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p8 on /data failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p5 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
-- Installing: /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
Finding update package...
I:Update location: /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "p3" || getprop("ro.build.product") == "p3"
assert failed: getprop("ro.product.device") == "p3" || getprop("ro.build.product") == "p3"
E:Error in /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip")
I:using /data/media, no /sdcard found.

OH YES! Don't worry, I figured it out. I needed to use the Recovery from here: http://droidbasement.com/db-blog/?p=2487, flashed with Odin.

use flash .zip from sdcard instead
BTW you can always flash it using the option "flash .zip from sdcard " insstead.It has never given me problems so far
p.s. I am a p4 user.

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.

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

Failed to change /cache file system from ext4 to f2fs

Hi guys... i want to ask whether anyone know how to solve this error,....i was succeed to change file system of /system and /data from ext4 to f2fs but i've got this error message after i'm trying to change file system of /cache by using twrp v2.8.70 :
E: mkfs.f2fs -t 1 /dev/block/mmcblk0p4 process ended with ERROR=255
E: Unable to wipe '/cache'
E: Error changing file system.
Thanks in advance for your attention