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?
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?
FIXED!
I took a stab in the dark after doing a pull of the partitions to my backup hard drive and formatted the last, and largest partition on the list. It calculated out to about what my internal storage was supposed to be, which made me fairly confident that it was the one.
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p28
I tossed that little command into the shell through adb and /emmc/ mounted right up.
Hey guys, I seem to have corrupted my mmcblk0 rather well. mmcblk0p1-4 have no bounds. (Edit 4: This sounds rather silly now that I know more of what I'm looking at. mmcblk0p4 contains all of the partitions after it. partitions 1 - 4 just don't fall on the cylinder lines like the file system expects it to) Anyway, I was wondering if anyone would be kind enough to either copy/paste a stock emmc partition table (/dev/block/mmcblk0), or toss together a CWM flashable that reformats it properly so I can get my internal storage back.
An example of what I'm talking about:
http://forum.xda-developers.com/showpost.php?p=25436995&postcount=2
Thanks!
What my partition table looks like...
Code:
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 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
Edit: I can tcp/ip adb into the device now. Still not sure what's up with my usb connectivity.
Both TWRP and CWM repartition. Have you tried them?
fprice02 said:
Both TWRP and CWM repartition. Have you tried them?
Click to expand...
Click to collapse
Yes, CWM. It can't mount /emmc/ which is why I'm trying to do it this way. I've spent most of the afternoon going through the steep learning curve that is android/linux file systems on a windows machine. Partition 4 actually contains all the partitions after it, which makes it more fun to figure out which one is the internal storage partition(s).
FIXED
So I fixed it. I took a stab in the dark after doing a pull of the partitions to my backup hard drive and formatted the last, and largest partition on the list. It calculated out to about what my internal storage was supposed to be, which made me fairly confident that it was the one.
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p28
I tossed that little command into the shell through adb and /emmc/ mounted right up.
MSDOS......classic on a linux platform.
hello all
i just trying to make cwm for my brand new SAMSUNG GALAXY STAR G-S5282 but coudnt find any source orsomething like that... its running jelly bean i try to dump boot image but its says
Code:
dump_image boot boot.img
/system/bin/sh: dump_image: not found
ok now something wron it dont have dump_image file in it
partitions of this mobile is
Code:
cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 3840 mmcblk0p1
179 2 3840 mmcblk0p2
179 3 5120 mmcblk0p3
179 4 5120 mmcblk0p4
179 5 10240 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 3840 mmcblk0p12
179 13 3840 mmcblk0p13
179 14 3840 mmcblk0p14
179 15 3840 mmcblk0p15
179 16 256 mmcblk0p16
179 17 256 mmcblk0p17
179 18 256 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 524288 mmcblk0p20
179 21 917504 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 10240 mmcblk0p24
179 25 2121728 mmcblk0p25
179 26 8 mmcblk0p26
179 27 1024 mmcblk0p27
mounts
Code:
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1
/dev/block/mmcblk0p21 /system ext4 ro,relatime,
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,node
mit,data=ordered 0 0
/dev/block/mmcblk0p20 /cache ext4 rw,nosuid,nod
bmit,data=ordered 0 0
/dev/block/mmcblk0p19 /efs ext4 rw,nosuid,nodev
commit,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev
up_id=1023,default_permissions,allow_other 0 0
now is there any wy to make dump of boot.img or recovery.img for making cwm?
touseefiqbal said:
now is there any wy to make dump of boot.img or recovery.img for making cwm?
Click to expand...
Click to collapse
Yes you can dump both boot.img and recovery.img provided you have root access by using the following commands:
First:
Code:
cd /dev/block/platform
Then list which platform name you have:
Code:
ls
After change into the platform name directory (The following is an example from my Verizon Galaxy S3):
Code:
cd msm_sdcc.1/by-name
Then:
Code:
ls -l
This command will list what partitions are the boot and recovery partitions make sure to note which block number the recovery and boot partitions are. Now that we know what block number the partitions we want are we can dump them:
Code:
cat /dev/block/recovery_partition_block number > /mnt/sdcard/recovery.img
cat /dev/block/boot_partition_block number > /mnt/sdcard/boot.img
You should now have recovery.img and boot.img files located on your sdcard. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
shimp208 said:
Yes you can dump both boot.img and recovery.img provided you have root access by using the following commands:
First:
Code:
cd /dev/block/platform
Then list which platform name you have:
Code:
ls
After change into the platform name directory (The following is an example from my Verizon Galaxy S3):
Code:
cd msm_sdcc.1/by-name
Then:
Code:
ls -l
This command will list what partitions are the boot and recovery partitions make sure to note which block number the recovery and boot partitions are. Now that we know what block number the partitions we want are we can dump them:
Code:
cat /dev/block/recovery_partition_block number > /mnt/sdcard/recovery.img
cat /dev/block/boot_partition_block number > /mnt/sdcard/boot.img
You should now have recovery.img and boot.img files located on your sdcard. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
sorry i didnt tell you that i dont have root access
I dnt hav root access
Sent from my GT-S5282 using XDA Premium HD app
touseefiqbal said:
sorry i didnt tell you that i dont have root access
Click to expand...
Click to collapse
If you want to root your device I would recommend checking out this thread
http://forum.xda-developers.com/showthread.php?t=2320771 on how to root the Galaxy Star.
Sent from my SCH-I535 using xda premium
As you can see, I can not find where is boot.img in, cuold you pls show me, thank.
shimp208 said:
If you want to root your device I would recommend checking out this thread
http://forum.xda-developers.com/showthread.php?t=2320771 on how to root the Galaxy Star.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My divice is rooted
Try to get recovery bro
Sent from my GT-S5282 using XDA Premium HD app
touseefiqbal said:
Try to get recovery bro
Sent from my GT-S5282 using XDA Premium HD app
Click to expand...
Click to collapse
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
hi
oldmanhp said:
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
Click to expand...
Click to collapse
can you plz share recovery? i will help you to get boot.img
one more thing is it recovery for galaxy star gt-s5282? if yes pl share
ter
oldmanhp said:
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
Click to expand...
Click to collapse
install terminal emulator and type
Code:
dump_image boot /sdcard/boot.img
touseefiqbal said:
can you plz share recovery? i will help you to get boot.img
one more thing is it recovery for galaxy star gt-s5282? if yes pl share
Click to expand...
Click to collapse
Here you are, post #48, it is for Galaxy Mega gt-i9152.
http://forum.xda-developers.com/showthread.php?p=44268116#post44268116
oldmanhp said:
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
Click to expand...
Click to collapse
To get boot.img I would recommend dumping the partition named KERNEL which from the output you provided is /dev/block/mmcblk0p5 the device's kernel is usually stored on the /boot partition, so from what I can tell /dev/block/mmcblk0p5 appears to be the boot partition that you could then dump to get a boot.img file.
q
shimp208 said:
To get boot.img I would recommend dumping the partition named KERNEL which from the output you provided is /dev/block/mmcblk0p5 the device's kernel is usually stored on the /boot partition, so from what I can tell /dev/block/mmcblk0p5 appears to be the boot partition that you could then dump to get a boot.img file.
Click to expand...
Click to collapse
also if you hav cwm reovery then through recovery go for a backup
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?