Database Users

[Q] Need assistance with Rom PORT

I've basically decided to try porting for learning purposes. At this moment I have a flash-able zip in idle until I get my phone this Friday.
So, with all the issues and controversies surrounding the Nexus 4 -- many of which are software related -- I decided that porting Jellybean 4.1.2 would be fitting. I need advice and critique from an experienced Rom Porter before I go ahead and flash my creation. I will detail my activities below but please PM me or reply here with your requests for files that may indicate the integrity of my port (build.prop for example).
Sources:
BASE
Factory Images "occam" for Nexus 4
Android 4.2 (JOP40C)
Click to expand...
Click to collapse
https://dl.google.com/dl/android/aosp/occam-jop40c-factory-cd3dc140.tgz
PORT
Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet)
Android 4.1.2 (JZO54K)
Click to expand...
Click to collapse
https://dl.google.com/dl/android/aosp/yakju-jzo54k-factory-92ff9457.tgz
Windows 7 with cygwin and dixisda kitchen
His thread: http://forum.xda-developers.com/showthread.php?t=633246
Build log
Ran both sources through kitchen and repacked to create manageable zip versions (no tweaks or modifications; only signed)
extracted both zips in separate directories
followed porting guide step by step by Oogway13 from Nexus S (my old phone) forums
his thread: http://forum.xda-developers.com/showthread.php?t=1791006&highlight=port
Base files copied to Port:
/system/
-app
-bin
-etc
-lib
-usr
-vendor
-xbin
/META-INF/
-all files and folders
build.prop was edited with lines from Base added to Port
boot.img from Base to Port
-Init.rc one line edit from Port to Base boot.img (BOOTCLASSPATH )
zipped resulting Port files
ran through kitchen and applied:
-SuperSU
-Busybox
-init.d support
-apps/data/ support
-generated updater_script applied
-signed

[GUIDE]How to port manufacturer ROM (Sense/Touchwizz...) [UPDATED For KITKAT]

How to port manufacturer ROM​​
As many people ask me how i’m porting ROMs to my Nexus S i share my method in this thread.
This method works for the Nexus but should also work on a lot of devices. The list of files that I would write in this thread is not exhaustive.
Please for all improvements, send me a MP. I’m french and it’s possible for me to misspellings
This thread is in constant progress thanks to your feedback.
Do not use this guide to port rom based on CM / AOSP roms. Please use this guide to port Sense / TouchWizz / Motoblur etc ... If you want to port based on AOSP roms there are others guide on XDA.
This method is not perfect, much work will then be necessary to fix all the bugs, and nothing says that this method is functional rather than every time ....​
I. What you need
Ubuntu and dsixda's Android Kitchen. Please refer to this link
Notepad++
Winrar
A brain =)
NB : Before you start porting a ROM you need to know several things. Over the phone you want to port the rom will have a hardware close to your, more porting will be simple and functional.
Example : Same screen resolution, processor of the same type (ARM6, ARM7, etc ....)
PORT is the ROM you want to port and BASE is the ROM developed for your device (AOSP/CM)
II. Let’s go !
1. Create new folder where you want and name it « Rom_port_for_yourdevice »
2. Download AOSP/CM developed for you device with the same android version which the rom you want to port
3. Download the rom you want to PORT
4. Extract each zip ROM in separate folder in « Rom_port_for_yourdevice »
{
"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"
}
5. Now it will appears two folders. Open both.
In PORT folder delete META-INF folder and copy/paste the META-INF folder of BASE in PORT folder.
6. Open system folder in PORT rom and delete vendor folder
7. Now in PORT folder open lib folder and delete these folders :
modules
hw
egl
8. Now go in BASE folder and select (if exists) these folders :
addon.d
bin
etc
customize
framework
lib
vendor
xbin
Now copy these in system folder of PORT but do not replace anything ! (If forgot « ETC » folder on screenshot)
 
9. Open bin folder in BASE and PORT folders. Copy and replace these files from BASE to PORT :
adb
brcm_patchram_plus
hostap
hostapd
init.vsnet
linker
logcat
logwrapper
radiooptions
rild
rmt_storage
vold
wpa_cli
wpa_supplicant
glgps
10. Now in BASE and PORT system folder open etc folder and copy and replace (if exist) these files/folders from BASE to PORT :
Bluetooth
Dhcpcd
Firmware
gps
init.d
permissions
ppp
pppd
security
ssh
terminfo
updatecmds
wifi
audio_effects.conf
audio_policy.conf
dbus.conf
gps.conf
init.*.sh
media_codecs.xml
media_profiles.xml
nfcee_access.xml
secomxregistry
vold.conf
vold.fstab
wrs_omxil_components.list
11. Now copy usr folder from BASE to PORT and replaces all files
12. Open lib folder in BASE and PORT folders. Copy and replace these files from BASE to PORT :
liblog.so
libsecril-client
libreference-ril.so
libril.so
libs3cjpeg.so
libaudioflinger.so (if port does not boot, use from PORT rom)
libaudioutils.so
libtinyalsa.so
libpn544_fw.so
libSEC_OMX_Core.so
libOMX.SEC.***.Decoder.so
For HTC devices:
libhardware_legacy.so
libhtc_ril.so
libhtc_ril_switch.so
For LGE devices:
lge-ril.so
More commonly:
Add all the lib files with "ril" in their name
13. Open framework folder in BASE and PORT folders. In both folder rename framework-res.apk to framework-res.apk.zip and open the two files with Winrar.
In both files go to /res/xml/ and replace storage_list.xml of PORT framework-res.apk with the one of BASE.
Now close Winrar and rename framework-res.apk.zip in framework-res.apk in both folders.
14. Very important: By the way, there are some proprietary binaries missing from the guide (just depending on the device, as it's impossible to include all), so what I recommend is if your device has official cm, go to github.com/themuppets, pick the repo corresponding to your manufacturer and branch corresponding to your android version and download it and copy the files in your device's folder to the ROM you are porting. Lib to lib, bin to bin, etc. You may also need to look at the Mk files in the cm device source for your device to see what is built from source that you'll need such as libs and bins. For example, if it has Product_packages += \libwifi \
You would need to copy libwifi from cm. [/QUOTE]
Source: http://forum.xda-developers.com/showpost.php?p=41294434&postcount=23
15. Now open build.prop of PORT rom and replace these lines with BASE build.prop :
Code:
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=
ro.product.cpu.abi=
ro.product.cpu.abi2=
ro.product.manufacturer=
ro.wifi.channels=
ro.board.platform=
ro.build.product=
ro.build.characteristics=
rild.libpath=
rild.libargs=
wifi.interface=
16. Reboot to Ubuntu.
Steps for android 4.3 and older
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
Save and recompile kernel
Use CM/AOSP modified kernel in your rom.
Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom.
17. Now ZIP your PORT rom folder and flash it.
Please don't forget to use LOGCAT to debug the rom..... And to thanks or/and donate to me .....
Thanks !
​GalaxyUser

Here, I give you some tips and may help you to fix issues..​
Files to fix ...
You can try to replace some of these files (if exists) to fix ...
NFC
/system/app/Nfc.apk
/system/lib/libnfc*.so
/system/bin/pcscd
Radio FM
/system/bin/fmradio
Sensors
/system/bin/akmd*
/system/lib/libsensors.so
Bluetooth
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
Wifi
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
RIL
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Camera
Copy libcamera*.so from base to port rom
If rom does not boot after that, replace file one by one and see which file is the problem.
If you port on HTC Devices, try these:​Fix Network auto select
Decompile framework-res.apk
Go to this folder \framework-res\res\values
Open bools.xml
Change <bool name="skip_restoring_network_selection">true</bool>
To Change <bool name="skip_restoring_network_selection">false</bool>
Fix graphichal issues
Decompile framework.jar
Change these files with your CM base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer

so there is hope that i can port xperia t jb rom to galaxy s3 using cm10 rom for galaxy s3

zeyadhan said:
so there is hope that i can port xperia t jb rom to galaxy s3 using cm10 rom for galaxy s3
Click to expand...
Click to collapse
Use CM10 and not CM10.1 to have the same version.
Try it i hope it will work

thank you for reply i saw your threads you ported lot of roms do you think it will boot
but sadly i use windows 7 so there is no way to decombile the kernel

zeyadhan said:
thank you for reply i saw your threads you ported lot of roms do you think it will boot
but sadly i use windows 7 so there is no way to decombile the kernel
Click to expand...
Click to collapse
I don't know if it will boot, when i do a port i never know if it will boot ^^
Read this: http://forum.xda-developers.com/showthread.php?t=633246
You could use kitchen in windows but it's not optimal i think.

i guess that the only way is install the Ubuntu and decombile kernel and make changes then combile it and copy the kernel to phone and back to windows (need a lot of time)

rom stuck at bootanimation maybe i do something wrong

zeyadhan said:
rom stuck at bootanimation maybe i do something wrong
Click to expand...
Click to collapse
Do a logcat and post pastbin link
Sent from my XT890 using xda app-developers app

Thanks for good tip!

Dear Galaxy_User,
i just port GT-I9100 rom for Nexus S, i am on Boot Animation and nothing working after that ..
http://pastebin.com/YBWDU1L4 here is the link for logcat .. kindly help me out
Regards,
Assassinoid

assassinoid said:
Dear Galaxy_User,
i just port GT-I9100 rom for Nexus S, i am on Boot Animation and nothing working after that ..
http://pastebin.com/YBWDU1L4 here is the link for logcat .. kindly help me out
Regards,
Assassinoid
Click to expand...
Click to collapse
Hi,
Your logcat is very weird
Try libaudioflinger.so to use from PORT

looks not bad
sent from my security handy talkie
talk free , no pay®

Nothing worked .. I just quit
Sent from my Nexus S using xda premium

assassinoid said:
Nothing worked .. I just quit
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Do you have correctly edited the kernel ?
You need to use CM kernel for Nexus S and to modify it with the BOOTCLASSPATH of Galaxy S Kernel.
Send me the boot.img of Nexus S and the boot.img of Galaxy S i will check that

GalaxyUser said:
Do you have correctly edited the kernel ?
You need to use CM kernel for Nexus S and to modify it with the BOOTCLASSPATH of Galaxy S Kernel.
Send me the boot.img of Nexus S and the boot.img of Galaxy S i will check that
Click to expand...
Click to collapse
OK I'll do that
Sent from my Nexus S using xda premium

Nice, the first actual tutorial on this instead of "just replace all apps/framework and media folder" which is a load of bull****,
Good job

Will this guide work if you want to port LG Stock ROM to another LG device? Like you ported O4X to Optimus Black.. I can use this guide to port O4X stock ROM to O2X?
Also, when porting stock ROM, I will need CM10 as base ROM or I must use same android version as the ROM I am porting?
Thanks.

natalya said:
Will this guide work if you want to port LG Stock ROM to another LG device? Like you ported O4X to Optimus Black.. I can use this guide to port O4X stock ROM to O2X?
Click to expand...
Click to collapse
I did it for Optimus Black, try it for O2X
natalya said:
Also, when porting stock ROM, I will need CM10 as base ROM or I must use same android version as the ROM I am porting?
Thanks.
Click to expand...
Click to collapse
You can use any rom with the same android version

GalaxyUser said:
I did it for Optimus Black, try it for O2X
You can use any rom with the same android version
Click to expand...
Click to collapse
Okay, can you please link me to the one you used as port (the O4X ROM) and do you recommend me to use that one as port or shall I use the one you already ported for Optimus Black as port?
PS: Is it easy to change bootclasspath?

Announcement for DualBooters [Only FOR DorimanX FANs]

Hi All,
you know that i always will serve your S2 to DualBoot all best 4.1.2 ROM you can find on XDA or other Forums.
you know that you can ask me to re-script all ROMs you want to DualBoot too.
Now, you have to know that, for all DualBoot ZIP i will provide in future, all will be done to flash my DualBoot moded Roms in 1rst ROM too
For that, i will always change zImage kernel of ZIP ROM for DualBoot by zImage DoeimanX kernel , so if you flash my provided DualBoot rom in 1rst position ROM, your ROM will be powered by @dorimanx V8.xx Last KERNEL.
If Modem exist in Original ROM ZIP from DEVs, it will be replaced by XXMS3 modem to, with RIL too , from last ModemRIL_XXMS3-FROM_I9100XWLSW_I9100VGFLS2_VGF .
If ROM ZIP manage AROMA MODS , this will be rescript too for DualBoot. Even for Modem or Kernel choice.
How i can provide for your :
- Only send me updater-script and aroma-config files for original ROM ZIP you want to DualBoot.
Species :
- If you already have a 4.1.2 stock rom, you can always try to flash my moded ROMs over it without wiping anything. I never tell you to WIPE anything before or after flash.
- my script never format partition, only will be done a delete of /system/ , /cache/ , /data/sec_data/ and /data/dalvik-cache/ folders
Thanks.

+1

+2

First
Wish you good luck
Sent from my GT-I9100 using Tapatalk 4

all my /Users-DEVs/ friends here soon
@bombaybadboy , @nik60 , Christian Nothing , @pargas , @krazy1101 , @immortalneo , @phenomarc ....
hahaha, all my best supporter friends are here
thanks , thats great for me.
no necessary to rethank this post, just your name will be appear here when you have thank OP

Troubadour666 said:
@bombaybadboy , @nik60 and Christian Nothing , @pargas too
hahaha, all my best supporter friends are here
thanks , thats great for me.
Click to expand...
Click to collapse
one friend in the square is best that 10 euro
ehehehe

I wonder if triple boot possible?

maybe you could take a look here but this is for sgs3
http://forum.xda-developers.com/showthread.php?t=1943928

This would be great, i'm waiting for

DualBoot - 1rst or 2nd ROM - I9100XWLSZ_NeatROM (Aroma Full&Lite soon)
Hi all,
based on principe in OP,
you can find my Last DualBoot ROM , based on last @_Sale_ Neatrom Full from yesterday.
In my ZIP, as a big test, you will find Viper4Android and Xpose and modules activated too. Modem is conserve, not change.
- last @dorimanx kernel version 8.41 inside too
Links to have a test of it : i named it Precious because when @_Sale_ provide a lite version, we can share a zip for ExtraLite_Full-Precious-I9100XWLSZ_NeatROM soon.
ExtraLite-Precious-I9100XWLSZ_NeatROM_Full.zip - 309.33 MB http://d-h.st/Dr2
EDIT and after some test :
i have an already "AROMA mod" to choose Full or Lite Install of ROM but, wait for the "REAL Lite with many features" from _Sale_ NeatRom too lol
i made it for 'dualbooters' , but i can 'drive' /preload/ managment folder for 'basic' users hahaha
I name it PreciousDualBootAromaFull-Lite-I9100XWLSZ_NeatROM.zip.
- xpose activated, xquicktoggles, appsettings modules too.
- viper activated and sdcard kernels installed
- walkman installed and sound activated too
- personal lite version (from last _Sale_ NeatRom Full) : (78 apks) no CSC sub-folders , rich features.xml, tts folder deleted
- full version : all things deleted from lite (133 apks)
When Real Lite will be available from @_Sale_ , AROMA will be ready and just perfect for all dualbooters friends.
thanks.

rom porter patch beta 1

after too many test i finally made a patch for porting ics stock roms from arc/s (and maybe other xperia 2011 devices) to pur lovely xperia play
it will install all the things that you need for fully working rom on xperia play and deletes the cybershot camera(because it not working on our device)
installation guide:
there are 2 ways for installing
1-if the rom has armo installer
2-if it doesnt have armo installer
if it has armo installer its very easy to use this
here is the instruction
1-open rom zip and ics rom porter.zip files with winrar
2-find the device section in rom zip file
3-drag all the files inside system folder in the ics rom porter.zip to lt28i(xperia arc) folder of rom zip
4-now simply flash the rom zip ans choose xperia arc as your device and everything will be fine
if the rom doesnt have armo installer
do the same thing as i said for the the roms with armo installer but instead of draging the files to lt28i folder drag them to system folder
bugs:
1-no touchpad. i need help for this part.
2-flashable.zip is broken. i need help for this one too
3-build.prob will be replaced with xperia z v5 by markphyton so you wont see the original tweaks after the port
4-some of the roms will give bootloop because they have more space than our system partition. if some one can repartiton a kernel with more system storage it will be great
to do list:
1-making an armo zip with all build.prob form popular roms and the requested roms
2-adding touchpad fix
tested on(working):
1-anzumi : by myself
2-4.1.b.1.13(arc version by jader) : by myself
tested on(not working):
xperia ray 4.1.b.1.13 (touchscreen had some problems)
download link:
http://d-h.st/eJv
thanks to:
1-markphyton : i have taken my files from his rom
2-all the developers of xperia arc :for making roms(that gived me the idea of this patch)
3- xda: all of us know why
4-dev host : i use it for uploading my files
5-xperia play users : for not giving up

reserved
please help me for fixing the bugs
i will start working on gb and jb patch as soon as i get time

waiting for reports now
that all i can do now
if you want to help for completing this patch i need help for these things
1- someone with good knowledge in making armo installer and update.zip files
2-someone for helping me in making build.prob files of requested roms
3-(the moost ipmortant) helping me for fixing touchpads

Smokerman is good in porting roms, you should ask him for touchpad fix
I have basic knowledge of aroma installer and build.prop editing, if i can, i'll help

touchpads
@smokerman
can you help me for fixing the touchpads?

i will release an update soon
things that i changed:
1-fixed the flashable zip
2-im using 4.0.4 ics build.prob instead of xperia z rom by markphyton
jb patch is being tested now
for now i only get bootloops
but im trying to solve the problem
i aslo wanted to make an gb patch but i saw that we will get a little problem in gamepad after porting gb roms from arc
(always open game pad. you cant use touchscreen for gaming anymore in ported gb roms.)

pedyvirus said:
@smokerman
can you help me for fixing the touchpads?
Click to expand...
Click to collapse
i can help for sure..what is the rom? send me the link..i will look into it on the weekend.

well im making a patch for all of the roms
i need to know the way so i can support all the roms that xperia play users want
do you use farenheith's patch for fixing the touchpad in stock based roms?

update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem

pedyvirus said:
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
Click to expand...
Click to collapse
is it possible to port ics stock rom of arc to our device(xperia miro) (2012) ?????
a help would be appreciated!!! and i know @pedyvirus you can help me

[Q] build CM7 for Galaxy Y GT-S5363 from source

Hi all.
I have successfully flashed PsychoGame's CyanogenMod 7 ROM for GT-s5360 together with its kernel.
Now i would like to make some changes in the source code of CM7 and to build it from source. Unfortunately i have spent already 4 days without success.
Those are the steps that i did:
1. I have downloaded CM7 source code from git://github.com/CyanogenMod/android.git -b gingerbread
2. I have cloned PsychoGame's totoro device code into /devices/samsubg/totoro
3. i have connected my device via USB and run the script extract-files.sh which successfully extracted all files.
4. during the building i realized that the above script extract all essential files (like camera related), so i cloned PsychoGame's vendor directory from github.com/PsychoGame/android_vendor_samsung_totoro.git
5. now i realized that the file cyanogem_totoro.mk in the directory vendor/cyanogen/products is missing. where i can find a suitable file?
i have found somewhere such file and succeeded to build an ROM, unfortunately CWM does't let me to flash it because the assert command checks that the current device in "totoro" but it fails. i have tried to open the zip file of the ROM and to delete the assert command but CWM still can''t flash the new ROM.
can somebody please help me with some guild about how PsychoGame built his last vertion of CM - CyanogenMod 7 Alpha 5 Release
Thank you very much!

Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing

marcussmith2626 said:
Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing
Click to expand...
Click to collapse
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!

yuripo said:
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!
Click to expand...
Click to collapse
Percys github is
https://github.com/percy-g2
I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy

I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy[/QUOTE]
can please somebody explain how to build only Percys ROM without the kernel?
thank you

Hi all.
Can somebody please give a small guide for how to build percy's CM7 ROM from source?
which directories in the CM7 i should replace? does the process of building is the same as with official ports?
Thank you!