How To Port a Rom
Most efficiant way .
Hello Guys i have been triying a lot of methods to port roms and i found this method brilliant and a 100% Working on HTC And samsung devices 90% On others as i did not test them myself
Let us start .First you need the following :
1.DsiXDA Android Kichen.
2.Kernel Sooting the rom that you want to port to device .
3.A little knowlege on how to port roms.
4.Device with same resolution to port rom from.
5.Note pad++ Or adobe dreamware.
6.Winrar Zip archieve.
Ok so now make 2 folders one named base and the other named port.
Copy the rom that you want to port to your device to port folder and copy a rom that works on device to base folder.
In Port folder delete USR Folder and replace it with USR Folder from base folder.
Now lets open bin in port folder And in base folder.
Copy and replace the following from base to port.
Code:
[SIZE="3"]1.rmt_storage.
2.vold
3.wpa_cli
4.wpa_supplicant[/SIZE].
Again lets open ect folder in base and port folder.
Now Delete the following in port folder:
Code:
[SIZE="3"]1.hw folder .
2.modules folder. [/SIZE]
And Replace them with HW And modules folder from base folder.
Now copy and replace the following lib files from base rom to port.
Code:
[SIZE="3"]1.libhardware_legacy.so
2.libhtc_ril.so
3.libhtc_ril_switch.so
4.libril.so[/SIZE]
Now lets open ect folder in port and base folders.
Delete the following folders from port rom:
Code:
[SIZE="3"]1.Firmware.
2.init.d
3.Sound Image. [/SIZE]
And replace them with the following from base rom:
Code:
[SIZE="3"]1.Firmware.
2.init.d
3.Sound Image[/SIZE]
Now copy and replace the following in ect folder from base rom to port rom:
Code:
[SIZE="3"]1.AdieHWCodec
2.AIC3254_REG
3.AIC3254_REG_XD
4.AudioBTID
5.CodecDSPID
6.TPA2051_CFG
:You might not find them all So dont panic.[/SIZE]
Now If your your using "adreno processor or any processor" and the port rom has "lets say portprocessor" in ect of base rom you will find "yourprocessor_config" Copy and paste it in ect of port rom now delete "Portprocessor_config"
Now copy and replace vold.fstab from base rom to port.
Last step delete boot.img in port and replace it with the one from base.
:if both devices have same storage mods "I mean both need sd cards"You can continue if one of them has "SD CARD AND THE OTHER NO SD CARD MAKE SURE!!! to copy and replace ext.jar from framewrok folder in base rom to framework folder in port rom.
Now lets open customize folder in port rom
Customize/MNS/default.xml
And search for the following code:
Code:
[SIZE="3"]
[COLOR="Red"]HTC_Sensation_xl[/COLOR]/1.0
[/SIZE]
Now i am using htc sensation xl rom as a base as base and need to port it to desire hd replace code with this:
Code:
[SIZE="3"]
[COLOR="Red"]HTC_Desire_HD[/COLOR]/1.0
[/SIZE]
Exit and save
Ok now open customice/cid/default.xml with the note pad ++ or adobe dreameware and find the following code :
Code:
[SIZE="3"]
[COLOR="Red"]HTC Sensation xl with beats audio[/COLOR]
and replace it with this code:
Code:
[COLOR="Red"]HTC Desire HD with Beats Audio[/COLOR]
[/SIZE]
Exit and save
now lets open Build.prop in port folder and in base folder with note pad ++ or adobe dreamware
no find the following codes:
Code:
[SIZE="3"]# ro.build.product is obsolete; use ro.product.device
ro.build.product="Replace with one of base rom"
ro.build.product="Replace with one of base rom" [MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
ro.product.processor="Replace with one of base rom"
ro.product.ram="Replace with one of base rom"
ro.product.display_resolution="Replace with one of base rom"
ro.product.main_camera="Replace with one of base rom"
ro.product.front_camera="Replace with one of base rom"
ro.product.bluetooth="Replace with one of base rom"
ro.product.wifi="Replace with one of base rom" [MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
ro.build.host="Replace with one of base rom"
ro.product.model="Replace with one of base rom"
ro.product.brand="Replace with one of base rom"
ro.product.name="Replace with one of base rom"
ro.product.device="Replace with one of base rom"
ro.product.board="Replace with one of base rom"
ro.product.cpu.abi="Replace with one of base rom"
ro.product.cpu.abi2="Replace with one of base rom"
ro.product.manufacturer="Replace with one of base rom"
ro.product.version="Replace with desired name"
ro.build.id="Replace with desired name"
ro.build.display.id="Replace with desired name" [/SIZE]
Exit and save
Now delete Meta-inf folder in port and replace it with one from base
Now you can open updater script and change some name like name of rom......
Like my work ?Donate to me and help me expand or you can just hit the thanks button Thanks{Pleaze list donations on thread}
Thanks The Epik Dude For Figuring Out Some Mistakes and Helping me In Tests
Build.Prop Tweaks
Tweaks
No Rom Is complete with out tweaksBuild.prop tweaks:
Code:
Add these to you Build.prop:
# Disable checkin services
ro.config.htc.nocheckin=1
ro.config.nocheckin=1
# Enable noice cancelling mic
media.a1026.enableA1026=1
# Enable Dual Transfer Mode
ro.ril.enable.dtm=1
# Disable debugging notify icon
persist.adb.notify=0
# For emmc phone storage
ro.phone_storage=0
# Render UI with GPU
debug.sf.hw=1
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
# Improve overall media quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Disable 3 Dot menu
qemu.hw.mainkeys=1
# Increase overall touch responsiveness
windowsmgr.max_events_per_sec=[COLOR="Red"]300 For newer devices you can go up to 400 [/COLOR]
debug.performance.tuning=1
video.accelerate.hw=1
# Disable checkin services
ro.config.htc.nocheckin=1
ro.config.nocheckin=1
# Improve Dalvik
dalvik.vm.heapsize=128m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapstartsize=5m
dalvik.vm.execution-mode=int:jit
# Disable sending data and logging
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
dalvik.vm.checkjni=false
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
# Disable HTCs Screenshot feature
ro.htc.framework.screencapture=false
# Disable Bytecode Verification
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v,m=y
# Enable 3 fingers swipe
ro.framework.gestureservice=1
[COLOR="Red"]#Bravia Engine
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1 Only if you want to add bravia engine[/COLOR]
# Enable GPU Acceleration
debug.fb.rgb565=0
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
persist.sys.composition.type=gpu
[COLOR="Red"]# Qualcomm display settings
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
com.qc.hardware=true Only if you have qualcom chipset.[/COLOR]
How to add bravia engine:
Donload this View attachment 1803234 and extract copy both folders and merge with folders of rom
Like my work ?Donate to me and help me expand or you can just hit the thanks button Thanks{Pleaze list donations on thread}
For htc devices only Rsie+systemui tweaks
Rosie + Sytem Ui Tweaks
First i wanted to teech you how to enable unlock animation one sese 4 and up roms .
What uou need is apktool <If your new to apktool use i bot peaches apktool> and one click signer.
No after you install framework files lets decompile rosie.apk with this code :
Code:
Apktool d rosie.apk Animrosie
After decompiling navigate to animrosie and go into :
animrosie\res\values\arrays.xml and open arrays with notepad++ or adobe dreamware
Now you will probably see this code :
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string-array name="app_sort">
<item>Alphabetical (A to Z)</item>
<item>Date (Most recent)</item>
<item>Date (oldest)</item>
</string-array>
<string-array name="default_scene_folder_title">
<item>Favorites</item>
</string-array>
<string-array name="default_scene_folder_title_id">
<item>nn_favorites</item>
</string-array>
<string-array name="default_scene_folder_title_local">
<item>Favorites</item>
</string-array>
<string-array name="default_scene_folder_title_id_local">
<item>default_scene_folder_title</item>
</string-array>
<string-array name="custom_pause_wallpapers">
<item>com.htc.android.WeatherLiveWallpaper.Weather</item>
<item>com.htc.android.weatherlivewallpaper.service.WeatherWallpaperService</item>
</string-array>
</resources>
I want you to change this code to this code :
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string-array name="app_sort">
<item>Alphabetical (A to Z)</item>
<item>Date (Most recent)</item>
<item>Date (oldest)</item>
</string-array>
<string-array name="default_scene_folder_title">
<item>Favorites</item>
</string-array>
<string-array name="default_scene_folder_title_id">
<item>nn_favorites</item>
</string-array>
<string-array name="default_scene_folder_title_local">
<item>Favorites</item>
</string-array>
<string-array name="default_scene_folder_title_id_local">
<item>default_scene_folder_title</item>
</string-array>
<string-array name="custom_pause_wallpapers">
<item>com.htc.android.WeatherLiveWallpaper.Weather</item>
<item>com.htc.android.weatherlivewallpaper.service.WeatherWallpaperService</item>
</string-array>
[COLOR="Red"] <string-array name="unlock_spin_markers">
<item>unlock_to_00</item>
<item>unlock_to_01</item>
<item>unlock_to_02</item>
<item>unlock_to_03</item>
<item>unlock_to_04</item>
<item>unlock_to_05</item>
<item>unlock_to_06</item>
</string-array>[/COLOR]
</resources>
Add the worlds in red
Now let us recompile with this code :
Code:
Apktool b animrosie animrosie.apk
Now if you had problems compiling rosie add this line to publick.xml same folder:
Code:
<public type="array" name="unlock_spin_markers" id="0x7f050006" />
Now copy anim rosie.apk to one click signed and sign it and its ready to be flashed or replaced in root browser
Now lets learn how to make rosie 4x5 or 5x5 appdrawer <That means all apps>
Decompile rosie.apk and navigate to com\res\valuse and open dimens.xml
Now Lets get ready to code .
Start searching for this :
Code:
app_icon_size_ext
You will find this
<dimen name="app_icon_size">[COLOR="Red"]60.0px[/COLOR]</dimen>
Now 40.0 px is my icon size If i need to make an 5x5 app drawer i will need to change it to [COLOR="Red"]40.0 px[/COLOR]
And for 4x5 rosie 49.0px<You should get the point>
Now save and exit.
Here comes the tricky part's
Now we need to change portrait mode you will need to go to this folder:
Values-norma-hdpi or in some cases valuse-portrat lw630 or valuse-normal-xhdpi ........
Now lets open that folder and search for the folloowing :
Code:
page_view_icon_cell_width
you will find this
<dimen name="page_view_icon_cell_width">[COLOR="Red"]140.0px[/COLOR]</dimen> in my case its 140.px yours might be 120 px I will explain in pic
[ATTACH]1804254._xfImport[/ATTACH]
Now i need to change that code to
<dimen name="page_view_icon_cell_width">[COLOR="Red"]126.0px[/COLOR]</dimen>
now you need to also search for this :
page_view_icon_cell_height
and you will find this
<dimen name="page_view_icon_cell_height">[COLOR="Red"]148.0px[/COLOR]</dimen> in my case
I will need to change it to
<dimen name="page_view_icon_cell_height">106.0px</dimen>
Now for landscape same thing but its in values-land ......... And diffrent valuses .
Now in valuse-Portrait .......... Open integres.xml file and search for the following :
Code:
<integer name="config_allAppsTabbedCellCountX">[COLOR="Red"]4[/COLOR]</integer>
<integer name="config_allAppsTabbedCellCountY">[COLOR="Red"]4[/COLOR]</integer>
Now Change them to these :
<integer name="config_allAppsTabbedCellCountX">[COLOR="Red"]5[/COLOR]</integer>
<integer name="config_allAppsTabbedCellCountY">[COLOR="Red"]5[/COLOR]</integer>
That will make 5x5 apps in drawer
Now same thing in land but diffrent values if you have 480x800 rsolution i suggest cellcount x 6 and cell count y to 3 .
And we are finished recompile rosie and sign and its ready to be flashed .
Rosie empty flashable zip .
Like my work ?Donate to me and help me expand or you can just hit the thanks button Thanks{Pleaze list donations on thread}
reserv 3
Reserved 3
reserved 4
reserved 4
dude there isnt any rmt-storage in port or base
Re: [Guide]How to Port a rom and manage tweaks and More.
Nice guide
Another thing u can add as you have used Dxdia kitchen. Is how to change kernel boot splash screen. In boot.img
-Rik[Rittik]
also , my base rom doesnt have hw folder
hw and module folder in port is in lib and not etc
i dont have the 3rd and 2nd lib file you mentioned
Arjav23 said:
also , my base rom doesnt have hw folder
hw and module folder in port is in lib and not etc
i dont have the 3rd and 2nd lib file you mentioned
Click to expand...
Click to collapse
You are Using samsung right ?
Re: [Guide]How to Port a rom and manage tweaks and More.
S.a.M.e.R_d said:
You are Using samsung right ?
Click to expand...
Click to collapse
Ya
Sent from my GT-I5800 using Tapatalk 2
Re: [Guide]How to Port a rom and manage tweaks and More.
I will be making tutoriol tell me what Rom you sana port
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Re: [Guide]How to Port a rom and manage tweaks and More.
S.a.M.e.R_d said:
I will be making tutoriol tell me what Rom you sana port
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
Lezo and miui from galaxy ace to cm7 galaxy Apollo
Also can i port stock roms to cm7 via this
Sent from my GT-I5800 using Tapatalk 2
Porting a rom from galaxy y to galaxy ace s5830i
U know what's happening here
Device stuck at Samsung galaxy ace s5830i
Here is the logcat
www.pastebin.com/Uia91s4k
Sent from my GT-S5830i using xda premium
Sent from my GT-S5830i using xda premium
Edit
I figured it out
Sent from my GT-S5830i using xda premium
rahulnandwani said:
Edit
I figured it out
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
What was the problem and how did u fix it
Sent from my GT-I5800 using Tapatalk 2
I forgot to copy some lib files from port rom
Lib files given in op
Sent from my GT-S5830i using xda premium
How about hitting the thanks button nate
Sent from my GT-N7100 using xda premium
Hi there,
I have tried to port MIUI roms onto Galaxy Apollo On cm7/alpha 9. The Port has been successful, but there are a few issues, Dailer is stretched and hazy ,so is tthe lockscreen and few other layouts.
I have tried porting from
Galaxy Ace (ARMV6- larger screen than Galaxy Apollo)
Galaxy Spica (ARMV6- almost same screen as Galaxy Apollo)
Galaxy 5 (ARMV6- smaller screen than Galaxy Apollo)
Any help regarding where i need to resize
THe original ROms are resized properly for their own devices.
So what is the issue?
Arjav23 said:
Hi there,
I have tried to port MIUI roms onto Galaxy Apollo On cm7/alpha 9. The Port has been successful, but there are a few issues, Dailer is stretched and hazy ,so is tthe lockscreen and few other layouts.
I have tried porting from
Galaxy Ace (ARMV6- larger screen than Galaxy Apollo)
Galaxy Spica (ARMV6- almost same screen as Galaxy Apollo)
Galaxy 5 (ARMV6- smaller screen than Galaxy Apollo)
Any help regarding where i need to resize
THe original ROms are resized properly for their own devices.
So what is the issue?
Click to expand...
Click to collapse
Mmmm as i think your problem is resolution type ok i have a small fix
Go to build.prop and search for screen densety and make it a little bit smaller if it is 240 make it lets say 238 and check for progress .
Sent from my GT-N7100 using xda premium
Could succesfully create a 4x5 rosie, thats cool.
Now i'm searching for a "How to" of making Advanced Power Menu, Quicksettings (from Status bar) and Cubic Animation.
If some has an idea or could make one would be nice.
Related
I want to modify my settings.apk so that I can use the rotation mod to get up to 360 rotation.
I have attached 2 smali files, first one is the original smali from my settings.apk and the second one is the smali from a settings.apk that has the rotation mod setting that I want.
How can I port it over???
Hi,
as far as I know settings.apk is part of android source tree. Why do u decompile the .apk when you can have available the java source for your modifications ?
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?
Dear Friends / Dev / Vistors.,
I am looking for a long time for cm7 without no bug.. Finally CyanogenMod 7.2 for Galaxy Y (S5630) Has been released By bieltv.3 http://forum.xda-developers.com/member.php?u=4686683 With CM Specific Kernel :good:
But FM radio and usb tetherstill have a bug
other than
RC 4:
Fixed al 3g and Data issues on EXT4
My FIX.zip integrated on the ROM zip
IMEI is showing on EXT4 data partition
RILD is now prebuilt and updated last LibRIL.
Broken WIFI hotpost os wprking again
Icon of Wifi Hotpost is working well
ethd back again
RNDIS and USB0 are initialized in USB tether (still not working)
Added all offline charging files
Fixed offline charging using my 3.0 #7 kernel
NOTE: No format is needed, update-script has been modify to format the partition automatically
many dev have created hundreds of there rom on "CM 7 RC.2" which is most nicely theamed :good:
I Decide to use there Rom on Rc4.
LIKE PORTING ROM
Simple method
1, RC.4 Rom as base rom
2, Any rom based on cm7
3, Open base rom zip with Winrar (or other) ( pls not exctact zip file) and open system folder.
4. Delete app folder, font, framework, build.prop (" dont delete media because it consist offline battery chargering animation files")
5, Open Rom u need to Port to Rc.4 copy those folder and files (app folder, font, framework, media, build.prop)
and directly drag into base rom /system/ (If you can work with build.prop to change ver info) but i am lazy :silly:
6, on base rom open system/etc/ and delete init.d and permissions
7, copy those folders from other cm7 rom and drag into the base rom system/etc/
8, last META-INF on base rom just go into Meta-inf/com/google/andriod then delete updater-script
9. darg updater -script from port rom to base rom RC4
"the flash as per Insturction given by Mr bieltv.3"
"And please do it with your own risk"
By this method I Ported many CM7 rom..
And for MIUI, lewa some more files to be copy like media, and libs etc.... i have some doubt on that so let we decuse about that later
and this is my 1st post so Any mistakes please tel me.. thanks
My porting method is a little bit quick and faster.
aniket.lamba said:
My porting method is a little bit quick and faster.
Click to expand...
Click to collapse
can u give me your method ?:victory:
AhZhi said:
can u give me your method ?:victory:
Click to expand...
Click to collapse
See this video: https://www.youtube.com/watch?v=0MBLCPnrMww&feature=youtube_gdata_player
aniket.lamba said:
My porting method is a little bit quick and faster.
Click to expand...
Click to collapse
Both are good, i tried yours aniket and I will post the rom soon
Gonna give this a try
Sent from my GT-S5360 using Tapatalk 2
Hello XDA members, in this guide, i'll give you the easiest way to porting rom for your device, i've broken my porting record by ported 5 roms in less than 1 hour using this method, have enjoy and hope it'll works for you too
What you need ?
- Rom base (CM or AOSP)
- Rom port (any roms that you like to port)
- Apktool (for compiling .apk and .jar files)
- Note++ (for editing .txt and .xml files)
- Winrar or 7zip (for extracting and repacking rom)
- dsixda's Android Kitchen, you really need this to Port MIUI, PAC, and Slimrom
- Open mind and never give up to trying
Rules
1. Find the rom port with similar CPU like your device, clock speed doesn't matter here, the important is the number of CPU Cores, if your device is single core, find the single core rom, dual-core with dual-core, etc
2. Forget about screen sizes(4, 5, or 7 inci), the important is screen DPI(pixels destiny) you can port rom from tablet or devices that have bigger/smaller screen sizes
example
> LDPI & LDPI
> MDPI & MDPI
> HDPI & HDPI
> xHDPI & xHDPI
> etc
3. Same Android SDK version(Check in build.prop)
Example, you can port Android 4.4.3 using Android 4.4.2
4. GSM and GSM, CDMA and CDMA
Step by step
Extract booth of the roms(rom base and rom port)
> In rom port folder <
1. Delete all files and folders except "system" folder
{
"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"
}
2. Delete these folders and files in system
> tts
> usr
> vendor
> build.prop
3. Delete these folders in system/etc
> Bluetooth
> Firmware (if exist)
> Wifi
4. Delete these folders in system/lib
> hw
> modules
5. Go to system/framework
> Open framework-res.apk
> Go to res/xml
> Replace storage-list.xml with your rom base
> In rom base folder <
1. Copy all files and folders except "system" to rom port folder
2. Copy these folders and files in system folder to rom port system folder
> tts
> usr
> vendor
> build.prop
3. Copy these folders in system/etc to rom port system/etc
> Bluetooth
> Firmware (if exist)
> Wifi
4. Copy these folders in system/lib to rom port system/lib
> hw
> modules
Repack the rom then flash it in the recovery
Now the rom port should booted(to menu) now, not stuck on bootanimation anymore
if you still stuck on bootanimation, check bootclasspath in boot.img, unpack it, and check in "init.environ.rc", use note++ to edit it, there's must be something miss there
If the rom doesn't boot to menu or stuck on manufacturer logo(LG, Sony, Samsung, etc), find the same rom port from other devices. I've this experience while porting Liquid Smooth, then i used other devices and it's booted
Notes :
If you successful ported the rom, please do these before your releasing your ROM
> Ask the permission from the developers of the rom base and rom port
> Give credit for them
> And give credit for me too if you using this guide
> And don't forget to hit THANKS button
For porting MIUI Kitkat, you need to unpack boot.img from both roms, then do these
- Copy paste init.miui.rc from rom port to rom base ramdisk folder
- Open init.rc from both roms, then compare it, there's some line you need to be edited...
Troubleshooting
Now, to fix some issues in rom port, do these...
1. Information about rom
Open build.prop from booth of the rom then edit information just like the rom port
You can edit these lines in build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.display.id=
ro.build.date=
ro.build.user=
ro.build.host=
ro.product.name=
ro.product.locale.language=
ro.product.locale.region=
ro.cm.device=
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.root_access=
ro.modversion= > replace with rom port
ro.cm.version= > you can delete this
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.sf.lcd_density=
and the other lines relating information about rom
2. RIL
Replace these files in rom port with your rom base files
system/bin/rild
system/lib/libreference-ril.so
system/lib/libril.so
system/lib/librilutils.so
system/lib/libsec-ril.so
system/lib/libsecril-client.so
And add any files with "ril" in the name of file
3. Sensor
Replace these files in rom port with your rom base files
system/bin/sensord
system/bin/sensorservice
system/lib/libsensorservice.so
system/lib/libhardware.so
system/lib/libhardware_legacy.so
4. WiFi
Replace these files in rom port with your rom base files
system/bin/wifimac
system/bin/wpa_cli
system/bin/wpa_supplicant
system/lib/libwpa_client.so
5. Missing files
You have to copy the rest of files in base rom to port rom to make rom better, but don't replace it if the files/folders was exist
6. Files can be replace in your ported rom using files from base rom
Bin
>adb
>dalvikvm
>debuggerd
>dhcpcd
>dnsmasq
>drmserver
>gdbserver
>glgps
>hostapd
>hostapd_cli
>ime
>ip
>ip6tables
>iptables
>logcat
>logwrapper
>media
>mediaserver
>mtpd
>ndc
>netcfg
>netd
>ntfs-3g
>ping
>ping6
>pppd
>radiooptions
>rild
>screenshot
>sdcard
>sensord
>sensorservice
>service
>servicemanager
>toolbox
>vdc
>vold
>wifimac
>wpa_cli
>wpa_supplicant
Lib
>lge-ril.so (for LG devices)
>libbluetooth_jni.so
>libbt-hci.so
>libbt-utils.so
>libhardware.so
>libhardware_legacy.so
>liblgehdmi.so
>libnfc.so
>libnfc_jni.so
>libnfc_ndef.so
>libreference-ril.so
>libril.so
>librilutils.so
>libsensorservice.so
>libwpa_client.so
>
>
7. Video streaming
> libstagefright.so
and all libs with "libstagefright" of the lib's name
Rom that can be ported
What roms can be ported using this guide ?
This guide should can port any costum roms base on AOSP or CM, not manufacturer roms, not yet...
My experience, I've ported these roms
Mokee Open Source Project
Carbon Rom
Paranoid Android
Xperience
SDK NX v1
AOKP
Hellfire
Codename Lungo
AOSB Project
OMNI Rom
SlimKat
PAC man
SOKP
AICP
MIUI V5 Kitkat
Rom ported by XDA Members using this guide
- Liquid Smooth
Bonus :
Need Aroma Installer on your rom ?
please go to this thread
If this guide helping you, please do these
> Donate to me
> Hit my THANKS button
> Rate the thread
> Poll the thread
> Hit "Tip us" ? to make this thread on portal, so many people will know it the easiest way to porting any costum rom
> Mention me (@Nasheich Xfiles) at your rom thread
> Keep this thread at first page with your posting
> Like this thread at Facebook, Google+ and Twitter
Best Regards
Nasheich
Credits
> Nasheich Xfiles : it's me
>ZduneX25
Very nice bro :good::good::good:
Thanks for this Awesome Guide
Will Try and let u know
Great guide.. is there a way we can get Tmobile Z1S stock rom (with wifi calling) to Z ultra? I am ready to do it myself with some guidance.
Great guide, ported a hellkat rom with it
Thanks for the guide but it's more interesting to port KitKat (4.4.x) to Jelly Bean (4.3.x), like Xperia ZR 4.4 ROM to Xperia SP with only 4.3 available. It's Qualcomm, many things possible with it. Any ideas?
D-SHEL said:
Thanks for the guide but it's more interesting to port KitKat (4.4.x) to Jelly Bean (4.3.x), like Xperia ZR 4.4 ROM to Xperia SP with only 4.3 available. It's Qualcomm, many things possible with it. Any ideas?
Click to expand...
Click to collapse
No You can't
Try using AOSP binaries (4.4) to port ZR 4.4 Rom
Sent from a Beast :')
---------- Post added at 04:57 AM ---------- Previous post was at 04:54 AM ----------
Rules
1. Find the rom port with similar CPU like your device, clock speed doesn't matter here, the important is the number of CPU Cores, if your device is single core, find the single core rom, dual-core with dual-core, etc
2. Forget about screen sizes(4, 5, or 7 inci), the important is screen DPI(pixels destiny) you can port rom from tablet or devices that have bigger/smaller screen sizes
example
> LDPI & LDPI
> MDPI & MDPI
> HDPI & HDPI
> xHDPI & xHDPI
> etc
In fact you can PORT Custom Roms from an HDPI Device to MDPI Device if they shares the same CPU core
Sent from a Beast :')
Can I port 4.4.2 lg optimus l9 ii using 4.4.3 pure aosp.
Sent from my Xperia S using xda premium
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
pepitoff said:
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
Click to expand...
Click to collapse
Haish, AOSP is smoother than CM11 because it's not modified (Pure android).
Btw, you can't get anything diffirent if you rebased overlay to CM11
MT27i said:
Haish, AOSP is smoother than CM11 because it's not modified (Pure android).
Btw, you can't get anything diffirent if you rebased overlay to CM11
Click to expand...
Click to collapse
OK. But is it possible to port XperiaOverlay to CM11 LX with this guide?
pepitoff said:
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
Click to expand...
Click to collapse
It's Kinda Possible !!
But Chances are 40-45%
Since XO uses AOSP binaries
Sangeet007 said:
Thanks for this Awesome Guide
Will Try and let u know
Click to expand...
Click to collapse
Yes, let me know, I'll do my best to help you
royalva said:
Great guide.. is there a way we can get Tmobile Z1S stock rom (with wifi calling) to Z ultra? I am ready to do it myself with some guidance.
Click to expand...
Click to collapse
just try it, and let me kbow
Aaskereija said:
Great guide, ported a hellkat rom with it
Click to expand...
Click to collapse
Nice
D-SHEL said:
Thanks for the guide but it's more interesting to port KitKat (4.4.x) to Jelly Bean (4.3.x), like Xperia ZR 4.4 ROM to Xperia SP with only 4.3 available. It's Qualcomm, many things possible with it. Any ideas?
Click to expand...
Click to collapse
no, you can't, different files system between JB and KK
Black_Eyes said:
In fact you can PORT Custom Roms from an HDPI Device to MDPI Device if they shares the same CPU core
Sent from a Beast :')
Click to expand...
Click to collapse
Yes, you can port lower LCD destiny and Lower CPU too, i just make a simple explanation
nisu4717 said:
Can I port 4.4.2 lg optimus l9 ii using 4.4.3 pure aosp.
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
yes, you can, I've ported many rom base on AOSP, and you can ported 4.4.2 using 4.4.3, cause it has same Android SDK version (check on build.prop)
pepitoff said:
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
Click to expand...
Click to collapse
Yes, there's always possibility to port any rom, cause the fact is 80% of Android files is same ..
Sorry if this sounds idiotic, but can I port SOKP from nexus 5 to xperia z1 using this method since they share the same chipset?
allinkiran said:
Sorry if this sounds idiotic, but can I port SOKP from nexus 5 to xperia z1 using this method since they share the same chipset?
Click to expand...
Click to collapse
yes, you can, if the specification of the hardware just like what I've wrote, not just the same chipset, but RAM too
Thank you. Would try tomorrow since nexus has son many roms that I want to try on my z1
hey guys,
im trying to port a rom for Lenovo a1000 t I found this rom for a device called lava iris(with similar MTK 6577 chipset) which is a lollipop themed rom.
need some assistance in editing the build prop.
Since you are porting from a lower processor to a higher , you'll have to edit the build.prop a lot.
revolutionyzer said:
Since you are porting from a lower processor to a higher , you'll have to edit the build.prop a lot.
Click to expand...
Click to collapse
like, I edited the permissions section in the updater-script, I also made some changes in build-prop.
when I flashed it, it got flashed but it was stuck in a boot loop...
Check these :
vnktdpl said:
like, I edited the permissions section in the updater-script, I also made some changes in build-prop.
when I flashed it, it got flashed but it was stuck in a boot loop...
Click to expand...
Click to collapse
* The dpi ( if its more or less than your device's dpi , the ROM won't boot).
* Re-check if you have edited the systemui.apk or the framework.apk such that the values don't match.
* Check if the port has ' update-script ' or ' updater-script '. many new recoveries now don't support the amend format.
* Confirm that the updater-script values are not obsolete.
* Make sure you have an updated recovery.
Good Luck
Launcher
Hello Guys I Am Trying To Port sk17i's Laucher In My S duos 2 ......i am not able to do so.
Can anyone help me on how to port launchers of sony to samsung devices......please reply???:crying:
revolutionyzer said:
* The dpi ( if its more or less than your device's dpi , the ROM won't boot).
* Re-check if you have edited the systemui.apk or the framework.apk such that the values don't match.
* Check if the port has ' update-script ' or ' updater-script '. many new recoveries now don't support the amend format.
* Confirm that the updater-script values are not obsolete.
* Make sure you have an updated recovery.
Good Luck
Click to expand...
Click to collapse
Will check all the values by this weekend
Has it got anything to do with the build fingerprint??
Thanks for ur help