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!
Related
Hello all! I'm sorry for my english.
I am trying to port CWM into my device Huawei Vision U8850, 'recovery mode' compiling from a source code Cyanogen
and i have some errors when starting RecoveryMode
1) E: can't find misc
2) E; Can't mount /cache/recovery/command
3) E: Can't moun( and open) /cache/recovery/log
4) E: Can't mount (and open) /cache/recovery/last_log
My recovery.fstab
Code:
# mount point<->fstype device <-->[device2]
/boot mtd boot
/cache ext3 /dev/block/mmcblk0p11
/data ext3 /dev/block/mmcblk0p8
/misc emmc /data/misc
/recovery mtd recovery /dev/block/mmcblk0p1
/sdcard vfat /dev/block/mmcblk1p1
/system ext3 /dev/block/mmcblk0p7
#/sd-ext ext4 /dev/block/mmcblk0p2
in device "misc" in /data/misc
When i mount "misc ext3 /data/misc" - E: unknown fs type
"misc mtd /data/misc" - E: can't found misc
"misc emmc /data/misc" - Can't open misc
Mounts from device
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/ru.dublgis.dgismobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
My partitions
Code:
major minor #blocks name
7 0 24980 loop0
7 1 27660 loop1
179 0 1867776 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 253952 mmcblk0p7
179 8 1122304 mmcblk0p8
179 9 81920 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 204800 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 32 3929088 mmcblk1
179 33 3924992 mmcblk1p1
254 0 24979 dm-0
Can be corrected in the boot init.rc section, but then what rights the user and group, options set?
Please help me. Thanks...
Cant help you but good luck for you, i have that phone and i really would like cwm
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 http://yadi.sk/d/R4p2T6b30Edt
GriefNorth said:
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 http://yadi.sk/d/R4p2T6b30Edt
Click to expand...
Click to collapse
Anyone confirm this is working?
Anyone confirm this is working?
Click to expand...
Click to collapse
Only russian users from http://4pda.ru/forum/index.php?showtopic=257207&st=2320 and http://4pda.ru/forum/index.php?showtopic=358221&st=280 May be problem if you device sim-lock.
Ok, thanks. Im MAYBE trying this
Sent from my Vision
in this firmware original bootloader. and the possibility of obtaining brick is zero %
GriefNorth said:
in this firmware original bootloader. and the possibility of obtaining brick is zero %
Click to expand...
Click to collapse
really? have you installed it?
Sent from my Vision
yes
so is it for 2.3.5 version or 2.3.7 , cos i have 2.3.5
Sent from my Vision
this is full firmware 2.3.7
GriefNorth said:
this is full firmware 2.3.7
Click to expand...
Click to collapse
and its based china version? because on not chinese
Sent from my Vision
Yes it's china version, after installing change language. China because file system ext4 switch off on my official firmware (russian), but in chaina firmware ext4 switch on in kernel and used. CWM recovery not working with ext3.
GriefNorth said:
Yes it's china version, after installing change language. China because file system ext4 switch off on my official firmware (russian), but in chaina firmware ext4 switch on in kernel and used. CWM recovery not working with ext3.
Click to expand...
Click to collapse
ok, but can i change back to original if i dont like that?
Sent from my Vision
Yes...
GriefNorth said:
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 ...... ...
Click to expand...
Click to collapse
I have many problems with this firmware. Keyboard isn't contained and every keyboard I install won't work - it disappears every time i write one letter.
And the second problem is that CWM is not working for me. It is there, but I can't do anything in it, because back button is not working.
Is there anybody else having the same problem?
i'm sorry, this firmware not have a keyboard, you should install any keyboard from google market. And in recovery going on the last position and press Vol+andVol- (at the same time) then show @Back button menu [email protected]
GriefNorth said:
i'm sorry, this firmware not have a keyboard, you should install any keyboard from google market. And in recovery going on the last position and press Vol+andVol- (at the same time) then show @Back button menu [email protected]
Click to expand...
Click to collapse
Thanks, I'll give it a second try.
try it's all works, without keyboard *sorry* )))
Oh, the "back button" I ment was the one used for confirming an action in recovery, that one is not working for me, when I use it, the selected action will not perform, nothing will happen, so I canť do anything in it, because there's no working button for confirming actions. Do you know what I mean? I'm not that good at english, so I don't know how to express some things
For some reason my sd-card partition can't be mounted anymore by cwm after I followed this guide http://forum.xda-developers.com/showthread.php?t=1601942 to stop cwm boot loop into recovery.
My CM10 doesn't boot anymore after I flashed latest version (2012-08-06) and I'm trying to manually adb shell into the tf201 to try and mount the partition myself.
What's the block device for sdcard?
I have:
Code:
# ls /dev/block
loop0 loop4 mmcblk0 mmcblk0p3 mmcblk0p7 sda
loop1 loop5 mmcblk0p1 mmcblk0p4 mmcblk0p8 sda1
loop2 loop6 mmcblk0p10 mmcblk0p5 mmcblk0p9
loop3 loop7 mmcblk0p2 mmcblk0p6 platform
and the following is mounted:
Code:
mount
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/mmcblk0p2 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /system type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
fstab
Code:
# cat /etc/fstab
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p1 /system ext4 rw
and trying to mount mmcblk0p8:
Code:
# mount /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
help?
Ok, RaYmAn on the irc channel helped me out! I cleared my mmcblk0p8 partition with fastboot:
Code:
fastboot -i 0xb05 erase userdata
And voila! Now I can use /data to copy my roms to and use CWM to flash them.
Thanks all! Peace!
can u please elaborate more on this? how to fastboot and stuff? i cannot flash other roms after i flashed recovery v5.5.0.4 because in recovery my sd card is not seen
dimushor said:
can u please elaborate more on this? how to fastboot and stuff? i cannot flash other roms after i flashed recovery v5.5.0.4 because in recovery my sd card is not seen
Click to expand...
Click to collapse
Go into the dev thread, look at the twrp thread there, it explains how to use fastboot. If I were you I would seriously consider installing twrp, isn't that an old version of cwm your using?
http://forum.xda-developers.com/showthread.php?t=1615990 TWRP external sd card support
http://forum.xda-developers.com/showthread.php?t=1533697 CWM 5.8.2.0
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
Hope this is the right place to post, I've been lurking around the forums since I got my first smart phone a few years ago but never posted as I've usually found what I'm looking for through googling and rtfm'ing, only reason I came out of the shadows was to get my Kobo Arc 7 rooted. No way I could live without it, I had been watching this thread http://forum.xda-developers.com/showthread.php?t=2507886, checking it every few days to see if there was any development when I saw development was pretty much abandoned on the Arc 7. So this all started with a pm that made me try getting root myself with a little help from dazza9075.
Basically was told to trade in the arc 7 for an arc 7hd, barring that I could try the new cydiaimpactor update and see if it worked. It went something like this. I followed the instructions for the 7hd:
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Click to expand...
Click to collapse
Everything went fine until plugging in the device to let it install a USB composite device. As expected it did fail on the third but when trying to install Google USB drivers it couldn't find any for the device. Just for kicks I opened up Impactor and pressed "Start" it did nothing, I then clicked "USB Scan" and let it complete, then pushed "Start" again. Quick popup on the screen, so I swiped the screen and ran Root Checker Basic and voila I had root.
Since then I've pretty much been badgering dazza9075 through pm to see about getting a recovery for it, I'm an old school linux guy, but never spent much time doing any development, so trying to figure things out myself is usually not an issue but this is new to me. I've been utilizing my google fu to try getting a recovery image made and had some success. Basically started with the instructions for dumping the partition info via dazza's instructions. Turned out to be a little more frustrating than anything, all the commands were turning up nothing, then finally I checked chipset specific stuff, it's running an MTK8125 so after getting nowhere with:
cat /proc/mounts
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /storage/emulated tmpfs rw,relatime,mode=705,uid=1023,gid=1023 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
cat /proc/partitions
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
179 0 7523456 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 786432 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 6145664 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
So trying to find the ls -al /dev/block/platform/dw_mmc/by-name was the first hurdle as there was no "by-name"
Code:
ls -al /dev/block/platform/dw_mmc/by-name
ls -al /dev/block/platform
drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.0
drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.1
ls -al /dev/block/platform/mtk-msdc.0
drwxr-xr-x root root 2014-01-29 20:33 by-num
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p7 -> /dev/block/mmcblk0p7
ls -al /dev/block/platform/mtk-msdc.1
drwxr-xr-x root root 2014-01-29 20:33 by-num
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1p1 -> /dev/block/mmcblk1p1
but an ls -l revealed:
Code:
[email protected]:/ # ls -l
ls -l
drwxr-xr-x root root 2014-01-31 08:16 acct
-rw-r--r-- root root 16927 1969-12-31 18:00 advanced_meta_init.rc
drwxrwx--- system cache 2014-01-28 19:01 cache
dr-x------ root root 2014-01-31 08:16 config
-rw-r--r-- root root 4 1969-12-31 18:00 custom_build_verno
lrwxrwxrwx root root 2014-01-31 08:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-01-31 08:17 data
-rw-r--r-- root root 185 1969-12-31 18:00 default.prop
drwxr-xr-x root root 2014-01-31 08:16 dev
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p7
So I focused on googling emmc partition tables and stumbled upon this thread http://forum.xda-developers.com/showthread.php?t=2450045 which again I followed with little success. I had already tried way 1 and way 2 and way 3 couldn't read the partition table. So I followed the comments and #3 mentioned "cat /proc/emmc", so:
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00006800 00005000 "protect_f"
emmc_p3: 0000b800 00005000 "protect_s"
emmc_p4: 00016c00 00003000 "sec_ro"
emmc_p5: 00020c00 00180000 "android"
emmc_p6: 001a0c00 00100000 "cache"
emmc_p7: 002a0c00 00bb8d00 "usrdata"
Still not giving me a good picture of the partition table so I followed that thread till the end which took me to this thread, http://forum.xda-developers.com/showthread.php?t=1959445. So in fashion I started following that. So
Using fdisk:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Disk /dev/block/mmcblk0: 7704 MB, 7704018944 bytes
1 heads, 16 sectors/track, 940432 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1665 2944 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2945 4224 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5825 6592 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8385 106688 786432 83 Linux
parted:
Code:
[email protected]:/ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Error: Can't have a partition outside the disk!
gdisk:
Code:
[email protected]:/ # gdisk -l /dev/block/mmcblk0
gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
EBR signature for logical partition invalid; read 0x0000, but should be 0xAA55
Error reading logical partitions! List may be truncated!
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Disk /dev/block/mmcblk0: 15046912 sectors, 7.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E01B69E6-D822-467F-B1D2-97C0B7BA9ABA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15046878
Partitions will be aligned on 1024-sector boundaries
Total free space is 13420733 sectors (6.4 GiB)
Number Start (sector) End (sector) Size Code Name
2 26624 47103 10.0 MiB 8300 Linux filesystem
3 47104 67583 10.0 MiB 8300 Linux filesystem
4 93184 105471 6.0 MiB 8300 Linux filesystem
5 134144 1707007 768.0 MiB 8300 Linux filesystem
Still no love. So I read on to the emmc section of that thread and understand nothing, more google fu gets me here: https://github.com/ameer1234567890/OnlineNandroid/wiki/How-To-Gather-Information-About-Partition-Layouts. So now I'm looking at the emmc stuff thinking this really doesn't help me, but remembering I'm running an mtk chip I was pretty happy when I got:
Code:
[email protected]:/ # cat /proc/dumchar_info
cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
resv 0x0000000000080000 0x0000000003400000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003480000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0
android 0x0000000030000000 0x0000000004180000 2 /dev/block/mmcblk0p5
cache 0x0000000020000000 0x0000000034180000 2 /dev/block/mmcblk0p6
usrdata 0x00000001771a0000 0x0000000054180000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
Bingo, so finally, root, partition info, next recovery. Again I'm green here so I searched and searched and searched until finally I found the lenovo has the same chip that someone else had managed to get a recovery installed. So I've spent most of my day with this page, trying to get a recovery installed http://forum.xda-developers.com/newthread.php?do=postthread&f=613. So I managed to get everything done, booted into CWM recovery, finished up all excited, then started testing CWM first reboot and I'm back to the stock android recovery. So I ended up finding the recovery.img that was created through the steps in the above link and did:
Code:
adb shell
mount -o remount,rw /system
mv /system/recovery-from-boot.p /system/recovery-from-boot.p-orig
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-orig
As this was apparently a known problem with some samsung devices. Then:
Code:
fastboot flash recovery "path to recovery"
Which I cut and pasted the path, then rebooted the Arc 7 into fastboot by holding down the Volume up and power slider for aproximately 30 seconds. Fastboot was successful but hung after installing the recovery.img so I hard rebooted and got back into the arc. So I've tested it a few times and now it's booting into CWM recovery, I had two backups made during the image creation process and have been able to restore from both backups, tried creating a backup which completed with an error, can't remember what it is at this point though I will try again later. Only thing I'm noticing is when I boot into recovery it throws the following errors.
Code:
CWM automade 03.02.2014 11:23:02
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
At this point I'm not sure if this is a problem or not as so far everything seems to be working, I will continue testing this recovery out then hopefully post it to dazza9075's original thread. At this point I really don't know what to do from here and any input would be greatly appreciated, dazza has been a great help but I'm at the mercy of being in different countries and timezones, so the pm process is always a little hurry up and wait. Apologies again if this is the wrong place to post, and thanks to all the people in the other posts above for all the hard work they have put in. Hopefully having some of this information in one place will help others with Microtek Chips.
Good work mate!
Have you tried creating a backup yet? and can you post the contents of your FSTAB?
The important one for you is probably to get the SD card mounted, with the internal storage quite low backups will be tricky, so we need to be able to mount an external SD card and use that for the backup.
I wouldn't be to worried about the other partitions that haven't mounted yet, lets concentrate on the important ones, /system /cache /recovery /boot
once we can confirm that you can back then restore we can tidy up the other issues.
Good work mate!
Here is my fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
It appears that my external sdcard is getting mounted for backups anyways as my backups are all being found in /storage/sdcard1/clockworkmod/backup/. Here is the output from CWM during the backup:
Code:
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
SD Card space free: 7225MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
Backing up cache...
Can't mount /cache!
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
Checking the new backup folder created only yields boot.img, data.ext4.tar, recovery.img and system.ext4.tar
Pretty much looks like we just need to get the /cache mounting properly then it should go off without a hitch.
Correction, just tried wiping the cache from CWM rebooted to delete the failed backups off the device, booted back into recovery and was greeted by the stock android recovery.
Okay so after getting the stock android recovery after wiping the cache 3 times I decided to start fresh.
Factory reset
Selected english
Forced to update
Rooted with impactor
Installed SU
Installed rom toolbox
fastboot flash recovery "path-to"\recovery.img
power down the volume up powerslider til menu pops up
select fastboot
image flashes and says complete, hold power slider to power down and
rebooted into cwm (volume up and power slider till menu pops up then restore) and this is what I got:
Code:
rua1 autoCWM v5.5.0.4 for arc 7
-reboot system now
-install zip from sdcard
-wipe data/factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
CWM automade 03.02.2014 11:23:02
SD Card space free: 7852MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No sd-ext found. Skipping backup of applications on external storage.
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
Rebooted
From rom toobox "Rom Management"
selected custom cwmr
swiped to backups
selected backup I just made and rebooted into cwm from rom toolbox
Code:
CWM automade 03.02.2014 11:23:02
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
#############################
# ROM Toolbox Lite v. 5.9.8 #
# Feb 04, 2014 #
#############################
E:unknown volume for path [/storage/sdcard1/clockworkmod/backup/2014-02-04.17.00.21]
Can't mount backup path
/tmp/recovery.log was copied to /sdcard/clockworkmod/revoery.log. Please open ROM Manager to report the issue.
So for kicks I tried to restore the backup manually from /storage/sdcard1/clockworkmod/backup/*
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore complete!
rebooted kobo, everything seems to be in place. Boot back into recovery to make sure it's cwm not stock android.
Rom Toolbox Lite -> Rebooter -> Reboot Recovery. Bam, back into CWM.
So it is backing up to the external sdcard and can restore from there it just can't do it automagically!?
Regardless aside from not finding ext-sd everything seemed to work.
Have you disabled the auto recovery repair thing? I'm away from my computer at mo but if you kook at the arc recovery rom process there is a file you need too delete, that stops custom recovery getting replaced at boot
Sent from my GT-I8750 using XDA Windows Phone 7 App
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard.
I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
howlinwolf430 said:
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard.
I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
Click to expand...
Click to collapse
your Fstab is very odd looking, it does look exactly like what you find within android but the recovery ones I have been using are a little different
here is mind
Code:
/system ext4 /dev/block/mmcblk0p3
/sdcard datamedia /dev/block/mmcblk0p8 /dev/block/platform/mmcblk0
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p1
/boot emmc /dev/block/mmcblk0p2
/misc emmc /dev/block/mmcblk0p5
/staging emmc /dev/block/mmcblk0p6
/metadata emmc /dev/block/mmcblk0p7
That is for the 10HD, /SDcard in this case is an internal chip, there is no external chip, I have to have it set at "data media" but on the original Arc I have it set to "vfat". For the 10HD I cant manually mount /SDCARD, but it does do it itself when backing up and restoring but on the Arc it works fine, I can manually mount and unmount. Im a little unsure why its not working on the 10HD, a chap was going to have a look for me but hasn't yet got back to me.
format is
/mount_point Mount_type /location
below is the fstab of Astrali, his been a good help with mine
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p16
/cache ext4 /dev/block/mmcblk0p18
/data ext4 /dev/block/mmcblk0p21 length=-16384
/recovery emmc /dev/block/mmcblk0p13
/misc emmc /dev/block/mmcblk0p11
[B]/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B]
/system ext4 /dev/block/mmcblk0p17
/sys_boot vfat /dev/block/mmcblk0p3
/FOTA emmc /dev/block/mmcblk0p19
[B]/sdcard1 vfat /dev/block/mmcblk0p20[/B]
[B]/sd-ext auto /dev/block/mmcblk1p2[/B]
#added sd-ext support by Astrali
[B]/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B]
#added for rom manager support
Here we can see /external_SD and /sdcard are actually the same thing (?) mounted from blk1p1 (likely an external Sdcard) I don't know why there is two mounts, perhaps different software looking for the same thing but in different places?
/SDcard1 is mounted from blk0p20 so probably internal storage,
/sd-ext however is mounted from blk1p2, likely a second partition on an external card
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/sd-ext ext4 /dev/block/mmcblk0p2
keep this in mind, im just building a recovery img just now based on this...
Can you please upload kobo arc 7 stock rom or system.img
[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?