[9001][SCRIPTS] The making of ... an ODIN installable package [2011-12-21]

---

Hi all,

Based on the instructions broodplank posted in the Cranium thread (here), I created some scripts to automate the entire process. Not sure whether you find it useful, but here it is.

If you want to do it directly on your device with an cwm-installable zip, please go to this topic:
The making of ... an ODIN installable package with CWM

It will create a zipped version of the md5-tar file of the package compatible with Odin.

Instructions

1. Build your ROM using packages in the forum. Add new apps, change battery, etc., etc. till your satisfied. Make sure not to add sensitive data (user credentials etc)

2. Download a base-ROM like XXKPS and put the following files in the BaseRom folder:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4

3. Boot your device

4. Make sure you have BusyBox installed

5. Connect your device with USB, make sure your sdcard is not mounted on the PC

6. Make sure you have enough space on the internal sdcard; at least 1,84 GB:
system.img.ext4 = 532 MB
tar file = 644 MB
base rom = 100 MB
md5 file = 644 MB

(it would be possible to delete tar file, but I perfer to be safe than sorry)

7. Start BuildOdin.cmd

Thanks to broodplank1337 I now also created some scripts to do it through Cygwin. After rethinking this I could have done it easier by invoking the cygwin commands directly, but for now I am doing it through the shell . See attached.

Downloads... see next post

Regards,

Nika.

Downloads

---

Just the scripts:
http://forum.xda-developers.com/atta...1&d=1324250313

File that includes BaseRom XXKPS (80 MB):
http://www.multiupload.com/FYGRD3LDFG

What it does...

---

Here's a little more explanation of what the script does:

BuildOdin.cmd allows minor customization:

• ROMName = name of the ROM you are creating (CraniumRC5 in my case)
• BaseRomFolder = location it takes the BaseRom files from (default = BaseRom)
• TempBuildFolder = location on device it will use to build your ROM (default = /sdcard/BuildRom, I guess you can also use your /sdcard/external_sd - haven't tested it)

It will execute the following scripts:

• adb-PushBaseromSdcard.cmd - this will push the files from your baserom folder to the build folder on the device
• adb-ExtractRom.cmd - will dump your raw ROM data to files
• adb-MakeImageShell.cmd - will create a tempfile that contains the shell commands that will be executed for tarring and md5-ing the ROM
• adb-GetRom.cmd - will retrieve the ROM and make a zip-file. It retrieves the ROM and renames it to a time/date based file, this may need some customization in some cases as the date/time naming depends on regional settings...

Any questions? Any tips and tricks to make this better? Let me know!



Regards,


Nika.

Wow! Thanks man, very nice! You can create the tar/md5 on your computer by just copying the files from your sdcard to /home/username in cygwin folder then use the same commands

Thank you! Do I have to use Linux or Windows is good?

edit: I've understood by myself :P, thanks again for your work

Originally Posted by broodplank1337

Wow! Thanks man, very nice! You can create the tar/md5 on your computer by just copying the files from your sdcard to /home/username in cygwin folder then use the same commands

Thanks, I'll try cygwin. I tried unxutils, but that added an CRLF instead of LF only at the end of the file and rendered the checksum invalid

Originally Posted by nikagl

Thanks, I'll try cygwin. I tried unxutils, but that added an CRLF instead of LF only at the end of the file and rendered the checksum invalid

Maybe if you invoke a dos2unix? Or 'perl -i -p -e 's/\r//' <your .md5 file>?

Originally Posted by wintel_mac

Maybe if you invoke a dos2unix? Or 'perl -i -p -e 's/\r//' <your .md5 file>?

Good thinking, I did try manually changing the file using a hex-editor but that didn't work and wouldn't be a good permanent fix for something automatic.

I'll try soon ...

Thanks to broodplank1337 I now also created some scripts to do it through Cygwin. After rethinking this I could have done it easier by invoking the cygwin commands directly, but for now I am doing it through the shell . See post #1

Originally Posted by nikagl

Thanks to broodplank1337 I now also created some scripts to do it through Cygwin. After rethinking this I could have done it easier by invoking the cygwin commands directly, but for now I am doing it through the shell . See post #1

Very nice addition! I will use the script for sure