This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
How to mount 20170511-tinker-board-android-marshmallow-userdebug-v13.11.0.4.img?
#1
I've written the disk image to an SD card, but I have been unable to mount it under Ubuntu 16.04.

Looking at the disk image, I noticed that the the first 32KB is all zero - there's no partition table.

What is the structure of this disk image, and how can I mount the filesystems under Linux?

$ cat 20170511-tinker-board-android-marshmallow-userdebug-v13.11.0.4.img | xxd | head -3000
00000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000030: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
...
00007f50: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f60: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f70: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f80: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f90: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fa0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fb0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fc0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fd0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fe0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007ff0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00008000: 3b8c dcfc be9f 9d51 eb30 34ce 2451 1b98  ;......Q.04.$Q..
00008010: ff0c f236 0550 c8bb 3fec ddbd 0685 fab7  ...6.P..?.......
00008020: b3ab 6aea c868 e008 ad9d 6f9c 3c98 b08c  ..j..h....o.<...
00008030: 4513 541c 1d1b 1f15 a7f1 f00b e34e 0cc7  E.T..........N..
00008040: 6096 016a b5f0 e2c1 50c6 249e 12f7 588e  `..j....P.$...X.
00008050: 40b9 b7be 8bfa 25dd 74d7 6f59 467e 1341  @.....%.t.oYF~.A
00008060: eefd f591 39bc 7495 253c 1ae1 f157 3005  ....9.t.%<...W0.
00008070: caf8 729a 1be6 9d26 355d 812b 2b93 bd01  ..r....&5].++...
00008080: 3a54 0ca1 4b11 0698 a191 194a 4e92 301a  :T..K......JN.0.
00008090: f2b2 d5ae 596c 9e96 fdf4 ffa4 88e3 9f87  ....Yl..........
000080a0: 496c 3a76 6d3d 1aac 1e77 0a5e ff92 5261  Il:vm=...w.^..Ra
Reply
#2
(07-12-2017, 03:50 PM)chrisdew Wrote: I've written the disk image to an SD card, but I have been unable to mount it under Ubuntu 16.04.

Looking at the disk image, I noticed that the the first 32KB is all zero - there's no partition table.

What is the structure of this disk image, and how can I mount the filesystems under Linux?

$ cat 20170511-tinker-board-android-marshmallow-userdebug-v13.11.0.4.img | xxd | head -3000
00000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000030: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
...
00007f50: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f60: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f70: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f80: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007f90: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fa0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fb0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fc0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fd0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007fe0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00007ff0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00008000: 3b8c dcfc be9f 9d51 eb30 34ce 2451 1b98  ;......Q.04.$Q..
00008010: ff0c f236 0550 c8bb 3fec ddbd 0685 fab7  ...6.P..?.......
00008020: b3ab 6aea c868 e008 ad9d 6f9c 3c98 b08c  ..j..h....o.<...
00008030: 4513 541c 1d1b 1f15 a7f1 f00b e34e 0cc7  E.T..........N..
00008040: 6096 016a b5f0 e2c1 50c6 249e 12f7 588e  `..j....P.$...X.
00008050: 40b9 b7be 8bfa 25dd 74d7 6f59 467e 1341  @.....%.t.oYF~.A
00008060: eefd f591 39bc 7495 253c 1ae1 f157 3005  ....9.t.%<...W0.
00008070: caf8 729a 1be6 9d26 355d 812b 2b93 bd01  ..r....&5].++...
00008080: 3a54 0ca1 4b11 0698 a191 194a 4e92 301a  :T..K......JN.0.
00008090: f2b2 d5ae 596c 9e96 fdf4 ffa4 88e3 9f87  ....Yl..........
000080a0: 496c 3a76 6d3d 1aac 1e77 0a5e ff92 5261  Il:vm=...w.^..Ra

I had Android written to a 64GB card but it wouldn't boot. I gave up an used an 8GB I had spare. I've read around the problem here and elsewhere, and there seems to be a known issue with certain cards. However, I never tried verbatim the directions given on the asus tinkerboard product page:

dd if=/home/yihsin/Rockchip/aa7-demo/out/target/output.img of=/dev/sdc seek=0 bs=16M conv=notrunc

I just suspect that maybe these extra flags would help?
Reply
#3
Thanks for the extended dd options, but my point is that the *image*'s first 32KB are zeros, even before they are written to an SD card, hence there is no boot sector.  The "conv=notrunc" option only applies to file destinations. https://stackoverflow.com/a/20531600/129805  "seek=0" seems pointless, as it just tells dd to start writing at the beginning of the device, which is the default behaviour.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)