Database Users

Porting ClockworkMod - Kernel is 1.8GB!

Hey guys,
I am trying to port the ClockworkMod recovery to the incredible S, and everything goes fine until the last step, getting the files neccessary from the recovery image using mkvendor.sh works, but it produces a kernel that is 1.8GB (!), so when I go to build, the recovery is far too large and it aborts.
Anyone know why this might be happening? Surely the kernel can't be that big, the recovery partition is only ~8.5MB and the dd of the recovery come out the same, so how is the kernel so huge?
Any help will be greatly appreciated
EDIT I have uploaded the dump if anyone needs / wants to take a look: http://www.multiupload.com/JSY1HUI6Y7

What guide are you following, if any?
For example

marcnvidic said:
What guide are you following, if any?
For example
Click to expand...
Click to collapse
Yes, that's the guide I initially used

l0st.prophet said:
produces a kernel that is 1.8GB (!)
Click to expand...
Click to collapse
Try this,
Get a working ROM for the Incredible S, and extract boot.img
Extract the the kernel from the .img and place it in your
Code:
<android-source-root>/out/target/product/<phone>/
-- overwriting the 1.8GB kernel (ie recovery-kernel)
Then run
Code:
make recoveryimage
to pack it into an img

I got a file called boot.img-kernel.gz which wouldn't open as an archive so I just renamed it 'kernel' and that got the image built... now to see if it flashes! thanks for the pointer

[Guide] Create your own ROM (Beginners Welcome)

Did you Ever Wanted your Own Custom ROM? Did you don't understand other Guides? Do you don't Like ROM Kitchens? Than this Guide is the right Guide for you! Just Try It and you can create your Own Custom ROM!
​​​

General Information​
So, Before we start with this Guide, i just want to tell you some General Informations about [highlight]Custom Roms[/highlight]. When you buy your phone, you will have a [highlight]Stock ROM [/highlight]installed. A [highlight]Stock ROM [/highlight] is just that Software, your Company has created, especially for your phone. It's a Software like Android 2.3.4 with Touchwiz 4 or Android 4.0.4 with Sony UI. Those Softwares may be good, but there are many Things to Improve, for the Best Xperience, while using your Phone. A [highlight]Custom ROM [/highlight]can be complete different to [highlight]Stock ROM [/highlight], like [highlight]Cyanogenmod 10 [/highlight], or be just a improved Version of the [highlight]Stock ROM [/highlight]. To Build a [highlight]Custom ROM [/highlight] you need to know a few Words, and have a Phone with Root Acess + S-OFF / Unlocked Bootloader. So in this Guide we will concentrate on the Easy Way, the [highlight]Improved Stock ROM [/highlight]. You Can also Build a [highlight]ROM [/highlight] out of Source from Google, but thats too complicated for beginners. Setting up compile envirment can be quite complicated . So let's take a look at stuff you need to know:
[highlight]Root Acess[/highlight]
Complete Acess to all System Files, like Administrator on Windows. To Root Your Phone, search XDA. Rooting your Phone is done by putting su library to /system and manage acess with SuperSu or Superuser. When you buy your Phone, it doesn't have Root Acess. Root Acess is needed for installing CWM, mount your /system as Read & Writeable ----> You can delete system files, and installing apps to /system/app, by copying them to /system/app. By Rooting your Phone you loose Warranty, but you can reinstall stock software and no one will notice
[highlight]ClockWorkMod Recovery (CWM)[/highlight]
Recovery Mode of your Phone. In Recovery you can install flashable zips and roms, wipe and format your device, mount different partititons and fix permissions... To Get CWM search XDA. There are different Ways for every Device. You can enter recovery before your device is fully booted, and since touchscreen drivers are not yet available you need to use the volume buttons for controlling the recovery. There are different ways of entering cwm for every device.
[highlight]Rom & Kernel[/highlight]
ROM means: [highlight] Read-Only-Memory[/highlight] . The Funny Thing is that we can Read and Write on our Read-Only-Memory. Anyway, its a partition which includes large parts of the OS ----> operating system of your Phone. In a [highlight]ROM[/highlight] for Android Phones are included apps, framework, libs & many more and since android is modular, there is an app for everything (keyboard, launcher, statusbar). Together with a [highlight]Kernel[/highlight] it's the "Life" of your Phone.
The Kernel is needed for a working Phone. You Can Install Stock or Custom Kernel. When you buy a Phone Stock Kernel is preinstalled of course. The kernel includes many drivers, controlls the cpu and does many more... Just rember that word ​​

General Information
1. Install Stock ROM to your Phone - This Can be Done by Flashing via Flashtool or Odin. You Need a Clean Base to Start. Recomnend is a Stable, Official ROM, like Gingerbread, Ice Cream Sandwich or maybe Jelly Bean.
2. Root the ROM. This Can be done with Different Tools, Very Popular is for Example SuperOneClick Tool.
Just search for "my device name root" in xda if your not sure
3. Improve Stock ROM on Your Phone. So, After You Have Installed the Stock ROM and Rooted the ROM You Can Start. Now You Need To Change Some Things, To Make the Stock ROM to a Customized ROM. You Can do a lot Things, Here are a Few Examples:
- Install Latest Superuser SuperUser
- Install Latest BusyBox Auto-Installer
- Supercharge the ROM, enable Zipalign etc.. ----> here
- Remove Bloatware. Use Es File Explorer to remove not longer needed apps in system/app partitition
- Tweak Build.prop by going with ES File Explorer to /system and editing your build.prop. now you can change the Name shown in Settings and do a lot more ----> http://forum.xda-developers.com/showthread.php?t=1227269
- Change the Bootanimation. You can find a lot of them by Going to themes and apps of your own device.
- Add or Change Apps. Check out Themes and Apps Selection of Your Device and Install a few Of Them, If You Are Allowed to use MooDeD Apps created by other Users
3.1 Now Delete/remove all backups in clockworkmod/backup folder
4. Now Make Sure You Have Installed CWM. If You Have Changed a Lot Things and You Think Your ROM is good enough, Boot to CWM, select wipe data/factory reset and Boot up again. If You Are Still able to Boot, Check the ROM for Bugs or Problems. Write them Down. Try to fix them. You can always take a logcat (adb logcat)
Than Boot again to CWM select wipe data / Factory reset ---> yes advanced ---> wipe battery stats ---> yes. Now Select backup & Restore ---> Backup.
5. Connect Your sd card to PC and go to Clockworkmod/backup folder. Now Go to the only 1 backup folder and copy "system.img" to your PC.
6. On PC Open Yaffey and Choose Open ---> system.img and than extract to empty folder called system.
7. Now You Will Get a Folder "system" which contains the System of your Phone. Now Create an Empty .zip file and paste in extracted Meta-inf folder Download and copy folder "system" inside. ROM should be flashable for NOW!
Remeber to mount /system before flashing // replace with mount Script for ur device... You can check this by dowoading any rom 4 ur device
NOTE: This has nothing to do with developmemt or original development in any way. Its theming a stock ROM in the simplest way...
Just Press thanks if this was helpfull in any way...

How to
[[ Placeholder ]]

[[ Placeholder ]]

[!][RESERVED][!]
[[ Placeholder ]]

1 year later:laugh:

Sorry... I will finish this guide later...

And so on...
Sent from my GT-S7500 using xda premium

To infinity and beyond!

saiz136 said:
To infinity and beyond!
Click to expand...
Click to collapse
Beyond Smart xD

Updated Thread and Added a First Guide

so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin

ruizit0 said:
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
Click to expand...
Click to collapse
There is a guide lol

