[5 Aug 2012][TOOL][CWM] zImage Injector v1.1 [MULTI-REPACK][AROMA] - FIXED

Search This thread
By:
Advanced…
besttt

besttt

Senior Member
Jun 19, 2012
3,990
4,512
54
athens
Daekin said:
in the log you can see:
Code: 
> Building boot.imgabout to run program [/tmp/mkbootimg.sh] with 1 args
BOARD_KERNEL_CMDLINE 
BOARD_KERNEL_BASE 200000
PAGE_SIZE 131072
[COLOR="red"][B]Error: wrong pagesize: 131072[/B][/COLOR]
BOARD_KERNEL_CMDLINE 
BOARD_KERNEL_BASE 200000
PAGE_SIZE 131072
[B][COLOR="Red"]Error: wrong pagesize: 131072[/COLOR][/B]
cat: can't open '/tmp/ramdisks/boot.img-cmdline': No such file or directory
cat: can't open '/tmp/ramdisks/boot.img-base': No such file or directory

usage: mkbootimg
       --kernel <filename>
       --ramdisk <filename>
       [ --second <2ndbootloader-filename> ]
       [ --cmdline <kernel-commandline> ]
       [ --board <boardname> ]
       [ --base <address> ]
       [ --pagesize <pagesize> ]
       [ --ramdiskaddr <address> ]
       -o|--output <filename>
run_program: child exited with status 1
so input and output kernel have some unusual (and unsupported page size).
I have never used non-HTC (a.k.a AOSP and CM) kernels so I dot exactly know why the page is that.
try repacking Sense kernels and post log to see what page size is used there...

but I think you would need updated unpacbootimg/mkbootimg binaries for your kernels...
Click to expand...
Click to collapse
where i can find that binaries???look the log my friend now all ok if i use kernels from cm9 why cant create kernels from cm 10 or cm 10.1 they are for same devises not other cant create kernels above cm9 kernel why?
 

Attachments

  • 2recovery.rar
    2.1 KB · Views: 13
Last edited:
Daekin

Daekin

Senior Member
Mar 23, 2009
2,107
1,872
Bratislava
Samsung Galaxy S21 Ultra
hard to say where to find working binaries....search XDA forums in CM10 threads...

the reason for not being able to repack those kernels is because CM10 and above use different page size parameter inside boot.img (problably because either it is JB kernel or it is 3.x kernel)
 
  • Like
Reactions: besttt
besttt

besttt

Senior Member
Jun 19, 2012
3,990
4,512
54
athens
Daekin said:
hard to say where to find working binaries....search XDA forums in CM10 threads...

the reason for not being able to repack those kernels is because CM10 and above use different page size parameter inside boot.img (problably because either it is JB kernel or it is 3.x kernel)
Click to expand...
Click to collapse
ok and where to put that binaries if i found
 
You must log in or register to reply here.

Similar threads

mike1986.
[ROM] Android Revolution HD 33.1 | High Quality & Performance | Sense 5 | 4.18.401.3
Replies
50K
Views
9M
C
cmaz
hamdir
HTC Flagship 2012 - HTC One X (Endeavor) - Tegra 3 - Mega Information Thread
Replies
20K
Views
3M
hamdir
hamdir
m0narx
[ROM][05.06] Team Venom presents: ViperX 4.1.1 - welcome to the future
Replies
26K
Views
4M
izzulhafiz
izzulhafiz
tbalden
[ROM][official] HTC OneX CyanogenMod 10.1 (4.2) release
Replies
16K
Views
3M
IllUMINATUz
IllUMINATUz
baadnewz
  • Poll
[ROM]InsertCoin 19.0-4 | SENSE 5 | JellyBean 4.2.2 | 4.18.401.2
Replies
10K
Views
2M
pressytcn
pressytcn

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 88
    Daekin
    Daekin
    I have created small CWM package that can be used to inject zimage from one boot.img into other boot.img so that one can create proper boot.img for specific ROM that contains desired ramdisk.

    NEW: Now supports full multi-source to multi-target repacking!
    Click to expand...
    Click to collapse


    Usage
    1. download attached RAR
    2. unpack it and place all source boot images (with new kernels) into tools/kernels folder
    3. place destination boot images (with target ramdisks) into tools/ramdisks folder
    4. pack all unpacked content into ZIP that can be flashed in CWM (original two folders must be in the root of ZIP to be CWM compatible)
    5. put repacked injector ZIP file to SD card
    6. flash the ZIP file which will result in creating new boot images in the root of internal SD card (they will be named using following pattern: kernel-ramdisk.img)
    7. mount as USB mass storage and grab new boot images to PC

    Screenshots

    2cih4qq.gif
    23kce81.png
    zkiypf.png
    et7daf.png



    Troubleshooting

    Problem
    You must use this tool prior using USB mass storage in recovery or else output boot images will not be created.
    It is a bug of recovery.
    Click to expand...
    Click to collapse

    Solution
    Copy ZIP file to SD card in ROM and then reboot to recovery or reboot recovery once more prior using the tool.
    Click to expand...
    Click to collapse


    Download
    thunder07 said:
    Hi i revamped zimage injector with aroma and added a couple of options to it,
    i added repack from sd option where the kernels and ramdisk are take from /sdcard/kernels/ & /sdcard/ramdisks/ to make it easier to manage through the phone,
    i also added a flash option so that you can flash kernel through the phone after repacking it (although we cant use it some ppl with s-off can make use of it),
    kernel&ramdisk must be named boot.img and placed in the zip or in the sdcard in correct folders for this to work, also repack a single kernel works in the same way.
    lastly i added repacks into a repack folder to keep the sdcard organised... this is especially helpful for ROM repackers
    i just though you should release it..
    Click to expand...
    Click to collapse


    Compatibility

    This tool should be compatible with all devices running CWM-based recovery.
    You will only need to replace the update-binary with the one for your device.
    View
    6
    Daekin
    Daekin
    new UPDATE

    finally managed to make next version of injector tool - as promised it is able to repack one kernel into multiple ROMs at once....can automate a lot of work ;)
    View
    4
    Daekin
    Daekin
    Update - multi-source Repack

    I have added new version that is capable of repacking several kernels for one ROM...
    the principle is the same as in version 0.2 only there is one destination boot.img and several source boot.img-s
    View
    3
    Daekin
    Daekin
    Update v1.0 final

    OK, I added final version of injector in the OP

    ENJOY!
    View
    3
    Daekin
    Daekin
    KLUVJ said:
    hey, i was wondering if any of you can clarify things....

    so unzip the rar
    put the boot.img of a custom kernel in the specified folder
    put all the boot.img of rom(s) original boot.img in other folder
    repack all the files into zip
    (NO NEED TO SIGN)?
    and flash in cwm.

    after that, you will get the boot.img you need to flash.

    another question, if you put multiple original boot.img, how will the repacked boot.img be specified so as to know which rom its for?

    Thanks
    Click to expand...
    Click to collapse

    1. cwm recovery by default does not check signatures, so I never signed zips to save time, I only checked MD5 sums of downloaded ones to verify thay downloaded OK
    2. the resulting files will be called as originals, so you could do this:
    you put boot.img in src_img folder and you put boot_arhd6.img, boot_ic630.img and boot_coredroid.img in dst_img folder
    and you will get boot_arhd6.img, boot_ic630.img and boot_coredroid.img files on root of SD card that will contain new zImage from boot.img file
    View

New posts