Description: Utility (hereinafter - the kitchen) to make changes to the firmware image for the Lenovo K900.
Operating System Requirements: Any Linux-like system (I recommend Ubuntu), any digit. For correct working kitchen must be installed packges: p7zip, p7zip-full, jdk, jre, python, ia32-libs.
Features: Removing the preinstalled Chinese software from the VibeROM firmwares; other firmware - manual; deodexing firmware; adding ROOT rights in firmware; editing build.prop; installing Google apps (* not verified), repacking the system.img.gz image.
Instructions for use:
- unpack the archive to any folder;
- Run the kitchen with console command ./kitchen.sh and enter the root password (required for file operations);
- Copy the file system.img or system.img.gz in a folder /in/;
- Enter 1 if throwing system.img.gz image archive folder in /in/, or go to step 2 if the folder /in/ drop files system.img;
- Type 2 to mount the image, while in the kitchen wearing the phrase "System: unmounted" will change to "System: mounted". The system is mounted in a folder /mount/;
Then simply describe the menu items:
3 - removes Chinese preinstalled software according file cn-apps in /scripts/ folder;
4 - "easier" firmware by deleting unnecessary files, animation off; applies mods - Record video to MP4, boot animation changed to "clipped " (you can change your folder /scripts/mod/);
5 - deodexing firmware (it takes quite a long time , up to 10 min);
6 - adding ROOT rights (used SuperSU 1.93). If you want to use a different version, you can replace the files in the /scripts/root/;
7 - editing build.prop file by using gedit;
8 - Set the Google apps light with a minimum set of software, you can further install more right already from Google Market (not tested);
9 - edited image packaging system system.img.gz. Ready to pick up the file from the folder /out/;
10 - unmount mounted image. Performed at the end of all operations with an editable manner;
0 - unpack inb firmware;
x - exit.
Download link:
http://forum.xda-developers.com/devdb/project/dl/?id=5359
Download mirror:
https://drive.google.com/folderview?id=0Bz3X7ZuowQimM3c0ZFV2QlZMR2c&usp=sharing
XDA:DevDB Information
Lenovo K900 kitchen, Tool/Utility for the Lenovo K900
Contributors
xxx-man-by
Version Information
Status: Testing
Stable Release Date: 2014-02-17
Created 2014-02-19
Last Updated 2014-06-07
What a great job！:good:
Amazing
Now its time to cook some ROM's
Lenovo K900 kitchen 1.21 beta
Released new version 1.21 beta
Whats new:
- Added support for firmware format INB (unpacking only);
- SuperSU binaries updated to version 1.93;
- Added support for complex tools with Android 4.3 (deodex, zipalign, optipng). Work is not very stable.
great, I hv prepared ubuntu and hv started cooking
Released new version 1.23
Whats new:
- Changed the script for implementation Root rights firmware (to fully support Android 4.3)
Just asking...
no kitchen for Windows7?
pjsplayez said:
Just asking...
no kitchen for Windows7?
Click to expand...
Click to collapse
No. Only for Linux-like OS, because Windows cannot work with images, mounting, rights etc...
Thank you i try it and install root Good Job
Just ask
xxx-man-by.. why not just "inb" file in "sdfuse" folder ?!. thanks before
Thank you, I am being to buy that device ^_^
Dual boot
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
help XXX-Man
i think the link is not working anymore.
REupload please
pjsplayez said:
help XXX-Man
i think the link is not working anymore.
REupload please
Click to expand...
Click to collapse
Ok. I`ll upload to the mirror. Please wait. DONE.
pjsplayez said:
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
Click to expand...
Click to collapse
if you need linux just for cooking, dont install it to harddrive.. just throwit on some usb drive and run it live..
use pendrivelinux or yumi to make live linux on usb.
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
sev7en said:
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
Click to expand...
Click to collapse
I do not understand what you mean.
xxx-man-by said:
I do not understand what you mean.
Click to expand...
Click to collapse
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
sev7en said:
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
Click to expand...
Click to collapse
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
xxx-man-by said:
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
Click to expand...
Click to collapse
thank you for getting me back sooner, with your unique Kitchen we are able to manage that files as well to repack them but when done how we get the final package to flash?
thanks once again for that
Related
LINUX ONLY
For LG Optimus
This is an implementation for the Android Kitchen 0.195 - by dsixda, a new option is added to the menu 0 - ADVANCED OPTIONS
The option is 25 - Tools for recovery image (unpack() re-pack etc)
This tool made it to modify the TWRP Recovery and give that look 3D, hope you find it useful.
INSTALLATION:
Before that nothing we need to have installed the Android Kitchen 0.195 - by dsixda
UnRAR the attached file and copy the 2 folders inside the kitchen.
Ready.
Source: www.todomovillg.es
Version 197 of dsixda's kitchen already does this.
Yes, does it, but should rename boot.img, and use the option 20
With this implementation already recognized the recovery.img, you can only work on without having to work with the full ROM.
It is more convenient to work with the option 25
Homero2 said:
Yes, does it, but should rename boot.img, and use the option 20
With this implementation already recognized the recovery.img, you can only work on without having to work with the full ROM.
It is more convenient to work with the option 25
Click to expand...
Click to collapse
Actually the latest version doesn't require you to rename the boot.img to recovery.img
OK, thanks for the info on the Linux version do not see this option, it could even change the compression ratio or size of the memory, I had to modify the code in order to have those options, which the version batch if they were.
I am reluctant to use Wine
EDIT:
" it could even change the compression ratio or size of the memory, I had to modify the code in order to have those options, which the version batch if they were."
Sorry for, I confused program
Can I explain how to unpack the recovery.img file? can not find such option.
Thank you
can you post direct download link here?
i can't link in that forum/site
thanks
ron gokhle said:
can you post direct download link here?
i can't link in that forum/site
thanks
Click to expand...
Click to collapse
OK, I have already posted the link on xda
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | lessshowed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...
Hi, I want to execute (then install) an personalized Android ROM on my PC, I tried to change the distribution of Android x86 but the ISO file reconstructed (by Nero) is not read (An error tells me that no files were found for the start) and are not able to open (for modding) the file in SFS inside the original ISO. So I tried modding the files of Windroy Project and the result was more than excellent! (I have modded files of Windroy in C drive) but now I do not know how to make these files "installed" as indipendent OS, it is possible, and if so, how? Thanks for the answers
UP!!
I would like to run the. exe file in an base operating system (also CMD) that start the .exe by start, exist?
---blacksoul--- said:
Hi, I want to execute (then install) an personalized Android ROM on my PC, I tried to change the distribution of Android x86 but the ISO file reconstructed (by Nero) is not read (An error tells me that no files were found for the start) and are not able to open (for modding) the file in SFS inside the original ISO. So I tried modding the files of Windroy Project and the result was more than excellent! (I have modded files of Windroy in C drive) but now I do not know how to make these files "installed" as indipendent OS, it is possible, and if so, how? Thanks for the answers
Click to expand...
Click to collapse
try in here
http://forum.xda-developers.com/showthread.php?t=1272270
hawaja said:
try in here
http://forum.xda-developers.com/showthread.php?t=1272270
Click to expand...
Click to collapse
My problem is not knowing how modding a ROM, but to bring a ROM on PC and open that file type, which requires a separate procedure.
HERE IS A GUIDE FOR YOU ALL YOU CAN CREATE YOUR OWN ROM BY THIS METHOD.I AM NOT RESPONSIBLE FOR BRICKED DEVICES.
Click to expand...
Click to collapse
Requirement to make a custom rom
*JAVA JDK installed on your SYSTEM
*WIN XP/ 7/8/8.1.
*package given in download section
Who is this kitchen for ?
Those who are brand new to
creating custom ROMs and
want an easy place to start
learning
Those who just want to modify
shipped ROMs or someone
else's custom ROMs to their
liking
Those who are confused by all
those scripts and complex
commands required for
building and extracting
This is NOT a tool to
automatically turn you into a
full-fledged ROM developer.
ROM development normally
involves work from the ground
up and involves time , research
and patience .
Click to expand...
Click to collapse
PRESS THANKS IF YOU LIKE MY WORK..
Kitchen setup
setting up dsixda kitchen
1.download all the three link and unzip kitchen.rar and cywin package.
2.open cywin_package then open folder now, you can see 3 icons, a read-
me,a setup, and a folder. Choose
the setup. Here you will choose
install from local directory. Next,
navigate to the the folder of
extraction of cygwin and choose
the folder cygwin_packages inside
the cygwin extraction folder. Wait
for some time. Then, you will come
across a list of file. Click the 2-
circle-arrows,untill, it displays
“install”
after the procedure is complete,
run the batch file cygwin.bat . Now, minimise
it and copy kitchen folder,
keep it in some location where you have installed your cygwin package open home/ajay-pc(in my case this is administrator name of my pc)kitchen
now, open the batch file window
and type
cd c:\kitchen
wait for some time and then when
the location the changed, type
./menu
Click to expand...
Click to collapse
press thanks if you like my work
GUIDE
now minimize the batch file and extract official rom there you will find system.img then extract it using magic iso or flash
the official stock rom using odin the take a nandroid backup u will get system.rfs.tar in your sd card extract it using magic iso then make a folder in called rom and open it. again create a folder called system and copy all data from system.rfs.tar which u have extracted(do drag and dropping).
Now copy meta-inf of any stock rom and copy and kernel to rom folder.
Now you will get two folder and one file in your rom folder zip the folder content and copy the file where you have installed cygwin/home/ajay/kitchen/original update folder.
now open command shell which you have minimized 1st create working folder then add root permission,deodex your rom.
and at last press 99 to build your rom..
note-if it ask you to change updater script to update script change it but dont forget to change it back to updater script.now you will get your rom in output folder copy it to your sd card flash it if error occur unzip the zip file and delete meta-inf and boot.img and again copy meta-inf of any rom and kernel to it and zip it..again flash the rom..
PRESS THANKS IF YOU LIKE MY WORK
DOWNLOADS
Downloads
Link for cygwin click here :good:link for kitchen click here :good:link for magic iso click here :good:
Link for official firmware click here :good:
PRESS THANKS IF YOU LIKE MY WORK
CREDIT
DSIXDA for Android Kitchen
Samsung for this awesome device
ME for this Guide
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk