View Single Post
Old 05-29-2012, 03:06 AM   #255
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,827
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by ppoo View Post
@geekmaster: THANKS!!! My KT is COMPLETELY DEBRICKED
I think you should add these code to your topic, to check whether image is OK:
Code:
mount -o loop -text3 /mnt/us/mmcblk0p1-kt-5.0.0.img /mnt/mmc
ls /mnt/mmc
umount /mnt/mmc
If you want to check it, why not run fsck on it?

losetup -f <find next device, here, assume loop1>
losetup /mnt/us/mmcblk0p1-kt-5.0.0.img /dev/loop1
fsck -f /dev/loop1
losetup -d /dev/loop1

WARNING: Do not run fsck on a mounted filesystem. Some versions of the command do not output that warning message.
Just listing the directory (with ls) tells you next to nothing about the condition of the file system.

Last edited by knc1; 05-29-2012 at 09:12 AM.
knc1 is offline   Reply With Quote