yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] :
Sory, in this case you have to use the windows version. I only have one pc with an ubuntu on 64 bits installed and a windows 7 (dual boot). I don't want to wipe it out just to install a 32 bits version to build those binaries again. I will need a second pc but I have no money for this (I can't afford even a phone with lollipop), and all the users that uses my tools aren't very supportive (in the last 8 months I only received something around 9 euros), so... that's the situation. Also you may want to find other tools to do the job if this is not good enough.
[Miscellaneous Android Development] DarkHeart Z:
I know your feelings

I am exactly in a same state bro . Your works were legendary . i tried your touch recovery but mt6572 phone doesnt have touch support on recovery or I don't know how to make that work . your recovery worked great . But navigation issues . I can help you if you can point me on what I have to do . I am currently not that much busy . I have time . So just tell me or point me to the right directions on how do I give 32 bit support on the executable . If I become successful i will send you the executable files . If you don't mind i can help you with these . I don't need anything in return i just want to learn more :)

P.S : Bro , why don't you use the multiarch feature of ubuntu . You can have 32 bit userspace on 64 bit os by these way . and you dont even have to change to 32 bit ubuntu if you use multiarch .
[Miscellaneous Android Development] :
It is already multiarch, but that means you can use 32 bits builds on 64 bits architecture not viceversa, because depends on your kernel. If it is a 32 bits kernel it won't work unless the binary is build as 32 bits executable. The 64 bits kernel is actually a x86_64 build (at least in ubuntu) and can run 32 bits executables if you have the corresponding libraries installed.

Anyway, I didn't wanted to make this public, but I've lost my sources and works at the beginning of this summer when one of my hdd crushed. To be able to build those again I have first to re-make those sources then to get a new PC and so on. I don't have time to do android and xda stuffs now, so that's one reason I didn't make any update on any of my tools.
[Miscellaneous Android Development] DarkHeart Z:
I will help you I dont need anything in return which lines of code has to be patched just tell me ? I will do the rest and send it back to you u can check them if they are properly patched . What do you say bro ? I have time I am not busy that much nowadays . If you dont mind I can help you . There always is a solution for every problem let me help you with that if u dont mind :)
[Miscellaneous Android Development] :
If I would have time to tell you what to do I surely have time to recreate the code myself, but as I said I don't have that time. I'm very busy with my day to day job (barely found it and I intend to keep it). So, I enter here from time to time but that's all I can do now.
[Miscellaneous Android Development] DarkHeart Z:
Ok bro , I understand that . Waiting for the 32 bit compatibility of your kitchen :)
[Miscellaneous Android Development] DarkHeart Z:
little help please

[MENTION=5186178]carliv[/MENTION] bro I moved to windows 7 few days back and I set cygwin for working on superr's kitchen for my projects . I have copied your win32 executables and placed them in your directory under /tools/boot/ and modified the the unpack repack mtk img , img just with the .exe extensions . It decompiles the boot.img properly but repacking the boot.img doesn't work . Can you just give me hint on which lines need to be modified to make it work while repacking ? There's n other problem by the way . I checked the kitchen scripts also , they are good and properly pointed to the right location :)
[Miscellaneous Android Development] :
I don't know, post here a screenshot with the error. Have you checked if you have all dependencies installed (mkbootfs and minigzip with exe, etc)?
[Miscellaneous Android Development] GoJo ^^:
Hi there, i just grabbed this recovery https://yadi.sk/d/xv4TEgAbjD4cm and wanted to modify it but i get error, please have a look and tell me if i (or you) can change it so it can be modified with the app.. Thanks!
[Miscellaneous Android Development] :
It is unpacking very well for me.
[Miscellaneous Android Development] superdragonpt:
Hi

yup confirmed, it's unpacking without issues for me also.

This is one piece of good work ;)

cheers
[Miscellaneous Android Development] DarkHeart Z:
Never mind I got it . Looks like I have to revert back to linux now for the way I am thinking now .
[Miscellaneous Android Development] bovirus:
[MENTION=5186178]carliv[/MENTION]

I used your tools without problems.

But now I found some boot.img that I cannot decompress with your tool.

It's the boot.img of some new devices with MTK6753 CPU.

The error is

Your image: boot.img

Create the boot folder.

Printing information for "boot.img"

Unpack mtk image utility by carliv@xda

Header:

Magic : ANDROID!

Magic offset : 0x00000000

Page size : 2048 (0x00000800)

Base address : 0x40078000

Kernel address : 0x40080000

Kernel size : 6377775 (0x0061512f)

Kernel offset : 0x00008000

>> kernel written to 'boot/boot.img-kernel' (6377263 bytes)

Ramdisk address : 0x44000000

Ramdisk size : 1152072 (0x00119448)

Ramdisk offset : 0x03f88000

>> ramdisk written to 'boot/boot.img-ramdisk.unknown' (1151560 bytes)

Second address : 0x40f00000

Tags address : 0x4e000000

Tags offset : 0x0df88000

Board name : '1443504244'

Cmdline : 'bootopt=64S3,32N2,64N2'

Compression used: unknown

Unpacking the ramdisk....

Your image ramdisk is packed with an unsupported archive format.

Please inform the author of this tool about the error and provide the image for helping him to find a solution. Exit the script.

The boot.img file - http://www8.zippyshare.com/v/PPfnS9WG/file.html
[Miscellaneous Android Development] :
You could fix it yourself if you have read two pages back in this very thread here and here.

Your image is unpacking very well with regular commands.
[Miscellaneous Android Development] bovirus:
[MENTION=5186178]carliv[/MENTION]

Thanks for the reply.

Very strange. The boot.img is for Mediatek device and I believed to be use MTK command section.

Do you think that it's better Android regular compress or Mediatek compress comnad after the changes in teh sources?
[Miscellaneous Android Development] :
As I already said in one of those posts, for the latest platforms, MTK just removed the MTK header, making these images like any other CPU powered phone, and so you have to use the "regular" script. The MTK binaries and scripts address only images with MTK header in place.

This has nothing to do with compress method, it's just a matter of MTK header on top of image or not.
[Miscellaneous Android Development] AP756:
[thread stated] [MENTION=5186178]carliv[/MENTION] please contact me (best over at forum zopomobileshop) [tread stated off]

Bye for now Fred
[Miscellaneous Android Development] bovirus:
[MENTION=5186178]carliv[/MENTION]

I found recently the boot.img of recent device (Mlais M7 Plus / Plunk Hero Pro) that I can decompress it (without error) but I cannot recompress because kernel is missing.

The original boot.img is here

https://drive.google.com/open?id=0ByL-fx0GbfuiUjRocnBoTlpFczQ

Decompressing with 1 (standard android decompress ebcause has standard header) it report no error

but in "boot" subfolder I found boot.img-zImage (instead boot.img-kernel) file.

Thanks.
[Miscellaneous Android Development] antr34:
thank you, the best image tool, i have tried 5 other tools but non worked
[Miscellaneous Android Development] workdowg:
Fantastic... Works as expected!
[Miscellaneous Android Development] dedalos91:
please can you help me to resize the font or screen of an cwm recovery image (have success with unpack / repack), the recovery is for Doogee Valencia 2 Y100 Pro (MTK6735) and unfortunately custom twrp recovery has no working touch. thanks
[Miscellaneous Android Development] :
You are probably talking about a ported recovery. Sorry but you can't do that with CWM. You have to build it from source defining a bigger font and your phone resolution.
[Miscellaneous Android Development] ghost45:
Ohhh... The Great is turned back!

Welcome Carliv. :eek::eek:
[Miscellaneous Android Development] dedalos91:
o, thanks for answer,

please can you tell me little more about that (to build it from source defining a bigger font and your phone resolution)? can you guide me or give me some links for reading?

thanks again and Merry Christmas

edit

find this and will try http://xdaforums.com/showthread.php?p=32965365#post32965365
[Miscellaneous Android Development] :
Or you can use my guide to build CWM based recovery. Just take a look in my threads.
[Miscellaneous Android Development] ghost45:
I wish to all of you... Merry Christmas holidays... And of course to my friend... The Great Carliv!
[Miscellaneous Android Development] :
Thank you! Merry Christmas and A happy new year to you too and to all of you who celebrate these holidays.
[Miscellaneous Android Development] Ax1qwer:
Decompile boot.img from MT6735P ROM - fail

Hi, I am trying port ROM to MT6735P (Homtom HT6), but when I try to decompile boot.img - this appear:

Your image ramdisk is packed with an unsupported archive format. Please inform the author of this tool about the error and provide the image for helping him to

find a solution. Exit the script.

Can I decompile new ROMs for 64BIT MTK with your tool? (MT6735/p 6752 etc.) ? thanks

Can you please look at it, thanks :)

I am noob in porting ROMs, sorry. And sorry for my bad English.

boot.img attached.
[Miscellaneous Android Development] :
Yes, i explained this few pages back.

You have to use menu option 1 for unpack and 2 for repack. For the new MTK platforms they didn't used mtk header anymore. Check the pictures to see how goes your image.
[Miscellaneous Android Development] Ax1qwer:
Carliv: many thanks :)

For porting MTK 64 Bit roms I should use classic rom porting guide, instead of mtk porting guide? I am right ? Thanks

Odesláno z mého HT6 pomocí Tapatalk
[Miscellaneous Android Development] rajlko:
[MENTION=221114]carl[/MENTION],

Sir,

I have an issue, if I just unpack a boot image & repack same boot image without any modification, then modified boot image flash well but goes in boot loop mode, can you tell me why this is happening.
[Miscellaneous Android Development] :
Sorry but I can't. I don't have the ability to read minds or to see things far away with my mind :) .

Since you don't give any informations about your phone (brand, name, platform cpu, android version) or a boot/recovery image attached I can't tell you what could be the problem.
[Miscellaneous Android Development] rajlko:
sorry for that

asus zenfone laser

model name z00ld, ze550kl.

msm8916 snapdragon410

Quad-core Cortex-A53

Adreno 306

5.0.2
[Miscellaneous Android Development] :
Ok, I took a look and I can't tell you exactly what is the problem without having the phone for tests, but these are few things that may narrow the problem: my utility uses minigzip for repack which compress the ramdisk better, try other one (there are a few around here on xda) with gzip and see the results; also your phone has a dt blob and I couldn't test this on real when I made the tool so that may be the problem (although I compared the original and the repacked one and they are identical which means my tool didn't break that); and last, maybe your phone has some bootloader lock and you can't use non-original images for boot or recovery.

I attached the image for boot repacked by me just like you said without changing anything... probably won't work eigther since didn't work first time when you did it.
[Miscellaneous Android Development] rajlko:
Dear Sir,

I am here to provide test result whenever you asked.

I have tried others but most tools unpack images successfully but can not repack images.

most time I used to use your tool & it works very well, I created some recoveries & those works well.

Last time when I unlocked my bootloader, I used modified boot image but same results.

my device was repaired in asus service center, now have locked bootlaoder with same results.

I tested this one & same result. :crying:

Hope you will provide any solution in future.

Thanks
[Miscellaneous Android Development] :
Well, you have to be patient then. I need to recreate my source code again after a hdd failure last summer. After that I'll try to make some improvements.
[Miscellaneous Android Development] rajlko:
of course, I will wait sir, Thanks a lot for positive response.
[Miscellaneous Android Development] bemolx:
I've got a problem.

Your utility doesn't unpack ramdisk from my boot.img. It says it's unsupported archive format, so I'm informing you about that. My device is Allview X2 Xtreme (same as Blu Pure XL or Gionee Elife E8). I've attached my original boot.img below. Thanks!
[Miscellaneous Android Development] :
Check the OP again. I added a red attention info block. It applies to you too.
[Miscellaneous Android Development] bemolx:
Yeah, right. Thank you very much! :)

Wysłane z mojego X2_Soul_Xtreme
[Miscellaneous Android Development] wertzPH:
i have MT6592M, so im suppose to use ANDROID REGULAR 1/2 right because its new soc? but, it gives gz error and cannot unpack ramdisk, so i use MEDIATEK #1 to unpack. so should i also use mediatek #2 to repack and place in mediatek header or should i repack with normal Android repack? its Android 5.1

thanks.
[Miscellaneous Android Development] :
Well the mt6592 or 6592m it's not a "new" SOC. Those are starting with mt6732 and go to x10 helios or whatever is the latest mtk cpu - basically the new 64bit CPUs.

About using unpack and repack commands, as an advice for any of those who want to know, not only for you:

- if the image is unpacking well with option 1 then you must repack it with option 2, if it is unpacking well with option 3 then you must repack it back with option 4.

Cheers
[Miscellaneous Android Development] wertzPH:
thanks for that clarification. more power with your works :D
[Miscellaneous Android Development] kitcostantino:
Many thanks for this amazing tool [MENTION=5186178]carliv[/MENTION] !!! it is awesome!!!
[Miscellaneous Android Development] :
Glad you liked it.
[Miscellaneous Android Development] vampirefo:
I will be trying your scripts when I get home from vacation, my old faithful script I have used for a long time failed me, it was unable to get ramdisk from engery x, I got kernel but not ramdisk.

https://mega.nz/#!Z0Y1yJIQ!P3nRC4_9_TQQcuGuintRNdEYLCu7-0J36zwl78BIOT4

I had been using below script never failed til now.

https://github.com/bgcngm/mtk-tools

I use Ubuntu 14.04 64bit, if that makes any difference.
[Miscellaneous Android Development] :
That's because these new mtk phones dont use mtk header anymore and bgcngm's tool is designed specific for those with mtk header.

In my kitchen use option 1 (android regular) for unpacking and 2 for repacking and it will work.
[Miscellaneous Android Development] AdamDevlopper:
Someone has an idea?

Your image ramdisk is packed with an unsupported archive format. Please inform the author of this tool about the error and provide the image for helping him to find a solution. Exit the script.
[Miscellaneous Android Development] :
Well, as the message informs you,

you need to attach your image here and to specify what phone is it for, android version, and what options from menu you used.
[Miscellaneous Android Development] AdamDevlopper:
Ohhh yeah om so dumb sorry " As the teacher say read before start asking" well here is the bootimg : http://www21.zippyshare.com/v/myIpbS16/file.html

Its for the Lenovo k3 Note (MT6752) 64-Bit Device and the kernel is for Android 6.0
[Miscellaneous Android Development] :
It's unpacking very well for me (see attach) using option 3 (unpack mtk).

I know I said for the new mtk phones it needs to be used option 1 and 2, but not for all of them. Some manufacturers still want to use mediatek header on images.

You guys should just try first option 3 or 1 and if that doesn't work delete the unpacked folder and try the other option. That can't do any harm, it's a "dry" process that happens in your computer not live in your phone.

And, again this is not just for you, guys please try first, and after that ask.
[Miscellaneous Android Development] AlexZap:
From what I have seen,the 6732, 6752, and 6795 all use the mediatek headers, whereas anything newer then that use standard android headers 6735, 6753, probably 6755 and 6797. I think it is up to mediatek and the kernel source they provide for specific processors to the manufacturers.
[Miscellaneous Android Development] :
Mostly yes, but I've seen mt6752 images without mtk header and mt6753 or 35 with mtk header (this one also for some lenovo phone if I remember correctly, just like the one above). So, maybe mediatek provide both ways (see mt6582 with and without mtk header) and the manufacturers choose what they want.
[Miscellaneous Android Development] superdragonpt:
Hi

I said it on bgcngm's thread some time ago ...

Pretty much, even on newer SoC's, its up to the vendor (OEM), not Mediatek,

How is it packed .

Most vendors , have their own customized way to do things , others will often change source tree with their own scripts, other aditions, Etc.

On 6752/6753 , that also includes 6735/6732 ( same platform )

There's either both situations

;)

Cheers
[Miscellaneous Android Development] hardwork07:
Great tool

Finally found a tool that really worked in modifying boot.img of MTK in Lollipop 0S, after few hours of

searching. The only problem now is how to make it insecure, which was way easier in Kitkat & lower versions.

