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.

[Q] Splash screen lock up & mounting issues

Hi folks,
I rooted my GT-P7300 and upgraded it to Jellybean (cm-10-20120804-UNOFFICIAL-p5) without problem (besides picasa sync not working), I noticed there was a later version cm-10-20120808-UNOFFICIAL-p5 and that's when it all went wrong
Now my tab locks up at the samsung galaxy tab splash screen.
I can go in recovery mode (running CWM v5.5.0.4) - Odin seems to be OK as this is how I installed CWM recovery
Wiping dada gives me the following
--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 tried moving back to stock recovery, but it has problems from the get go :
-- updating application...
E:failed to mount /system (invalid argument)
E:install_application_for_customer:Cant mount /system
copy application failed
-- appling Multi-CSC...
E:failed to mount /system (invalid argument)
E:install_application_for_customer:Cant mount /system
E:failed to mount /system (invalid argument)
E:multi_csc:cant mount /system
I'm kindda stuck now. so if anyone has somme smart suggestion...

fixed
larryhk said:
Hi folks,
I rooted my GT-P7300 and upgraded it to Jellybean (cm-10-20120804-UNOFFICIAL-p5) without problem (besides picasa sync not working), I noticed there was a later version cm-10-20120808-UNOFFICIAL-p5 and that's when it all went wrong
Now my tab locks up at the samsung galaxy tab splash screen.
I can go in recovery mode (running CWM v5.5.0.4) - Odin seems to be OK as this is how I installed CWM recovery
Wiping dada gives me the following
--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 tried moving back to stock recovery, but it has problems from the get go :
-- updating application...
E:failed to mount /system (invalid argument)
E:install_application_for_customer:Cant mount /system
copy application failed
-- appling Multi-CSC...
E:failed to mount /system (invalid argument)
E:install_application_for_customer:Cant mount /system
E:failed to mount /system (invalid argument)
E:multi_csc:cant mount /system
I'm kindda stuck now. so if anyone has somme smart suggestion...
Click to expand...
Click to collapse
Fixed using Odin to flash a stock ROM

Same Problem!
Can u help me with a guide? I have GT-I9070P 16G. THANK'S!

CyanogenMod stuck on boot screen Xperia Z

I just installed CyanogenMod using the instructions from the CM wiki using the latest STABLE release.
When I booted my device, it was stuck on the CyanonMod loading screen (blue looping circle). I've wiped and reinstalled multiple times but cannot fix the problem.
I used the ClockWordMod "show log" command from the advanced menu, and got this:
I : Can't partition non-vfat: datamedia
I : Can't partition non-vfat: auto
I : Can't format unknown volume: /emmc
mount: mounting /dev/block/platform/msm/sdcc.1/by-name/userdata on /data failed: Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (Invalid argument)
The last line probably refers to my attempt to wipe the dalvik cache
I've noticed that CWM can't mount /data

Solved by installing TWRP recovery. Apparently CWM does not support encrypted partitions.

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

Help recover data after trying to encrypt CM13 (partially successful)

Hey, here's my situation:
Device: L90 405n
TWRP recovery
CM13
No SD-Card present
Tried to "encrypt phone" from the settings menu, the encryption step seemed to finish fine. However after the phone reboots and I enter my passcode, it hangs on the CM loader logo forever.
I thought this was a lost deal, especially after looking through the forums where the only recommendation is to wipe clean and reinstall.
And when I try to enter recovery, I can only get to the default "factory reset" and not TWRP recovery.
BUT
I can decrypt phone with a passcode I have
I can take screenshots on that passcode screen, so some things are working
After entering encryption passcode, and while the phone is showing CM logo, I can (briefly) see device as online using `adb devices` command, after about a minute
I can reboot into TWRP recovery by running `adb reboot recovery`
While in recovery, I'm able to see this in terminal:
Code:
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Failed to mount '/data/media/TWRP/.twrps'
MTP Enabled
Is there anything I could do to recover my data, or is it a lost cause?