1. Check out our companion app, Forums for Android! Download from Google Play

Little help with boot.img repack...

Discussion in 'ROM Development' started by exile1975, Apr 1, 2012.

  1. exile1975

    exile1975 Well-Known Member
    Thread Starter
    43

    Nov 24, 2011
    213
    47
    43
    Cupertino, CA
    I've been at this for days learning to unpack my boot.img,, now I'm trying to repack it and for some reason it always comes out too small, a little more than half the original. I'm using cygdrive on windows. I've got a samsung admire using the stock kernel. Judging from the size I'd say it isn't re adding the kernel but I'm not sure.. Any help is much appreciated
     

    Advertisement

  2. karandpr

    karandpr Well-Known Member
    443

    Feb 16, 2011
    2,951
    1,815
    443
    Male
    unpack it again .
    if you have zimage and ramdisk then it was packed properly .

    Usually stock ROM are/have boot.img dumps which are larger in size .
    Dont be shocked if the packed kernel comes 50 p.c of size .
     
    exile1975 likes this.
  3. exile1975

    exile1975 Well-Known Member
    Thread Starter
    43

    Nov 24, 2011
    213
    47
    43
    Cupertino, CA
    Its unpacking fine, and repacking fine, but when I mkbootfs it comes out half the size of the original. I'm using the correct page size and base. Next doing a usb linux install. F.ck windows

    Edit:
    Wait, are you saying to use it? That its normal?

    Edit 2:
    Holy crap. I was afraid to try because of the size difference, but it works. Thank you so much for taking the time to answer
     
  4. karandpr

    karandpr Well-Known Member
    443

    Feb 16, 2011
    2,951
    1,815
    443
    Male
    It's perfectly normal.
    I have seen "10 MB" boot.img compressed to roughly 2-3 MB and they worked fine .
     

Share This Page

Loading...