jader13254 said:
There is a guide lol
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
ahaha sorry .. i was thinking that was a little intro explaining clocklowrk and stuff .. to a coocking tutorial ahaha
maybe you can expecify more in title or something
nice tutorial to create a rom this way .. i read somewhere that the next clockwork will have this feature

Will try..
Sent from my GT-N8000 using Tapatalk 2

kaipro said:
Will try..
Sent from my GT-N8000 using Tapatalk 2
Click to expand...
Click to collapse
You need different commands for wiping on g Note, just search your device forum
Sent from my LT18i using xda app-developers app

Where is the system.img? I didnt have one when i backed up with cwm

very noob-friendly !

CovXX said:
Where is the system.img? I didnt have one when i backed up with cwm
Click to expand...
Click to collapse
check clockworkmod/backup folder... there should be system.xxxx.img

[Q] What about the Alcatel OT Fire C (4019X)?

Hello!
I've been trying to see if there's any root exploits, ROMs, whatever for this phone. Is it Hamachi (4012) compatible? Or is it another species? It does seem there's not much about it.

The only thing I've found is this mail thread.
comments DOT gmane DOT org / gmane DOT comp DOT mozilla DOT devel DOT b2g / 12487
The Fire C is a Jelly Bean based one. Start from there.
If I can successfully flash mine will post results. Wish me luck.
resetreboot said:
Hello!
I've been trying to see if there's any root exploits, ROMs, whatever for this phone. Is it Hamachi (4012) compatible? Or is it another species? It does seem there's not much about it.
Click to expand...
Click to collapse

mancvso said:
The only thing I've found is this mail thread.
comments DOT gmane DOT org / gmane DOT comp DOT mozilla DOT devel DOT b2g / 12487
The Fire C is a Jelly Bean based one. Start from there.
If I can successfully flash mine will post results. Wish me luck.
Click to expand...
Click to collapse
Nope. Bricked phone.
Anyone knows how to use this files?
forum DOT gsmhosting DOT com / vbb / f272 / flash-file-request-alcatel-4019x-1883599

Where did you find these files? Can you point me to them?
Maybe I can make something out of it. The MTK Droid Tools is totally unable of dumping anything from this phone and it's supposedly designed for these kind of phones (the chipset is a MediaTek).
If only I could snatch the boot image...! But the /dev/ block devices do not make any sense to me, otherwise I'd have at least something to go back when I screw the boot loader.

The URL is in the post above, just replace " DOT " with "." and delete spaces.
Anyway, the direct link is
mediafireDOTcom/?t6x77dxpb9bucbf
Which one is boot, system, userdata? Do you have the original file sizes?
I've tried with various Hamachi (4012X) boot.img but none of them works.
PD: I cannot post links.

I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.

Wonderful! This is really useful info.
Now we can try to couple it with the FFOS SDK and try to get root and maybe upgrade to 2.0...
D'loading so I can start hacking...

resetreboot said:
Wonderful! This is really useful info.
Now we can try to couple it with the FFOS SDK and try to get root and maybe upgrade to 2.0...
D'loading so I can start hacking...
Click to expand...
Click to collapse
Please do so! An upgrade to 2.x is crucial even for copy/pasting text.

mancvso said:
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Click to expand...
Click to collapse
Great news, remember you can type *#3228# to know what are all these filenames in your device.
I have a 4019M (sold unlocked in this country) and I am interested on this, however I don't have experience flashing yet, as this is my first smartphone. If you need to do some tests from here for this particular device to get root and upgrades, feel free to ask!
This device is qualcomm based and gonk is jelly bean based, if I recall correctly.

Some news, they finally uploaded this month 4019X / 4019A GPL compliance sources into sourceforge · net / projects / alcatel / files /

