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.
Related
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.
After a few headaches and some claps on the forehead i finished a very alpha build of CM9 for the IDEOS X5. It was ported from the Galaxy W port of arco68 with the files of Aurora ICS and this guide.
I don't know the bugs, so please PM me if you find a bug.
NOTE: I think i am only too stupid to sign a zip, so you have to sign it by yourselves or toggle verification in the recovery.
Download
Mediafire
Thanks to fjsferreira for re-packung the boot.umg
Thanks to dzo for Aurora ICS
Thanks to arco68 for the Galaxy W ICS port
Thanks ti freeeyourandroid.com for the porting guide
alex1301 said:
After a few headaches and some claps on the forehead i finished a very alpha build of CM9 for the IDEOS X5. It was ported from the Galaxy W port of arco68 with the files of Aurora ICS and this guide.
I don't know the bugs, so please PM me if you find a bug.
NOTE: I think i am only too stupid to sign a zip, so you have to sign it by yourselves or toggle verification in the recovery.
Download
Mediafire
Thanks to fjsferreira for re-packung the boot.umg
Thanks to dzo for Aurora ICS
Thanks to arco68 for the Galaxy W ICS port
Thanks ti freeeyourandroid.com for the porting guide
Click to expand...
Click to collapse
Can't flash it, starts but then getting error and no message as the phone reboots. First time ever it has done something like this and my heart skipped...
cirnocirno said:
Can't flash it, starts but then getting error and no message as the phone reboots. First time ever it has done something like this and my heart skipped...
Click to expand...
Click to collapse
Did you toggle signature verification first?
Is there any chance for u8800pro?
Sent from my u8800pro using XDA
... finished a very alpha build of CM9 .....
Click to expand...
Click to collapse
Please go to advance edition and put a big ALPHA warning in the title thread.
why? is it that bad?
have you tyed? whats working and not?
thanks for ypu effort alex1301
r1c4rd0 said:
why? is it that bad?
have you tyed? whats working and not?
thanks for ypu effort alex1301
Click to expand...
Click to collapse
Alpha is not bad nor good, just a phase of software development. Please confirm the rom is working, otherwise I will move it to general section.
poyensa said:
Alpha is not bad nor good, just a phase of software development. Please confirm the rom is working, otherwise I will move it to general section.
Click to expand...
Click to collapse
i´m downloading it right now, and will test it in one hour and i will say someting here...
It doesn't install, always Error status 6 in CWM. I replaced the METAINF folder in the zip with aurora, and changed the name of the zip itself, then it installs, but doesn't boot...
Next, I replaced the boot.img inside with the 3.0.8_v2 from DZO, then it boots but never goes further than boot animation
It is not rom development if you just switch some of the files, compress the file into a .zip and post it here.
Can anyone have a look at it and help me? I think the problen is the updater script, because i've only copied the one from aurora.
Sent from my SGH-T989 using xda premium
I will do a port from desire z
Sent from my SGH-T989 using xda premium
will test it soon btw yeah port from desire z would be better.
i have only one problem. the guide says the Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
but when i take the boot.img-kernel from the unpacked aurora boot.img, it has 2,6 mb, but when i rename the packed boot.img from aurora to boot.img-kernel it has 3.0 mb. which one should i take?
alex1301 said:
i have only one problem. the guide says the Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
but when i take the boot.img-kernel from the unpacked aurora boot.img, it has 2,6 mb, but when i rename the packed boot.img from aurora to boot.img-kernel it has 3.0 mb. which one should i take?
Click to expand...
Click to collapse
Boot.img is ramdisk and kernel, compiled into one. You need kernel.
Unpack both boot images, replace kernel with auroras and change init.rc scripts to mount the correct partitions.
On mobile now so can't give a tutorial.
Sent from my U8800 using Tapatalk 2 Beta-5
the guide i follow says, that i only have to rename the init.devicename.rc to init.huawei.rc. should i also change the init.rc to the one of aurora?
does anyone have the mkbootimg for the X5?
alex1301 said:
does anyone have the mkbootimg for the X5?
Click to expand...
Click to collapse
We don't need to have any device specific mkbootimg, any mkbootimg will do it just fine
Sent from my U8800 using Tapatalk 2 Beta-5
i've uploaded a new version. it's ported from the desire z, but i think it's too big for the x5. i can't upload it to mediafire, because it doesn't load my files correct. so i only can upload it to dropbox, but there is also a limitation of downloads. http://db.tt/u8PrGM5m
alex1301 said:
i've uploaded a new version. it's ported from the desire z, but i think it's too big for the x5. i can't upload it to mediafire, because it doesn't load my files correct. so i only can upload it to dropbox, but there is also a limitation of downloads. http://db.tt/u8PrGM5m
Click to expand...
Click to collapse
Can you confirm this one boots?
Sent from my U8800
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.
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. YOU are
choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
There are two phases or rom porting
1) Its finding the correct port and source roms for ROM PORTING copying the files which is explained here
2) After a succefull port also the rom may not work properly ,we have to sort out the bugs to for a rom to become perfectly working
So with no more blahh blahh blahh Lets start the PORTING procedure :fingers-crossed: :fingers-crossed:
Click to expand...
Click to collapse
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
What you'll need:
WinRAR/7zip
Notepad++ (When developing, always use this)
Android SDK (For Logcatting & DDMS)
Some basic knowledge about Android
If you are on Linux/Unix/BSD use your favorite Archiving Tool & Text Editor.
Click to expand...
Click to collapse
What is base Rom:
The ROM which is Developed For your Mobile..
You can use either CM or any other AOSP roms as your Base ROM
Click to expand...
Click to collapse
What is Port Rom:
The Rom Which you want to port to your Device.
Make sure that the rom has most of the hardware specifications as of your base rom
Click to expand...
Click to collapse
STEP1;
Take any clean CM9, AOSP, CM7, CM10 ROM which is running on your device as Base ROM
Click to expand...
Click to collapse
STEP2:
Extract it Using Winrar.
{
"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"
}
Click to expand...
Click to collapse
STEP3:
Take the ROM you want to port. This Port ROM. Extract it also using Winrar.
Click to expand...
Click to collapse
STEP4:
Delete app, Framework, Fonts and Media folder in System Folder of Base ROM.
Click to expand...
Click to collapse
STEP5:
Now copy app, Framework, Fonts and Media folder in System Folder from Port rom to base rom system folder.
Click to expand...
Click to collapse
STEP6:
Now open etc folder in both the ROMs folder.
Click to expand...
Click to collapse
STEP7:
In etc folder of base ROM open permissions folder and copy all the permissions files in Port rom to your base ROM folder except platform and handheld_hardware
Click to expand...
Click to collapse
STEP 8: .And Then open init.d Folder in Base ROM and Delete Every thing except banner and then copy all the files inside init.d folder of port ROM to Base ROM.
Click to expand...
Click to collapse
STEP9:
Now open buid.prop file using Notepad++ and make changes to these of Base Rom as you wish.
ro.build.id=
ro.build.display.id=
ro.build.date=
ro.modversion=
Click to expand...
Click to collapse
STEP10:
In build.prop file change these to same as Port Rom build.prop values.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.cmversion=
ro.modversion=
Also Copy anything you Find Extra in ADDITIONAL BUILD PROPERTIES related to theme..
Click to expand...
Click to collapse
STEP11:
COPY THE set_perm Lines in META-INF/com/google/android/updater-script From Port to Base ROM After Deleting set_perm lines in Base ROM's Updater-Script.
Click to expand...
Click to collapse
STEP12:
If You find any extra file or folder in system folder of PORT rom than copy them to your base rom system folder.
Click to expand...
Click to collapse
STEP 13:
Last Step to ZIP THE FOLDERS IN ONE..
SELECT META-INF, system, boot.img(if it is having), data(if it is having).
Right Click and Select Add to Archive..
Select Zip..
Type the Name.
Click OK..
Click to expand...
Click to collapse
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
Copy telocation.db and yellowpage.db From /system/etc folder to yours..
Copy content-types.properties file From /system/lib to yours..
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");
Note:It is needed for backup & themes app to work
Copy liblbesec.so from miui 4 to /system/lib and give permission on updater-script
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
It is needed for superuser app from miui to work
Change values Some of the Values in build.prop of your ROM:
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
FOR ParanoidAndroid And PAC:
Copy paranoid folder inside system/etc to yours..
Go to META-INF/com/google/android/Updater-Script of your base ROM and open it with Notepad++
Copy this line:
set_perm(1000, 1000, 0644, "/system/etc/paranoid/properties.conf");
Specially For PA:
Now Open Build.prop in /system with Notepad++
Copy these lines in Additional Properties of Build.prop:
Depends on Resolution Of your device can be pa_hdpi/pa_mdpi/pa_xhdpi. Change it according to your device.
ro.pa.family=pa_mdpi
Depend on pa version. Replace x.xx with the version of PA you are porting.
ro.pa.version=x.xx
Click to expand...
Click to collapse
Specially For PAC Rom:
Now Open Build.prop in /system with Notepad++
Copy these lines in Additional Properties of Build.prop:
Replace the x.x.x with your PAC Rom version
ro.pac.version=x.x.x
Customize these lines according to your wish.
ro.pacrom.version=mesona_PAC_jb-alpha-v19.0.0
ro.modversion=mesona_PAC_jb-alpha-v19.0.0
Depends on Resolution Of your device can be pa_hdpi/pa_mdpi/pa_xhdpi. Change it according to your device.
ro.pa.family=pa_mdpi
Depend on pa version. Replace x.xx with the version of PA you are porting.
ro.pa.version=x.xx
Modify this line according to your AOKP version
ro.aokp.version=mesona_jb-Milestone-1
Modify it according to your base ROM's build.prop
ro.cm.version=xxxxxxxxxxxx
Replace any line in Your build.prop which appear twice mainly ro.cm.version and ro.modversion
Click to expand...
Click to collapse
FOR SPECIFIC MANUFACTURE DEVICE
For HTC Devices:
To fix network auto select-
Decompile framework-res.apk
Go to \framework-res\res\values\bools.xml and change change <bool name="skip_restoring_network_selection">true</bool> to false
To Fix Graphichal issues:
Code:
Decompile framework.jar
Change these files with your base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
Click to expand...
Click to collapse
IF YOU ARE HAVING BOOTLOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Click to expand...
Click to collapse
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
After a succefull port also there can be many bugs present which has to soved logically
here are somethings which can help in DEBUGGING
1) IF GALLERY FC :
open the system/framework and find framework-res.apk file[can use any extracting app]
in both the roms and go to res folder then to xml subfolder and copy and replace the storage_list.xml file from source to port rom
( framework-res.apk\res\xml\storage_list.xml)
Porting Wallpapers | Lockscreen Wallpapers | bootanimation
Usually you get a wallpaper/bootanimation that doesn't fit your device. Here's a quick tutorial on how to port it to your device.
Download & Install FreeImageConverter then launch it.
For Wallpapers & Lockscreen Wallpapers:
Click Add Folder... and add the folder were the wallpapers are
Then click Advanced Convert...
Select Exact Size and set the image quality to 100
Set your Width and Height resolutions for your device.
Uncheck Add "Converted by www.freeimageconverter.com"
Select Leave the same file name and leave the Postfix & Prefix empty. Then set your output in a folder.
For bootanimation:
Extract /system/media/bootanimation.zip OR /data/local/bootanimation.zip OR /system/customize/resource/bootanimation.zip (For Oxygen ROM, the bootanimation is built into the framework-res)
Do the steps above
Move the new resized folder(s) into your bootanimation workspace
Edit the desc.txt to match your device resolutions
Zip the contents ( folder_name desc.txt )
Set compression method to Store
Delete the extracted bootanimation files
Make sure this new bootanimation.zip is in PORTED
Click to expand...
Click to collapse
Sources
http://cleanimport.xda/index.php?threads/1598713/
http://cleanimport.xda/index.php?threads/1908008/
Click to expand...
Click to collapse
Credits & Thanks to
# rishabh.raj37
# Peteragent5
Happy porting!
:laugh:
Click to expand...
Click to collapse
reserved
for clarification
This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
Yes. This method gives a lot of bootloops. It only can be used on devices with hairline differences between specs.
Sent from my GT-N7000 using XDA Premium 4 mobile app
lozohcum said:
This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
Click to expand...
Click to collapse
not really ,,i have tried porting with this and it worked succefullyy
:laugh:
may be you have to try it perfectly
1c3_5n0w said:
Yes. This method gives a lot of bootloops. It only can be used on devices with hairline differences between specs.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
have you tried this methode,,iam sure it will work,,:laugh::laugh:
ArjunrambZ said:
have you tried this methode,,iam sure it will work,,:laugh::laugh:
Click to expand...
Click to collapse
I started porting roms about year ago so... yes I did, I tried many "methods". This works mostly for similar devices.
Now I'm trying to use source code
lozohcum said:
I started porting roms about year ago so... yes I did, I tried many "methods". This works mostly for similar devices.
Now I'm trying to use source code
Click to expand...
Click to collapse
yah trying with source code is the best way ,but this tut is for users who really cant get it using source :good:
Arjunramb456651 said:
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. YOU are
choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
FOR ParanoidAndroid And PAC:
Specially For PAC Rom:
FOR SPECIFIC MANUFACTURE DEVICE
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
After a succefull port also there can be many bugs present which has to soved logically
here are somethings which can help in DEBUGGING
1) IF GALLERY FC :
open the system/framework and find framework-res.apk file[can use any extracting app]
in both the roms and go to res folder then to xml subfolder and copy and replace the storage_list.xml file from source to port rom
( framework-res.apk\res\xml\storage_list.xml)
Credits & Thanks to
# rishabh.raj37
# Peteragent5
Happy porting!
:laugh:
Click to expand...
Click to collapse
Can you port an AOSP/CM based rom using a Manufacturer/maufacturer based ROM as the base (i.e. touchwiz rom)?
Click to expand...
Click to collapse
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed? I would be using a rom that runs on another tab 2 10.1 but not for AT&T. Or even if i wanted an AOSP rom, would be that difficult?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SGH-I337 using XDA Premium 4 mobile app
HitBobLer said:
Arjunramb456651 said:
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. YOU are
choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
FOR ParanoidAndroid And PAC:
Specially For PAC Rom:
FOR SPECIFIC MANUFACTURE DEVICE
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
Can you port an AOSP/CM based rom using a Manufacturer/maufacturer based ROM as the base (i.e. touchwiz rom)?
Click to expand...
Click to collapse
no i dont think so,because cm /pa have modified source code ,which differ from manufacture rom hence ,,not possible ,u will possibly end in boot loop
Click to expand...
Click to collapse
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes of course ,this methode is for aosp or for cm roms and not for manufacture roms,,there are other guids for porting manufacture roms ,go search the forum
only boot loop no progress!!!
i had tried this method more then 4 times but it didnt worked....
rom is not booting up and its stucked on boot animation and shows no progress although i left it for an hour but still stucked....
any idea??
and for details...
i am porting chameleon OS built for htc one s just see this....-
android v is 4.2.2
so i used aokp 4.2.2(stable) first as base rom but i failed more then 2-4 times then i tried cm10.1 as base rom but still i am at bootanimation.
i had also used the three libs from the port rom and base rom as mentioned in the guide but still nothing is going good......:crying:
can you tell me that am i missing something or i should try other guides?
if your answer is that i should try other guides so please lead me to a guide.....
thanks.
regardslayboydroid
playboydroid said:
i had tried this method more then 4 times but it didnt worked....
rom is not booting up and its stucked on boot animation and shows no progress although i left it for an hour but still stucked....
any idea??
and for details...
i am porting chameleon OS built for htc one s just see this....-
android v is 4.2.2
so i used aokp 4.2.2(stable) first as base rom but i failed more then 2-4 times then i tried cm10.1 as base rom but still i am at bootanimation.
i had also used the three libs from the port rom and base rom as mentioned in the guide but still nothing is going good......:crying:
can you tell me that am i missing something or i should try other guides?
if your answer is that i should try other guides so please lead me to a guide.....
thanks.
regardslayboydroid
Click to expand...
Click to collapse
bro firstof all,, porting is not that easy as to read,,, here logcat is your only friends,,, get me the logcat
hmm
ArjunrambZ said:
bro firstof all,, porting is not that easy as to read,,, here logcat is your only friends,,, get me the logcat
Click to expand...
Click to collapse
okay just wait for a day...
and thanks for your quick reply..
playboydroid said:
okay just wait for a day...
and thanks for your quick reply..
Click to expand...
Click to collapse
okay
Good evening to all, first of all thanks for the guide.
The rom part, it works most of the things, porting is a rom for nexus 5 to take on g2.
I have problems with wifi, vpn and security in the setting menu.
Practically the vpn and security go on crash, while the wifi is active but can not find anything.
Do you have suggestions?
thanks
Sorry for my bad english
jokerpoker1 said:
Good evening to all, first of all thanks for the guide.
The rom part, it works most of the things, porting is a rom for nexus 5 to take on g2.
I have problems with wifi, vpn and security in the setting menu.
Practically the vpn and security go on crash, while the wifi is active but can not find anything.
Do you have suggestions?
thanks
Sorry for my bad english
Click to expand...
Click to collapse
it would only b possible if you could get a logcat about the problem,, and if the problem persist in the base rom,then its sure to be in ur port too,
ArjunrambZ said:
it would only b possible if you could get a logcat about the problem,, and if the problem persist in the base rom,then its sure to be in ur port too,
Click to expand...
Click to collapse
thanks for the reply, it is the first time I use logcat, this is what I said when I port ROM.un my friend was telling me That might be the update script.
Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk
jokerpoker1 said:
thanks for the reply, it is the first time I use logcat, this is what I said when I port ROM.un my friend was telling me That might be the update script.
Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk
Click to expand...
Click to collapse
yes when it coms to porting logcat is ur only friend,, well updater script doesn't have any relations with the rom actually its like a process to installing the rom as said, and fixing permision,,,
and please tell me when was this logcat obtained and this time get me a full logcat
How To Port for the Vibrant and Other Galaxy S Devices
This is a guide on how to port for the original Galaxy Devices.
Note: This is only for I9000,Vibrant, Captivate, Fascinate, and Epic 4g.
I dont think this will work on i9001 then again i have never tried it.
Things needed:
Winrar (Really just a file extractor so your preferred extractor will work as long as it will open up .rar or .zip)
Notepad++
A computer that can run both of these things.
Java Jdk 7 completely installed.
android sdk can't hurt. ( not necessary except that you can install google adb drivers through it)
The sign tool i will include in the end of the post.
If you are porting for the Vibrant these are the steps. The steps are the same for all galaxy devices except you have to change the base rom:
A Vibrant rom.(This is the base rom. This will change depending o which device you ARE PORTING FOR. therefore if your trying to make it run on the captivate use a captivate rom as the base rom.)
A rom from whichever of the original galaxy devices you wish to port from.?(This is the port rom, therefore the rom that you wish to port TO YOUR DEVICE. Say you were porting omni rom from i9000 to vibrant you would get the omni rom from the i9000 section to port that.)
If you want a certain kernel download that kernel FROM YOUR DEVICES DEVELOPMENT THREAD. Not from the other phone.
Steps:
1. unzip both the vibrant rom, the kernel, and the porting rom.
2. Open up the Vibrant rom and the i9000 (or whichever phone) rom.
3. In the i9000 (or whichever device you downloaded the rom from) rom delete the:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
4.replace all those files with the same files from the kernel that you downloaded. by copying and pasting into the vibrant folder.
5. delete the modem.bin and replace it with the one that was in the vibrant folder
Note: if you want to use the kernel that came with the vibrant rom, all of these files can be taken straight from the vibrant folder. your port rom will then have that kernel.
6. open up the system folder in your port rom and delete the usr folder then replace it with the usr folder from the vibrant rom.
7. Then open up notepad++ and go to file in the top left hand corner. click open and navigate back to the i9000 folder. Here is where you need to go. Meta-Inf>COM>Google>Android Then click updater-script.
8 delete the lines that pertain to a certain device so for i9000 devices it is the first four lines. It should look like this when done.
View attachment 2470792
9.Now go back to wherever you downloaded the roms and delete the .ZIP FILE OF YOUR PORT ROM NOT THE PORT ROM FOLDER THAT YOU EXTRACTED.
10. Go into the port rom and highlight all the files then click add to archive. make sure on the dialog box that pops up you select .zip file and and add and update files.
11 once that is done rename the file that was just zipped to "update" (dont include the quotes).
drag this file all the way through the sign tool folder after you have unzipped it. then once it has copied there click the rom batch file.
12. If it finished with no errors then you should be good to flash your newly ported rom!
If you have any questions, feel free to ask!
Credits:
Jrongi1
CannondaleV2000
Rizwan Khan
Downloads:
http://www.mediafire.com/download/96f4sly59d46y2i/Sign_Tool.zip
Thanks a sharing
Let me know who ports what so we can get the original galaxy's back to life. Now if only I could build...
Sent from my Nexus 4 using xda app-developers app
skinzy98 said:
How To Port for the Vibrant and Other Galaxy S Devices
This is a guide on how to port for the original Galaxy Devices.
Note: This is only for I9000,Vibrant, Captivate, Fascinate, and Epic 4g.
I dont think this will work on i9001 then again i have never tried it.
Things needed:
Winrar (Really just a file extractor so your preferred extractor will work as long as it will open up .rar or .zip)
Notepad++
A computer that can run both of these things.
Java Jdk 7 completely installed.
android sdk can't hurt. ( not necessary except that you can install google adb drivers through it)
The sign tool i will include in the end of the post.
If you are porting for the Vibrant these are the steps. The steps are the same for all galaxy devices except you have to change the base rom:
A Vibrant rom.(This is the base rom. This will change depending o which device you ARE PORTING FOR. therefore if your trying to make it run on the captivate use a captivate rom as the base rom.)
A rom from whichever of the original galaxy devices you wish to port from.?(This is the port rom, therefore the rom that you wish to port TO YOUR DEVICE. Say you were porting omni rom from i9000 to vibrant you would get the omni rom from the i9000 section to port that.)
If you want a certain kernel download that kernel FROM YOUR DEVICES DEVELOPMENT THREAD. Not from the other phone.
Steps:
1. unzip both the vibrant rom, the kernel, and the porting rom.
2. Open up the Vibrant rom and the i9000 (or whichever phone) rom.
3. In the i9000 (or whichever device you downloaded the rom from) rom delete the:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
4.replace all those files with the same files from the kernel that you downloaded. by copying and pasting into the vibrant folder.
5. delete the modem.bin and replace it with the one that was in the vibrant folder
Note: if you want to use the kernel that came with the vibrant rom, all of these files can be taken straight from the vibrant folder. your port rom will then have that kernel.
6. open up the system folder in your port rom and delete the usr folder then replace it with the usr folder from the vibrant rom.
7. Then open up notepad++ and go to file in the top left hand corner. click open and navigate back to the i9000 folder. Here is where you need to go. Meta-Inf>COM>Google>Android Then click updater-script.
8 delete the lines that pertain to a certain device so for i9000 devices it is the first four lines. It should look like this when done.
View attachment 2470792
9.Now go back to wherever you downloaded the roms and delete the .ZIP FILE OF YOUR PORT ROM NOT THE PORT ROM FOLDER THAT YOU EXTRACTED.
10. Go into the port rom and highlight all the files then click add to archive. make sure on the dialog box that pops up you select .zip file and and add and update files.
11 once that is done rename the file that was just zipped to "update" (dont include the quotes).
drag this file all the way through the sign tool folder after you have unzipped it. then once it has copied there click the rom batch file.
12. If it finished with no errors then you should be good to flash your newly ported rom!
If you have any questions, feel free to ask!
Credits:
Jrongi1
CannondaleV2000
Rizwan Khan
Downloads:
http://www.mediafire.com/download/96f4sly59d46y2i/Sign_Tool.zip
Click to expand...
Click to collapse
Can you tell me how to Port Omni while taking CM as base?
noumanhamid said:
Can you tell me how to Port Omni while taking CM as base?
Click to expand...
Click to collapse
To take cm as a base would involve decompiling and recompiling for all the framework files to work so as of now no. But why use cm as a base though?
Don't have OMNI base
---------- Post added at 08:53 PM ---------- Previous post was at 08:29 PM ----------
@skinzy98 i was porting Mokee but systemUI force close ?
Any help please ?
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
@skinzy98 i was porting Mokee but systemUI force close ?
Any help please ?
Omni can be ported from the i9000. Is the system ui force closing in then other mokee thread? Also make sure everything was a clean download and make sure everything was done correctly
I tried normal porting (replace framework , app , media , fonts )
Rom booted but systemUI force close
---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------
I tried normal porting (replace framework , app , media , fonts )
Rom booted but systemUI force close :silly:
Oh well that's probably why. You can't replace the certain frameworks with another ROM because each ROM is unique. It is built with certain features for each rom. If you'll follow the guide it should work fine.
tried to port miui , stuck at boot screen, used miui by gtbluesky for i9000 and cm 10.1 for vibrant.
smokey155193 said:
tried to port miui , stuck at boot screen, used miui by gtbluesky for i9000 and cm 10.1 for vibrant.
Click to expand...
Click to collapse
Is miui 4.3 or 4.2?
4.2.2
smokey155193 said:
4.2.2
Click to expand...
Click to collapse
Well then you need to download 4.2 ROM and use it to port it
The is numbers have to be the same
Can you port this rom:
http://forum.xda-developers.com/showthread.php?t=1874086
Possibly. Right now porting from fascinate and captivate and epic is questionable I'm still working on them booting
Port from fascinate is very easy. I ported PA from fascinate, but its CMDA and you will not have Data and Network. Port only from i9000 or Galaxy S 4G, and try to keep clean developer section.
Dont port every ROM from i9000, port 1-2 ROM's so you can update it faster.
Thanks for you guide.
Sent from my T959 using xda app-developers app
Galaxy3HELL said:
Port from fascinate is very easy. I ported PA from fascinate, but its CMDA and you will not have Data and Network. Port only from i9000 or Galaxy S 4G, and try to keep clean developer section.
Dont port every ROM from i9000, port 1-2 ROM's so you can update it faster.
Thanks for you guide.
Sent from my T959 using xda app-developers app
Click to expand...
Click to collapse
Ever ported from captivate. I've been working on getting dirty unicorns going and for some reason won't boot but I can't seem to get a log of the boot process from anybody.
skinzy98 said:
Ever ported from captivate. I've been working on getting dirty unicorns going and for some reason won't boot but I can't seem to get a log of the boot process from anybody.
Click to expand...
Click to collapse
I can port it, but i dont know if anybody is still using 4.3.1 Android version. bye
---------- Post added at 06:06 PM ---------- Previous post was at 05:13 PM ----------
skinzy98 said:
Ever ported from captivate. I've been working on getting dirty unicorns going and for some reason won't boot but I can't seem to get a log of the boot process from anybody.
Click to expand...
Click to collapse
DirtyUnicorn 4.0 will be uploaded tommorow.
I must say, its great ROM, if 4.4.x version come, i will surely port it.
Thanks
I can port it as I was doing it first just wondering if you had ever tried. I will set up the thread once a successful boot take place. I was just asking if you had