Related
I've searched through the all the XS forums and Backup & Restore within CWM Recovery seems to work for everyone, on all the different ICS Based Kernels with Recovery except for me.
I get the error below whenever I try to format my /system partition through recovery; as the Restore tries to format the partition before restoring to it by restores always fail and I'm left with a /system partition that I can't mount. Only through restoring through Flashtool can I get the phone to boot again. Has anyone seen this before or have any idea what the problem is? Someone having a similar issue on the Samsung Galaxy Player had a similar issue and it was down to a corrupt partition table Galaxy Player Problem
Error From Recovery
Code:
Formatting /system...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /system!
Error mounting /system!
My Partition Table (if it's any use)
Code:
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders, total 62324736 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 4096 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 4097 5120 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 8192 49151 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 49152 61071359 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 50176 51199 512 46 Unknown
/dev/block/mmcblk0p6 53248 59391 3072 4a Unknown
/dev/block/mmcblk0p7 61440 67583 3072 4b Unknown
/dev/block/mmcblk0p8 69632 75775 3072 58 Unknown
/dev/block/mmcblk0p9 77824 88063 5120 70 Unknown
/dev/block/mmcblk0p10 90112 106495 8192 83 Linux
/dev/block/mmcblk0p11 106496 139263 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 139264 2236415 1048576 83 Linux
/dev/block/mmcblk0p13 2236416 2748415 256000 83 Linux
/dev/block/mmcblk0p14 2748416 6942719 2097152 83 Linux
/dev/block/mmcblk0p15 6942720 61071359 27064320 c Win95 FAT32 (LBA)
I was sondering if anyone had any suggestions, or could at least post their Partition Table to see if I need to sort mine out
(From ADB:
fdisk /dev/block/mmcblk0
U,
P
Then paste it here)
Cheers,
Andy
hello Andy..
mine partition table is just the same with you. but i can restore my backup (which include /system backup) just fine.whick kernel are you on?
It happened to me once. I formated data partition and it worked, don't know why
I've had the same problems with the FXP kernels ( both CM9 & CM10) ,Advanced Stock and SSpeed. I'm starting to wonder if the memory is actually damaged.
It's hit and miss as to which partitions it'll let me format, system and cache almost always fail, data sometimes works,but then frequently won't mount afterwards.
Sent from my LT26i using xda premium
Hi!
I've the same problems.
My phone has a srange behavior... Often can't ormat partitions, can't mount them, but after few retries i can manage it. And it's totally random..
You think is a software memory or a damaged memory ?
I never can't restore a nandroid backup because it give me an error restoring system partition.
Any ideas ?
mrscope said:
Hi!
I've the same problems.
My phone has a srange behavior... Often can't ormat partitions, can't mount them, but after few retries i can manage it. And it's totally random..
You think is a software memory or a damaged memory ?
I never can't restore a nandroid backup because it give me an error restoring system partition.
Any ideas ?
Click to expand...
Click to collapse
I've found a sort of work around. It appears to only be recoveries that use an ICS kernel that give me issues, so I loaded Doom's Advance Stock GB Kernel onto the phone and the recovery on that works flawlessly everytime. (it also has better features than regular CWM Recovery)
All the ICS kernel's that I tried will always successfully back up and restore the boot partition, so I use them to do that. Then restore DoomKernel (advanced restore, restore boot) then do all my backups, restores, and flashing with DooMRecovery. Then you can tidy everything up by moving the ICS Kernel BootPartion image into the DooMRecovery system/data backup folder, then insert the boot.img line from the checksum MD5 file at the start of the ICS MD5 file into the DooMRec MD5 file. (so you have all the correct files in the same folder, with the correct MD5 sum for each of the images in the folder). Then you can do a restore via DoomRecovery if you ever need to.
I grant you it's a bit messy and if the timestamps don't work properly a little confusing, but it does do the job, and it means you can easily swap between ROM's on the go.
sixdaysandy said:
I've found a sort of work around. It appears to only be recoveries that use an ICS kernel that give me issues, so I loaded Doom's Advance Stock GB Kernel onto the phone and the recovery on that works flawlessly everytime. (it also has better features than regular CWM Recovery)
All the ICS kernel's that I tried will always successfully back up and restore the boot partition, so I use them to do that. Then restore DoomKernel (advanced restore, restore boot) then do all my backups, restores, and flashing with DooMRecovery. Then you can tidy everything up by moving the ICS Kernel BootPartion image into the DooMRecovery system/data backup folder, then insert the boot.img line from the checksum MD5 file at the start of the ICS MD5 file into the DooMRec MD5 file. (so you have all the correct files in the same folder, with the correct MD5 sum for each of the images in the folder). Then you can do a restore via DoomRecovery if you ever need to.
I grant you it's a bit messy and if the timestamps don't work properly a little confusing, but it does do the job, and it means you can easily swap between ROM's on the go.
Click to expand...
Click to collapse
I had the same thing last week, couldn't restore a backup form CWM (on Xperia S/FXP CM10 207). Formatting cache and system 'manually' in CWM also failed. /data was OK.
I ended up formatting from adb (mkfs.ext2 -T ext4 /dev.... ) and mounting the partitions through CWM. Then I untarred the different partitions of my CWM-backup and everything was fine.
Is this a problem of CWM or my phone, or ...?
Thanks
Frank
I am having the exact same issue. I cannot -ever- format the cache . So every restore attempt ends in error.
I have rooted stock .55 , with locked bootloader.
Did anybody ever found a fix for this.
I have read the other recovery option but it requires kernel changing and possibly unlocked bootloader.
I created a thread with my issues, here
http://forum.xda-developers.com/showthread.php?t=2163141
e.g which partition is the dalvik cache? mmcblk0p*?
i know mmcblk0p18 is emmc, and mmcblk0p12 is system or cache i think. I ask this because a while ago, a battery outage during a flash has corrupted a few partitions such that when i do a certain amount of activity on the phone, it locks up, all apps FC and no amount of reboots fix it. I removed and formatted partitions in the above locations and now i can freely restore my backups (they used to fail on flashing system probably due to corrupted partition there). I still get FC here and there, only when i haven't used the phone in a while (enters deep sleep) and whatsapp/messaging also FC so it's a serious problem which affects my daily life.
The only important place i haven't removed and wiped is the dalvik cache, so i specifically need the location to that.
Thanks!
I'm pretty sure Ive read that the Dalvik cache is part of the normal cache partition.
dblades said:
I'm pretty sure Ive read that the Dalvik cache is part of the normal cache partition.
Click to expand...
Click to collapse
I don't think so. I think it's in the /userdata/ partition. Anyways, i found a comprehensive list here: http://pastebin.com/hxugnyQC
There is no partition specifically designated for dalvik cache. Depending on your ROM/setup, dalvik cache can be in many places. Typically system apps (those in /system/app) have their dalvik cached at /cache/dalvik-cache, and user apps (those in /data/app and /data/app-private) have it in /data/dalvik-cache. If you have apps2sd, there could be another one at /sd-ext/dalvik-cache. There could be even more, depending on your ROM/setup.
I have the complete Atrix partition map saved on my computer but have no access to it right now since I'm on my phone.
EDIT: Here you go. Based on http://forum.xda-developers.com/showthread.php?p=12687720 and my own research.
Code:
mmcblk0p1 ? 3.5 MB
mmcblk0p2 ? 512 kB
mmcblk0p3 /pds 2 MB
mmcblk0p4 <extended> -
mmcblk0p5 /signature 1 MB
mmcblk0p6 ? 512 kB
mmcblk0p7 /misc 512 kB
mmcblk0p8 /logo 1 MB
mmcblk0p9 /kernelpanic 2 MB
mmcblk0p10 /recovery 8 MB
mmcblk0p11 /boot 8 MB
mmcblk0p12 /system 320 MB
mmcblk0p13 /osh 768 MB
mmcblk0p14 /cdrom 20 MB
mmcblk0p15 /cache 640 MB
mmcblk0p16 /data 2 GB
mmcblk0p17 /preinstall 345 MB
mmcblk0p18 /emmc ~11 GB
I've been running Energy_2.27.2012.Stock.Kernel.Amaze on my TMo Amaze 4g almost since I acquired it about 22 months ago. It's rooted and hboot is set with S-on. I still have the TMo account app on it, and lately it's been reminding me to reboot every so often. Odd, since I've always done it like I would a PC, etc. I remember the first notice a couple of months ago, restarted and ultimately had to go through recovery to bring everything back. I've ignored the posts from TMo since then, but I restarted the phone last week as a regular practice and it never came up. I went to recovery, but the message I get is this: unable to mount \internal_sd_card. No recovery sequence I tried has worked. Everything on my external sd is backed up. If anyone can give me something to work with, I would really appreciate it.
I'm relegated to my old HTC HD2 running AOKP/Tytung ICS 4.0.4. I wish it was 4G.
Which recovery ye using
Sent from my Amaze using xda app-developers app
daorderdillon said:
Which recovery ye using
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
I've tried 3: 4ext, TWRP, and CWM. I'm using CWM at the moment, but was on 4ext when this debacle took place. Thanks for asking!
More information:
When booting into recovery, the initial information that's returned is:
CWM Recovery v5.5.0.4 Xboarders Ruby Source
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When attempting to mount the /internal_sdcard, the return message is:
Error mounting /internal_sdcard!
All other functions like wiping *whatever*, backup and restore, install zip from sdcard, will fail.
Format it..
jauhien said:
Format it..
Click to expand...
Click to collapse
Tried to, but can't...because it's not mountable. I've run Ruby Superwipe as well, only to get the same results regarding inaccessibility to the same directories mentioned earlier. If you know another way, please, let me know.
daorderdillon said:
Which recovery ye using
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Just a heads-up, daorderdillon: I switched to the latest TWRP because what I read about it looked promising. It didn't work, but it sure looks good!
:silly:
Try mounting and formatting with help of TWRP..
jauhien said:
Try mounting and formatting with help of TWRP..
Click to expand...
Click to collapse
Have the same issue. Something happened while installing a custom ROM wia CWM. I'm on a Galaxy Note GT-N7100...any help would be appreciated! I'd love to go back to the stock ROM but flashing with Odin seems to work but then the phone says that "something went wrong with the update process"...and CWM & TWRP & Stock recovery all say the same thing: Can't mount internal or external SD's...what could it be?
jauhien said:
Try mounting and formatting with help of TWRP..
Click to expand...
Click to collapse
You might notice the message just before yours . I switched back to the latest TWRP and tried that. Everything regarding formatting and wiping I've read about and attempted...with no luck at all. As they say, been there, done that, bought the t-shirt. What about a heavy magnet?
jdh2000 said:
I've been running Energy_2.27.2012.Stock.Kernel.Amaze on my TMo Amaze 4g almost since I acquired it about 22 months ago. It's rooted and hboot is set with S-on. I still have the TMo account app on it, and lately it's been reminding me to reboot every so often. Odd, since I've always done it like I would a PC, etc. I remember the first notice a couple of months ago, restarted and ultimately had to go through recovery to bring everything back. I've ignored the posts from TMo since then, but I restarted the phone last week as a regular practice and it never came up. I went to recovery, but the message I get is this: unable to mount \internal_sd_card. No recovery sequence I tried has worked. Everything on my external sd is backed up. If anyone can give me something to work with, I would really appreciate it.
I'm relegated to my old HTC HD2 running AOKP/Tytung ICS 4.0.4. I wish it was 4G.
Click to expand...
Click to collapse
NEW INFORMATION!!! I really hope this helps you help me.
I got to fooling around with adb.exe contained in Hasoon 2000's latest All-in-one kit (v5.1), and with my languishing HTC Amaze 4G connected and booted into recovery, I started a shell session. Low and behold, I ran a /ls -a -l command and I saw this:
See attached JPEG...
I was leery at first, so I changed directories to the sdcard (the external one), and saw my files there. Sooo, this must be the root directory, or the infamous INTERNAL_SDCARD. If ANYONE has a suggestion on what I can do from here to restore this phone, give me a shout.
I'm currently running TWRP v.2.3.3.0 for recovery. I like it...
Ok, man, seems I've been out of a similar "merde" just now. After having tapped by mistake onto the "factory reset" in the bootloader I could no longer mount my internal_sdcard (4ext would say "error mounting internal_sdcard"). I thought that I had corrupted partition table. So I decided to check fstab. The internal sdcard on my device was supposed to be mounted through
Code:
/dev/block/mmcblk0p36
Then I've checked it with the fdisk:
Code:
fdisk -l /dev/block/mmcblk0p36
Disk mmcblk0p36: 10.4 GB, 10468982784 bytes
4 heads, 16 sectors/track, 319488 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
It could see the disk but could not mount it:
Code:
mount mmcblk0p36
mount: mounting /dev/block/mmcblk0p36 on /internal_sdcard failed: Invalid argument
Next you can either try to format and partition the disk manually or use "format sdcard" function from a recovery.
Finally I was able to mount and use the internal sdcard.
zandgreen said:
Ok, man, seems I've been out of a similar "merde" just now. After having tapped by mistake onto the "factory reset" in the bootloader I could no longer mount my internal_sdcard (4ext would say "error mounting internal_sdcard"). I thought that I had corrupted partition table. So I decided to check fstab. The internal sdcard on my device was supposed to be mounted through
Code:
/dev/block/mmcblk0p36
Then I've checked it with the fdisk:
Code:
fdisk -l /dev/block/mmcblk0p36
Disk mmcblk0p36: 10.4 GB, 10468982784 bytes
4 heads, 16 sectors/track, 319488 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
It could see the disk but could not mount it:
Code:
mount mmcblk0p36
mount: mounting /dev/block/mmcblk0p36 on /internal_sdcard failed: Invalid argument
Next you can either try to format and partition the disk manually or use "format sdcard" function from a recovery.
Finally I was able to mount and use the internal sdcard.
Click to expand...
Click to collapse
This is outstanding. One issue I came across was finding the actual volume name that I needed to mount. The /dev/block directory shows this:
/dev/block # ←[6nls -l
ls -l
brw------- 1 root root 7, 0 Jan 2 00:00 loop0
brw------- 1 root root 7, 1 Jan 2 00:00 loop1
brw------- 1 root root 7, 2 Jan 2 00:00 loop2
brw------- 1 root root 7, 3 Jan 2 00:00 loop3
brw------- 1 root root 7, 4 Jan 2 00:00 loop4
brw------- 1 root root 7, 5 Jan 2 00:00 loop5
brw------- 1 root root 7, 6 Jan 2 00:00 loop6
brw------- 1 root root 7, 7 Jan 2 00:00 loop7
brw------- 1 root root 179, 0 Jan 2 00:00 mmcblk0
brw------- 1 root root 179, 1 Jan 2 00:00 mmcblk0p1
brw------- 1 root root 179, 10 Jan 2 00:00 mmcblk0p10
brw------- 1 root root 179, 11 Jan 2 00:00 mmcblk0p11
brw------- 1 root root 179, 12 Jan 2 00:00 mmcblk0p12
brw------- 1 root root 179, 13 Jan 2 00:00 mmcblk0p13
brw------- 1 root root 179, 14 Jan 2 00:00 mmcblk0p14
brw------- 1 root root 179, 15 Jan 2 00:00 mmcblk0p15
brw------- 1 root root 179, 16 Jan 2 00:00 mmcblk0p16
brw------- 1 root root 179, 17 Jan 2 00:00 mmcblk0p17
brw------- 1 root root 179, 18 Jan 2 00:00 mmcblk0p18
brw------- 1 root root 179, 19 Jan 2 00:00 mmcblk0p19
brw------- 1 root root 179, 2 Jan 2 00:00 mmcblk0p2
brw------- 1 root root 179, 20 Jan 2 00:00 mmcblk0p20
brw------- 1 root root 179, 21 Jan 2 00:00 mmcblk0p21
brw------- 1 root root 179, 22 Jan 2 00:00 mmcblk0p22
brw------- 1 root root 179, 23 Jan 2 00:00 mmcblk0p23
brw------- 1 root root 179, 24 Jan 2 00:00 mmcblk0p24
brw------- 1 root root 179, 25 Jan 2 00:00 mmcblk0p25
brw------- 1 root root 179, 26 Jan 2 00:00 mmcblk0p26
brw------- 1 root root 179, 3 Jan 2 00:00 mmcblk0p3
brw------- 1 root root 179, 4 Jan 2 00:00 mmcblk0p4
brw------- 1 root root 179, 5 Jan 2 00:00 mmcblk0p5
brw------- 1 root root 179, 6 Jan 2 00:00 mmcblk0p6
brw------- 1 root root 179, 7 Jan 2 00:00 mmcblk0p7
brw------- 1 root root 179, 8 Jan 2 00:00 mmcblk0p8
brw------- 1 root root 179, 9 Jan 2 00:00 mmcblk0p9
brw------- 1 root root 179, 64 Jan 2 00:00 mmcblk1
brw------- 1 root root 179, 65 Jan 2 00:00 mmcblk1p1
drwxr-xr-x 4 root root 80 Jan 2 00:00 platform
However, catting fstab gave me the actual volume name: mmcblk1p1
What the heck are the rest of those volumes listed?
AND, I haven't taken the steps to correct the mounting issue, yet, but you will know the outcome.
Again, OUTSTANDING reply. I will keep you, and everyone up to date.
jdh2000 said:
What the heck are the rest of those volumes listed?
Click to expand...
Click to collapse
Code:
cat /proc/emmc
Good luck
Having the same problem as you are. I flashed the PAC MAN ROM'S newest version, everything worked fine, shut it off and to my surprise, this happened in the morning, it's super weird.
broker32 said:
Having the same problem as you are. I flashed the PAC MAN ROM'S newest version, everything worked fine, shut it off and to my surprise, this happened in the morning, it's super weird.
Click to expand...
Click to collapse
Have you been able to re-flash, or recover? If you did, let me know how you did it.
I'm still soft-bricked, and I can't get the internal memory partition to format. I'm sill exploring solutions available from the adb shell. It's allowed me to really brush up on my linux/unix commands; however, I don't think I'm close to any recovery...yet.
If I get a break, you'll know it. I plan to document the whole thing right here.
Have you been able to re-flash, or recover? If you did, let me know how you did it.
I'm still soft-bricked, and I can't get the internal memory partition to format. I'm sill exploring solutions available from the adb shell. It's allowed me to really brush up on my linux/unix commands; however, I don't think I'm close to any recovery...yet.
If I get a break, you'll know it. I plan to document the whole thing right here.
Click to expand...
Click to collapse
I tried mounting system, cache, internal/external cards, flashing the latest ruu.. everything and it's next to impossible, hell even USB won't work.
Much obliged.
broker32 said:
I tried mounting system, cache, internal/external cards, flashing the latest ruu.. everything and it's next to impossible, hell even USB won't work.
Much obliged.
Click to expand...
Click to collapse
Can you "see" the directory tree when using adb shell? Or, can you get to your recovery so you can initiate a shell session?
That's one of the promising developments I've encountered since I posted this plea for help. If I can use the command-line to format I think I'll be able to flash another image and get back to square one.
At this point, reassigning rights (CHMOD) has NOT worked for some reason, but I'm continuing to try this one directory at a time. I hope to hear about your own success.
jdh2000:
assuming that
you have your internal sdcard backed up
you can boot into a recovery
you can access the root using 'adb shell'
the mounting point of your internal sdcard is /dev/block/mmcblk1p1
what is the result of
Code:
dd if=/dev/zero of /dev/block/mmcblk1p1
run from 'adb shell'? (This is supposed to overwrite your partition with null bytes, thus formatting it).
P.S. it's not quite clear whether you have tried formatting the internal card from the 4ext recovery (Wipe/Format - format sdcard) or not.
zandgreen said:
jdh2000:
assuming that
you have your internal sdcard backed up
you can boot into a recovery
you can access the root using 'adb shell'
the mounting point of your internal sdcard is /dev/block/mmcblk1p1
what is the result of
Code:
dd if=/dev/zero of /dev/block/mmcblk1p1
run from 'adb shell'? (This is supposed to overwrite your partition with null bytes, thus formatting it).
P.S. it's not quite clear whether you have tried formatting the internal card from the 4ext recovery (Wipe/Format - format sdcard) or not.
Click to expand...
Click to collapse
I'll answer the P.S. question first:
I had 4ext recovery on from the beginning of this issue. I used the Wipe/Format feature within that recovery and was NOT successful. The key directories were not mountable. It is the same with TWRP (v2.3.3.0): those directories are not mountable. As you know, if I can't mount them, then I can't format them/wipe them. When I'm in the adb shell, I CAN see them, cd to them, ls to them. They contain nothing.
Now for the results of the copy/conversion command dd:
----------------------------------------------------------------------------------------
~ # ←[6ndd if=/dev/zero of /dev/block/mmcblk1p1
dd if=/dev/zero of /dev/block/mmcblk1p1
BusyBox v1.20.1-cm7 bionic (2012-05-28 03:56 +0200) multi-call binary.
Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
[seek=N] [conv=notrunc|noerror|sync|fsync]
Copy a file with converting and formatting
if=FILE Read from FILE instead of stdin
of=FILE Write to FILE instead of stdout
bs=N Read and write N bytes at a time
ibs=N Read N bytes at a time
obs=N Write N bytes at a time
count=N Copy only N input blocks
skip=N Skip N input blocks
seek=N Skip N output blocks
conv=notrunc Don't truncate output file
conv=noerror Continue after read errors
conv=sync Pad blocks with zeros
conv=fsync Physically write data out before finishing
Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)
----------------------------------------------------------------------------------------
Does it matter that BusyBox is utilized when the command dd is used? It appears as if BusyBox is in control of the logic.
Thanks for your continued inquiries. Hope to hear back soon.
Oops!
I overlooked part of your requirements: you asked whether "the mounting point of your internal sdcard is /dev/block/mmcblk1p1"
How would I tell?
Hi,
first i want to say i viewed and searched a lot of threads, and am posting here just because i'm not sure which way to follow.
I installed mateo111's 10.2 custom rom, and after a few days it started acting weird, slow and stuff... when i rebooted it, it stuck at cm logo and it stayed like that for 2 days now. When i enter cwm i get a lot of errors, can't mount anything basically.
It can't mount cache, data, system, sd card, it can only mount extsd. It also can't show any recovery logs, and thus i can't format any of it. So i'm guessing some partition got messed up or something, but i'm not that experienced to be sure. I tried restoring backup but it can't restore anything except boot.
What are my options? I can't flash any roms, i can only use adb sideload, so any advice is very welcome and i will be most thankful if someone helps me in this matter.
Thanks in advance.
Bokee88 said:
Hi,
first i want to say i viewed and searched a lot of threads, and am posting here just because i'm not sure which way to follow.
I installed mateo111's 10.2 custom rom, and after a few days it started acting weird, slow and stuff... when i rebooted it, it stuck at cm logo and it stayed like that for 2 days now. When i enter cwm i get a lot of errors, can't mount anything basically.
It can't mount cache, data, system, sd card, it can only mount extsd. It also can't show any recovery logs, and thus i can't format any of it. So i'm guessing some partition got messed up or something, but i'm not that experienced to be sure. I tried restoring backup but it can't restore anything except boot.
What are my options? I can't flash any roms, i can only use adb sideload, so any advice is very welcome and i will be most thankful if someone helps me in this matter.
Thanks in advance.
Click to expand...
Click to collapse
You don't need to mount partition to format it. Did you try to format system and data in CWM? Did it get any error log? If even CWM cannot format your partition, it may be a hardware problem.
If you can boot into CWM you can use adb to push rom file to external sdcard and install it.
> adb push your-rom.zip /external_sd/
Thank you for your response. ADB doesn't recognize my device, probably because i've managed to format system before. Because i'm a newbie, i tried pushing the file through adb nonetheless, but it displays error: device not found.
Is the only solution for this going back to stock?
system and cache can be formatted, data and sdcard can't (error mounting /data!, Skipping format... Done.). I've tried it all and after that tried installing rom and gapps, it appears as it's a succesfull install and when i reboot i'm stuck at static LG logo.
Bokee88 said:
Thank you for your response. ADB doesn't recognize my device, probably because i've managed to format system before. Because i'm a newbie, i tried pushing the file through adb nonetheless, but it displays error: device not found.
Is the only solution for this going back to stock?
system and cache can be formatted, data and sdcard can't (error mounting /data!, Skipping format... Done.). I've tried it all and after that tried installing rom and gapps, it appears as it's a succesfull install and when i reboot i'm stuck at static LG logo.
Click to expand...
Click to collapse
It's ok that you cannot mount /data because in some CWM that patition cannot be mounted. Please try to wipe dalvik cache in advanced menu. You need to do this everytime you install new rom.
artit said:
It's ok that you cannot mount /data because in some CWM that patition cannot be mounted. Please try to wipe dalvik cache in advanced menu. You need to do this everytime you install new rom.
Click to expand...
Click to collapse
When i try to wipe dalvik nothing happens, the menu just reloads quickly, no log, nothing.
Regarding data, i said "mount" because i'm getting errors when i try to wipe data "can't mount data". Also, when i try to restore a cwm backup i can only restore boot, other parts - data, system, cache - can't be mounted "error mounting /system" for example.
edit: could this have to do with my previous rom's feature that removes internal memory simulation? * disabled internal sdcard emulation: http://forum.xda-developers.com/showpost.php?p=43382611&postcount=2
I took out a log, this is what i get after trying to hard reset from cwm:
E:can't mount /cache/recovery/log
E:can't mount /cache/recovery/last_log
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't partition non-vfat : datamedia
I:Can't format unknown volume: /emmc
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (Invalid argument)
Bokee88 said:
I took out a log, this is what i get after trying to hard reset from cwm:
E:can't mount /cache/recovery/log
E:can't mount /cache/recovery/last_log
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't partition non-vfat : datamedia
I:Can't format unknown volume: /emmc
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (Invalid argument)
Click to expand...
Click to collapse
I'm not sure maybe your CWM is damaged. Please try to boot into CWM then issue following commands
Code:
> adb shell
# cat /proc/partitions
You should get some output like
Code:
major minor #blocks name
179 0 3784704 mmcblk0
179 1 384 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 20480 mmcblk0p8
179 9 512 mmcblk0p9
179 10 1024000 mmcblk0p10
179 11 2482176 mmcblk0p11
179 12 204800 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 16384 mmcblk0p14
179 40 2048 mmcblk0boot1
179 20 2048 mmcblk0boot0
179 60 7798784 mmcblk1
179 61 7797760 mmcblk1p1
Then check your mount point
Code:
# mount
This is my output
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata on /data type ext4 (rw,nodev,noatime,nodiratime,resuid=1000,user_xattr,barrier=1,data=ordered)
If there're something broken, please try to flash new recovery. If that still don't help, try to flash stock rom or recovery your phone by LG tool.
artit said:
I'm not sure maybe your CWM is damaged. Please try to boot into CWM then issue following commands
Code:
> adb shell
# cat /proc/partitions
You should get some output like
Code:
major minor #blocks name
179 0 3784704 mmcblk0
179 1 384 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 20480 mmcblk0p8
179 9 512 mmcblk0p9
179 10 1024000 mmcblk0p10
179 11 2482176 mmcblk0p11
179 12 204800 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 16384 mmcblk0p14
179 40 2048 mmcblk0boot1
179 20 2048 mmcblk0boot0
179 60 7798784 mmcblk1
179 61 7797760 mmcblk1p1
Then check your mount point
Code:
# mount
This is my output
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata on /data type ext4 (rw,nodev,noatime,nodiratime,resuid=1000,user_xattr,barrier=1,data=ordered)
If there're something broken, please try to flash new recovery. If that still don't help, try to flash stock rom or recovery your phone by LG tool.
Click to expand...
Click to collapse
As i said, i cannot use ADB because i formatted system, hoping to flash a new ROM, which i later discovered to be mission impossible.
I have tried troubleshooting through LG mobile tools, it upgraded to 50% and then just stopped with an error. Also, installed fastboot and tried flashing a KDZ, also stopped at 50%.
Bokee88 said:
I have tried troubleshooting through LG mobile tools, it upgraded to 50% and then just stopped with an error. Also, installed fastboot and tried flashing a KDZ, also stopped at 50%.
Click to expand...
Click to collapse
This sounds like a hardware failure
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
This sounds like a hardware failure
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the end you were right, i returned the device to my operator and fortunately, they couldn't see that i rooted it and played with it for over a year now so they replaced the hardware in the phone, not saying what it was that died (i'm thinking the internal memory).
Anyway, thanks for your help!
[Troubleshoot] Android Phone in Read Only mode - "Internal SD" is unmounted/damaged
Android model: VKWorld VK700 old version, 1GB RAM/8GB ROM, MTK6582, running Android 4.4.2 (Kernel Version 3.4.67 [email protected]#1), rooted.
Problem: Phone works albeit very unstable. Looks to be locked in read-only mode. The internal storage was 1GB for apps, rest for the other various stuff including user data. Now phone sees only that 1GB, claims that "SD Card is damaged". ES Explorer claims "SD Card is unmounted". Can't mount it of course. I've put an external SD and that appears also to be Read only, but not sure about that (file explorers simply say copy failed).
Cause: Used an app (HKPHONEROMEDITTOR2014) that increases the partition size for the apps. Unfortunately it was set up for 4GB phones so it probably messed up my partitions/mount points, ebr's or something.
Tried:
Hardware reset/recovery does nothing, it says deleting stuff for 2-3secs, reboots, nothing changes. Uninstalling apps, making whatever changes and rebooting, phone again has all the same apps, needs the same updates etc. Copying files via ADB to say /sbin is successful. Reboot and the files are gone. Of course the same goes for apps. Install app, app works, reboot phone, app is gone.
Tried flashing the phone with various ROMS, from stock to custom, with various recovery images. Used two methods:
1) Via SPMultiPortFlash and .bin images, flashing fails at the end producing a CHKSUM(EBR1) ERROR.
2) Via SP_Flashtool and .txt scatter. Flashing is reported success. The progress is correct, everything should be ok. However boot into the phone, nothing changes. Selected Firmware upgrade, Format and download and download only, doesn't make a difference. Selected format flash, reported success. Again, nothing changes.
Installed busybox, checked parted and fdisk. Parted doesn't work (can't have partition outside the disk error). Checked fdisk, internal flash size is reported correct, two blocks start before they end
Code:
/dev/block/mmcblk0p1 Start 65: End 64
/dev/block/mmcblk0p6 Start 260033: End 64
however the exact scheme is followed by a stock VK700pro (same processor / ROM size) so I don't think that's the problem.
Included below are whatever I could think that might be of other help to troubleshoot.
Can anybody give me a hand? I am way beyond my waters here, I had zero knowledge about flashing / linux / rooting etc up until yesterday and my mind is all mush right now from all the reading...
vold.fstab
Code:
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
dev_mount usbotg /mnt/usbotg auto /devices/platform/mt_usb
vold contents:
Code:
brw------- root root 179,0
brw------- root root 179,1
brw------- root root 179,2
brw------- root root 179,3
brw------- root root 179,4
brw------- root root 179,5
brw------- root root 179,6
brw------- root root 179,7
brw------- root root 179,8
brw------- root root 179,96
brw------- root root 179,97
/proc/partitions
Code:
7 0 1254 loop0
253 0 524288 zram0
179 0 7605248 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 921600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2097152 mmcblk0p7
179 8 4374016 mmcblk0p8
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3858432 mmcblk1
179 97 3857408 mmcblk1p1
So to recap:
Mount points are messed up. Partitioning is messed up. EMMc is on read only because of that, so can't flash a new ROM or recovery. Current recovery does nothing but erase for 1-2 secs something (which is not the /data partition) and reboot the phone. There's no option to delete caches, delvik etc. Fastboot erase takes hours and does nothing. It produced a "too many links" but I think that's because the phone eventually died of because of the battery (I'm retrying with full charge and new usb port). Bootloader is locked on the device so can't use fastboot to try to flash the device that way.
Is there any way to ef2chk the /dev/block/mmcblk0 from edb shell? I can't since it's being used by the system, maybe unmount it or something?