Related
Hi everyone, i was wondering if other brands like htc, motorola, sony ericson, so on have websites like the "samfirmware.com" that samsung phones have, somewhere where all the stock firmwares are listed and available for download + instructions and too many handy yet simple options like in samfirmware.com..... if you know such websites please post the links here. thanks!
naranova7 said:
Hi everyone, i was wondering if other brands like htc, motorola, sony ericson, so on have websites like the "samfirmware.com" that samsung phones have, somewhere where all the stock firmwares are listed and available for download + instructions and too many handy yet simple options like in samfirmware.com..... if you know such websites please post the links here. thanks!
Click to expand...
Click to collapse
WELL... the answer its... there isn´t any sites like samsungfirmwares or samfirmwares because the rest of phones have another functioning... samsung works with odin and you can flash the new rom from the pc,,, but the majority of the rest of devices works with a recovery menu and from here you flash it... in a few words you dónt need any program like odin etc...
here in XDA you have a lot of pretty and useful threads for scroll the rom that you likes and flash it.....and the better thing all of them are customized for better performance and for do it more beautiful...
the last thing.. sorry for my bad english,,, and if you want any link browse by yourself for it,,, and select that you likes...
at the XDA main page you can select the specific thread of your device, and then select the development section and browse roms....
your device deserves a hard work
You can download the stock roms for the Evo in RUU form from HTC, and they are ran on the computer. You can also download the RUU in zip form to flash through the bootloader. You can get these from the shipped roms site.
Sent from my Evo using Tapatalk
dsixda's Android Kitchen - Now for Samsung Galaxy SII Skyrocket
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S2 Qualcomm MSM8660-based (non-Exynos) custom ROMs. This also applies to the following devices:
AT&T Skyrocket
T-Mobile SGH-T989
Telus Galaxy SII X
Rogers Galaxy SII LTE
Bell Galaxy SII HD LTE SGH-I757M
Galaxy Note SGH-I717
IMPORTANT: If you have the original Galaxy SII GT-I9100 or its variants such as the Galaxy Note SGH-N7000, then click here to follow this other thread instead.
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.181, you can now create your own Galaxy S2 Skyrocket ROMs with the kitchen.
I'd like to thank twopumpchump (who owns an AT&T Skyrocket) and -Mr. X- (Telus Galaxy S2 X) 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 S2 Skyrocket or equivalent with a ClockworkMod 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, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT: To verify your variant of the Galaxy S2 Skyrocket works in the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2x_variants/ folder then just create a blank file there with same file name as your device's ro.product.device value.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S2 Skyrocket, 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, tomb.img.ext4 (if it exists) and boot.img (and optionally: cache.img.ext4)
TAR file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4) NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
ZIP file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
Custom ROM:
ZIP file created only 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 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:
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 S2 Skyrocket or equivalent SGS2 LTE devices in this thread!
Most of all, have patience, take your time and enjoy!!
Reserved...
Reserved ...
Nice work guys. Enjoyed cooking rims fir my g2 and mt4g with this. I know what I'm gonna be doing soon
Sent from my SGH-I727 using Tapatalk
now we should have roms popping up everywhere
Sent from my SAMSUNG-SGH-I727 using xda premium
Nice job on the guide I'm gonna sticky this, hopefully alot of people will learn how to cook their own roms for Skyrocket!
A must use for new people who wants to get their feet wet with deving
Sent from my SGH-I727 using xda premium
I will be playing w this during the weekend.
Thanks!
Oh yes, I will be having fun with this! As a non-dev this will be a great way for me to get my feet wet. Thank you!
saweeeeet!!
Thanks again for getting this set up.
I was about to post this last night but dozed off. Great stuff...!
Awesome! Much appreciated! Thought you were done updating this...nice surprise!
Cboss said:
Awesome! Much appreciated! Thought you were done updating this...nice surprise!
Click to expand...
Click to collapse
Yes I was done but felt I needed to put a stop to those persistent tweets/questions from the original SGS2 thread.
thanks so much!
Awesome, great to see this for SkyRocket. Now if we can cook from ICS sources, that had be amazing! I guess we will haev to wait till atleast Galaxy S2 gets ICS officially. Nexus S got it today, jealous!
kornklown69 said:
now we should have roms popping up everywhere
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah, can't wait for those "roms"
Is there currently a way to develop on top of a vanilla android rom? I personally don't like touchwiz or the carrier branded roms whatsoever. New to the development for this device so i am not exactly sure what's available.
Seannoxious said:
Is there currently a way to develop on top of a vanilla android rom? I personally don't like touchwiz or the carrier branded roms whatsoever. New to the development for this device so i am not exactly sure what's available.
Click to expand...
Click to collapse
Well, creating a custom ROM with the kitchen is not really development. You would need to compile the AOSP source code or a Cyanogen source to develop a vanilla ROM. The kitchen could be used afterwards to add other things to it like deodexing, root etc.
I have had limited success using the kitchen with a Samsung Galaxy S2 Cyanogen ROM, it depends on how complex the updater-script is. It did work fine on other devices like the Nexus S.
dsixda said:
Well, creating a custom ROM with the kitchen is not really development. You would need to compile the AOSP source code or a Cyanogen source to develop a vanilla ROM. The kitchen could be used afterwards to add other things to it like deodexing, root etc.
I have had limited success using the kitchen with a Samsung Galaxy S2 Cyanogen ROM, it depends on how complex the updater-script is. It did work fine on other devices like the Nexus S.
Click to expand...
Click to collapse
Understood i read some things on the cyanogen forums stating that they dont have plans to send out a skyrocket rom. They said that the att gs 2 is so similar to the international and the skyroxket using different chips for the blazay blazay blazay highly unlikely to develop a from for the skyrocket.
If he ports of a cyanogen are flakey and cm has no plans to support the phone BC of little demand or whatever do you know of anybody trying to pursue compiling a source code for the gs2 sr? I have Dev experience and would like to see more options for rooms. Not to discount the work that has already been done atall. I just personally love that vanilla feel. I also like launched pro and works much better in that environment from my experience.
Please i need to download the OFFICIAL - ORIGINAL rom which named [android-4.0.4_r2.1 - Build num. IMM76L]
please provide me with link, i tried to download it from the android developer site but i couldnt deal with that site !
i think that rom could be installed on p6800 without any problems, am i right ?
thnxs for your time & helping
All firmware for Galaxy tab 7.7
http://samsung-updates.com/device/?id=GT-P6800
Thnxs 4 replaying
is that OFFICIAL roms or customized ones ?
can you tell me how can i backup the original rom which installed on my tab in case the new rom cause any problems ? i think its by Odin but not sure how !
eng. Badr said:
is that OFFICIAL roms or customized ones ?
can you tell me how can i backup the original rom which installed on my tab in case the new rom cause any problems ? i think its by Odin but not sure how !
Click to expand...
Click to collapse
Please review these links for your initial answers these links are in the Galaxy Tab 7.7 General thread section. Searching these threads can be very helpful before you do changes to your Tab. You can then ask very specific questions and should get lots of help. Lots of the people who post to these threads provide superb help if you show and can explain what you did or want to do after a little research on your part. Hope this helps you some.
http://forum.xda-developers.com/showthread.php?t=1587072 and http://forum.xda-developers.com/showthread.php?t=1487991
Hello,
to all of you.
Actually, from some days, I am seeing a strange command or flashing of "Sending..." command on mine Galaxy Tab 7.7, I am using base version of the Operating System that is Honeycomb.This "Sending..." command appearing above the Taskbar and keep there for few seconds and then disappears, it even comes when I not use Internet or other type of connectivity.So, please solve this, I have scanned the Tab but not found any virus or malware.Please advice.Thank you.
Regards,
MOBILGEEK
Maybe some ad based process/service.?
Try AppBrain Ad Detector ; https://play.google.com/store/apps/details?id=com.appspot.swisscodemonkeys.detector&hl=en
Or Air Push Detector app.
Would also strongly suggest to get rid of the HC for ICS or JB firmware
Sent from my GT-I9500 using xda premium
Hello,
UpInTheAir
Firstly, Thank You very much for the reply, I also want to upgrade my Tab's Operating System to ICS or JB, preferably to JB, so, Can you please tell me some good and reliable JB ROM?, actually, here in my Country, I didn't find the official update from Samsung.So, please advice.Thank You.
Regards,
MOBILGEEK
I don't know what model you have. P6810 or P6800?
I won't recommend any custom ROM (not to say anything wrong with any), but probably better for you to start with official, enjoy it, then decide what may interest you in the way of mods etc. Rooting guides and methods found in the forum.
For official firmware, search samsung-updates.com or sammobile.com . I am not sure what language may be supported though, but English is in all cases.
Use ODIN to flash, there are many guides around the forums. NEVER tick "re-partition" unless flashing a PIT file. You will not need this unless a partition becomes corrupted etc. There are morons out there that suggest to do that !
There are supported 4.2.2 JB custom ROMs by daniel for both device models, search the forums. For P6800 JB 4.1.2 there is erobot ROM (based on official Samsung MD3 firmware), but unsupported now.
For P6810, there it's only official ICS available (I don't support custom SkyHigh ROM anymore). As mentioned, custom JB from daniel, built from source, but not based on official Samsung firmware.
One thing, never factory reset from stock HC or ICS stock recovery to avoid the "brick bug".
Just search around the forum, and do your homework before doing anything.
Best of luck and enjoy your "new" device, because it'll feel new once you get rid of that garbage HC
Cheers,
UITA
Sent from my GT-I9500 using xda premium
Like all of you who purchased this product since it's release in Spring 2012, I/we have all been awaiting an update from ICS 4.0.4 to JB. And up till now it hasn't happened.
Over the last 8 months I have been in contact regularly with AU's tech support to find out when it will be released and which version of JB it will be. The answer has always been;" we are working on it"; "we don't want to make any mistakes, since an update on another phone was a poor release", etc.
Well today I was browsing through Joshin and saw the spects of the new Galaxay Note 3 KDDI AU has just release. It's OS? JB 4.3. Yahoo I thought, we're going to get our update.
So I go to my local AU shop, where I bought my phone and showed them a copy of the new Note 3 specs and asked when will the update roll out for the Galaxay S3 SCL21 Progre? Answer direct from a Technical Services Manager: "We have never had any intention to release an OS update beyond ICS 4.0.4, because by the time your contracts run out you'll be wanting the Galaxy S4".
WTF! They have never had any intention and just thought that we would roll over and take it up the arse and just by the next version.
Well I'll tell you what I'm going to do, and I told the Service Rep the same.
When my contract runs out I'm going to DOCOMO. Their customer service is way better than AU's, the range of their XI LTE is much broader and faster than Au's (ever had no bars next to a DOCOMO user with full bars?), and they give their android users rapid, regular updates.
KDDI AU needs to be taught a lesson in company ethics. If every KDDI AU Galaxy S3 user changed over to DOCOMO at the end of their contract, they would get the message. DON'T SCREW YOUR CUSTOMER BASE!
***************************************************
On a side issue, since we are not going to get our update, I've been researching possibilities for a custom stock ROM to bring us at least up to JB 4.2.2 is to use Verizon's current stock ROM since it has the same ROM structure and specs as the Progre. I'm a complete novice but if there is anyone willing to assist I have the Stock ROM, which seems to have been removed from SamMobile for some reason.
Confused what is the question .
There is no question.
This is an announcement. And information sharing post.
firechild said:
There is no question.
This is an announcement. And information sharing post.
Click to expand...
Click to collapse
is it for GT-i9300/i9305 ?
This is for the KDDI AU SCL21 also known as the Progre.
After a lot of searching I found it has exactly the same specs as the Verizon SGH-1535.
That is a Qualcomm MSM8960 Snapdragon 1.5GHz Dual-core with the Adreno 225 GPU.
Therefore the JB4.2
2 for the Verizon should be compatible with the KDDI AU Progre, with a little tweaking.
firechild said:
This is for the KDDI AU SCL21 also known as the Progre.
Click to expand...
Click to collapse
This forum is not for this device....
firechild said:
Verizon SGH-1535.
Click to expand...
Click to collapse
Nor is it for this. This is the GT-i9300 forum which has no specs the same as the verizon S3.
Also Q&A is for questions and answers, not announcements.
Suggest using the report /!\ button to request a moderator review your post and move it to wherever is correct
rootSU said:
This forum is not for this device....
Nor is it for this. This is the GT-i9300 forum which has no specs the same as the verizon S3.
Also Q&A is for questions and answers, not announcements.
Suggest using the report /!\ button to request a moderator review your post and move it to wherever is correct
Click to expand...
Click to collapse
Wrong... This is the sch-i535 forum bud.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Wrong... This is the sch-i535 forum bud.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
This thread was moved to our forums.
Sent from my SCH-I535 using Tapatalk 4
Thanks to the moderator
Thank you for the help in giving this announcement a proper home.
Since I haven't used the forums since we were doing the translations for the Softbank HTC X01HT Windows phone way back in the early 2000's, the forum has become a lot more diverse.
So I sincerely apologize for the original incorrect placement.
Thank you you again.
Creating a KDDI AU Galaxy S3 SCL21 (Progre) JB 4.2.2 ROM
If there are any developers that would like to assist in modding the Verizon SGH-1535 JB 4.2.2 ROM to suit the KDDI AU Galaxy S3 SCL21 (Progre), any assistance or pointers would be appreciated.
My initial thoughts are to take the I535VRBMF1_I535VZWBMF1_VZW.zip extract the files;
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
And replace NON-HLOS.bin and recovery.img from the current KDDI AU Galaxy S3 SCL21 (Progre) ROM (SCL21KDALJD_SCL21KDIALJD_KDI).
Now as I've said previously I am a complete novice to ROM cooking. So would this be a viable solution, or would it need to be done differently?
Our MF1 ROM is only 4.1.2 by the way.
Oh I was under the impression that it was 4.2.2.
4.1.2 is better than 4
0.4.
tylerlawhon said:
Wrong... This is the sch-i535 forum bud.
Click to expand...
Click to collapse
Not when I wrote it, it wasn't
firechild said:
If there are any developers that would like to assist in modding the Verizon SGH-1535 JB 4.2.2 ROM to suit the KDDI AU Galaxy S3 SCL21 (Progre), any assistance or pointers would be appreciated.
My initial thoughts are to take the I535VRBMF1_I535VZWBMF1_VZW.zip extract the files;
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
And replace NON-HLOS.bin and recovery.img from the current KDDI AU Galaxy S3 SCL21 (Progre) ROM (SCL21KDALJD_SCL21KDIALJD_KDI).
Now as I've said previously I am a complete novice to ROM cooking. So would this be a viable solution, or would it need to be done differently?
Click to expand...
Click to collapse
Interesting, I had the same idea, but never followed up b/c it seemed troublesome. I had asked about how to extract files from ROMs on android stackexchange but never got a reply. If you have an idea of how to do it, I could give it a shot.
Extracting Files from a ROM
filmost said:
Interesting, I had the same idea, but never followed up b/c it seemed troublesome. I had asked about how to extract files from ROMs on android stackexchange but never got a reply. If you have an idea of how to do it, I could give it a shot.
Click to expand...
Click to collapse
It's fairly simple really to extract the individual files from a ROM. If you're using Windows based OS you can extract with WinRAR (Google it if you don't already have it)
When you first open the zip file with WinRAR you will see 2 files, the .dll file is unimportant it's the I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 file you'll be using.
Double click on this and after a while another WinRAR windows opens, again with the file I535VRBMF1_1152558_REV09_user_low_ship.tar.md5, but when you double click this you will see the ROM file structure.
IF YOU DON'T HAVE A COPY OF THE SGH-I535 (4.1.2) ROM YOU CAN DOWNLOAD FROM HERE:
http://www.androidfilehost.com/?fid=23125694133305576 (Thanks to Senior Member, DarkMenace for providing a download link)
IF YOU DOWNLOAD FROM HERE PLEASE GIVE DarkMenace SOME THANKS!
Of course if you're running Unbuntu or similar the extraction is just as easy using either a terminal or Gnome GUI.
Then I guess filmost it's just a matter of replacing the recovery.img and NON-HLOS.bin from the KDDI AU Galaxy S3 SCL21 Progre ROM into the Verizon ROM.
Does That help you in any way?
Adding to the above Post
To view the contents of each file is easily done using Unbuntu. But if you're using Windows;
Read this thread by Forum moderator rwilco12:
http://forum.xda-developers.com/showthread.php?t=2138885
And remember to give thanks.
firechild said:
It's fairly simple really to extract the individual files from a ROM. If you're using Windows based OS you can extract with WinRAR (Google it if you don't already have it)
When you first open the zip file with WinRAR you will see 2 files, the .dll file is unimportant it's the I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 file you'll be using.
Double click on this and after a while another WinRAR windows opens, again with the file I535VRBMF1_1152558_REV09_user_low_ship.tar.md5, but when you double click this you will see the ROM file structure.
IF YOU DON'T HAVE A COPY OF THE SGH-I535 (4.1.2) ROM YOU CAN DOWNLOAD FROM HERE:
http://www.androidfilehost.com/?fid=23125694133305576 (Thanks to Senior Member, DarkMenace for providing a download link)
IF YOU DOWNLOAD FROM HERE PLEASE GIVE DarkMenace SOME THANKS!
Of course if you're running Unbuntu or similar the extraction is just as easy using either a terminal or Gnome GUI.
Then I guess filmost it's just a matter of replacing the recovery.img and NON-HLOS.bin from the KDDI AU Galaxy S3 SCL21 Progre ROM into the Verizon ROM.
Does That help you in any way?
Click to expand...
Click to collapse
I'm on Linux actually, and I should probably clarify. I was trying to figure out how to extract APKs. The img files are no problem. Also, instead of porting to Stock Verizon, I am thinking to port to a Cyanogenmod rom for the Verizon SCH-I535.
Today I figured out how to create a deodexed version of the SCL21 stock rom downloaded from sammobile. I have created several CWM compatible images, but got a status 0 during flashing. It took me awhile to track down the cause. Hopefully this last image I created will flash properly, but I won't be able to tell until later tonight. If it's successful, then I'll look at porting to Cyanogenmod.
filmost said:
I'm on Linux actually, and I should probably clarify. I was trying to figure out how to extract APKs. The img files are no problem. Also, instead of porting to Stock Verizon, I am thinking to port to a Cyanogenmod rom for the Verizon SCH-I535.
Today I figured out how to create a deodexed version of the SCL21 stock rom downloaded from sammobile. I have created several CWM compatible images, but got a status 0 during flashing. It took me awhile to track down the cause. Hopefully this last image I created will flash properly, but I won't be able to tell until later tonight. If it's successful, then I'll look at porting to Cyanogenmod.
Click to expand...
Click to collapse
You're status 0 could be due to CWM issue: I found this post http://forum.xda-developers.com/showthread.php?t=2154762 to create odin flashabale ROMS (I used this to create a backup of SCL21's recovery.img.tar.md5 compatible with Odin and had no problems. Prior I had the status O issue . Perharps that thread will help
You're a lot further along cooking than I am. So have you been able to created a 4.1.2 ROM (or greater than) for the SCL21?
And with porting to Cygenmod, what's the idea behind that?
Extracting the APKs doesn't Titanium backup deal with that?
firechild said:
You're status 0 could be due to CWM issue: I found this post http://forum.xda-developers.com/showthread.php?t=2154762 to create odin flashabale ROMS (I used this to create a backup of SCL21's recovery.img.tar.md5 compatible with Odin and had no problems. Prior I had the status O issue . Perharps that thread will help
You're a lot further along cooking than I am. So have you been able to created a 4.1.2 ROM (or greater than) for the SCL21?
And with porting to Cygenmod, what's the idea behind that?
Extracting the APKs doesn't Titanium backup deal with that?
Click to expand...
Click to collapse
Yeah I have created packages for use with Heimdall (too lazy to VM windows just to use Odin). And actually I think Heimdall is way easier and safer to use.
Anyway, no I haven't worked with anything other than the stock rom. If I can get this to work, then I'll think about other things.
The idea behind porting a Cyanogenmod rom is that its lighter and easier to port (at least from the looks of it). Most custom roms come deodexed (single file apks) so if we have a working deodexed stock rom, we could try copy pasting relevant files, and deleting unnecessary bloat.
Technically we could still try simply replacing certain image files from the verizon stock rom, but I the way I have been going about it is safer and allows for more fine tuned control. Besides, even if the SCL21 and SCH-I535 are basically the same spec, if its as easy swapping certain images files out, someone should have made it by now. For the record though, the SCH-I535 and SCL21 are not only very similar hardware wise, their partition layout from what I have noticed is basically the same.
See what you mean.
filmost said:
Yeah I have created packages for use with Heimdall (too lazy to VM windows just to use Odin). And actually I think Heimdall is way easier and safer to use.
Anyway, no I haven't worked with anything other than the stock rom. If I can get this to work, then I'll think about other things.
The idea behind porting a Cyanogenmod rom is that its lighter and easier to port (at least from the looks of it). Most custom roms come deodexed (single file apks) so if we have a working deodexed stock rom, we could try copy pasting relevant files, and deleting unnecessary bloat.
Technically we could still try simply replacing certain image files from the verizon stock rom, but I the way I have been going about it is safer and allows for more fine tuned control. Besides, even if the SCL21 and SCH-I535 are basically the same spec, if its as easy swapping certain images files out, someone should have made it by now. For the record though, the SCH-I535 and SCL21 are not only very similar hardware wise, their partition layout from what I have noticed is basically the same.
Click to expand...
Click to collapse
filmost - you are a hell of a lot more knowledgeable than me in this. For one thing I wouldn't even know how to compare the partition layout.
As you may have guessed I'm more knowledgeable about windows based, so haven't tried hemdal. As for someone else already have done it, I think it's due to to the smaller user base with the SCL21 than the DOCOMO variations
which are based on the international version.( It seems only KKDI AU, Verizon and Sprint went with the Qualcomm Chip ,whilst the others went with the Exynos chip)
Back to ROMS, have you looked at Android Kitchen?
http://forum.xda-developers.com/showthread.php?t=633246
I just haven't had the time as a house dad with a chronic pain syndrome (can't sit in front of the PC for long periods)
Perhaps this will allow the more fine tuning your looking for.
I actually been looking at SlimROM http://www.slimroms.net/ as an ulternative down the road for a lighter ROM. Have you had a look at them?