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?
Related
I've seem many threads about it, but couldn't really find a solution.
I just pulled out my sdcard to do some updates in my rom (I was running Th3Bill's miui v4).
I've copied a couple of .zips to try, and when I inserted back, my I /sdcard wasn't mounting.
I've tried to format in windows (fast and normal mode); I've putted this very same card in my tabled (xoom2 me) and it was working fine.
I've tried to run format /sdcard in cwm. same error mounting;
I went to advance > show log:
CWM-based Recovery v5.0.2.7-atrix5
Error mounting /sdcard!
ro.bootloader=unknown
ro.hardware=olympus
ro.revision=33776
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand. file not found...
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
W:failed to mount /dev/block/mmcblk1 (No such file or directory)
Error mounting /sdcard!
I've tried some stuff on adb (someone mentioned it, not sure what it means):
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ln -n -s /data/media /sdcar
d
ln: /sdcard/media: File exists
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ls -a -l
drwxr-xr-x 21 root root 0 Aug 7 02:15 .
drwxr-xr-x 21 root root 0 Aug 7 02:15 ..
drwxr-xr-x 2 root root 0 Aug 7 02:15 boot
drwxrwx--x 5 system cache 4096 Aug 7 01:43 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Aug 7 02:15 datadata
-rw-r--r-- 1 root root 3875 Jan 1 1970 default.prop
drwxr-xr-x 9 root root 3260 Aug 7 02:15 dev
drwxr-xr-x 2 root root 0 Aug 7 02:15 emmc
drwxr-xr-x 2 root root 0 Aug 7 02:15 etc
-rwxr-x--- 1 root root 94404 Jan 1 1970 init
-rwxr-x--- 1 root root 783 Jan 1 1970 init.rc
drwxr-xr-x 2 root root 0 Aug 7 02:15 osh
drwxr-xr-x 2 root root 0 Aug 7 02:15 pds
drwxr-xr-x 2 root root 0 Aug 7 02:15 preinstall
dr-xr-xr-x 95 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Sep 5 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Aug 7 02:15 sd-ext
drwxr-xr-x 2 root root 0 Aug 7 02:16 sdcard
drwxr-xr-x 14 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Aug 7 02:15 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 9731 Jan 1 1970 ueventd.olympus.rc
-rw-r--r-- 1 root root 4078 Jan 1 1970 ueventd.rc
What do I need to do?
Maybe is there some pins not working in my phone? Because I've tried another micro sd and got same error!
Thanks in advance!
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
ravilov said:
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
Click to expand...
Click to collapse
Well, Actually those commands weren't trying to fix it, and I know what ls does, I wasn't much sure about how ln works, but I know that it wouldn't damage my stuff.
I just checked some stuff here, it seems to be a hardware issue indeed, when I put my nail under the card, it reads! Unfortunately I can't claim warranty. I bought this phone used, via ebay, like and year ago, from a seller in USA (I'm in Brazil). I'll try to arrange some workaround (maybe some paper under it might work,...) and hope it works properly.
**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!
Hi im trying to make a CWM recovery for the LG P714,i made a rom dump using this thread:
http://forum.xda-developers.com/showthread.php?t=1771347
but i only got this files:
checksum.md5
config.gz
system.info.gz
system.tar
i was reading and i found this website to make CWM recovery: http://builder.clockworkmod.com/
i need my image file,but i dont have it,i also read that i need to convert system.tar to image.img,but i dont know how to do that,does anyone can point me into the right direction please,in order to get a CWM for this device.
btw im using Win 8 x64
thanks.
UP
Nobody?
kalel29 said:
Hi im trying to make a CWM recovery for the LG P714,i made a rom dump using this thread:
http://forum.xda-developers.com/showthread.php?t=1771347
but i only got this files:
checksum.md5
config.gz
system.info.gz
system.tar
i was reading and i found this website to make CWM recovery: http://builder.clockworkmod.com/
i need my image file,but i dont have it,i also read that i need to convert system.tar to image.img,but i dont know how to do that,does anyone can point me into the right direction please,in order to get a CWM for this device.
btw im using Win 8 x64
thanks.
Click to expand...
Click to collapse
You will need to dump a copy of your recovery.img file in order to make clockworkmod recovery. You can determine which partition is your recovery partition by running the following commands as root from adb shell or terminal emulator:
Code:
cd /dev/block/platform
ls
After you list the contents of the platform directory take note of what the platform name is (For my Nexus 10 it's dw_mmc.0). Then change directory into the name of the platform directory (Make sure to substitute dw_mmc.0 with your devices platform name):
Code:
cd dw_mmc.0
Then change directory into the by-name part of the platform directory and then list the directory with the following commands:
Code:
cd by-name
ls -l
After listing the partition names you should see a partition block named recovery, SOS, or similar this is the recovery partition you want to dump to create a recovery.img. Once you have noted which block number is the recovery partition you can then dump a copy of the recovery.img to your phones storage with the following command:
Code:
cat /dev/block/{recovery partition block number here} > /mnt/sdcard/recovery.img
You should now have a copy of the recovery.img file on your phones storage. If you upload a copy of the recovery.img file that you dumped to your phones storage I can try and compile Clockworkmod Recovery for you .
thanks after the first input i have this output:
msm_sdcc.1
msm_sdcc.3
kalel29 said:
thanks after the first input i have this output:
msm_sdcc.1
msm_sdcc.3
Click to expand...
Click to collapse
Cd into the msm_sdcc.1 directory:
Code:
cd msm_sdcc.1
Then run the rest of the commands listed above :good:.
shimp208 said:
Cd into the msm_sdcc.1 directory:
Code:
cd msm_sdcc.1
Then run the rest of the commands listed above :good:.
Click to expand...
Click to collapse
ok im inside msm_sdcc.1 ,when i list the folders i just got this folders:
by num
mmcblk1
mmcblk1p1
kalel29 said:
ok im inside msm_sdcc.1 ,when i list the folders i just got this folders:
by num
mmcblk1
mmcblk1p1
Click to expand...
Click to collapse
In that case try cd into msm_sdcc.3 and run the commands listed above that should contain the by-name directory.
Sent from my SCH-I535 using xda premium
shimp208 said:
In that case try cd into msm_sdcc.3 and run the commands listed above that should contain the by-name directory.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
thanks,i already did that and there is not any directory named like that,only by-number :/
ok i got it,but its only 142 bytes its ok to be that small?
im using online recovery builder btw
kalel29 said:
ok i got it,but its only 142 bytes its ok to be that small?
im using online recovery builder btw
Click to expand...
Click to collapse
That's way to small, It should be anywhere from 4-8 Megabytes in size can you list your partition layout that the by-num directory shows or also run the following command:
Code:
cat /proc/partitions
And I can try and determine which partition is the recovery partition.
Sent from my SCH-I535 using xda premium
shimp208 said:
That's way to small, It should be anywhere from 4-8 Megabytes in size can you list your partition layout that the by-num directory shows or also run the following command:
Code:
cat /proc/partitions
And I can try and determine which partition is the recovery partition.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
here you go:
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 4190 loop1
7 2 18743 loop2
7 3 4190 loop3
7 4 4190 loop4
7 5 11466 loop5
7 6 6269 loop6
7 7 18743 loop7
179 0 3866624 mmcblk0
179 1 20 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 1 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 12288 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 28672 mmcblk0p12
179 13 28672 mmcblk0p13
179 14 1241088 mmcblk0p14
179 15 12288 mmcblk0p15
179 16 307200 mmcblk0p16
179 17 12288 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 12288 mmcblk0p19
179 20 1896448 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 53248 mmcblk0p25
179 26 4096 mmcblk0p26
179 32 15558144 mmcblk1
179 33 15550919 mmcblk1p1
254 0 2110 dm-0
254 1 4189 dm-1
254 2 18742 dm-2
254 3 4189 dm-3
254 4 4189 dm-4
254 5 11466 dm-5
254 6 6268 dm-6
254 7 18742 dm-7
7 8 8348 loop8
254 8 8347 dm-8
7 9 2111 loop9
254 9 2110 dm-9
7 10 8348 loop10
254 10 8347 dm-10
7 11 38493 loop11
254 11 38493 dm-11
7 12 5229 loop12
254 12 5229 dm-12
7 13 5229 loop13
254 13 5229 dm-13
7 14 7308 loop14
254 14 7308 dm-14
7 15 7308 loop15
254 15 7308 dm-15
7 16 47849 loop16
254 16 47848 dm-16
7 17 8348 loop17
254 17 8347 dm-17
7 18 6269 loop18
254 18 6268 dm-18
kalel29 said:
here you go:
[email protected]:/ # cat /proc/partitions
Click to expand...
Click to collapse
Try dumping mmcblk0p25 that looks like it could be the recovery partition based on size.
shimp208 said:
Try dumping mmcblk0p25 that looks like it could be the recovery partition based on size.
Click to expand...
Click to collapse
so the command should be:
cat /dev/block/mmcblk0p25> /mnt/sdcard/recovery.img ???
----------------ok got it but now its 52 mb
wait if im not mistaken and my logic its right ,you are saying that the image should be around 8mb,so if i do the math its 1024*8 its 8192 and the only block with that number its the number 18.
well its just my opinion ,im just learning.
kalel29 said:
wait if im not mistaken and my logic its right ,you are saying that the image should be around 8mb,so if i do the math its 1024*8 its 8192 and the only block with that number its the number 18.
well its just my opinion ,im just learning.
Click to expand...
Click to collapse
Yes, I would recommend dumping block mmcblk0p18. The previous block I misread the block size and though it read ~5 MB rather then the approximately ~50 MB is came out to be.
shimp208 said:
Yes, I would recommend dumping block mmcblk0p18. The previous block I misread the block size and though it read ~5 MB rather then the approximately ~50 MB is came out to be.
Click to expand...
Click to collapse
And just search since /cache/recovery/last_log be more easy no?
I can make recovery.img of 12 mb but i dont know be correct.
Sent from my LG-P714 using XDA Premium 4 mobile app
before doing anything,check this page shimp208 ,raffles496 is also searching on a way to build a recovery for this device,his only problem is that he does not speak english,but he´s smarter than me.
http://androidforums.com/venice-all-things-root/662166-dev-recovery-clockworkmod-recovery.html
maybe we can use it to search the correct block to pull the image and make CWM.
kalel29 said:
before doing anything,check this page shimp208 ,raffles496 is also searching on a way to build a recovery for this device,his only problem is that he does not speak english,but he´s smarter than me.
http://androidforums.com/venice-all-things-root/662166-dev-recovery-clockworkmod-recovery.html
maybe we can use it to search the correct block to pull the image and make CWM.
Click to expand...
Click to collapse
I'm more then happy with teamwork :good:. After browsing that thread you can figure out what partition recovery is by booting into the stock recovery on your phone, then in the stock recovery select the wipe cache option. Then once you have done that reboot the phone and navigate to the /cache/recovery folder on your device and inside that will be recovery.log. If you upload the recovery.log file then we should finally be able to determine which partition truly is the recovery partition.
shimp208 said:
I'm more then happy with teamwork :good:. After browsing that thread you can figure out what partition recovery is by booting into the stock recovery on your phone, then in the stock recovery select the wipe cache option. Then once you have done that reboot the phone and navigate to the /cache/recovery folder on your device and inside that will be recovery.log. If you upload the recovery.log file then we should finally be able to determine which partition truly is the recovery partition.
Click to expand...
Click to collapse
yes i also saw that,the only thing is that i dont know how to enter to default recovery to wipe cache,i see the path with root explorer,but there's nothing inside the folder,thats the last step in order to start making a working recovery for this phone,and also thanks again for your help and advice.
:highfive:
kalel29 answer already for PM. Greetings.
Sent from my LG-P714 using XDA Premium 4 mobile app
---------- Post added at 04:51 PM ---------- Previous post was at 04:27 PM ----------
Hello. My result after into to stock recovery, see in /cache/recovery/last_log is this. But say I cant make wipe, this option no available in this recovery. I think no be necessary wipe, no?
Starting recovery on Thu Aug 22 21:33:57 2013
Recovery main : arg[1] = (null)
frstflag = flag7
Enter C/S Recovery~~~
framebuffer: fd 4 (480 x 800)
[RAINEDAY]Display_Width = 480
[RAINEDAY]bnr_recovery = 0, bnr_recovery_s = 1
backup_img = backup_restore_eng_HDPI
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/platform/msm_sdcc.3/by-num/p9 (null) 0
2 /cache ext4 /dev/block/platform/msm_sdcc.3/by-num/p16 (null) 0
3 /data ext4 /dev/block/platform/msm_sdcc.3/by-num/p20 (null) -16384
4 /misc emmc /dev/block/platform/msm_sdcc.3/by-num/p8 (null) 0
5 /recovery emmc /dev/block/platform/msm_sdcc.3/by-num/p17 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /system ext4 /dev/block/platform/msm_sdcc.3/by-num/p14 (null) 0
8 /FOTA emmc /dev/block/platform/msm_sdcc.3/by-num/p19 (null) 0
get_args(), argc = 1
I:fopen_path 1 /data/fota/ipth-muc.prop
I:fopen_path 2 /data/fota/ipth-muc.prop
I:fopen_path 3 /data/fota/ipth-muc.prop
I:Failed to open /data/fota/ipth-muc.prop, use default pkg location:/cache/fota
Ielta package does not exist /cache/fota/ipth_package.bin
END OF while ~~~
[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?
I've create a directory /storage/sdcard2 and mounted it as follows:
mkdir sdcard2
chmod 771 /storage/sdcard2
chgrp 1015 /storage/sdcard2
So it has looks like:
drwxrwx--x 3 root sdcard_rw 60 Feb 12 20:17 sdcard2
Now the external storage looks like:
drwxrwx--x 19 root sdcard_rw 32768 Dec 31 1969 DE52-F3E6
So they match exactly, but for some reason while most apps (non-root) can see and view /storage/DE52-F3E6 nothing but root apps can see /storage/sdcard2 (if I su* others can see it in a console but not access it). In Android (CM12) 5.1, this worked fine, in (CM13) 6.0.1 I'm going crazy. I thought it might be namespace separation in Super SU, but that does not appear to be the case it is as if there is another block that only allows root to see non-standard directories (or files) since creating a file in /storage has the exact same issue.
How do I fix this as it makes using 6.0.1 useless as I can not manually mount my secondary partition on the SD Sard and get access to the data on it (except as root).
su - u_10034
127|[email protected]:/storage # su - u0_a334
[email protected]:/storage $ ls -al
drwxr-xr-x 6 root root 140 Feb 12 20:06 .
drwxr-xr-x 28 root root 0 Feb 12 19:59 ..
drwxrwx--x 19 root sdcard_rw 32768 Dec 31 1969 DE52-F3E6
drwx--x--x 5 root sdcard_rw 4096 Dec 31 2014 emulated
drwxrwx--x 3 root sdcard_rw 60 Feb 12 20:17 sdcard2
drwxr-xr-x 2 root root 60 Aug 2 2015 self
[email protected]:/storage $
At a minimum I want to at be able to access the sdcard2 directory same as I can access DE52-F3E6 the permissions match, but the SE (ls -n) setting differ, but I can not find what setting I need to use there to allow the same access as DE52-F3E6 since DE52-F3E6 is a device and sdcard2 is a directory.
Thanks,
ERIC