[GUIDE] How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs [Update: Sept.25.2012]
- Thread starter Peteragent5
- Start date
That happns only due to errors in copying not due to size of the rom.....
Sent from my GT-I5500 using Tapatalk 2
Hey, I managed to port JoyOS ROM from Samsung Nexus S to Samsung Galaxy S by using CM7.1 stable with your guide mate. But I'm expecting an issue: android.process.acore FCs repeatedly and the phone is like unusable. Do you know a way to fix it? Thanks man
I already tried deodexing and zipaligning the ROM but no luck
Here is the logcat: http://pastebin.com/nwp4fJVr
.
ok im trying to port AOKP build 35 but when i go to install in with CWM i get:
do you know of any fixes? and there isnt an error number given out o.0
Code:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Check the structure of your update.zip you should see two folders, meta-inf & system, iirc.
Sent from my R800x using XDA Premium App
jmz
Inactive Recognized Developer
no you are completely wrong. No recovery will tell you its out of space. You will have no indications of device out of space till you look at the recovery.log.
Is it possible to port rom from dual core to monocore phone ? Curious.
Sent from my LG-P970 using xda premium
SAME CPU!!! man you think that a dual core its the same cpu of monocore???
so very useful guide !!!, i just tried to port a galaxy s rom to the desire hd... but int the galaxy s rom there is no boot.img to extract the kernel.... so what should i do?? the roms are: PORTED:galaxy s simplicyti 2.2.1
BASE: CM7.2 rc1
it has to be either structure of your zip rom or your updater script
Flashing Problem
i followed all of the instructions and went to flash my final base zip and it would not work, do i need to rezip the files and sign it w/something like androidZip? Or was i supposed to do all of this on my phone???
i followed all of the instructions and went to flash my final base zip and it would not work, do i need to rezip the files and sign it w/something like androidZip? Or was i supposed to do all of this on my phone???
I have a kyros 7022 with CM7. The camera only works with stock rom, if I do this procedure, do you think it might make the camera work on cm7?
Sent from my T-Mobile G2 using Tapatalk
Sent from my T-Mobile G2 using Tapatalk
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
462Code:
/* * ~ Please READ ME ~ * * I do not guarantee any successful porting. I am not responsible * for bricked devices, dead SD cards, or a broken device. [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. But I will try * my best to explain all the necessities, so you won't mess up your Device. * * ~ END OF AGREEMENT ~ */
Before we start, let's read the Title of this Guide. Notice it says: based
This means, if you do not have a GB/ICS/JB already compiled for your device, then this Guide is useless for you.
Android Source | Compile GB | Compile ICS | Compile JB ~ Thanks dastin1015 |- Building/Compiling - Durations
Before you a port a ROM, make sure you asked permission from the Developer!
This Guide applies the same principle for porting the following: Sense, Lewa OS, JoyOs, MIUI, LiGux OS, etc...
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.
Notes:- I will be referring to the following:
- BASE = The GB/ICS/JB ROM made for your Device only.
- PORTED = The ROM you are trying to port from.
- BASE and PORTED must be the same CPU. e.g. ARMv7, ARMv6, ARMv5
- You must have the same settings in Notepad++ like mine.
- Ignore the procedure, if the file or folder is not present!
- BASE & PORTED should be the same Android version.
- If you are porting a custom GB ROM, then use a GB BASE, the same goes for ICS and JB
- Make sure both BASE & PORTED are deodexed (It's hard to port an odexed ROM)
- Final ROM is inside PORTED Folder
(Don't get confused! This is a Major change from the previous Guide because this method is a lot faster and easier)
Inside PORTED:
Remove kernel:
- boot.img | zImage | kernel.sin | etc...
Remove the following inside /system:
- cameradata
- tts
- usr
- vendor
- firmware
- modules
- wifi
Now you get 2 options:Remove every folder inside /system/etc except:
- Delete bin & xbin & lib folder, but keep libandroid_runtime.so inside /system/lib
- Keep bin & xbin & lib folder
- If PORTED has no tweaks or addons to those folders.
- If PORTED has tweaks and addons.
- init.d
- permissions
- license
Remove the following inside META-INF:
- CERT.RSA
- CERT.SF
- MANIFEST.MF
Remove: META-INF/com/google/android/update-binary
Inside BASE:
Move kernel to PORTED:
- boot.img | zImage | kernel.sin | etc...
Delete libandroid_runtime.so inside /system/lib
Move the following inside /system to PORTED:
(If prompted, select YES to copy and Replace all)
- cameradata
- bin
- lib
- tts
- usr
- vendor
- firmware
- modules
- wifi
- xbin
Move everything inside /system/etc
To: PORTED's /system/etc
(If prompted, select YES to copy and Replace all)
Move: META-INF/com/google/android/update-binary
To: PORTED's META-INF/com/google/android/
For ICS & Newer:
Move the following inside /system/media to PORTED's media:
- LMprec_508.emd
- PFFprec_600.emd
build.prop
Inside PORTED:Open /system/build.prop
Copy & Replace the following:
- ro.modversion
- ro.cm.version
- ro.config.ringtone
- ro.config.notification_sound
- ro.config.alarm_alert
- ro.config.sms_received_sound
- ro.config.sms_delivered_sound
- persist.sys.themeId
- persist.sys.themePackageName
For MIUI:
Add & Make sure the following values are like this:
- ro.build.id=MIUI
- ro.build.display.id=MIUI x.x.x
- ro.build.version.incremental=x.x.x
- ro.config.ringtone=MI.ogg
For Lewa OS:
Add & Make sure the following values are like this:
- ro.build.display.id=LeWa_ROM_DeviceNickname_xx.xx.xx
- ro.lewa.version=LeWa_ROM_DeviceNickname_xx.xx.xx
- ro.lewa.device=DeviceNickname
- ro.lewa.swapper.part_path=PORTED's_Value
- ro.lewa.swapper.flash_swappiness=PORTED's_Value
- ro.lewa.swapper.sd_swappiness=PORTED's_Value
- ro.error.receiver.system.apps=com.lewa.fc
- ro.error.receiver.default=com.lewa.fc
Make sure the following is for your Device:
- rild.libpath=
- rild.libargs=
Inside BASE:Open /system/build.prop
Highlight from: ro.build.tags=
to: # ADDITIONAL_BUILD_PROPERTIES
Shown in this picture
Copy & Replace that highlighted part to: PORTED's build.prop's highlighted part
Copy everything from: # ADDITIONAL_BUILD_PROPERTIES
To: the end of the file
Paste it to PORTED's build.prop
Shown in this picture
For XPERIA devices:The whole build.prop is untidy and filled with tweaks and addons.
To edit an XPERIA build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do
For HTC devices (Sense):The whole build.prop is filled with tweaks, addons and extra libs values.
To edit an HTC build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do
updater-script
Inside BASE:Move the following, to PORTED:
(If prompted, select YES to copy and Replace all)
- META-INF/com/google/android/update-binary
- META-INF/com/android/metadata
- META-INF/com/android/otacert
Open: META-INF/com/google/android/updater-script
Replace the following values, to PORTED:
- mount("xxxxxx");
- format("xxxxxx");
- retouch_binary
- The installation of the kernel (Something like: assert(package_extract_file("boot.img",)
- Take note of the added set_perms & set_perm_recursives that PORTED added. Then replace all set_perm and set_perm_recursive from BASE to PORTED. Put back in the noted set_perms & set_perm_recursive you wrote down, to PORTED's updater-script
For ICS & Newer itself:- If the updater-script in PORTED is modded to have tweaks & addons do the set_perms procedure above
- Now use BASE's entire META-INF Folder. Copy it to PORTED
For MIUI v4:Add the following values to PORTED:
- set_perm(0, 0, 06755, "/system/xbin/invoke-as");
- set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
For AROMA Installer:It's actually too hard & time consuming to explain on how to make the script work on your Device when it came from another.
So it's best to use BASE's META-INF folder, rather than try to make the AROMA Installer work on your Device. (Becuase it will be time consuming)
Porting from a different Manufacturer
If you are porting from a different manufacturer like, HTC or Sony, you have to check the kernel from them.
- Unpack the kernel from PORTED
- Unpack your Device's kernel
- Open PORTED's init.rc
- Replace the BOOTCLASSPATH from PORTED's init.rc to BASE's init.rc
- Compare the two files, and addon to your Kernel's init.rc
- Packup/Repack your Kernel
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
Logging & DDMS
This is very important if your a developer in the Android world. These tools help you debug your device to search for errors or see which processes are running.
Tutorial - How to Logcat
Tutorial from Android
If you want me to help you, don't give me a Logcat from ADB. Instead, give me a screenshot of your DDMS.
Review
- Make sure you did everything inside PORTED first, then work your way up/down to BASE.
- Did you replace Kernel?
- Is libandroid_runtime.so from PORTED?
- Did you edit the updater-script, format & mount values?
- Make sure dalvik.vm.heapsize is BASE's value inside build.prop
- Make sure build.prop is mostly for your Device
- If the Port doesn't boot, try using your own META-INF folder. But backup the previous
Sources
Credits & Thanks to
- proxuser
- nims11
- dhk.-
- Lens_flare
- SpaceCaker
- fundoozzz
- Delanoister
- TeamCooper
Happy porting! :laugh:90Frequently Asked Questions
Q: How do you port a higher CPU ROM to my lower CPU device?
A: P.M me or any big-name developers. You must already know what to do. The person you P.M will give you extra info...
Q: Is it possible to port a lower CPU ROM to my higher CPU device?
A: I think it'll work (But why would you do this). If it doesn't boot try changing the DPI values in the build.prop
Q: How do I make a bigger DPI ROM work on my smaller DPI device?
A: Resize all PNGs in every app & framework-res using Android Resizer Tool
Q: Can I Port a smaller DPI device to my device?
A: Yes. It probably won't run & it wouldn't look good if you did. The icons would be small or if you resized it, the icons would be blurry.9Updated the Guide! GO READ! It looks better when I was editing it... :S
LOL :laugh:7
You can port any Rom as long as it's based on CM7/GB/Stock Rom, the same CPU (Armv6, Armv7, Armv5) as your BASE, and it's best to port a Rom from the same manufacturer, if not, you can still do it, just change BOOTCLASSPATH
If there is no data then it's fine to not include it
Lol. No not yetPeteragent5 your arm7 port rom problem solve from this way?
6