Replacing adbd from sbin didn't worked & ended up in offline mode, so difficult in making some modifications in the system. Even used superR's kitchen but just gets stuck in logo. :(
[Miscellaneous Android Development] :
Update to version 1.1

2016-03-24 Update to version 1.1 stable

Changelog:

- rebuilt all executables using Cyanogenmod 13 source;

- a new way to handle MTK images - use same menu and everything it's done by the Kitchen under the hood;
[Miscellaneous Android Development] :
Windows version 1.1 fixed

I'm sorry, it was a problem with previous upload for windows - an error on batch script. Fixed now and reuploaded, so if you use windows version and had problems with it just download it again now.

PS If you guys have problems with any release please post it here for helping me to fix it.
[Miscellaneous Android Development] JBCDev:
Nice Job !

Cheers and thanks
[Miscellaneous Android Development] bovirus:
[MENTION=5186178]carliv[/MENTION]

Thnaks for your tool.

In the past your tool had separate options to comrpess/decompress boot/recovery with standard Android header or Mediatek Header.

Now the option is unique.

How can your tool detect if the header is Android Standard or Mediatek during decompression?

How can your tool decide if you have to use during compression Android standard header or Mediatek header?
[Miscellaneous Android Development] 4llerbuntu:
Hello. Please i need help.

I have a Mediatek device with MT8382 Processor

Lollipop 5.0 Screen Size 800 x 1280 with a secured boot.img i have been trying to make it unsecured by changing ro.secure in default.prop

I managed to do this successfully with this tool and have made the kernel adbd insecure.

but auto TWRP and CWM installers do not work for the device so if anyone can assist me with building a custom recovery for it i'll be grateful

this is a link to the boot.img, recovery.img and scatter file:

https://drive.google.com/open?id=0B3...ktFaXE0NnVRSkk
[Miscellaneous Android Development] :
Well that can be understood easily by a developer who look at my code on github. You need to know some scripting (shell or batch) and some C coding, not very complicate. Everything it is done now on built binaries and in script. To understand just unpack an image with mtk header and one without and then compare those two folders.
[Miscellaneous Android Development] 4llerbuntu:
@ carliv please help me.

This is what i get
[Miscellaneous Android Development] :
That could be a wrong fstab definition for cache partition. Anyway you should try to port or build twrp for lollipop.
[Miscellaneous Android Development] hohassan444:
thanks [MENTION=5186178]carliv[/MENTION] for the amazing tool..But i have problem in MTK boot.img. it is successfully unpacked using kitchen V1.0 , but failed on V1.1.....As in V1.0 , i have option to unpack using regular vs MTK mode..the boot.img is unpacked using regular but not MTK mode.

https://mega.nz/#!apQgEZhD!u6TQ2CPU-e0ylld2DeooHA553CRVtfIToKpary0OHhc
[Miscellaneous Android Development] :
That's because the image you linked has a MTK header only over kernel and not over ramdisk. The version 1.0 doesn't check the mtk header before repacking and using regular script it will split the kernel containing the mtk header and the ramdisk which is gzip compressed and it will unpack it correct. The new version just check for mtk header before unpack and if detects at least one mtk header in image it will unpack it accordingly removing the mtk header part from both kernel and ramdisk.

The image you linked is a new kind for me, I never saw an image with mtk header only on kernel or ramdisk. Are you sure that image is working in your phone? Did you tested before uploading it? It may be a wrong unpack and repack using different tools before...

If you say it's working and there are other people who confirm there are images like that with mtk header only over one component I'll modify the script to unpack mtk headered images only if there are two mtk headers present for kernel and ramdisk.

---------

PS I repacked that image without mtk header on kernel. Test it to see if it works. If it does than your posted image was faulty.
[Miscellaneous Android Development] hohassan444:
thanks for your reply.....both my boot.img and your uploaded boot.img works for my device (jiayu s3 mt6752)..but i want to add that this image is ported one ( from another mt6752 device) to my device.

thanks in advance
[Miscellaneous Android Development] prantokp:
#help

I'm using Carlive Kitchen v1.1. It works on windows 10 fine. But tody I have setup windows 7 ultimate for some reason & the kichen couldn't repack the boot. (Rrpacked files are 0B). But it can unpack file fine.
[Miscellaneous Android Development] :
You should give more info (windows 32 or 64 for both 10 and 7). I have a windows 7 64 bit but the executables are built for 32 bits and in my PC everything works well. If you say there are problems only on repack that clearly are related to cygwin utilities. So tell me more about your system. One other test you can make is to replace cygwin dlls from version 1.1 with the correspondent ones from version 1.0 (and also few exe like cpio, gzip, and maybe mkbootfs if it still doesn't work).

If you don't give me more informations I won't be able to fix it (if it's something to fix because for me it is working very well).
[Miscellaneous Android Development] prantokp:
I'm using Windows 7 32bit, previous Windows 10 was also 32bit.

V1.0 is able to repack img. But the file name is like this "boot~8,6.img". & I didn't test this img works or not.
[Miscellaneous Android Development] :
The output boot image can be renamed in what you want, but you still failed to do what I ask about replacing those cygwin dlls and also you didn't mention if you run it as administrator, if UAC is disabled, or you by mistake blocked the mkbootimg.exe from execution or other executables from inside... There are a lot of possible wrong things but I can't know all of these if you don't tell.
[Miscellaneous Android Development] prantokp:
I'm really sorry bro. I've already changed my os to windows 10. So that I can't give you the details. ��

Edit: your kitchen is again working fine on windows 10 32bit
[Miscellaneous Android Development] encol:
linux 64bit?

Hello linux version seems compiled for 32bit.

It is possible to get a 64 bit linux version?

thanks in advance
[Miscellaneous Android Development] :
Done. Check the links.
[Miscellaneous Android Development] encol:
Thanks man! :good: