• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Utility] Android Image Kitchen & Flasher APK

Status
Not open for further replies.
Search This thread

bigsupersquid

Senior Member
Sep 22, 2010
2,253
1,671
BFE, MO
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.
 

atoxyd

Senior Member
Jan 3, 2014
72
65
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.

Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.
 

Attachments

  • 1458932491006.jpg
    1458932491006.jpg
    83.6 KB · Views: 283

bigsupersquid

Senior Member
Sep 22, 2010
2,253
1,671
BFE, MO
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.

I can unpack, edit, and repack successfully.

but, it wont boot.

I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.

the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
 
Last edited:

atoxyd

Senior Member
Jan 3, 2014
72
65
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay ;)
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,910
33,750
Halifax
GT-i9250
Google Nexus 4
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay ;)

The scope of my tools is for Google's Android image standard as defined in the bootimg.h header from AOSP/CM. My tool forks have the widest support available for images which are standards compliant, supporting all commonly used ramdisk compression formats.

Supporting Sony's ELF, MTK's labeled and Samsung's headerless image formats along with the standard images (not to mention Samsung's and others' various deviations based on the standard header) and having the script/app differentiate between them would be a very large and difficult undertaking indeed. If that's your plan then I wish you the best of luck in your efforts. :)
 
Last edited:

bigsupersquid

Senior Member
Sep 22, 2010
2,253
1,671
BFE, MO
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.

here, for your devices.xml

Code:
   <!-- Desire 816 a5 (710C) added by bigsupersquid -->
    <device>
        <model>710C</model>
        <kernel>/dev/block/mmcblk0p40</kernel>
        <recovery>/dev/block/mmcblk0p41</recovery>
        <cache>/dev/block/mmcblk0p42</cache>
    </device>

thanks for your work.
eagerly awaiting your open source as well ;)
 
  • Like
Reactions: atoxyd

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,910
33,750
Halifax
GT-i9250
Google Nexus 4
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.:cowboy:
This apk need root.

All credit of unpak/repack tools used in my apk are to @osm0sis

Thank you for adding the appropriate credit back to your post. Patching, cross-compiling and scripting has taken significant work. :) :good:

The only other thing that I'd ask is that you do not use the name of Android Image Kitchen or AIK in the title of your app. I'd like to suggest maybe "Image Editor and Flasher" as a snappy alternative? :)
 
Last edited:

atoxyd

Senior Member
Jan 3, 2014
72
65
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.

here, for your devices.xml

Code:
   <!-- Desire 816 a5 (710C) added by bigsupersquid -->
    <device>
        <model>710C</model>
        <kernel>/dev/block/mmcblk0p40</kernel>
        <recovery>/dev/block/mmcblk0p41</recovery>
        <cache>/dev/block/mmcblk0p42</cache>
    </device>

thanks for your work.
eagerly awaiting your open source as well ;)

Thank you my friend , you are the only one who supported me , and from the beginning.
 

bigsupersquid

Senior Member
Sep 22, 2010
2,253
1,671
BFE, MO
Thank you my friend , you are the only one who supported me , and from the beginning.

it's a useful project, definitely worth a little testing and feedback.
besides, i remember what a pain it was getting my xda account eligible for posting the project i was all gung-ho about sharing (optimus v boot from sd card if i remember correctly)
sharing is cool, but a lot of the feedback tends to be annoying when there's no logs or other usable information, just "it's broken" or "can you implement for me on device XYZ."
 
  • Like
Reactions: atoxyd

atoxyd

Senior Member
Jan 3, 2014
72
65
I can unpack, edit, and repack successfully.

but, it wont boot.

I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.

the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
Did you have an unlocked bootloader ?
 

bigsupersquid

Senior Member
Sep 22, 2010
2,253
1,671
BFE, MO
nothing changed on the device, unlocked and still s-on, I'm not sure what went wrong the first try.
PEBKAC error probably
(problem exists between keyboard and chair)
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.:cowboy:
    This apk need root.

    All credit of unpak/repack tools used in my apk are to @osm0sis
    2
    Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay ;)

    The scope of my tools is for Google's Android image standard as defined in the bootimg.h header from AOSP/CM. My tool forks have the widest support available for images which are standards compliant, supporting all commonly used ramdisk compression formats.

    Supporting Sony's ELF, MTK's labeled and Samsung's headerless image formats along with the standard images (not to mention Samsung's and others' various deviations based on the standard header) and having the script/app differentiate between them would be a very large and difficult undertaking indeed. If that's your plan then I wish you the best of luck in your efforts. :)
    1
    hey, ran more tests.
    no issues with the dtb or other functions either.
    backup and flash functions working fine too.

    here, for your devices.xml

    Code:
       <!-- Desire 816 a5 (710C) added by bigsupersquid -->
        <device>
            <model>710C</model>
            <kernel>/dev/block/mmcblk0p40</kernel>
            <recovery>/dev/block/mmcblk0p41</recovery>
            <cache>/dev/block/mmcblk0p42</cache>
        </device>

    thanks for your work.
    eagerly awaiting your open source as well ;)
    1
    Thank you my friend , you are the only one who supported me , and from the beginning.

    it's a useful project, definitely worth a little testing and feedback.
    besides, i remember what a pain it was getting my xda account eligible for posting the project i was all gung-ho about sharing (optimus v boot from sd card if i remember correctly)
    sharing is cool, but a lot of the feedback tends to be annoying when there's no logs or other usable information, just "it's broken" or "can you implement for me on device XYZ."
    1
    I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.