Related
I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.
Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.
Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all
Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks
Wrong post
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.
Here I present,
An easy to use and effective, Flashable-zip(or update.zip) Signer!
There are many update-zip(flashable zip) Signers available, but this is special.
This Signer WHOLE-FILE signs your update.zips/flashable-zips, so it can pass even recovery's Signature Verification(Tested on CWM 5.0.2.8 on HTC Wildfire S)!
Unfortunately, as I am not very veryGood at C/C++ Programming, this tool does not have a Graphic User Interface(GUI).
I apologize, but as I am new to XDA, I don't know how to insert pictures, "Code:" etc, so this thread may look very ugly to you.
Oh yes! And DON'T EVER delete any file included in the zip, as it will cause the zip signer to malfunction.
I may have made this flashable-zip Signer, but I couldn't have done it without this people:
zeppelinrox ( for teaching me a little C/C++ Programming with his scripts )
The creator of signapk.jar ( an important part of this tool )
Google ( For Creating Android so that these tools can be developed )
YOU! ( for testing out my flashable-zip Signer )
And many more, who I apologize for leaving you out
Guide to using this zip signer
To Use this Signer:
1) Unzip the file(Obviously!)
2) Copy & paste the update-zip(a.k.a flashable zip) that you want to sign into that folder.
3) Run ROM Signer.bat
4) Follow the instructions in the application.
5) When it says "File successfully signed......", You are DONE!
After File signing operation succeeds, check the "signed" folder for your signed zip file.
Thank you for Using my Flashable-zip Signer!
I would appreaciate if you would hit the "Thanks" button.
Portable Java(jPortable by PortableApps.com) DIRECT link
Here are the direct links for the 32-bit & 64-bit Windows Portable version of the Java(R) Runtime Environment:
32-bit : http://jaist.dl.sourceforge.net/pro...Versions/jPortable_7_Update_25_online.paf.exe
64-bit: http://jaist.dl.sourceforge.net/pro...rsions/jPortable64_7_Update_25_online.paf.exe
Just click on the link and the Portable Java RE should start downloading!
Nice work
Marília de Oliveira said:
Nice work
Click to expand...
Click to collapse
Lol didn't expect to see you here. Hi @haoyangw long time no see mate
Hi thanks for this signer! good work!
Please if someone can help me,
i have all firmware files for the Nokia 8110 4G and im not sure how to make the META-INF file what do i need to put in there and how to do it, as im trying to sign the package and it dose not go
yowejowe said:
Hi thanks for this signer! good work!
Please if someone can help me,
i have all firmware files for the Nokia 8110 4G and im not sure how to make the META-INF file what do i need to put in there and how to do it, as im trying to sign the package and it dose not go
Click to expand...
Click to collapse
Sorry let me better understand your issue first, you want to create a flashable update.zip for installing your firmware files right? So you want to create the correct META-INF files from scratch? Do you have TWRP recovery installed on your phone already? Cos it supports a newer kind of META-INF structure that makes a lot easier. Also your firmware files are for installing into the /system partition, or to be flashed? Sorry for having so many questions haha, I can better help you if I understand the technical details
haoyangw said:
Sorry let me better understand your issue first, you want to create a flashable update.zip for installing your firmware files right? So you want to create the correct META-INF files from scratch? Do you have TWRP recovery installed on your phone already? Cos it supports a newer kind of META-INF structure that makes a lot easier. Also your firmware files are for installing into the /system partition, or to be flashed? Sorry for having so many questions haha, I can better help you if I understand the technical details
Click to expand...
Click to collapse
HI thanks for the reply,
i have all .img files for this model i want to flash, its a kaios phone, and i have the original recovery still on it, (will the TWRP recovery work on kaios?) and yes i need to create a META-INF file from scratch.
THANKS FOR MAKING THIS TOOL!!!
You just saved me from a chao of broken bootanimation issue!
I REALLY REALLY APPRECIATE YOU AND I ALMOST CRIED( •̥́ ー •̀ू )!!!
THAAANK YOU!!!!Ｏ(≧▽≦)Ｏ
Is there a Linux version
I want to unpack the img but don't want to use in my pc(too confused).
so I want to unpack by the phone,
thank you
ytyyutianyun said:
I want to unpack the img but don't want to use in my pc(too confused).
so I want to unpack by the phone,
thank you
Click to expand...
Click to collapse
I don't think there is. Maybe I'm wrong too.
Basically all these boot.img tools are written in shell/bash and is made specifically to run in Linux distros.
Anyways there is an Android app called, Complete Linux Installer that lets you install any Linux OS in your phone. But I doubt whether boot.img tools work, as it needs various library files for it to work.
On a side note, I guess it would be more complex to do it in phone rather than in PC, if there is some way for it to work.
coolsandie said:
I don't think there is. Maybe I'm wrong too.
Basically all these boot.img tools are written in shell/bash and is made specifically to run in Linux distros.
Anyways there is an Android app called, Complete Linux Installer that lets you install any Linux OS in your phone. But I doubt whether boot.img tools work, as it needs various library files for it to work.
On a side note, I guess it would be more complex to do it in phone rather than in PC, if there is some way for it to work.
Click to expand...
Click to collapse
Thank you for your reply, but do you feel strange that the IMG is created by the recovery, so it is rational that there is a tool about IMG building. then why there is no apk. I mean some professional can extract just from the CWM recovery, I think.
need root
if you wanna get boot.img i think you must be rooted.
k0tsompakos said:
if you wanna get boot.img i think you must be rooted.
Click to expand...
Click to collapse
yes, I root, so I can use the recovery to back and restore,
I think any app that can access zip files in the internal and external memory can extract boot.img.
Like ASTRO File Manager and stuff...
recovery?
You wanna install a rom?
or recovery??
or we speak about boot.img? (Boot img is the boot animation when you turn on your phone.)
k0tsompakos said:
You wanna install a rom?
or recovery??
or we speak about boot.img? (Boot img is the boot animation when you turn on your phone.)
Click to expand...
Click to collapse
Nooooo
boot.img is the kernel (zImage + Ramdisk packed into an image file) that lies in the /boot partition
@ OP - If you want to extract boot.img itself, there are various methods and from CWM recovery like you said. I thought you were mentioning about how to unpack the contents of the boot.img say like zImage, Ramdisk and other files.
0ops
0ops yeah... :silly:
Searching for 1 minute and found this tool :good:
--> [TOOL] Boot.img tools [unpack, repack, ramdisk] <--
( I do not send link cause i am new here and can't :angel: )
It works. Have a nice day
k0tsompakos said:
0ops yeah... :silly:
Searching for 1 minute and found this tool :good:
--> [TOOL] Boot.img tools [unpack, repack, ramdisk] <--
( I do not send link cause i am new here and can't :angel: )
It works. Have a nice day
Click to expand...
Click to collapse
Yes, that's the tool and it works :good:
But as OP mentioned, he wanted to do it within phone, I highly doubt though.
coolsandie said:
Yes, that's the tool and it works :good:
But as OP mentioned, he wanted to do it within phone, I highly doubt though.
Click to expand...
Click to collapse
It could be done using this post http://forum.xda-developers.com/showpost.php?p=20227868&postcount=1124 and a hex editor from play store on your phone. But would be even more fiddly than on pc I would imagine, unless your phone has a largish screen. It could be done though.
If editing the ramdisk, you would need to unpack and repack after editing, which usually requires linux. I recently found http://forum.xda-developers.com/showthread.php?t=2036528 for PC, but have not had a chance to try it yet, seems best solution for OP
coolsandie said:
Yes, that's the tool and it works :good:
But as OP mentioned, he wanted to do it within phone, I highly doubt though.
Click to expand...
Click to collapse
thank you coolsandie, the android is based on linux, isn't it, and if I can, I can install busybox.and using the terminal like Android Terminal Emulator, but I do not know the procedure. like you, it's more complex,
Robbie P said:
It could be done using this post http://forum.xda-developers.com/showpost.php?p=20227868&postcount=1124 and a hex editor from play store on your phone. But would be even more fiddly than on pc I would imagine, unless your phone has a largish screen. It could be done though.
If editing the ramdisk, you would need to unpack and repack after editing, which usually requires linux. I recently found http://forum.xda-developers.com/showthread.php?t=2036528 for PC, but have not had a chance to try it yet, seems best solution for OP
Click to expand...
Click to collapse
it's good tool, it can unpack the boot.img, but as to the kernel, I don't know how to unpack. but this tool add to my favorite, thanks Robbie.
OK, I find the app, names: yaffs, the author I don't know because I found in the search engine. so I also cannot find the course
then the app,
Hi All,
I'm looking for a windows utility, that can edit, customize and update an existing rom...
Basically, I am trying to tweak a Chinese rom to make it more INTERNATIONAL... However I'm not seeing many Windows (GUI) Apps that can do this, and if there is, they've been discontinued at ICS or earliest JB build.
Does anyone know an updated tool that can help me with this please...??
PhilzTouch is supposed to support this, but the package didn't work either...
Thanks, Lister
Lister Of Smeg said:
Hi All,
I'm looking for a windows utility, that can edit, customize and update an existing rom...
Basically, I am trying to tweak a Chinese rom to make it more INTERNATIONAL... However I'm not seeing many Windows (GUI) Apps that can do this, and if there is, they've been discontinued at ICS or earliest JB build.
Does anyone know an updated tool that can help me with this please...??
PhilzTouch is supposed to support this, but the package didn't work either...
Thanks, Lister
Click to expand...
Click to collapse
Philz touch is a recovery, not a ROM editing utility
Hi @DSA,
Yeah I'm aware it's a recovery, as I use it on my Note. However when I've tried to research looking for one of these Apps, some people suggested (and have seen in past, on unrelated topics) that with PhilzTouch you can clone your existing LIVE OS, and package it up to a Flashable Zip.
Well it did create a flashable zip, and it even puts it in a folder called "Custom Roms" which is based on a "Update.zip" file, even though it has a different name... However it doesn't flash, and when opened the file, it has .TAR files included and not a normal rom package.
So yeah, struggling to find anything that works... I came close to building/porting a rom earlier, however I received FCs afterwards...
Thanks, Andy
DSA said:
Philz touch is a recovery, not a ROM editing utility
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi @DSA,
Yeah I'm aware it's a recovery, as I use it on my Note. However when I've tried to research looking for one of these Apps, some people suggested (and have seen in past, on unrelated topics) that with PhilzTouch you can clone your existing LIVE OS, and package it up to a Flashable Zip.
Well it did create a flashable zip, and it even puts it in a folder called "Custom Roms" which is based on a "Update.zip" file, even though it has a different name... However it doesn't flash, and when opened the file, it has .TAR files included and not a normal rom package.
So yeah, struggling to find anything that works... I came close to building/porting a rom earlier, however I received FCs afterwards...
Thanks, Andy
Click to expand...
Click to collapse
adb pull /system then zip with 7zip or winrar you will also need to make an updater script and updater binary for your device. with correct blocks so that the rom flashes correctly. so, you need to search for how to create an updater binary for your device and the correct blocks for data, system, and boot img. for your device. if cm has one for your device, you can usally download their rom zip and put all your info you pulled using adb into their zip deleting their's but note you will need your boot image to be pulled also which i do not know how to do