Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Partition Layout

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Partition Layout

    Partition Layout
    1 4 MiB bootloader U-Boot
    2 64 MiB reserved Not certain what this is
    3 512 MiB cache Android cache
    4 8 MiB env environment variables
    5 32 MiB logo boot/restore pictures
    6 32 MiB recovery Android Recovery
    7 8 MiB rsv unused all 0x00
    8 8 MiB tee unused all 0x00
    9 32 MiB crypt unused all 0x00
    10 32 MiB misc unused all 0x00
    11 512 MiB instaboot unused all 0x00
    12 32 MiB boot Android Boot
    13 1024 MiB system Android System
    14 rest data Android Data

    #2
    Anyone have a different partition layout, or know what the reserved partition is used for and where the data comes from?

    Comment


      #3
      Originally posted by calc View Post
      Anyone have a different partition layout, or know what the reserved partition is used for and where the data comes from?
      what command did you run to show the partition table? cat /proc/mtd is empty, however cat /proc/ntd returns the following on my nexbox A3 (same as A1):

      root@NEXBOX_A3:/ # cat proc/ntd
      dev: size erasesize name
      inand01: 400000 80000 "bootloader"
      inand02: 4000000 80000 "reserved"
      inand03: 20000000 80000 "cache"
      inand04: 800000 80000 "env"
      inand05: 2000000 80000 "logo"
      inand06: 2000000 80000 "recovery"
      inand07: 800000 80000 "rsv"
      inand08: 800000 80000 "tee"
      inand09: 2000000 80000 "crypt"
      inand10: 2000000 80000 "misc"
      inand11: 20000000 80000 "instaboot"
      inand12: 2000000 80000 "boot"
      inand13: 40000000 80000 "system"
      inand14: 30c200000 80000 "data"

      Also I haven't managed to get adb running on the box to download the rom image while in recovery mode, did you dump your using this method or something else?

      Comment


        #4
        The following should help:

        cat /proc/partitions
        ls -l /dev/block/platform/d0074000.emmc/by-num

        adb connect ipaddr:5555
        adb shell

        I dumped while running in regular mode, haven't tried getting into recovery yet.

        Comment


          #5
          Thanks calc, that worked well; for reference here is the output of the two commands:

          cat /proc/partitions
          major minor #blocks name

          253 0 512000 zram0
          179 0 15267840 mmcblk0
          179 1 4096 mmcblk0p1
          179 2 65536 mmcblk0p2
          179 3 524288 mmcblk0p3
          179 4 8192 mmcblk0p4
          179 5 32768 mmcblk0p5
          179 6 32768 mmcblk0p6
          179 7 8192 mmcblk0p7
          179 8 8192 mmcblk0p8
          179 9 32768 mmcblk0p9
          179 10 32768 mmcblk0p10
          179 11 524288 mmcblk0p11
          179 12 32768 mmcblk0p12
          179 13 1048576 mmcblk0p13
          179 14 12781568 mmcblk0p14
          179 96 4096 mmcblk0rpmb
          179 64 4096 mmcblk0boot1
          179 32 4096 mmcblk0boot0

          ls -l /dev/block/platform/d0074000.emmc/by-num
          lrwxrwxrwx 1 root root 21 Jan 1 2015 p1 -> /dev/block/bootloader
          lrwxrwxrwx 1 root root 15 Jan 1 2015 p10 -> /dev/block/misc
          lrwxrwxrwx 1 root root 20 Jan 1 2015 p11 -> /dev/block/instaboot
          lrwxrwxrwx 1 root root 15 Jan 1 2015 p12 -> /dev/block/boot
          lrwxrwxrwx 1 root root 17 Jan 1 2015 p13 -> /dev/block/system
          lrwxrwxrwx 1 root root 15 Jan 1 2015 p14 -> /dev/block/data
          lrwxrwxrwx 1 root root 19 Jan 1 2015 p2 -> /dev/block/reserved
          lrwxrwxrwx 1 root root 16 Jan 1 2015 p3 -> /dev/block/cache
          lrwxrwxrwx 1 root root 14 Jan 1 2015 p4 -> /dev/block/env
          lrwxrwxrwx 1 root root 15 Jan 1 2015 p5 -> /dev/block/logo
          lrwxrwxrwx 1 root root 19 Jan 1 2015 p6 -> /dev/block/recovery
          lrwxrwxrwx 1 root root 14 Jan 1 2015 p7 -> /dev/block/rsv
          lrwxrwxrwx 1 root root 14 Jan 1 2015 p8 -> /dev/block/tee
          lrwxrwxrwx 1 root root 16 Jan 1 2015 p9 -> /dev/block/crypt

          Comment


            #6
            I also managed to connect to adb using wifi, I didn't know I could do this just by using wifi, thank you very much!

            Sorry for hijacking the thread: I managed to dump the system partition to sdcard, I suppose i should be able to mount it on linux as an ext4 image; if I add and remove files will i then be able to push it back to the box (again using dd)?

            Thanks

            Comment


              #7
              You could just individually push the files themselves over if you want. If you try to push the whole fs over you probably will need to be in recovery with /system not mounted. I haven't tried to do that before.

              Comment


                #8
                Originally posted by mcklane View Post
                I also managed to connect to adb using wifi, I didn't know I could do this just by using wifi, thank you very much!

                Sorry for hijacking the thread: I managed to dump the system partition to sdcard, I suppose i should be able to mount it on linux as an ext4 image; if I add and remove files will i then be able to push it back to the box (again using dd)?

                Thanks
                Hi how did you manage to dump the above? I have the same like you but I would like to dump "data" which is mmcblk0p13 (which is mmcblk0p14 in yours)?
                I am using AirDroid and Terminal app so don't need adb etc. Which commands did you execute to dump stuff?

                Comment

                Working...
                X