Re: Debian on my tablet?
On Sun, Jan 22, 2017 at 12:21:50PM +0000, Rodolfo Medina wrote:
> Paul Wise <pabs@debian.org> writes:
>
> > Do you get anything other than 'data' when running file on them?
>
> I do with mmcblk0p4; mmcblk0p7 is too big as I said; and
>
> ~$ file mmcblk0p1
> mmcblk0p1: DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x0,0,0), end-CHS (0x0,0,0), startsector 164864, 3145728 sectors; partition 2 : ID=0x83, start-CHS (0x0,0,0), end-CHS (0x0,0,0), startsector 3310592, 258048 sectors; partition 3 : ID=0x83, start-CHS (0x0,0,0), end-CHS (0x0,0,0), startsector 3568640, 4291398655 sectors
>
> $ file mmcblk0p2
> mmcblk0p2: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
>
> ~$ file mmcblk0p3
> mmcblk0p3: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
>
> $ file mmcblk0p5
> mmcblk0p5: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
>
> $ file mmcblk0p6
> mmcblk0p6: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
>
>
>
> >> There are no such files. In /dev/block/platform/mtk-msdc.0 there is
> >> only:
> >
> > Woops, that was a typo for /dev/block/platform/mtk-msdc.1
>
> mtk-msdc.1 is no more there:
>
> $ adb ls /dev/block/platform/
> 000041ed 0000003c 588464b9 .
> 000041ed 000001cc 588464c0 ..
> 000041ed 00000104 588464b9 mtk-msdc.0
>
> Thanks,
>
> Rodolfo
>
First, mtk-msdc.1 is probably a external SD card.
Then, it seems you have a system that likely boots from FAT, maybe? I am
not familiar with the mediatek family, but that could be possible.
You should assign that mmcblk0p1 file to a loop device, then create the
partitions of it, mount them, and check it.
Do it in your own Debian desktop:
sudo losetup /dev/loop0 mmcblk0p1
sudo kpartx -a /dev/loop0
sudo mount /dev/loop0p1 /mnt/
ls /mnt/
But, please, do some of the home work, and if anything fails, look out
for the manpages of the commands on what they do, how you should use
them, or read the errors. For example, it might be that mount will fail
because loop0p1 is not there, so check what kpartx has created for you,
maybe list what is in /dev/, what is in /dev/mapper/, do ls /dev/loop0*,
etc.
Do an fdisk on /dev/loop0 too, or even directly on mmcblk0p1. fdisk -l
/dev/loop0 would tell you what partitions are there. But note: loop0 is
assigned the contents of mmcblk0p1 only after you run the losetup
command.
About the very large partitions from your gadget, they may be the
system/data/userdata filesystems that Android uses. I usually copy only
the small partitions, but it's hard to say what is small and what is
not. In order to check the size of a block device before copying it, you
may check on /sys/block/$BLOCKDEVPATH/size. Left as an exercise to find
what $BLOCKDEVPATH is for each partition. I can't help you more with
that.
Cascardo.
Reply to: