• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE]How To Port ROMS to Your Device [AOSP]

Search This thread

Tanuj97

Senior Member
Jun 7, 2014
574
663
Mumbai
well i am tying to port euphoria rom for htc one x from lg p880 ...i downloaded the zip files and unziped it
but in the system folder there is only boot.img and no other file all the system is compressed in a system.new.dat file how should i port now ??pls help
Thank you
 

TechGeekD

Senior Member
Nov 6, 2013
84
70
Navsari
well i am tying to port euphoria rom for htc one x from lg p880 ...i downloaded the zip files and unziped it
but in the system folder there is only boot.img and no other file all the system is compressed in a system.new.dat file how should i port now ??pls help
Thank you

1)All you gone need is SystemExtractor

2)Which will extract .DAT file and you will get system files extracted

3)then just use this extracted system along with boot.img to build your ROM

4)and ya you will gone need new updater_script as updater_script within euphoria Is lollipop version updater_script

5)so to flash ROM with extracted system as we use to do before lollipop version you will need new updater_script,extracted system.new.dat & boot.img !

6)you can use android script creator for getting new updater_script ! ;)
 

Tanuj97

Senior Member
Jun 7, 2014
574
663
Mumbai
1)All you gone need is SystemExtractor

2)Which will extract .DAT file and you will get system files extracted

3)then just use this extracted system along with boot.img to build your ROM

4)and ya you will gone need new updater_script as updater_script within euphoria Is lollipop version updater_script

5)so to flash ROM with extracted system as we use to do before lollipop version you will need new updater_script,extracted system.new.dat & boot.img !

6)you can use android script creator for getting new updater_script ! ;)
i dont think i am going to need new updater_script coz i am using cm12.1 as my base rom which is too lollipop
And thanks for your help
i could use android kitchen to port roms too . Just got to know now :p
 

TechGeekD

Senior Member
Nov 6, 2013
84
70
Navsari
i dont think i am going to need new updater_script coz i am using cm12.1 as my base rom which is too lollipop
And thanks for your help
i could use android kitchen to port roms too . Just got to know now :p

Actually you're gone need new updater_script if you only extract .DAT file and just use it as kitkat way with extracted system folder,boot.img

But if you extract the .DAT file and modify the system folder and repack it back as .DAT file then you're not gone need new updater_script
 
  • Like
Reactions: ArjunrambZ

Tanuj97

Senior Member
Jun 7, 2014
574
663
Mumbai
Actually you're gone need new updater_script if you only extract .DAT file and just use it as kitkat way with extracted system folder,boot.img

But if you extract the .DAT file and modify the system folder and repack it back as .DAT file then you're not gone need new updater_script

pls suggest me a system extractor that can extract and compress .dat file
 

theonlykamph

Senior Member
Sep 14, 2014
310
112
Okay i have now tryed to port a rom from meizu mx4 pro to lg g3.
When i flash my rom i get:
set_perm: some changes failed
E: Error executing updater binary in zip '/sdcard/Download/flymeos.zip

Please help!

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

Sorry for the late as I was busy for few days, your answer is in Q&A section of this thread !

Mate can you help me please? :)
 

m0nt3s

Senior Member
Oct 14, 2015
100
70
The TwEEzY
Your guides have been helpful

Thank you for taking the time to make this quick and dirty guide for us. I've read numerous tutorials but my problem is that I'm trying to port MT6735 12.1 from MT67355.1 but there are a couple of differences from your kit kat guides like priv-apps which I assumed I would port over since i'm already porting over the apps folder. I can get the rom to boot all the way up until the "Android is optimizing screen" and then it just stays there forever. If I restart my device then it boot loops, how would you trouble shoot my problem? thank you for your help
 

mF^

Member
Jul 16, 2014
19
7
Need Help from Experts

hey m newbie here guys..! What i want to say that i want to port touchwiz rom to my redmi 2 ! can anyone help me how can i ?
which base rom ? and which Port rom should i take ? please help :) sry bad English
 

primski

Senior Member
Jul 10, 2012
172
10
Milky Way
explain a noob please,

so if you want to compile a new aosp rom from the repo for your device, say a new phone, do drivers matter? like on pc? or is that not an issue ? what else is an issue? locked/unlocked bootloader? most of phones have locked bootloaders, right? so how does one unlock it?

i'm looking at these cheap chinese phones in the 150-200€ range. they look good on paper, octa core MTK, 3gb ram and such but software is usualy crap and there aren't many rom ports. i've read a few porting tutorials, like for CM and it doesn't include any driver reverse engineering heh, so that's good i think.
 

yaro30383

New member
Jul 20, 2016
1
0
No folders in /system

My port rom (the latest cm13 snapshot for the google nexus 10) does not have folders in /system, it only has the build.prop file. How do I port this rom? (My base rom is cm9.1 stable for Asus tf101),
 

Rio Montella

Senior Member
Jun 29, 2014
74
20
I get these problem, here it is the logcat. Can you help me to fix the error?:eek:
 

Attachments

  • Error.txt
    2 KB · Views: 14

rahulsinh

Member
Jan 10, 2015
20
2
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! :cowboy::cowboy::cowboy:
:laugh:

.can i use this method for my gionee f103?
I don't have init.rc and permissions folder in system folder. I have port rom of meizu m2 which has same processor and almost all specification same. Please help me.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 83
    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:

    And lastly Before you a port a ROM, make sure you asked permission from the Developer!

    What you'll need:
    1. WinRAR/7zip
    2. Notepad++ (When developing, always use this)
    3. Android SDK (For Logcatting & DDMS)
      Some basic knowledge about Android
      If you are on Linux/Unix/BSD use your favorite Archiving Tool & Text Editor.



    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

    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

    STEP1;

    Take any clean CM9, AOSP, CM7, CM10 ROM which is running on your device as Base ROM

    STEP2:

    Extract it Using Winrar.
    image.jpg

    STEP3:

    Take the ROM you want to port. This Port ROM. Extract it also using Winrar.


    STEP4:

    Delete app, Framework, Fonts and Media folder in System Folder of Base ROM.
    image.jpg



    STEP5:

    Now copy app, Framework, Fonts and Media folder in System Folder from Port rom to base rom system folder.
    image.jpg



    STEP6:

    Now open etc folder in both the ROMs folder.


    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
    image.jpg

    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.
    image.jpg

    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=
    image.jpg


    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=
    image.jpg

    Also Copy anything you Find Extra in ADDITIONAL BUILD PROPERTIES related to theme..


    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.
    image.jpg


    STEP12:

    If You find any extra file or folder in system folder of PORT rom than copy them to your base rom system folder.

    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..

    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


    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

    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

    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

    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


    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


    Credits & Thanks to

    # rishabh.raj37
    # Peteragent5



    Happy porting! :cowboy::cowboy::cowboy:
    :laugh:
    5
    reserved

    for clarification
    3
    This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
    not really ,,i have tried porting with this and it worked succefullyy

    :laugh:
    may be you have to try it perfectly
    2
    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
    2
    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
    have you tried this methode,,iam sure it will work,,:laugh::laugh: