Database Info

[KITCHEN] dsixda's Android Kitchen - Now supports Galaxy S Plus (Windows/Linux/Mac)

dsixda's Android Kitchen - Now for Samsung Galaxy S Plus (I9001)
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S Plus custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.182, you can now create your own Galaxy S Plus ROMs with the kitchen.
I'd like to thank the guys in this thread, especially crybert, oisis and mbba67 for helping me out, as well as for testing on their devices and providing feedback. I only have a Bell Galaxy S2 I9100 so their assistance was greatly appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
​
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S Plus (I9001) with a ClockworkMod-based custom recovery.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows or Linux or Mac. Ensure you read the FAQ carefully.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S Plus, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
system.img.ext4 and boot.img (and optionally: cache.img.ext4)
TAR file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
ZIP file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
Custom ROM:
ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a system.img.ext4 but then didn't include the cache.img.ext4, then you have the option to add a cache.img.ext4 later using the Extract SGS2 CSC script in the Advanced menu's 'Plugins' section.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Here are some screenshots of how to use the kitchen for the I9001, thanks to crybert.
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss Samsung Galaxy S Plus in this thread!
Most of all, have patience, take your time and enjoy!!

Reserved...

Reserved, just in case

Great stuff .. Thanks for ur work

great work!
did anyone tried the porting option in this kitchen?
could be very usefull to port miui or cyanogenmod to our device
i know its signed as experimental but anyone know the chances that this option will lead to a success?

Blumdum said:
great work!
did anyone tried the porting option in this kitchen?
could be very usefull to port miui or cyanogenmod to our device
i know its signed as experimental but anyone know the chances that this option will lead to a success?
Click to expand...
Click to collapse
Would be kind of hard to do..., but I heard that the SGSPlus is similar to the Desire HD, so I would start with a ROM from there.

You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?

Desire HD uses the same cpu/gpu as i9001 so there should be a big similarity
im asking myself the same question wether there is a chance for a full brick
but the boot.img will be written on the right partition

I don't know much about porting apart from the generic steps in the kitchen scripts. But if you have a nandroid backup, how would you brick (unless you mean the wrong partition would mess it up.. In that case just double check the updater-script before building).

maybe a wrong boot.img could lead to a brick

crybert said:
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Click to expand...
Click to collapse
I dont know about porting or boot.img, but what if you just replace SGS+ boot.img over the DesireHD Cyanogenmd Rom boot.img then just fix them in the kitchen. I dont know..........

crybert said:
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Click to expand...
Click to collapse
if the porting of cynogenmod from DHD succeeds we will be able to port their ICS too then. with some modifications to boot.img, build.prop. etc.. , replacing drivers, maybe we can try camera drivers and libs from I9000 port , of course we'll need someone to compile the right kernel. imo it can be done if we put a team work into it

but we can first try to port the desireHD rom to our device using the kitchen and then see if the device boots

Blumdum said:
but we can first try to port the desireHD rom to our device using the kitchen and then see if the device boots
Click to expand...
Click to collapse
the rom from DHD won't boot on I9001 without the right kernel.

Can you tell me where can I find an information how to add to my fresh cooked rom CWM FeaMod Recovery?

rayiskon said:
the rom from DHD won't boot on I9001 without the right kernel.
Click to expand...
Click to collapse
did you try it?
EDIT:
when we need a CM kernel we could build one
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source

mr_omega said:
Can you tell me where can I find an information how to add to my fresh cooked rom CWM FeaMod Recovery?
Click to expand...
Click to collapse
1. just add the recovery.img to the main directory of your rom. Where /system and META-INF is located
2. add the following line to your updater-script:
package_extract_file("recovery.img", "/dev/block/mmcblk0p13");
P:S.
We should move the discussion about CM to another thread. I think this is a bit offtopic

Hi guys, I have updated the kitchen to 0.182. See the main thread (linked on post #1) for full release notes.

dsixda said:
Hi guys, I have updated the kitchen to 0.182. See the main thread (linked on post #1) for full release notes.
Click to expand...
Click to collapse
Hi, how come i can extract boot.img but cant repack, there is no option for repack

try porting MIUI instead of CM7. MIUI is not only fast but customize able and i think dsixda does the work for you and then minor bugs can be fixed.

What to do next after deodexing?

Hi all,
I've tried this tool package [Script/Tool][Windows]>>Auto-Deodexer 4.3<<[All Android Versions] and it worked fine but there's no specific instruction on how to flash/install it back to my phone. Can someone guide me on what to do next?
I'm done with the very last instruction but have no idea what to do with the generated "ROM" folder
"When done, copy the modified files (in the zipaligned__ folders) back to the original app and framework directories in the "ROM" directory"
I'm fairly new to doing this deodexing thing on my own, I usually just flash roms that are already deodexed but sadly this new phone doesn't have support yet from the experts.
Thank you in advance.

cshock2010 said:
Hi all,
I've tried this tool package [Script/Tool][Windows]>>Auto-Deodexer 4.3<<[All Android Versions] and it worked fine but there's no specific instruction on how to flash/install it back to my phone. Can someone guide me on what to do next?
I'm done with the very last instruction but have no idea what to do with the generated "ROM" folder
"When done, copy the modified files (in the zipaligned__ folders) back to the original app and framework directories in the "ROM" directory"
I'm fairly new to doing this deodexing thing on my own, I usually just flash roms that are already deodexed but sadly this new phone doesn't have support yet from the experts.
Thank you in advance.
Click to expand...
Click to collapse
Which phone are you using??
Its better don't go further if you hav no experience with this.. doing wrong or for first time will create some mistakes and will create problems...
Thums up if you are ready to take all responsibility and go further there are many guides around XDA to cook your ROM
Tel the clear information of your device... I.e. device name, android version..

SadEff said:
Which phone are you using??
Its better don't go further if you hav no experience with this.. doing wrong or for first time will create some mistakes and will create problems...
Thums up if you are ready to take all responsibility and go further there are many guides around XDA to cook your ROM
Tel the clear information of your device... I.e. device name, android version..
Click to expand...
Click to collapse
Cloudfone 400dx
Android 4.2.2
mt6572
Yes I would really like to learn how to cook my own rom from my rom dump and integrate the deodexed system there.
I've successfully loaded the deodexed framework and apps and removed .odex files via adb. Phone working fine after all that. :laugh:
Thanks!

cshock2010 said:
Cloudfone 400dx
Android 4.2.2
mt6572
Yes I would really like to learn how to cook my own rom from my rom dump and integrate the deodexed system there.
I've successfully loaded the deodexed framework and apps and removed .odex files via adb. Phone working fine after all that. :laugh:
Thanks!
Click to expand...
Click to collapse
May be this helps you

[Q] How to extract build.prop from system.img

I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.

gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
Try the tools in this thread . I used them last week to extract a build prop.
Just load up the system.IMG and drag the file from the system folder to your desktop.

gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ

daniel4653 said:
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
Click to expand...
Click to collapse
I already downloaded that file.... I just need to extract the build.prop from the system.img which I already have. The thing is I am having trouble getting the build.prop
Sent from my SAMSUNG-SM-G920AZ

gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps

tiboric said:
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
Click to expand...
Click to collapse
When I try to open the file the program just closes and i go to the log and this is what it says.
Error Opening \\.\PhysicalDrive1. Error Code 2
No of disks 1
Scanning \\.\PhysicalDrive0
index 0 ID 7 size 976769024
Partition Table Error on C:/Users/giovany/Desktop/New folder (2)/system.img
Invalid End of sector markerBad Super Block. The drive is not ext2 formatted.

Drive is not right formatted.

solution for img extraction/fix here

is possible tar.md5 to custom tar.md5?

Hi guys, i have a question...
Is possible create a custom rom (remove vendor apps) from XXXXXXXX.tar.md5 file downloaded from sammobile and make your own tar.md5 flasheable Odin file?
For example:
Original firmware:
XXXXXX.tar.md5
1.5 Gb
Removing vendor apps:
XXXXXX_my_firm.tar.md5
800 mb
I am interested in doing this without custom recovery, not zip flashable file, and not root.

xTxMIGUELxTx said:
Hi guys, i have a question...
Is possible create a custom rom (remove vendor apps) from XXXXXXXX.tar.md5 file downloaded from sammobile and make your own tar.md5 flasheable Odin file?
For example:
Original firmware:
XXXXXX.tar.md5
1.5 Gb
Removing vendor apps:
XXXXXX_my_firm.tar.md5
800 mb
I am interested in doing this without custom recovery, not zip flashable file, and not root.
Click to expand...
Click to collapse
Yes, you can do this, but things have changed a bit since this guide was written, you'll have to do some research to see what things have changed in this process from kit kat up to the current available android version. There have been some stock security changes that this guide doesn't cover and won't work with these new securities, but you should be able to figure out how to make this work with those securities if you learn to look in the right places.
https://www.rwilco12.com/forum/showthread.php?tid=92
This will help you create the .tar, you'll just have to figure out how to make the changes you want to make. You'll mostly be working with your system.img once you get it extracted.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

[TOOL][WIN] ROM Explorer - Browse Android ROM Files

ROM Explorer
From time to time I need to extract some files from various Android ROMs. So far I downloaded the ROM file and then started to search for further tools to extract files from the downloaded ROM. If all went well I ended up with an image I could open with ext4_unpacker to finally extract the files I needed. This whole procedure took a lot of time, involved tools from unknown sources and often simply didn't work. So I decided to create my own tool.
ROM Explorer can directly open the following files:
zip archives with img or new.dat entries
Samsung md5 archives
Sony ftf archives
Huawei update.app archives
img/ext4 image files
lz4 image files (used by Samsung)
sin fies (used by Sony)
In case you have a file which is not supported let me know. Maybe I find the time to add support. Or simply add it yourself - ROM Explorer is Open Source.
Usage
Download the installer and run it or build your own version with Visual Studio 2017.
Start the executable. You will see a window similar to ext4_unpacker. In the first line you select a file, in the second line you can choose an archive entry if the file is an archive file.
Loading a file or archive entry can take a significant amount of time and disk storage. ROM Explorer may need to create temporary files with several gigabytes. A fast flash disk helps a lot!
You can extract files or folders by dragging and dropping them to Windows Explorer.
Downloads
ROM Explorer 0.9
ROM Explorer 0.9.1
Thanks To
ROM Explorer would not exist without the distributed knowledge of this forum. Especially I want to thank worstenbrood, Androxyde, IgorEisberg for their work.
So I'm waiting for your comments - but be patient it may take some time for me to react

Reserved for whatever purpose...

Wew
Let me try and report you back

Thank you I will try this out. Thanks too for making it open source

Not Running on Windows 7 x64

samidos said:
Not Running on Windows 7 x64
Click to expand...
Click to collapse
0.9.1 should fix this. Be sure to first uninstall before installing 0.9.1.

After hours of google search and downloading countless apps that dont work I found this. This app is legit and works on windows 10 64bit. Thank you for your work.

Your app is GREAT! Thanks for sharing it.
Edit: Answered my own question. Windows 10 tip "Run As Administrator" and dont drag files "to the desktop" but instead to an Explorer window.

Can this program find the differences between compiled ROMs?
I ask this question because Xiaomi on the Mi 9 released an initial kernel with sourcecode that was changed over time without updating the GitHub https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cepheus-p-oss and because of this change, the ROMs have something different between how they connect to the cameras. The old ROM versions (4/1/2019 and before) connect fine to the cameras, but post that date, a custom kernel built from the GitHub source will fail to connect to the cameras. Since the change has not been made open source on GitHub, there has to be another way to find and patch new kernel builds in order for them to work. Would your software be able to extract these changes? If not, do you have any other ideas which may? Much appreciated.