Database Info

[GUIDE] How to create a your own ROM

How to create your own ROM update.zip for the T-Mobile MyTouch 3G
Things you will need to perform this:
Java SE Dev Kit from Sun. java.sun.com
May need Cygwin with zlib0 package, from cygwin.com
This will give you Android 1.6 with all the Google applications, Root access.
I never found one place where all this information is all together, so that is why I compiled this together.
Now anyone can do this themselves.
Thanks to all the hard work others have done before this.
1.
First Root your phone and install a new Recovery image, either Amon Ra or Cyanogens Recovery image.
Instructions for one-click root: http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
2.
Download the Android 1.6 System image from
http://developer.htc.com/google-io-device.html
extract the contents of signed-google_ion-img-14721.zip.
3.
You now need to extract the contents of system.img using a tool called unyaffs. The source code is here:
http://code.google.com/p/unyaffs/downloads/list
Or download a prebuilt win32 version here.
http://jiggawatt.org/badc0de/android/index.html
Note you may also need cygwin1.dll and cygz.dll (zlib0 package). Found at cygwin.com
Of course if you already have Cygwin installed with the GCC packages, you can just compile it yourself. Then also
if you comment out the line 67 to "// symlink(oh->alias, full_path_name);"
then it will not create the copies of the symbolic link file, and you will not have to worry about deleting duplicate
symbolic link files later.
Now in the directory where system.img exists, create a new directory called "system"
go into the "system" directory.
type the following command:
unyaffs ..\system.img
That should extract all the files from the system.img file into the system directory.
4.
Now we just need to clean up some items. Since the system.img is a linux file system, it has symbolic
links built into it, but when we extracted it, it just created duplicate files, if you used the prebuilt unyaffs.exe.
So we can just delete the duplicates and have a script recreate the symlink on install.
So we need to delete some extra files from the system\bin directory.
Run the attached DeleteExtras.bat file from the same directory where system.img is in.
If you notice, all the files it deletes are 28 byte files, and if you open them in notepad only contain:
"!<symlink>toolbox..."
And we will remake the symbolic link when it is installed.
5.
Now from the directory where the system.img is, enter the following commands
mkdir META-INF
mkdir META-INF\com
mkdir META-INF\com\google
mkdir META-INF\com\google\android
Now copy the included file "update-script.txt" into the "META-INF\com\google\android" directory
and RENAME it to just "update-script".
This update-script gets run to recreate the symbolic links.
Not sure if these two are needed but they are in some custom ROMs here:
Copy the two files "fix_permissions" and "flash_image" to the "system\bin" directory.
6.
-- Optional --
These add root and Superuser access to the ROM, plus the Terminal Emulator application.
Copy the file "su" from Cyanogen's rom to the folder "system\bin"
Copy the file "Superuser.apk" to the folder "system\app"
Copy the file "Term.apk" to the folder "system\app"
You can also replace the "system\etc\apns-conf.xml" with a more complete one from here:
http://forum.xda-developers.com/showthread.php?t=547718
or here
http://docs.google.com/Doc?docid=0AZNbAmKkmakoZGZxZHNwMnpfMjJkaHg3ejN3eg&hl=en
Turn data roaming off by default by editing line in the build.prop file:
ro.com.android.dataroaming=false
Also to fix the Market program to show "Protected" applications change the ro.build.fingerprint line to the following:
ro.build.fingerprint=tmobile/opal/sapphire/sapphire:1.5/COC10/150449:user/ota-rel-keys,release-keys
Only phones with a fingerprint of a "released" device can access some market applications.
--------------
7.
Now we just need to create a ZIP file for the final ROM
Zip up the following file and two folders:
boot.img
META-INF
system
8.
Now sign the zip file.
See here how to sign a ZIP file for flashing it.
http://androidforums.com/developer-101/8665-how-signing-roms.html
9.
Copy it to your SD card, boot into recovery, wipe, apply the update, Reboot.
You are now running Android 1.6!

the finger print is found in build.prop is this correct and what app do you use to edit your build.prop

Yes the fingerprint is in build.prop
Make sure to use an advanced text editor like TextPad, UltraEdit, or EditPlus. It has to handle UNIX text files.
Also use this for the update_script.

how abt kernel parameters?

How would one go about customizing this with Hero? Or is that not possible at this point?

detox702 said:
How would one go about customizing this with Hero? Or is that not possible at this point?
Click to expand...
Click to collapse
Would like more info on hot to incorporate senseui

Thanks for sharing... Got nothing to do today, so I experimented on my phone... I gotta say, I'm pretty amazed w/ this feature. Was able to sort out and organize my files.
Kudos!

How does one create the system.img file once one has the system files...
What I want to do is use some of the custom roms here and put it on an AVD emulator system.
Can someone help with this please.
NOTE: I dont have linux. So if there is an alternative to mkbootimg, it will be excellent.

the ion is the 32b if I'm not mistaken?
Is there an image for the 32a or do we always have to use the ion and throw a patch over it?
Sorry if this is a stupid question

in step 5. it says
Not sure if these two are needed but they are in some custom ROMs here:
Copy the two files "fix_permissions" and "flash_image" to the "system\bin" directory.
Where do i copy the files from or download please?
thanks in advance
P.S. any tips on changing the splash screen would be much appreciated.

DeleteExtras.txt or DeleteExtras.bat doesn't work. I have to delete the extra files by myself - one by one.

codysoloman said:
DeleteExtras.txt or DeleteExtras.bat doesn't work. I have to delete the extra files by myself - one by one.
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=633246

Perhaps someone here knows or could point me to the right resources, but if the phone isn't supported by Cyanogen, how would a custom rom be made in that case?
How is a custom rom made from scratch? Since android is just linux, is it simply a matter of building it with the right drivers for the phone and installing it? How can an image be manually copied to the phone if it isn't supported by Clockwork recovery? How can it's steps be manually done?

ping pong...

Can i install my own rom on samsung ace?????

anybody knows how to make a ROM customized and make a "update.img" to run on a un-rootable device? I know when you backup a linux image for example ubuntu, this image will run on all other PCs, the image will automatically knows the new PC's drivers and adapt everything with that, is it what happening to an android too ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------
and pls let me know how to open/edit a "update.img" file, thnx

Question
androidcustomrom said:
How to create your own ROM update.zip for the T-Mobile MyTouch 3G
Things you will need to perform this:
Java SE Dev Kit from Sun. java.sun.com
May need Cygwin with zlib0 package, from cygwin.com
This will give you Android 1.6 with all the Google applications, Root access.
I never found one place where all this information is all together, so that is why I compiled this together.
Now anyone can do this themselves.
Thanks to all the hard work others have done before this.
1.
First Root your phone and install a new Recovery image, either Amon Ra or Cyanogens Recovery image.
Instructions for one-click root: http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
2.
Download the Android 1.6 System image from
http://developer.htc.com/google-io-device.html
extract the contents of signed-google_ion-img-14721.zip.
3.
You now need to extract the contents of system.img using a tool called unyaffs. The source code is here:
http://code.google.com/p/unyaffs/downloads/list
Or download a prebuilt win32 version here.
http://jiggawatt.org/badc0de/android/index.html
Note you may also need cygwin1.dll and cygz.dll (zlib0 package). Found at cygwin.com
Of course if you already have Cygwin installed with the GCC packages, you can just compile it yourself. Then also
if you comment out the line 67 to "// symlink(oh->alias, full_path_name);"
then it will not create the copies of the symbolic link file, and you will not have to worry about deleting duplicate
symbolic link files later.
Now in the directory where system.img exists, create a new directory called "system"
go into the "system" directory.
type the following command:
unyaffs ..\system.img
That should extract all the files from the system.img file into the system directory.
4.
Now we just need to clean up some items. Since the system.img is a linux file system, it has symbolic
links built into it, but when we extracted it, it just created duplicate files, if you used the prebuilt unyaffs.exe.
So we can just delete the duplicates and have a script recreate the symlink on install.
So we need to delete some extra files from the system\bin directory.
Run the attached DeleteExtras.bat file from the same directory where system.img is in.
If you notice, all the files it deletes are 28 byte files, and if you open them in notepad only contain:
"!<symlink>toolbox..."
And we will remake the symbolic link when it is installed.
5.
Now from the directory where the system.img is, enter the following commands
mkdir META-INF
mkdir META-INF\com
mkdir META-INF\com\google
mkdir META-INF\com\google\android
Now copy the included file "update-script.txt" into the "META-INF\com\google\android" directory
and RENAME it to just "update-script".
This update-script gets run to recreate the symbolic links.
Not sure if these two are needed but they are in some custom ROMs here:
Copy the two files "fix_permissions" and "flash_image" to the "system\bin" directory.
6.
-- Optional --
These add root and Superuser access to the ROM, plus the Terminal Emulator application.
Copy the file "su" from Cyanogen's rom to the folder "system\bin"
Copy the file "Superuser.apk" to the folder "system\app"
Copy the file "Term.apk" to the folder "system\app"
You can also replace the "system\etc\apns-conf.xml" with a more complete one from here:
http://forum.xda-developers.com/showthread.php?t=547718
or here
http://docs.google.com/Doc?docid=0AZNbAmKkmakoZGZxZHNwMnpfMjJkaHg3ejN3eg&hl=en
Turn data roaming off by default by editing line in the build.prop file:
ro.com.android.dataroaming=false
Also to fix the Market program to show "Protected" applications change the ro.build.fingerprint line to the following:
ro.build.fingerprint=tmobile/opal/sapphire/sapphire:1.5/COC10/150449:user/ota-rel-keys,release-keys
Only phones with a fingerprint of a "released" device can access some market applications.
--------------
7.
Now we just need to create a ZIP file for the final ROM
Zip up the following file and two folders:
boot.img
META-INF
system
8.
Now sign the zip file.
See here how to sign a ZIP file for flashing it.
http://androidforums.com/developer-101/8665-how-signing-roms.html
9.
Copy it to your SD card, boot into recovery, wipe, apply the update, Reboot.
You are now running Android 1.6!
Click to expand...
Click to collapse
Could you tell me where I can correct the fake data in the phone like the real RAM is 512 MB but it say 1GB ,can you tell me how to
correct it thanks in advance:good:

[Q] doubt about boot animation

Hi, im using cm7 , and just flashed trinity 1.1uv
the boot animation changed for the trinity one.
but the one that comes with cm7 is way better!
how can i change it?
do i need to delete the bootanimation.zip from the kernel before flashing it?
thx for the attention

hamtar0 said:
Hi, im using cm7 , and just flashed trinity 1.1uv
the boot animation changed for the trinity one.
but the one that comes with cm7 is way better!
how can i change it?
do i need to delete the bootanimation.zip from the kernel before flashing it?
thx for the attention
Click to expand...
Click to collapse
Sorry for thanks ^^
1. extract your downloaded cm build and go to system/media copy bootanimation.zip
2. copy to your sdcard
3. push to system/media on phone & delete /system/media/audio/poweron
4. reboot
5. enjoy

Actually, you can extract the bootanimation.zip from the rom, and then directly use adb, skipping the sdcard altogether:
adb remount
adb push bootanimation.zip /system/media/
The above works provided your copy of adb is included in your PATH system variable and that you're running it from the directory you've extracted bootanimation.zip. Otherwise, type bootanimation.zip's full path in the push command, and type the command in the directory where adb is installed.
Voilà!
Now, some extra tips:
You can rename files as you push them with adb, which means you could have multiple boot animations in a directory on your computer, and push whichever one you want on a whim, ie:
adb push bootanimation_somethingelse.zip /system/media/bootanimation.zip
There are many articles out there on making your own animation, I'll just add that 7zip works pretty well to make the archive (use the "store" method), optipng might repair images that don't seem to work otherwise, also make sure you have a text editor that can handle Unix-style line returns for the desc.txt file.
I personally use the stock Nexus boot animation, but with one addition: I put contact information in case the phone is found.
Goodbye,
Darkshado

Darkshado said:
Actually, you can extract the bootanimation.zip from the rom, and then directly use adb, skipping the sdcard altogether:
adb remount
adb push bootanimation.zip /system/media/
The above works provided your copy of adb is included in your PATH system variable and that you're running it from the directory you've extracted bootanimation.zip. Otherwise, type bootanimation.zip's full path in the push command, and type the command in the directory where adb is installed.
Voilà!
Now, some extra tips:
You can rename files as you push them with adb, which means you could have multiple boot animations in a directory on your computer, and push whichever one you want on a whim, ie:
adb push bootanimation_somethingelse.zip /system/media/bootanimation.zip
There are many articles out there on making your own animation, I'll just add that 7zip works pretty well to make the archive (use the "store" method), optipng might repair images that don't seem to work otherwise, also make sure you have a text editor that can handle Unix-style line returns for the desc.txt file.
I personally use the stock Nexus boot animation, but with one addition: I put contact information in case the phone is found.
Goodbye,
Darkshado
Click to expand...
Click to collapse
My Version is more noob like so see what he will choose D

Hey guys,
i've found another 'very' good kernel which, i think, does not change your boot animation. It has bln-support and voodoo, it works for both 9020 and 9023 users. Just check it out:
http://forum.xda-developers.com/showthread.php?t=1100448

thank you guys!

Insecure Boot Image for the T-Mobile myTouch 4G Slide (for 'adb remount' access etc.)

You must have a 'S-OFF' device to install this recovery image!
Here is my insecure boot image for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. This will provide you with root ADB access (for 'adb remount' etc.) In order to flash this image, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the insecure boot image file from here
Copy the file to /data/local ('adb push doubleshot.boot.insecure.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.boot.insecure.img of=/dev/block/mmcblk0p20')
Reboot to test ('adb reboot').
That's it!
P

thank you. but i'm chinese so i not very understands. thank for your expend

This down loads a txt. I assume we just rename it .img?
Sent from my myTouch_4G_Slide using XDA Premium App

It should download a .img file
if you got a .txt, renamed it to a .img and then dd'd it, you probably destroyed your boot partition and will need to nandroid.

When I downloaded the file and extracted it I ended up with a txt and an img file. Make sure you use the IMG file like ratchetrizzo said; I'm not sure if renaming the txt file is enough.

And that is why I asked first!

paulobrien;15855875
[list said:
[*]Download the insecure boot image file from here
[*]Copy the file to /data/local ('adb push doubleshot.boot.insecure.img /data/local')
[*]Write the image to the recovery partition ('dd if=/data/local/doubleshot.boot.insecure.img of=/dev/block/mmcblk0p20')
[*]Reboot to test ('adb reboot').[/list]
Click to expand...
Click to collapse
Sigh, nvm.

[Q] use 7za.exe to create update.zip

I have created a batch file to edit new roms I download. Basicilly the batch file takes the rom extracts it, then deletes all the apk's etc I dont want and then zips it up again as update.zip.
Once it has done this, it then copies the update.zip to my SD card and then uses the adb commmand to reboot the phone into the recovery menu.
This all works fine. The problem I have is when I go to flash the zip I get error aborted. I found that when it creates the zip file it doesn't add the META-INF folder as uppercase in the update.zip file.
As linux is cse sensitive I think this is my problem. Is there any way to use 7za.exe to add it as upper case into the update.zip and all the other folders as lower case?
The command I use to create the zip is: 7za a -tzip update.zip *

Any ideas on how to zip the file in dos and preserve the uppercase folders?
Fixed it needed to use the -r switch with 7za. Now when I get a new rom I can fully extract it, delete all the files I want zip it transfer it to the phone and reboot the phone!

(Help) SD can not be mounted??

Not sure what happened during a ROM flashing, however, all in all, I can only boot my phone into Bootloader and recovery...nothing else, it says *error mounting /sdcard*So I can't restore or flash a previous backed up ROM. So I guess it would be called a soft brick. Any way of getting out of this? I tried to adb push, doesn't work. Tried the All in One kit, still nothing.
For anyone who can help me with my phone, I will compensate you for your time and knowledge.
If all else fails, I will just have to call and have the phone replaced.
Thanks in advance.

dont panic try this http://forum.xda-developers.com/showthread.php?t=1630459

I got as far as being able to mount my sdcard, now I can't push any files on to my phone?

put the rom in your adb folder, Use the command
adb push nameofrom.zip /sdcard
then in CWM it should appear
Check here for a full guide http://forum.xda-developers.com/showthread.php?t=1667929

C:\androidsdk\tools>adb push ROM.zip /sdcard/ROM.zip
cannot stat 'ROM.zip': No such file or directory
This is what it says when I try to push the ROM

and the rom is in the tools folder ?
you also naming it right ?

don't add the rom.zip after sdcard
i think that means you are pushing it to a rom.zip folder already on card--not 100% sure though

Thongvilay said:
C:\androidsdk\tools>adb push ROM.zip /sdcard/ROM.zip
cannot stat 'ROM.zip': No such file or directory
This is what it says when I try to push the ROM
Click to expand...
Click to collapse
Could also be you're not typing the path to the file correctly.
Do this, on your PC navigate to the folder where you have the ROM.zip file (in your case the tools folder in androidsdk.
Hold down the SHIFT button while right clicking on the "tools" folder
A drop down menu will appear and chose "Open Command window here"
You should get a CMD window with the correct path.
Also for me it's always "platform-tools" folder that I put my file to be push in.

hey BBF nice to see still around--loving my 1s
sorry for off-topic guys