Tutorial Modify boot.img for activating a2sd/link2sd features in gingerbread

Warning: I am not responsible for any damage caused to your handset. If you do not understand, you should ask until you understand before starting. I’ve managed to practice this way on the standard ROM Gingerbread 2.3.3 and 2.3.4 are obtained from samfirmware. com

Requirements: unix system.

  1. Download Bootimgutils and extracts, eg Bootimgutils into folders. We will get 3 files: mkbootimg, repack_bootimg.pl, split_bootimg.pl.
  2. Extract the firmware (If the firmware file is not a one-pack, just extract the firmware files with the name CODE_ …..).
  3. Copy the file boot.img reply was obtained from the extraction results into folders Bootimgutils (in step 1).
  4. By using the console, navigate to the folder active directory Bootimgutils before, and then run the command

    ./split_bootimg.pl boot.img

  5. Once successful, it will appear two new files, they are boot.img-kernel and-ramdisk.gz boot.img.
  6. Then type the following command:

    mkdir ramdisk
    cd ramdisk
    gzip -dc ../boot.img-ramdisk.gz | cpio -i
    cd ..

  7. This will bring up a new folder called ramdisk. Open the folder, then locate the file named init.rc. Open the file using a text editor init.rc.
  8. Find the section that stated as follows:
    Remove the hash mark (#) in the second row. So it becomes like the following

    #service flash_recovery /system/etc/install-recovery.sh
    # oneshot

    Remove the hash mark (#) in the second row. So it becomes like the following:

    service flash_recovery /system/etc/install-recovery.sh

    Warning: Do not change other parts if you do not know what you do.

  9. Back to the console, then run the command

    ./repack_bootimg.pl boot.img-kernel ramdisk bootnew.img

  10. Boot.img a new file is created with the name bootnew.img. As a precaution, rename the original file boot.img (in step 3) into another name, eg boot.img.orig. Then rename bootnew.img become boot.img.
  11. Copy the file to a folder boot.img new firmware extracted earlier. This process will overwrite the original boot.img file in that folder was extracted firmware.
  12. If you do not use the firmware with one type of package, you can skip and go to step 16.
  13. Navigate to the folder active directory console firmware extraction results. Then type the command as follows:

    tar -H ustar -c arm11boot mibib oemsbl qcsbl > APBOOT_NAME_IS_UP_TO_YOU.tar

  14. next step

    tar -H ustar -c csc.rfs > CSC_NAME_IS_UP_TO_YOU.tar
    md5sum -t CSC_NAME_IS_UP_TO_YOU.tar >> CSC_NAME_IS_UP_TO_YOU.tar

  15. next step

    tar -H ustar -c amss > MODEM_NAME_IS_UP_TO_YOU.tar
    md5sum -t MODEM_NAME_IS_UP_TO_YOU.tar >> MODEM_NAME_IS_UP_TO_YOU.tar

  16. next step

    tar -H ustar -c boot.img recovery.img system.rfs > CODE_NAME_IS_UP_TO_YOU.tar
    md5sum -t CODE_NAME_IS_UP_TO_YOU.tar >> CODE_NAME_IS_UP_TO_YOU.tar

  17. Now your  firmware are ready for  flashing process using odin. Do not forget to order:

    PDA => CODE
    CSC => CSC

Download support file

I already tried this using ubuntu 11:04, both on firmware 2.3.3 or 2.3.4 Gingerbread

nb: for gingerbread 2.3.3, if using link2sd, after each reboot, then dex and lib should be linked to re-application.
If you are using windows, could use a cygic win or use vmware.

For those who want to try GingetBread a2sd/link2sd but don`t want to use the custom ROM, can try this way.

thanks to ge88 for tutorial

Related Post