Some progress to get a proper factory image
When using One Touch Update, I tried to figure what happens with the factory image download from the vendor. It downloads a bunch of 64 KiB files stored in a downloaded/ subdir of the programfiles application folder. They are downloaded via TCP, not using HTTP. Once the download is complete, out1.data and out2.data are generated, I guess all these files get somewhat assembled into these. They are placed in the programfiles application folder too, 203 MiB each. They look like a couple of Android sparse image files, according to header magic numbers. These files should be copypasted somewhere before ending the flash operation and closing the application, otherwise they will be deleted. Maybe these files contain interesting stuff :good:. There is also a log file showing addresses where is flashing and sizes of the images of the factory flashing operation.
Maybe some USB sniffing is worth, but not tested.

4019X Brick
Hi guys.
I have a 4019X bricked becasuse i tried to install a wrong system.img.
Can you upload again the factory flash images? The mediafire link is broken.
I made a backup of the original system with adb pull /system /system as mozilla´s recommend in the Firefox OS build prerequisites.
But i dont know how to compile to restore my phone. I tried this:
ANDROIDFS_DIR=<path to system backup> ./config.sh tarako
ANDROIDFS_DIR=<path to system backup> ./build.sh
but always fail.
If you dont know, can you tell me how to use the source code of alcatel to unbrik my phone:
sourceforge.net ... OT_FF_4019X_20150408.tar.xz
Thanks

Backup of the stock One Touch Fire C files
https://www.dropbox.com/s/nzn6g4qhh585ho4/4019X-2[X=A,B,C,D]TBHU1.rar?dl=0
Please keep us informed on any progress, now that Firefox has freed itself.

can u tell me if this rom has portuguese language? i need 4019x android or firefox with portuguese language? or anyway to add language?
best regards

mancvso said:
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Click to expand...
Click to collapse
Hi! I can not fix my Alcatel OT- 4019A yet. ¿could you please help me with that?
I don't know exactly what do with that archives.
Thanks!

Gsmfanatic said:
can u tell me if this rom has portuguese language? i need 4019x android or firefox with portuguese language? or anyway to add language?
best regards
Click to expand...
Click to collapse
The firmware doesn't have the Portuguese language, flashed it myself ...

[6045*] [TWRP] custom recovery 2.8.7.0

TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!​

Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.

Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?

Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18

Thanks!

is it functional for backing up our system in TWRP?

@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk

gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.

famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive

Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...

Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.

we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).

DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex

famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....

Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?

Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.

Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))

Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?

Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745

So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!

[Utility] Android Image Kitchen & Flasher APK

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.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis

atoxyd said:
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.
This apk need root.
Click to expand...
Click to collapse
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk

Yes, you can try

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.

Well I use in my apk AIK.mobile tools proposed by osm0sis.

atoxyd said:
Well I use in my apk AIK.mobile tools proposed by osm0sis.
Click to expand...
Click to collapse
https://github.com/osm0sis/AnyKernel2/ ?
from http://forum.xda-developers.com/showthread.php?t=2670512

bigsupersquid said:
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.
Click to expand...
Click to collapse
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.

atoxyd said:
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.
Click to expand...
Click to collapse
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.

nero curin said:
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk
Click to expand...
Click to collapse
Hi, did my apk work for you?

atoxyd said:
Hi, did my apk work for you?
Click to expand...
Click to collapse
only unpacking and repacking,didnt help on my device but yet again nothing else helps me compile kernel for this idol 3 so i guess this app works just not for me, bad luck :/
Sent from my 6045X using Tapatalk

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

atoxyd said:
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
Click to expand...
Click to collapse
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.

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

atoxyd said:
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.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis
Click to expand...
Click to collapse
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?

bigsupersquid said:
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
Click to expand...
Click to collapse
Thank you my friend , you are the only one who supported me , and from the beginning.

atoxyd said:
Thank you my friend , you are the only one who supported me , and from the beginning.
Click to expand...
Click to collapse
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."

bigsupersquid said:
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.
Click to expand...
Click to collapse
Did you have an unlocked bootloader ?

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)

I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.

atoxyd said:
I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.
Click to expand...
Click to collapse
Please use a different name for your app as I have requested.