Related
Anyone know how to resolve this issue whereby I'm unable to do anything with the internal storage? As best I can tell, I just can't write to it anymore (some kind of corruption). Every time I turn the device on, it reverts back to the state it was in a few days ago when this started. Everything starts to FC because it can't write to the internal storage. I tried Odin to stock, it completes to success (green and everything), but when it restarts it's as if nothing happened. Same story with a CWM flash. Wipe/Factory Reset says success, but it's clear it isn't doing anything as it flies through it too quickly. Nandroid restore no good. Odin one-click no good. Format of system data or cache completes, but again clearly not doing anything as it happens too fast. ADB Shell coupled with e2fsck gives me an error about the superblock, and checking the CWM recovery log, I see something about wipe_block_device: Discard failed.
Any suggestions on what else I could try?
That sounds worse than a brick
jeff210 said:
That sounds worse than a brick
Click to expand...
Click to collapse
Indeed, the damned device is mocking me. "Haha! I'm ALIVE, but I'm USELESS!"
Just a stupid question but did you happen to install any antivirus/firewall program on your phone?
Also are there any device administrator on your phone other than your own? ie. Device admin from exchange server etc. Sometime those can lock-down your phone preventing any kind of data wipe.
icce007 said:
Just a stupid question but did you happen to install any antivirus/firewall program on your phone?
Also are there any device administrator on your phone other than your own? ie. Device admin from exchange server etc. Sometime those can lock-down your phone preventing any kind of data wipe.
Click to expand...
Click to collapse
Thanks for the suggestion, but no - no firewall/antivirus, and no device administrators that are active. Good question, though. Besides, I don't think any of those would be able to prevent an Odin, would they?
Well, I tried everything and it just won't take. Looks like it's back to the Nexus for me I'll keep it around in case an eventual fix is identified.
EDIT: This output doesn't look right. Any thoughts on how I can clear this table up?
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15756951552 bytes
1 heads, 16 sectors/track, 1923456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 92 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 1923584 15284271+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13313 13375 500 47 Unknown
/dev/block/mmcblk0p6 13825 14080 2048 45 Unknown
/dev/block/mmcblk0p7 14337 14649 2500 4c Unknown
/dev/block/mmcblk0p8 14849 16128 10240 48 Unknown
/dev/block/mmcblk0p9 16385 16447 500 46 Unknown
/dev/block/mmcblk0p10 16897 16959 500 5d Unknown
/dev/block/mmcblk0p11 17409 17471 500 91 Unknown
/dev/block/mmcblk0p12 17921 19200 10240 93 Unknown
/dev/block/mmcblk0p13 19457 32000 100352 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p14 32257 32640 3072 4a Unknown
/dev/block/mmcblk0p15 32769 33152 3072 4b Unknown
/dev/block/mmcblk0p16 33281 33664 3072 58 Unknown
/dev/block/mmcblk0p17 33793 46336 100352 8f Unknown
/dev/block/mmcblk0p18 46593 46976 3072 59 Unknown
/dev/block/mmcblk0p19 47105 47488 3072 5a Unknown
/dev/block/mmcblk0p20 47617 48000 3072 5b Unknown
/dev/block/mmcblk0p21 48129 49408 10240 ab Darwin boot
/dev/block/mmcblk0p22 49665 50944 10240 60 Unknown
/dev/block/mmcblk0p23 51201 52480 10240 94 Unknown
/dev/block/mmcblk0p24 52737 183808 1048576 a5 FreeBSD
/dev/block/mmcblk0p25 183809 446208 2099200 a6 OpenBSD
/dev/block/mmcblk0p26 446465 485120 309248 a8 Darwin UFS
/dev/block/mmcblk0p27 485377 501888 132096 a9 NetBSD
/dev/block/mmcblk0p28 502273 1923584 11370496 90 Unknown
Also, I tried playing around with parted to see if I can repartition the device, but it keeps complaining about "Can't have a partition outside the disk!"
I saw someone else have a similar problem with a different Samsung phone and they were able to get things working again by using Odin and the repartition option with a PIT file. I tried searching for the PIT file that goes with the i717 and I'm not getting any useful hits. Anyone know if such a beast exists?
So on previous devices, I'm used to the MTD filesystem/partition approach. Today, I was trying to find information on how to access the EMMC partitions from the internal command line and I was not able to find anything.
I know that typing the following gives me a list of all the EMMC partitions (I remember using /proc/mtd on the Evo 4G):
Code:
cat /proc/emmc
However, if I then go to backup my BOOT partition with this command, I find that there is no /dev/emmc device (or anything close):
Code:
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
So, perhaps stupid question, but I've spent 20 minutes running various searches on EMMC, MTD, mount points, etc. with no answer. How can I run the DD command listed above and access the proper partition?
Slappy_G said:
So on previous devices, I'm used to the MTD filesystem/partition approach. Today, I was trying to find information on how to access the EMMC partitions from the internal command line and I was not able to find anything.
I know that typing the following gives me a list of all the EMMC partitions (I remember using /proc/mtd on the Evo 4G):
Code:
cat /proc/emmc
However, if I then go to backup my BOOT partition with this command, I find that there is no /dev/emmc device (or anything close):
Code:
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
So, perhaps stupid question, but I've spent 20 minutes running various searches on EMMC, MTD, mount points, etc. with no answer. How can I run the DD command listed above and access the proper partition?
Click to expand...
Click to collapse
Off the top of my head, I forgot the commands and dont have the device in front of me .. BUT I do remember some of the information.
Starting off, the command you give /dev/emmc/mmcblk0p21 is close but not quite. You might need to double check, but I'm thinking /dev/block/mmcblk0p21 ... if that is correct, then the partitions should all be listed under /dev/block.
If not, I'd suggest looking around that area because that is where they are located.
Google'd "/dev/block/mmcblk0p21" and seems to be quite a few results. I'm thinking that should be the area where the partitions are listed, /dev/block. As you mentioned /proc/emmc should give the corresponding labels and block device names.
Hope that helps!
your device needs to be rooted
adb shell
adb su
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
joeykrim said:
Off the top of my head, I forgot the commands and dont have the device in front of me .. BUT I do remember some of the information.
Starting off, the command you give /dev/emmc/mmcblk0p21 is close but not quite. You might need to double check, but I'm thinking /dev/block/mmcblk0p21 ... if that is correct, then the partitions should all be listed under /dev/block.
If not, I'd suggest looking around that area because that is where they are located.
Google'd "/dev/block/mmcblk0p21" and seems to be quite a few results. I'm thinking that should be the area where the partitions are listed, /dev/block. As you mentioned /proc/emmc should give the corresponding labels and block device names.
Hope that helps!
Click to expand...
Click to collapse
Perfect - I didn't think to look under the "block" device. That was the missing piece for me. I appreciate the help.
globula_neagra said:
your device needs to be rooted
adb shell
adb su
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
Click to expand...
Click to collapse
Unfortunately, this won't work. The missing piece is that the device name is "block" not "emmc" - thanks to joeykrim above.
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 32 mmcblk0p13
179 14 6144 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 46080 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 8190 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 16383 mmcblk0p22
179 23 1022 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 4096 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 4 mmcblk0p27
179 28 256 mmcblk0p28
179 29 16 mmcblk0p29
179 30 1280 mmcblk0p30
179 31 64 mmcblk0p31
179 32 256 mmcblk0p32
179 33 256 mmcblk0p33
179 34 99239 mmcblk0p34
179 35 1277951 mmcblk0p35
179 36 229375 mmcblk0p36
179 37 2260991 mmcblk0p37
179 38 10418176 mmcblk0p38
179 64 30657536 mmcblk1
179 65 30653440 mmcblk1p1
/dev/block/mmcblk0p17 /firmware_radio
/dev/block/mmcblk0p18 /firmware_q6
/dev/block/mmcblk0p19 /firmware_wcnss
/dev/block/mmcblk0p26 /devlog
/dev/block/mmcblk0p35 /system
/dev/block/mmcblk0p37 /data
/dev/block/mmcblk0p36 /cache
I know I'm necrobumping a really old thread, and I'm sorry for that, but which one is for the internal sdcard?
**SOLVED**
I got a little restless waiting for a response, so I just went ahead and re-flashed the latest RUU. It worked. My internal sd card is fine and fully functional now.
(I'm leaving the original question below in case this helps someone else in a similar situation)
--------------------------------------------------------------------------------------------------------------------------------------
Hi. I tried to partition my internal sdcard and did something wrong. Now it won't mount.
About my phone:
-------------------------------------------------------------
Info at the top of my bootloader screen:
Code:
**vinylfreak89**
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
Radio-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
Currently running ra recovery v3.15
Currently on Neo's AOSP RAGERom 1.9.1
-------------------------------------------------------------
How I broke it:
I tried to partition my sdcard and use the s2e app to move my apps to the sd partition. In order to do this, I removed my external sd card, booted into recovery, and selected partition sdcard, then partitioned an ext2 section of about 1GB. I reinserted my external sdcard, rebooted and tried to use the app. I made some selections in the app, rebooted phone, and tried moving my apps to sd, but it still didn't work. Then I did some more stuff, accidentally wiped my external sd card, (i'm a little fuzzy on exactly the remaining details, but I don't think anything else beyond this point is pertinent... suffice it to say my internal sd is not working, but I fixed everything else).
Current symptoms:
Everything on my phone works fine, except that the internal sdcard doesn't mount. While running my phone normally, if I try to mount usb mass storage, It mounts my external sd, but not the internal sd.
From recovery, if I try to wipe my Internal SD, i get the following error:
Code:
Formatting INTERNALSD
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/!
Skipping format...
I get the same error when trying to mount Internal SD.
I tried other recoveries ( TWRP_v2.3.2.1, CWM_Touch_5.8.1.5v1.1, CWM_Touch_6.0.1.0v1 ) and get the same errors.
I know enough about linux to break my stuff on my own (or to follow directions if I have them). This being said, I know that that app s2e installed a script on my phone (not sure where). I Imagine that script changed the mount points for internal sd and sd-ext (that is the point, after all). I also imagine that this is my current problem (I could be completely wrong, of course).
So I imagine that one possibility for fixing this would be to remount and reformat the sdcard from within adb shell. I imagine this might involve the fdisk tool (which I don't have much experience with) and perhaps even the /etc/fstab file.
here's the output from
Code:
/dev/block # ls
Code:
loop0 mmcblk0 mmcblk0p16 mmcblk0p23 mmcblk0p30 mmcblk0p38 mmcblk1p1
loop1 mmcblk0p1 mmcblk0p17 mmcblk0p24 mmcblk0p31 mmcblk0p4 platform
loop2 mmcblk0p10 mmcblk0p18 mmcblk0p25 mmcblk0p32 mmcblk0p5
loop3 mmcblk0p11 mmcblk0p19 mmcblk0p26 mmcblk0p33 mmcblk0p6
loop4 mmcblk0p12 mmcblk0p2 mmcblk0p27 mmcblk0p34 mmcblk0p7
loop5 mmcblk0p13 mmcblk0p20 mmcblk0p28 mmcblk0p35 mmcblk0p8
loop6 mmcblk0p14 mmcblk0p21 mmcblk0p29 mmcblk0p36 mmcblk0p9
loop7 mmcblk0p15 mmcblk0p22 mmcblk0p3 mmcblk0p37 mmcblk1
Remember, the error I get says it can't mount mmcblk0p37 (which is present on this list) or mmcblk038 (which is not present - maybe it was the sd-ext partition that is no longer there?)
If I hadn't just spent the past two days breaking my phone, I'd probably tinker around with fdisk, mount, etc myself, but I figured it'd be better to ask at this point instead of likely causing some catastrophic damage.
I did try factory reset, wiping /data, /system, /boot, etc... and reflashing the rom from scratch. Still no go. As I mentioned above, I also tried several different recoveries to try to wipe the internal sdcard. Something else I haven't tried yet is to reflash the RUU. I don't know if that would fix this problem, but if there's a chance that it will, I'll try it. (maybe someone can point me to the correct RUU to flash if this is necessary?)
Anyway. That's my problem. I hope someone can help point me in the right direction, because while 32GB in my external sd is plenty of room, that 16GB internal memory card would be nice... and I just don't like having broken stuff!
Thanks!
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!