Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Nand Offsets - some info required

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

    Nand Offsets - some info required

    Guys, I am making some software and need to know the offsets for certain parts of the Minix Neo x7 nand.I have the following in my NAND after checking:

    Code:
    Nand size (count 0x2000000 = 17179869184 bytes)
    
    
    Param & Loader (4194304 bytes) (4mb) start offset - 0x00000000 -count (0x2000)
    Misc (4194304 bytes) (4mb) start offset - 0x00002000 - count (0x2000)
    Kernel (16777216 bytes) (16mb) start offset - 0x00004000 - count (0x8000)
    unknown 1 - (12582912) (12mb) start offset - 0x0000C000 - count (0x6000)
    Boot (16777216 bytes) (16mb) start offset - 0x00012000 - count (0x8000)
    unknown 2 - (12582912) (12mb) start offset - 0x0001A000 - count (0x6000)
    Recovery (33554432 bytes) (32mb) start offset - 0x00020000 - count (0x10000)
    Backup (67108864 bytes) (64mb) start offset - 0x00030000 - count (0x20000)
    Cache (134217728 bytes) (128mb) start offset - 0x00050000 - count (0x40000)
    User Data (4294967296 bytes) (4096 mb) start offset - 0x00090000 - count (0x800000)
    kpanic (4194304 bytes) (4mb) start offset - 0x00890000 - count (0x2000)
    System (637534208 bytes) (608mb) start offset - 0x00892000 - count (0x130000)
    unknown 3 - (6291456) (6m) start offset - 0x009c2000 - count (0x3000)
    User (11934892032 bytes) (11382mb) start offset - 0x009c5000 - count (0x163B000)
    I am looking to find the correct offsets for the loader and parameter and also what is stored at the offsets - unknown 1,2,3Thanks.
    Last edited by mrdude; 02 May 2014, 07:20.

    #2
    We may be able to help each other a bit. Pm me if your interested

    Sent from my MB860 using Tapatalk

    Comment


      #3
      Originally posted by LawlessPPC View Post
      We may be able to help each other a bit. Pm me if your interested Sent from my MB860 using Tapatalk
      Some more usefull info:

      I found that for my minix neo x7 -


      user.img (start 0x9c5000 - count 0x14f7000) - (11255414784 bytes) - internal sd card.


      I also found that the unknow parts in the nand - are just blank spaces between the partitions and don't contain any data - just ffff's. Basically the nand is just storage area - a loader boots the minix and the parameter file tells where the partitions are located. Each partition contains data. User.img is fat32 and can be opened on a pc with ultraiso. System.img can also be opened with ultraiso.

      Found partition size in user.img with winhex:


      (partition size - offsets 20 to 23, show this - 00 70 4f 01 = 14f7000) - also shown at offsets 420-423


      14f7000 - converted to decimal = 21983232 (pages)


      1 page = 512 bytes so 21983232 pages multiplied by 512 = 11255414784 bytes (10734 meg)

      A full brick (corrupted loader) can be recovered by putting the minix in MaskROM mode - you can do this by shorting out pins 8&9 on the nand.

      An image can be built by using dumps from your minix:

      Afptool -pack ./ new.img

      Once the image is built it can be put into flashable format:

      RKImageMaker.exe -RK31 RK3188Loader(L)_V1.24.bin new.img flashme.img -os_type:androidos

      All tools used for flashing and image manipulation can be found on this forum.
      Last edited by mrdude; 20 May 2014, 13:30.

      Comment


        #4
        Fantastic bit of info *80)

        Sent from my MB860 using Tapatalk

        Comment

        Working...
        X