Database Users

[guide] cdma (sprint) working ics guide

Hey All
Several ICS roms have been released for The Galaxy Tab, some claiming to work for the Sprint Cdma version of The tab
I have flashed them all, and I have a working guide for all sprint users to get ICS!
1. Odin back to stock Gingerbread (EF17), then flash the CWM Recovery
2. Download the V4 Rom, and Gapps 7.1 from ROOTZWIKI ([ROM] [CDMA] AOSP ICS / CM9 - BUILD 4.1 [02/03])
3. Go into the Rom Zip, and edit the updater-script and delete assert(getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab" ||
getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100");
3. Place both the rom and g apps on sd card
4. boot into recovery and clear data, them flash rom, mount system, them flash g apps, then reboot
5. You now Have working ICS
Ill post screen shots soon

Thanks! I've been looking for this, I've tried to flash ICS but it always ended up stuck at samsung logo

I am getting installation aborted. I have done all the steps, to include editing the updater-script. Please HELP!!

Can you please post links to what is needed to make this happen?
Sent from my SPH-P100 using XDA App

Really? So the updater-script in the rom starts w/
"ui_print"...
It is the updater that prevents it from working w/ sprint tabs; the edit makes it work
so try
1. MAKE SURE YOU HAVE THE ROM + GAPPS FROM ROOTZWIKI ([ROM] [CDMA] AOSP ICS / CM9 - BUILD 4.1 [02/03])
The rom is called TeamHacksung or something along those lines
2. DO not flash the sms fix
I have not tried it as I use my tab w/ wifi, but when I did flash I was stuck @ black screen
3. When editing the Updater script, unzip the rom, copy the updater-script, edit it, REPLACE THE ONE IN THE ROM THEN REZIP THE ROM, put on SD Card, then follow instructions
IT the GAPPS flash right after rom flash doesnt show up, boot back into recovery, mount system, then flash, then reboot, should fix that
Let me know how it goes

As for Links,
Until I get 8 posts I cannot post outside links
But google
[ROM] [CDMA] AOSP ICS / CM9 - BUILD 4.1 [02/03]
and a Rootzwiki link should appear w/ all the download links available
PM me if you need help

I DMed you too, but it is still not working. What version of CwM should I be on?

Updating build.prop?
Are there any issues if I were to edit the build.prop file to reflect Sprint and the Sprint model number for the Tab? I use wi-fi only, so it probably doesn't matter too much for me, but I'm just curious. It might be better for me to ask - is there anything in that file that I shouldn't modify?

irish98rm said:
Are there any issues if I were to edit the build.prop file to reflect Sprint and the Sprint model number for the Tab? I use wi-fi only, so it probably doesn't matter too much for me, but I'm just curious. It might be better for me to ask - is there anything in that file that I shouldn't modify?
Click to expand...
Click to collapse
Go to this link as he recently updated the pics from and just posted a patch for the sprint tab. Works great on my sprint tab.
http://rootzwiki.com/index.php?/topic/11697-[ROM]-[CDMA]-AOSP-ICS-/-CM9---BUILD-5-[02/18]
Sent from MY SPH-P100 running ICS

Thanks for this info. Gonna try this soon.
Sent from my SGH-T989 using XDA App

RockRatt said:
Go to this link as he recently updated the pics from and just posted a patch for the sprint tab. Works great on my sprint tab.
Sent from MY SPH-P100 running ICS
Click to expand...
Click to collapse
Thanks! I decided to take the plunge, downloaded and installed the v5 ROM from Rootzwiki, along with that patch. Working great, and I'm really loving ICS on my tab.

Once I found where "updater-script" (META-INF\COM\GOOGLE\ANDROID and extract updater-script) was located this worked. I used notepad++ to edit the script and then was able to re-zipe it and flash ISC!
Thank you for the info! It is not easy finding info for the Sprint tab in this form.

3g any way of fixing this
awesome work gentlemen, i love this rom very exciting but i have my p100 flashed to cricket i was wondering if there was any way to fix the internet.i really appreciate the effort you put into this i will buy you a six pack once i get back on my feet

teamhacksung build4 missing headphones
thank you to the great forum and handy work of all who have shown me the way....thank you so much..My only beef is with missing audio on my samsung tab 7 CDMA. I have ICS up and going but no audio out...im looking daily but any assistance would be awsome...

HOLY CRAP. Thanks guys for the information. I finally got CM9 on my P100 GTab.
There is absolutely no decent guide for doing this properly for someone who has never flashed a Gtab before. "update-script" sounds a lot like "updater.sh" script file that is in the root directory. Without a proper folder structure you are just wasting time.
Also Heimhall 1.1.11 or whatever doesn't have proper drivers to work with newer Windows. I had to hack n' slash a few different versions to get everything I needed. I did use the 1.1.11 or whatever version front end executable though. Flashing the zImage and Recovery file wasn't hard but the program is a bit confusing.
I'm going to make a fresh thread with some serious details because, while the information is out there, it is scattered and in a million places.

specialblend15 said:
Hey All
Several ICS roms have been released for The Galaxy Tab, some claiming to work for the Sprint Cdma version of The tab
I have flashed them all, and I have a working guide for all sprint users to get ICS!
1. Odin back to stock Gingerbread (EF17), then flash the CWM Recovery
2. Download the V4 Rom, and Gapps 7.1 from ROOTZWIKI ([ROM] [CDMA] AOSP ICS / CM9 - BUILD 4.1 [02/03])
3. Go into the Rom Zip, and edit the updater-script and delete assert(getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab" ||
getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100");
3. Place both the rom and g apps on sd card
4. boot into recovery and clear data, them flash rom, mount system, them flash g apps, then reboot
5. You now Have working ICS
Ill post screen shots soon
Click to expand...
Click to collapse
This is cool. It works with Milestone 6. This is the only way to get this running on SPH-P100. Thanks.

I've tried to flash a nightly/stable and I can't get it to flash.
I don't thing I'm editing the script correctly.
can someone help on this subject?
I read one post that says delete the first 3 lines.
I've done that.
I tried the way the op stated and still a no go.
I have the Sprint Tab with CWM.

[GUIDE] How to port MIUI v4 to your Device

Hi guys, last days i got messages about a guide port miui4 to each device.
that is my method i use on my miui4 ports.
take a any cm9 or aosp based ics rom as base. with this guide, you can port miui4 from any device to your one. for best compatibility use own brand base to port. if you have desire s then port from htc devices. if galaxy nexus then try port from nexus s
first of all replace complete folders with miui4 one.
system/app
system/framework
copy libandroid_runtime.so lib from miui 4 (rom you port). without this file rom will not boot. if you get bootloop, try with base libandroid_runtime.so file..
Click to expand...
Click to collapse
replace media folder with base rom (that themes, wallpaper, audio from miui work)
copy telocation.db and yellowpage.db to /system/etc folder.
copy content-types.properties file to /system/lib
copy invoke-as from miui4 rom to /system/xbin and give it permissions on updater-script
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
(for backup & themes app work)
Click to expand...
Click to collapse
copy liblbesec.so from miui 4 to /system/lib and give permission on updater-script
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
(for superuser app from miui work)
Click to expand...
Click to collapse
change values from build.prop
ro.build.id=MIUI
ro.build.display.id=MIUI
ro.build.version.incremental=2.x.x (version number)
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=GoodMorning.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
Click to expand...
Click to collapse
if your base rom has issues, these issues will seen on this port too. example, if camera not works on base rom, then will on miui4 port also not work!
then add your stuff (updated apps, wallpaper or installer whatever you want )
make your zip and there is it. if you open your thread, dont forget give a link to based ics and port rom's.
that is method actually i use. for more info please use search on xda or ask on this thread. no private messages will answered from now.
(if you like this guide, just give 5 star and click to thanks button)

good good study day day up! thanks very much!

thanks for your guide, work with tablet this guide???

Thx a lot,good work,please help me galaxy3.

any tips for motorola defy users (suggested rom base)..wajk is developing on a miuiv4 rom already .. but i thought i could give this method a try .
thanks

Does it work on ARMV6 CPU like in Galaxy 3 ??

Is it possible to port miui tho HTC explore ?
HTC Sense 3.5,Android 2.3.5

antaine said:
Does it work on ARMV6 CPU like in Galaxy 3 ??
Click to expand...
Click to collapse
Same question here. But we have a cm9 rom all we need is miui but it I'd a arm6 device with ldpi screen
Sent from my GT-S5670 using xda premium

We dont have a ice sandwich Rom on the vivid/hoilday would it be possible to port One this way
Sent from my HTC PH39100 using XDA App

I can't say anything about ldpi and mdpi devices. Miui is designed for hdpi devices. This guide is for hdpi devices only..
Some guys got it working on Mdpi devices with resizing but i don't know how's.
come at me bro said:
We dont have a ice sandwich Rom on the vivid/hoilday would it be possible to port One this way
Sent from my HTC PH39100 using XDA App
Click to expand...
Click to collapse
I don't think. You need special kernel for that like cm9 .
Sent from my HTC Desire S using xda premium

Are you saying that it should work on ARMV6 and ARMV7 ldpi mdpi (with resized framework and apps) and hdpi?

This sucks, I never seen a beast of a phone with no development, I shoulda went with the gs2 or the 4s
Sent from my HTC PH39100 using XDA App

I didn't find liblbesec.so in SGS II's MIUI 4. It's normal?

co2gaz said:
I didn't find liblbesec.so in SGS II's MIUI 4. It's normal?
Click to expand...
Click to collapse
its libibesec.so

thanks a lot, great!

I've never even considered porting a rom, but I followed the instructions and it worked!
Only glitch: it thinks my slide out keyboard is out when it's in, and vice versa. Oh well. Thanks!
Sent from my epic 4g using Tapatalk

Brilliant guide! Managed to port MIUI to my ZTE Skate - an arm6 device using this!

"copy invoke-as from miui4 rom to /system/xbin and give it permissions on updater-script
set_perm(0, 0, 06755, "/system/xbin/invoke-as")"
I'm really green when it comes to this stuff...just wondering how i'd go about giving it the permissions as above...? thanks

m4rk84 said:
"copy invoke-as from miui4 rom to /system/xbin and give it permissions on updater-script
set_perm(0, 0, 06755, "/system/xbin/invoke-as")"
I'm really green when it comes to this stuff...just wondering how i'd go about giving it the permissions as above...? thanks
Click to expand...
Click to collapse
Its for advanced users, you should better leave it before you do something wrong and write here in the thread that you fried your Phone.
No offense.

Any idea if this should work on CAF ICS roms? Took a quick attempt without success, libdvm.so was failing in a bootloop - needed phone so didn't investigate much further.

[GUIDE] How to port AOSP ICS roms to your Device

How to port any ICS AOSP based roms to your Device (AOKP, CM9 & many other)
- for best compatibilty
--> use same android versions. (4.0.4 -> 4.0.4 example)
--> use latest base from CM9 (is best choose for port) or any AOSPbased ICS ROM
--> use each brand for port (mean Desire HD -> Desire S or other HTC devices). you also can port other roms, but you will have issues.
PORT:
-> download latest cm9 base and extract it
-> download target rom and extract it
for Camera
use Camera.apk from base rom for camera issues fix.
Click to expand...
Click to collapse
copy
/app
/framework
/media
/fonts folders and replace in cm9 folder.
repack your zip and let it boot.
if it doesn't boot then copy /system/lib/libandroid_runtime.so from target rom and repack your rom.zip and install again.. if you get bootloop anyway, then just type in adb "adb logcat" and share it with us in this thread..
if you dont get success dont cry, just try to port another rom you can not port all roms
for HTC Devices
to fix network auto select,
decompile framework-res.apk
go to \framework-res\res\values\bools.xml change
<bool name="skip_restoring_network_selection">true</bool>
to false.
Click to expand...
Click to collapse
to fix graphichal issues,
decompile framework.jar
change these files with cm9 base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
Click to expand...
Click to collapse
Click to expand...
Click to collapse
enjoy!
if you like this guide, just give 5 stars to thread and click thanks button

hi, there, and i own a huawei u8800, we allready have a aosp ics 4.0.4 aurora room but i would like to have cm9 or aokp into our phone. in this case based is aosp ics aurora and ported will be cm9 or aokp for example? i´m right?
maybe is better port cm9 from desire z to my huawei u8800, since they have the same cpu and gpu.
dont want tou build a rom, just port.
please i need help. thanks anyway.

lol be thankful you have an ICS rom.. Huawei X6 users like me are trying our best to port from u8860's ICS.
I'd like to ask if the method works for a device that does not have official ICS? i.e. porting an ICS rom to official GB?
Kindly advise sir, and thanks again!

I get the same that in miui v4... boot loop and adb says no device

I get AtCmdFwd error.

Could you post the link of latest cm9 base?

im getting stuck in a bootloop...
INFO:
Device-Samsung Infuse
CM9 Base being used to port- http://forum.xda-developers.com/showthread.php?t=1601844
Rom trying to port- http://www.slimroms.com/ (the i9000 version aka galaxy s)
What i did:
1) opened cm9 base with 7zip, deleted app, framework, fonts, media folders
2) replaced deleted folders with app, framework, fonts and media folders from slim ics base 3.6
3) opened up slim ics 3.6 i9000 essentials with 7zip
4)navigated to app folder and moved apks files from ther to the cm9 base - did the same with framework, fonts, and media folders (I did not just copy the folders this time! i only copied the files inside the folders)
5) put zip on sdcard
6) rebooted and started log cat
any help would be apreciated if i dont answer back right away its because i have to pick my sister up from school
Here are the logcats: (All are the same logcat...but two of them are filtered)

I think I kniw what the problem is...gonna attemot a fix after dinner
EDIT i got out of the boot loops and booted into my portes slimics...now to fix the bugs...there is ALOT
thanks for the guide will def give you some credit once i get this stable...may be getting some help from another dev

So as long as the base and ported roms are from the same manufacturer, this will work?
Sent from my LG-E739 using Tapatalk 2

how to port aosp ics to cm9?

good guide
You can add
Copy etc\cron
And etc\init.d files to run RomControl fix

Am stuck at logo screen.
Can't get logcat because ADB can't find my device.
What to do?
Sent from my LG-E739 using Tapatalk 2

mg2195 said:
I think I kniw what the problem is...gonna attemot a fix after dinner
EDIT i got out of the boot loops and booted into my portes slimics...now to fix the bugs...there is ALOT
thanks for the guide will def give you some credit once i get this stable...may be getting some help from another dev
Click to expand...
Click to collapse
Can you please tell what was the problem and how did you fixed? Thanks.

medicjunKie said:
So as long as the base and ported roms are from the same manufacturer, this will work?
Sent from my LG-E739 using Tapatalk 2
Click to expand...
Click to collapse
It would be sane screen res e.g HDPI to HDPI
And also the same processor type too helps
Sent from my LT15i using xda premium

see i hve a question...., what does base mean? does it mean the ics rom which i hve for my device already ported or any ics rom available for my device's manufacturer?
like my phone is samsung galaxy 3....so shud the base be the rom which is available for my g3 or it can be any ics rom like say ics rom for samsung galax s?
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
i m seriously cponfused with that part..... m not gettin g what the base and the rom to be ported shud be?

My logcat ...?? what can i do? http://www.embedupload.com/?d=4HKCKXGIK2

I'm trying to port slimICS and it gets stuck at boot. Here's my logcat if it helps.
http://logcat.miui.us/893012

Zorua said:
I'm trying to port slimICS and it gets stuck at boot. Here's my logcat if it helps.
http://logcat.miui.us/893012
Click to expand...
Click to collapse
see here
Code:
169: E/dalvikvm( 1190): ERROR: couldn't find native method
170:
171: E/dalvikvm( 1190): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimation:(I)V
172:
173: E/JNIHelp ( 1190): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
baksmali classes.dex of services.jar
find PowerManagerService.smali file in the path com/android/server
add line
Code:
.method private native nativeStartSurfaceFlingerOffAnimation(I)V
.end method

tathanhlam66 said:
see here
Code:
169: E/dalvikvm( 1190): ERROR: couldn't find native method
170:
171: E/dalvikvm( 1190): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimation:(I)V
172:
173: E/JNIHelp ( 1190): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
baksmali classes.dex of services.jar
find PowerManagerService.smali file in the path com/android/server
add line
Code:
.method private native nativeStartSurfaceFlingerOffAnimation(I)V
.end method
Click to expand...
Click to collapse
I don't have the folder com/android/server/. What am I doing wrong?
EDIT: Wow, I sound so stupid. Nvm, I did that edit. I had to look up smali and baksmali guides. I'll flash it and see if it boots.
Okay, still refusing to boot.
New logcat: http://logcat.miui.us/894002
EDIT 2: Booted but storage isn't working.
Logcat: http://logcat.miui.us/889025

Zorua said:
EDIT 2: Booted but storage isn't working.
Logcat: http://logcat.miui.us/889025
Click to expand...
Click to collapse
Try decompiling the framework-res.apk and change the storage-list.xml in the xml folder.

[Dev] Development of Non-Carrier Specific Roms [Universal Roms For All Carriers]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Developers,
The Objective of this thread is to create a solution for flashing any rom on any carrier's GS3. (Us/Canada)
Every Rom on Every Carrier Will Be Supported.
Warm Roms developed by Myn, Myself and the rest of the Warm Team will be available on all carriers.
I will keep the OP updated.
Thanks, Incubus
First,
We need to Determine the Diffs and Seperate what each carriers device needs.
We will create an SVN Repo For Carrier Files.
We will Use An Updater.script and include all carrier files with in the Rom.zip and allow the script to determine the device and install the appropriate carrier files.
Any rom dev who wants to use this would place a folder in the rom.zip called "Devices" with all the carrier files seperated by sub-folders (Sprint, Verizon etc...)
The script would call for "Sprint" and install the carrier files from that sub- folder overtop of any carrier files that a rom might have in it. (boot.img, apns, libs etc...)
Example updater.script from Warm twopointthree on the Evo 3d. Worked very well.
Code:
#Mounting
ifelse(
getprop("ro.product.device") == "shooter",
(
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/system");
)
);
ifelse(
getprop("ro.product.device") == "shooteru",
(
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
)
);
ifelse(
getprop("ro.product.device") == "shooter",
(
mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/data");
)
);
ifelse(
getprop("ro.product.device") == "shooteru",
(
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/data");
)
);
#Install Device Files
ifelse(
getprop("ro.product.device") == "shooter",
(
package_extract_dir("devices/shooter/system", "/system");
),
package_extract_dir("devices/" + getprop("ro.product.device") + "/system", "/system");
);
ifelse(
getprop("ro.product.device") == "shooteru",
(
package_extract_dir("devices/shooteru/system", "/system");
),
package_extract_dir("devices/" + getprop("ro.product.device") + "/system", "/system");
);
So to this point I wonder if ro.product.device returns something different for each carrier device? If not we need another unique identifier.
If folks can
Code:
adb shell
getprop ro.product.device
and let us know what carrier they are on and what the getprop returns, we could determine this.
As soon as we obtain all the carrier files and put them into there proper layout, we will provide all files and code necessary to make your rom compatible with all carriers.

Unbrick Mods:
MSkips How-To Unbrick If you have Flashed a International GSM Boot.img

Well I m No Dev! But if you are thinking about making one Rom to Rule Them All then you will have to get different modems/radios for each carrier & that means may be libs modification? I might be wrong !
Here is what libs i m thinking off.
libsecril-client.so
libril.so
libril-qcril-hook-oem.so
libril-qc-qmi-1.so
libreference-ril.so

appdroid said:
Well I m No Dev! But if you are thinking about making one Rom to Rule Them All then you will have to get different modems/radios for each carrier & that means may be libs modification? I might be wrong !
Here is what libs i m thinking off.
libsecril-client.so
libril.so
libril-qcril-hook-oem.so
libril-qc-qmi-1.so
libreference-ril.so
Click to expand...
Click to collapse
Updated OP with a bit of info.

On gnex it was small changes , but all kernels worked gsm and cdma ....it should be easy but don't know about one size fits all roms they have to port to gnex and may be same way here....but it's easy port
Sent from my Galaxy Nexus using Xparent ICS Blue Tapatalk 2

Build.prop - ril stuff
Framework-res.apk/res/xml/eri.xml
Framework.jar/telephony stuff
Libril-*
etc/apns-conf.xml
Sent from my SPH-D700 using Tapatalk 2

I like the second suggestion , that way we can pick any existing Rom flash it and then flash the carrier specific zip. This is exactly what we had with at&t galaxy s ii, not sure who the dev was , but it worked great and we were able to use all the roms from the international s sii
Sent from my SAMSUNG-SGH-I747 using xda premium

anilkuj said:
I like the second suggestion , that way eek can pick any existing Rom flash it and then flash the carrier specific zip. This is exactly what we had with at&t galaxy s ii, not sure who the dev was , but it worked great and we were able to use all the roms from the international s sii
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I agree, that's the best (and likely easiest) way to do things.
Sent from my ADR6300 using Tapatalk 2

Just found the thread , the Dev was Entropy he did some awesome work for ATT Galaxy S II.
http://forum.xda-developers.com/showthread.php?t=1577015

Off the top of my head, the easiest thing to do after figuring out all the differences is to use Aroma Installer and have it ask which carrier the phone is on, and have it flash any specific files from there along with the rom.

All of it could be accomplished using aroma installer. One zip, different radio and lib options depending on what you select in the installer. Easy to do in my opinion.
Sent from my HTC One X using Tapatalk 2

I think devs should make Roms that would include a base rom and an additional zip for specific carriers
Sent from my iPhone using Tapatalk

Might I suggest that whoever comes up with this use Aroma (http://forum.xda-developers.com/showthread.php?t=1646108) for the installer. That way you COULD put all the stuff for the various carriers in the same zip, and use programming or user input to install only the items that pertain to a particular carrier. You would not need to flash multiple files.
For instance, just pick "AT&T" or "T-Mobile" (etc.) from an onscreen menu and hit Next. Not sure, but Aroma may even be able to programmatically tell what the current carrier is and then automatically flash the correct info with NO user input. The beauty is that you can also have options to flash particular programs, tools, etc. based on user input as well.
I know the dev for Aroma has stopped for awhile, but a lot of roms have been using it anyway...
EDIT: Well, from the time I started typing my post and the time I finished it, two others came up with the same idea

BakaNeko59 said:
Might I suggest that whoever comes up with this use Aroma (http://forum.xda-developers.com/showthread.php?t=1646108) for the installer. That way you COULD put all the stuff for the various carriers in the same zip, and use programming or user input to install only the items that pertain to a particular carrier. You would not need to flash multiple files.
For instance, just pick "AT&T" or "T-Mobile" (etc.) from an onscreen menu and hit Next. Not sure, but Aroma may even be able to programmatically tell what the current carrier is and then automatically flash the correct info with NO user input. The beauty is that you can also have options to flash particular programs, tools, etc. based on user input as well.
I know the dev for Aroma has stopped for awhile, but a lot of roms have been using it anyway...
EDIT: Well, from the time I started typing my post and the time I finished it, two others came up with the same idea
Click to expand...
Click to collapse
Pretty sure Aroma can't differentiate between the different carriers. But it for sure can do the rest.
Sent from my Transformer Prime TF201 using Tapatalk 2

Research entropys hellraiser package from the I777
Sent from my SAMSUNG-SGH-I747 using xda premium

Excellent Ideas Guys. Keep Them Coming. I will research everything I can.

RampageRR said:
Off the top of my head, the easiest thing to do after figuring out all the differences is to use Aroma Installer and have it ask which carrier the phone is on, and have it flash any specific files from there along with the rom.
Click to expand...
Click to collapse
This is actually a great, great idea.
Sent from my HTC Sensation 4G using xda app-developers app

Epix4G said:
On gnex it was small changes , but all kernels worked gsm and cdma ....it should be easy but don't know about one size fits all roms they have to port to gnex and may be same way here....but it's easy port
Sent from my Galaxy Nexus using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
I've already looked at the kernel (board platform set-up, at least). Between Sprint and AT&T it is 99.9% similar.
There are a few GPIO configuration flags that are different, and the Hardware Revision identifier flags are different (but the flags control the same settings).

jnadke said:
I've already looked at the kernel (board platform set-up, at least). Between Sprint and AT&T it is 99.9% similar.
There are a few GPIO configuration flags that are different, and the Hardware Revision identifier flags are different (but the flags control the same settings).
Click to expand...
Click to collapse
Thats what I like to here

incubus26jc said:
Excellent Ideas Guys. Keep Them Coming. I will research everything I can.
I love that Amonra is capable of that but I'm not sure about the dependency. Especially if Amonra is no longer supported. I'm thinking that we can make this available for anyone with any recovery.
Im just thinking out loud.
Click to expand...
Click to collapse
It's not that Aroma is no longer supported. The author broke his phone and can't test updates any more until he replaces it.
And Aroma zip files are flashed in CWM (or whatever other custom recovery you are using) so there's no dependency, at least as far as I understand your meaning.
EDIT: Just noticed you were talking about Amon RA, which is a recovery program. Aroma and Amon RA are two entirely different things (again, see http://forum.xda-developers.com/showthread.php?t=1646108). Aroma installers run FROM the recovery menu just like any other flashable zip file. They can be flashed with CWM, Amon RA, and TWRP recoveries, among others.

[TUT] How to easily port CM7,CM9,CM10 Based ROMs to HTC Aria

Easiest and best way to port CM7,CM9,CM10 Based ROMs to HTC Aria/Intruder/Gratia
Code:
I do not guarantee any successful porting.
I am not responsible for [B]bricked devices, dead SD cards, or a broken device[/B].
[B]YOU[/B] are choosing to make these modifications,
and if you point the finger at me for messing up your device,
I will laugh at you.
->Copied from some xda thread.
*****
But a rom, no matter how bad should *not* do any physical non recoverable harm to your device,flashing a rom or restoring a nandroid backup via cwm *should* immediately fix any problems what so ever.
And I will try to help in any ways I can.​
I am NOT a developer, I can not code,compile,etc, I am only an android enthusiast with half a brain able to follow specific instructions.
This guide is actually somewhat a good combination of various "how to port roms"
guides found here on xda suited and very slightly modified for our beloved Aria.
Thanks to all of those threads and their writers.
Click to expand...
Click to collapse
Actual Tutorial starts here:
I will try to make this guide as straight forward as possible. ​
PORT ROM:
First you need to figure out what rom you are going to be porting.
For our Aria, The rom you want to port should belong to a device that has:
HTC brand (optional but recommended)
A ArmV6 CPU (VVVV important)
A HVGA Resolution (optional, any mdpi should do,if not just open the system apk files using 7zip and resize all the BIG images.)
The Rom needs to be:
CM7 BASED OR CM10 BASED OR CM9 BASED.
The full zip size less than 150MB(Recommended).
What Does Port Mean:
This simply refers to the rom you will be trying to port.
Recommended device to port from is the HTC Wildfire S a.k.a Marvel.
But any other device
BASE ROM:
What Does Based Mean:
It means that the rom should have similar sources and stuff,
Meaning you can only attempt to port a android 2.3 rom if you already have a 2.3 rom on the device.(In our case cm7).
So,
For porting 2.3 roms, chose cyanogenmod 7.2 as BASE.
For porting 4.0 roms, chose cyanogenmod 9 as BASE.
For porting 4.1 roms, chose cyanogenmod 10 as BASE.
ETC... I hope you get the point.
:fingers-crossed:

Thing you will need:
A good Zip extractor and compressor. (I use 7zip, its free. If you have winrar or something else,it will also do.)
Notepad++ (This thingy is awesome! And you need it for some stuff)
Android SDK(Not the whole thing, just adb zip from our sticky thread will do.)
Some Basic Android Knowledge, Root knowledge.
Mostly Common Sense.
Click to expand...
Click to collapse
Step 1:
Extract our device rom zip and name the folder AriaRom,
Extract our Port rom zip and name the folder PortRom.
Step 2:
Delete the following folders on the AriaRom/system folder:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
Step 3:
Go to
Code:
PortRom folder/system
and copy:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
and then paste them to AriaRom/system.
Step 4:
You need to open these two folders side by side(on windows, open both folders then right click on the task bar and click "Tile windows vertically").
The two Folders are:
Code:
[LIST]
[*]AriaRom/system/etc
[*]PortRom/system/etc
[/LIST]
In
Code:
etc/permission
folder copy all the permissions files in PortRom to your AriaROM folder except
Code:
platform
handheld_hardware
Then open init.d Folder in AriaRom and Delete Everything except
Code:
banner
and then copy all the files inside init.d folder of PortRom to init.d folder of AriaRom.
Step 5:
Now
Code:
AriaRom/system/buid.prop
and
PortRom/system/buid.prop
files using Notepad++
On AriaRom Build.prop make changes as you wish.
Code:
[LIST]
[*]ro.build.id=
[*]ro.build.display.id=
[*]ro.build.date=
[*]ro.modversion=
[/LIST]
Copy and replace these values from PortRom buildprop to Aria rom buildprop.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
Also Copy anything you Find Extra and important-ish in ADDITIONAL BUILD PROPERTIES using common sense.(Not much major stuff, but if bootlooped, copy whole thingy.)
IMPORTANT Step of commons sense:
Open up both
Code:
META-INF/com/google/android/updater-script
using Notepad++.
Compare AriaRom AND PortRom line by line(on two tabs in notepad++ easily done).
Copy extra/additional lines from PortRom which are not present in AriaRom to aria roms updater script.
Step 6:
If You find any extra file or folder in system folder of PORTrom than copy them to your Ariarom system folder.
Finally, zip the
Code:
META-INF
system
boot.img
data(if exists).
folders/files togather and use "normal" compression if asked.
Name the zip to whatever you want, and walla you have successfully ported the rom!

:fingers-crossed:
Doing the above steps should land you a pretty solid rom, as solid as the base rom.
Still,Incase of problems:
If the ported rom does not boot:
Stuck at boot screen
Bootlooping
Then copy system/lib/
Code:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
files from PortRom to AriaRom system/lib.
It should boot, if it still doesnt, check the above steps and find out what you did wrong.
Common reasons could be:
Build.prop mess up
Updater Script mess up
Forgot to delete or copy file
After it boots,
Everything that worked on Base rom, should work on Ported.
Every problem on Base Rom will exist on Ported.
In case of root related problems(settings not being saved,system app FCs,etc), install a root app like titanium backup or something and check if it works,if it doesnt its surely root issue,just download and flash latest superuser zip.
If some FC,Port rom funciton not working,etc issues appear, you need to decompile framework-res.apk using apktool and change device specific xml files to ours.This is a part where I have the most trouble and suck at.
Just search xda for
How to Logcat,
Click to expand...
Click to collapse
this will help you to find the problems and search xda to solve them. Ask me if you want on this thread, & I will try to help, but I dont think I will be able to help much as I have very limited knowledge on compile De-compile stuff.
If someone is good at framework-res and framework decompile & recompile stuff, please help us.
Click to expand...
Click to collapse
Thanks for reading this,I hope you port over some awesome roms to our device.
:highfive:

I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...

dansou901 said:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
Click to expand...
Click to collapse
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Why are SMARTphones soo... Freaking Dumb?

sifat3d said:
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Click to expand...
Click to collapse
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.

hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )

rami.ejle said:
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
Click to expand...
Click to collapse
Here you go,
http://pastebin.com/62hbaQwL
on THAT ROM,
IF you follow the guide & use my posted script,
100% assurance rom will boot and work. except cm
The sdk is for getting the logcat when a problem occurs.
Why are SMARTphones soo... Freaking Dumb?

Nice tut very well done
XDA Moderator

dansou901 said:
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
Click to expand...
Click to collapse
In that case you'll need to unpack both boot.img aka the kernel , fix bootclass path in init.RC by replacing it with the value from port roms init.rc.
Ill try to port that rom soon and upload a fixed boot.img (if I can get it to boot),if you don't beat me to it. it looks cool.
Why are SMARTphones soo... Freaking Dumb?

Bootclasspath is the same on both roms. So there must be a mistake in updater-script and / or build.prop. I've just messed up my updater-script, I guess, so I'll make a new one and post it later together with the build.prop.

I got this pac rom booting & everything operational except per app dpi(exists in port rom).
This rom works with the guide.
http://forum.xda-developers.com/showthread.php?t=2118567
Why are SMARTphones soo... Freaking Dumb?

I'll try this and let you know if it worked.

Hi guys,
If you only want per app dpi,persistent apps,etc
Try this on winsuk bros cm10
http://forum.xda-developers.com/showthread.php?t=1574401
Its quite good.
...Devided by zero

dansou901 said:
I'll try this and let you know if it worked.
Click to expand...
Click to collapse
btw,
did it work?
...Devided by zero

Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.

dansou901 said:
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
Click to expand...
Click to collapse
That's a shame. Similar thing happened to me. I lost my Aria right before i had a chance to try this, and upgraded to the Nexus 4.

will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??

Could work, just try... I would do it if I still had the phone...

dansou901 said:
Could work, just try... I would do it if I still had the phone...
Click to expand...
Click to collapse
rami.ejle said:
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Click to expand...
Click to collapse
It should pretty much work,
If it doesnt, just send me the
Updater script
Build.prop
files of BOTH roms, And I'll have a look.
I wouldve tried myself but my aria has no network and has random reboot issues due to falling hard.