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

Recreation of CM 7 RC 4 (Allmost all Bugs Fixed)

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

[GUIDE]Porting any Custom ROMs[Mokee, AOSPA, PAC, MIUI, etc]

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

MiPatcher: A MIUI forking utility

No more free rides

Donor is Port Rom?

Black_Eyes said:
Donor is Port Rom?
Click to expand...
Click to collapse
Yes

Tqr said:
{
"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"
}
Introduction
Runs on Windows & Linux with WINE
MiPatcher is designed to append MIUI to any CM base that shares the same 'Build.id'. This can be found in build.prop.
At the same time this will also serve as a technical guide for folks just starting out with porting MIUI in the 4.4 era, those doing this by hand or others who are just returning to the game.
MiPatcher is not a substitute for PatchROM and is not the same in function by any means although it can use Patch components on the most basic level.
This is geared more toward people who are trying to build a functional MIUI for neglected devices and also for people testing various bases who may not yet be configured to build from source to accommodate some of MIUIs functionality.
MiPatcher is as of right now very straight-forward; you pick the resolution for the device you are porting for and it will adjust the Donor MIUI to 'look right' on your device.
Requirements
- Autohotkey (Only if you intend to run the source for this)
- CyanogenMod 11
*Disabled SELinux
*Boot.img edits (for full functionality if not using PatchROM)
*Modified seapp_contexts (At Kernel level for use with PatchROM, at source level for manual porting/using this tool)
**Stock CM with init.d support may also be used; although it will be sloppy.
- MIUI donor firmware with the same 'Build.id' found in /system/build.prop
- PatchROM resources (If your Donor is a different resolution, you do not 'need' them unless things look terrible)
*Or get PatchROM resources here if you intend to grab for every resolution; it's half the size of the one on Github better compression
- WinRAR or 7zip
Features
- Automatically append MIUI to any same code-base firmware.
- Append init.d on supported devices to force boot without changes to the kernel
Prep-work
Only three files must be edited for test-ports, which I'll cover now.
Framework-res.apk
Open your Base and donor Framework-res.apk, navigate to res/xml and import the following XMLs:
Code:
Storage List
Power Profile
Build.prop
Code:
ro.build.version.incremental=x.xx.xx
persist.sys.root_access=0
ro.config.notification_sound=xxx.ogg
ro.config.alarm_alert=xxx.ogg
ro.config.ringtone=xxx.ogg
ro.skia.use_data_fonts=1
ro.miui.ui.version.code=3
ro.miui.ui.version.name=V5
qemu.hw.mainkeys=0 **[U] If you have no physical HW keys.[/U]
Updater-Script
Code:
set_perm(0, 0, 06755, "/system/xbin/lbesec"); ***If LBEsec exists in your donor
set_perm(0, 1000, 06750, "/system/xbin/shelld");
set_perm(0, 0, 06755, "/system/xbin/su");
With these most basic edits, MIUI will boot but with the need to install MIUI Lite to fix themes partially; as native ThemeManager, updater and backup will FC continuously.
Planning to use PatchROM? If you have an unlocked BL device or a device that will accept an unsigned kernel you can split your boot.img's ramdisk and add the following entries to 'seapp_contexts' immediately under user=shell, like this :
user=shell domain=shell type=shell_data_file
Code:
user=theme seinfo=platform domain=platform_app type=platform_app_data_file
user=backup seinfo=platform domain=platform_app type=platform_app_data_file
user=updater seinfo=platform domain=platform_app type=platform_app_data_file
And above anything else that may follow user=shell.
If you are not planning on using PatchROM, you will have to disable SELinux fully and edit your 'seapp_contexts' in source. In CyanogenMod11 source it is located in the following directory:
Code:
external/sepolicy/seapp_contexts
Now it's time to kill SELinux, navigate to your Kernels config folder in source; generally found at:
Code:
kernel/brand name/kernelname-common/arch/arm/configs
and find 'kernelname_defconfig' or 'kernelname_selinux_defconfig', change the following value to 'n':
Code:
CONFIG_SECURITY_SELINUX=[B]n[/B]
This will yield a functional CyanogenMod11 that can be used with PatchROM without issue, and can also be used to just fork firmware which is useful in the case of unified device builds, which Patch does not really like so much.
Now that you've built your base the following edits must be made to the kernel's Ramdisk:
Init.rc
Add this line at the very end of init.rc
Code:
import /init.miui.rc
init.miui.rc
Create this file in the root of your ramdisk and place the following inside:
Code:
#service for shelld
service shelld /system/xbin/shelld
class main
#service for su
service su_daemon /system/xbin/su --daemon
class main
oneshot
service lbesec /system/xbin/lbesec
class main
oneshot
init.superuser.rc
Code:
Delete this file
init.cm.rc
Add a '#' to the following line to disable the calling of init.superuser.rc
Code:
[B]#[/B]import /init.superuser.rc
Default.prop
Change the following values:
Code:
ro.adb.secure=[B]0[/B]
ro.secure=[B]0[/B]
ro.allow.mock.location=[B]1[/B]
Once these edits have been made your base can now be adapted to MIUI.
MiPatcher Instructions
1. Extract the contents of baserom.zip to 'base'
2. Extract the contents of miuidonor.zip to 'donor'
3. Inside of the PatchROM resources zip, extract 'HDPI' 'xHDPI' and 'xxHDPI' into the 'PatchROM' folder
4. Run MiPatcher, select your resolution and if you haven't made any kernel editing or done special source building, use soft-mods.
5. Zip the contents of 'Base' and flash it.
6. If this yields a non-booting build your codebase is too distant from your donor, find another same Build.ID release and try again if not proficient with ADB.
Current version:0.01
0.01: First release, Basic functionality and enough to produce one-shot ports when the base is properly prepared.
0.01: x64 x86 stand-alone .exe
Next Version:0.02
0.02: Clean up redundant/inefficient code.
0.02: Add options for boot.img, build.prop, meta-inf backup and loading.
*to avoid having to edit or manually move these with each attempt on base.
Download
9/28/2014: MiPatcher x86&x64
This is stand-alone and requires nothing to run, PatchROM parts are optional but suggested nonetheless.
Source
To use this source as an executable 'program' you must download and install Autohotkey, after right-click on your desktop to create a new '.ahk' file, paste the contents of this inside of it and save.
Create the following folders in the same folder as your .ahk file, the folder structure should mimic the following in terms of layout with extracting things:
-base
*META-INF
*System
*Boot.img
-donor
*META-INF
*System
*Boot.img
-mod create two notepad++ files with no extension, name them the following and place the respective content inside:
*00lbesec
Code:
#!/system/bin/sh
/system/xbin/lbesec &
*00shelld
Code:
#!/system/bin/sh
/system/xbin/shelld &
-patchrom
*HDPI
*xHDPI
*xxHDPI
AHK source:
http://paste.ee/p/balNM
FAQ
Q: My ROM isn't booting!
A: Try another MIUI that uses the same Build ID as yours, or use ADB to debug your build as it will be really close either way.
Q: Is there any difference between using a .ahk file and a .exe?
A: Yes. It's easier to update by pasting new code into a .ahk text file than to download packed .exe files in the longrun; however when using a .exe you don't need to install Autohotkey.
I will make standalone .exe for this at some point soon today.
Q: Theme/Updater/Backup is FCing!
A: It's a SELinux related error, sounds like you may be using PatchROM or a unified build; in this case build from source with the Seapp_context, and with SELinux turned off.
Q: Storage isn't mounting!/File Explorer is closing!
A: Import CyanogenMod11's 'StorageList' located in Framework-res.apk/res/xml into MIUI's along with the 'PowerProfile' to resolve unreadable storage
Q: [Insert name] App is crashing...
A: Debug using ADB or find another donor if you're feeling lazy, most of the time this yields perfect results but some things will maybe need a little polish depending on how far the codebase from the Donor and your Base firmware are.
Big TY to:
Code:
* Sijav
* Chevelle
* Yun
* All the Russian firmware developers, ahead of everyone else by a bit..
XDA:DevDB Information
MiPatcher: A MIUI forking utility, Tool/Utility for all devices (see above for details)
Contributors
Tqr
Version Information
Status: Testing
Stable Release Date: 2014-10-04
Beta Release Date: 2014-09-30
Created 2014-09-28
Last Updated 2014-09-28
Click to expand...
Click to collapse
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?

h2o64 said:
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?
Click to expand...
Click to collapse
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux

Tqr said:
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux
Click to expand...
Click to collapse
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?

h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Sure, I don't mind Q&A

h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64

Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I'll try from one plus one (4.4.4)
If we need to wait. I prefer waiting for Redmi 1S which have a configuration very near to Moto G's one.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
Tqr said:
Sure, I don't mind Q&A
Click to expand...
Click to collapse
Works perfectly fine on Ubuntu 14.04 64 bits (I've used x64 one).
I'll flash the zip file. Keep you updated.

Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I just made a post for the Moto X, sorry about that lol

Tqr said:
I just made a post for the Moto X, sorry about that lol
Click to expand...
Click to collapse
Which base did You use?
Help us to Boot it on Moto g

Black_Eyes said:
Which base did You use?
Help us to Boot it on Moto g
Click to expand...
Click to collapse
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it

Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Click to expand...
Click to collapse
Ok Thanks i will be waiting
---------- Post added at 08:06 PM ---------- Previous post was at 08:02 PM ----------
Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
That will be Great :good:

Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?

h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
He will Build for Us

Black_Eyes said:
He will Build for Us
Click to expand...
Click to collapse
I'm a dev. I want to try it myself and to learn how to do.
I've work a lot on it :'( :'( :'(

h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change

Tqr said:
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change
Click to expand...
Click to collapse
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?

h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
@h2o64 Yes
and i think that's why Rom doesn't boot with manually Porting
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
How can i disable SELinux without Building the Kernel ?

h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
No; you will still have Fingerprint errors

[GUIDE] PORTING 64BIT MTK ROMs (CROSS PORT Too)

Hi All,
This Guide is For Lenovo K3 Note Other devices can use it but some files may vary.
Here is a quick guide for getting the basics of the rom working.
Display, sound ,GSM (3g) and Wifi .
I used this for CyanogenMOD based ROMS and MIUI and it worked for me.
If anyone finds additional items or wants to complete this guide please feel free to add it in here.
Please remember, i am posting this so that people will try things and usually when they do, they end up finding something better and awesome than not trying.
I use this from stock and make it a zip file so it makes easy porting by just dragging the system folder with stock files to the rom to be ported and replace.
NOTE: ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else.
FOR CROSS PORT
SO THE FILES NEEDED TO REPLACE FROM STOCK TO PORT:
BIN FOLDER:
Code:
afm_server
akmd09911
applysig
audiocmdservice_atci
climax
custom_sn
encfs
factory
factory_reset.sh
fusermount
gzip_static
ipod
kpoc_charger
mtkbt
nvram_proximity
seeder
updater
vold
IF YOU THINK SOME FILES ARE ABSENT, DONT WORRY JUST SKIP THEM
NOW MODEM FILES:
Code:
take the whole [COLOR="Red"]firmware[/COLOR] folder from system/etc/
take the whole [COLOR="Red"]mddb[/COLOR] folder from system/etc/
NOW THE MAIN THING OF K3 Note (Audio)
Code:
take the whole folder [COLOR="Red"]tfa98xx[/COLOR] from system/etc/
NOW LIBS Folder:
Code:
lib3a.so
libacdk.so
libbluetoothdrv.so
libbluetooth_mtk.so
libbypass.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcamera_client_mtk.so
libcam_hwutils.so
libcam_platform.so
libcustom_nvram.so
libdpframework.so
libfeatureio.so
libfeatureiodrv.so
libhardware_legacy.so
libimageio.so
libimageio_plat_drv.so
libipod.so
libJpgDecPipe.so
libJpgEncPipe.so
liblocSDK5c.so
liblocSDK_2_5OEM.so
libm4u.so
libMA3-wavesfx-Coretex_A9.so
libmhalImageCodec.so
libMiraVision_jni.so
libmtkjpeg.so
libmtk_drvb.so
libnetworklocation.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libshowlogo.so
libtfa9897_interface.so
libvc1dec_sa.ca7.so
libvcodecdrv.so
libvcodec_oal.so
libvcodec_utility.so
libweibosdkcore.so
mtk-ril.so [COLOR="Red"]<= IF U GET BOOT LOOP TRY WITHOUT REPLACING THIS FILE[/COLOR]
mtk-rilmd2.so [COLOR="Red"]<= IF U GET BOOT LOOP TRY WITHOUT REPLACING THIS FILE[/COLOR]
And this subfolder with these libs:
Code:
drm\libfwdlockengine.so
egl\egl.cfg
egl\libGLES_mali.so
hw\audio.primary.mt6752.so
hw\audio_policy.default.so
hw\bluetooth.default.so
hw\camera.mt6752.so
hw\gps.default.so
hw\gralloc.mt6752.so
hw\hwcomposer.mt6752.so
hw\lenovopower.default.so
hw\lights.default.so
hw\sensors.mt6752.so
soundfx\libdownmix.so
soundfx\libmaxxeffect-cembedded.so
NOW LIB64 Folder:
Code:
lib3a.so
libacdk.so
libbluetoothdrv.so
libbluetooth_mtk.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadata.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.sensorlistener.so
libcam.utils.so
libcam1_utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcamera_client_mtk.so
libcamera_metadata.so
libcam_hwutils.so
libcam_mmp.so
libcam_platform.so
libcam_utils.so
libcustom_nvram.so
libdpframework.so
libfeatureio.so
libfeatureiodrv.so
libhardware_legacy.so
libimageio.so
libimageio_plat_drv.so
libJpgDecPipe.so
libJpgEncPipe.so
libm4u.so
libmhalImageCodec.so
libMiraVision_jni.so
libmtkjpeg.so
libmtk_drvb.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libtfa9897_interface.so
libvcodecdrv.so
libvcodec_utility.so
And this subfolder with these libs:
Code:
drm\libfwdlockengine.so
egl\libGLES_mali.so
hw\audio.primary.mt6752.so
hw\audio_policy.default.so
hw\camera.mt6752.so
hw\gps.default.so
hw\gralloc.mt6752.so
hw\hwcomposer.mt6752.so
hw\lenovopower.default.so
hw\lights.default.so
hw\mmsdk.default.so
hw\sensors.mt6752.so
soundfx\libdownmix.so
NOW VENDOR FOLDER:
Code:
system\vendor\etc\audio_effects.conf
system\vendor\etc\default.mps
FOR DIFFERENT CHIPSET (i.e. 6795 to 6752)
Proceed as above THEN
open build.prop
EDIT THESE LINES
Code:
ro.mediatek.platform=[COLOR="Red"]MT6795[/COLOR] to [COLOR="Red"]MT6752[/COLOR]
mediatek.wlan.chip=[COLOR="Red"]MT6630[/COLOR]to [COLOR="Red"]CONSYS_MT6752[/COLOR]
mediatek.wlan.module.postfix=[COLOR="Red"]_mt6630[/COLOR]to [COLOR="Red"]_consys_mt6752[/COLOR]
And Now Boot.img
Unpack both stock and port boots from CarlivImageKitchen Tool
{
"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"
}
Now
In port boot.img
replace the boot.img-kernel
and in ramdisk folder add these files:
fstab.mt6752
init.mt6752.rc
init.mt6752.usb.rc
AND DELETE THOSE with mt6795 and mt6595 words.
REPACK THE KERNEL
MAKE THE FLASHABLE ZIP
AND FLASH THE ROM
If u get WIFI AND BLUETOOTH NOT SWITCHING ON OR BATTERY PERCENTAGE WRONG THEN REPLACE init.project.rc
FOR SAME CHIPSET PORTING
Just replace
Code:
etc/firmware
etc/mddb
and from lib and lib64 hw folder replace all libs named like this camera.mt6752.so
and replace audio_policy.default.so from both hw folder
from lib and lib64
replace
Code:
libcameracustom.so
libaudiocomponentengine.so
libaudiocustparam.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libcustom_nvram.so
UPDATE :
TIP:To BOOT a rom with minimal replacements
Replace the boot.img files as usual
in system:
ETC FOLDER
etc/firmware
etc/mddb (not needed tho)
etc/tfa**(if your device uses)
LIB & LIB64
lib/libjni_pq.so
lib/libmtk_drvb.so
lib/libtfa****.so
lib64/libjni_pq.so
lib64/libmtk_drvb.so
lib64/libtfa****.so
HW folder
All the 67xx files if crossporting
VIOLA UR A PORTER

Can you add some image :3

Syaoran Lord said:
Can you add some image :3
Click to expand...
Click to collapse
i can add but image of what should i add

Porting to Ulefone be touch 2
Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance

Ufoner said:
Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance
Click to expand...
Click to collapse
yes it will work
no need to do anything about kernel u just proceed as the guide says

Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.

Ufoner said:
Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.
Click to expand...
Click to collapse
try taking logcat while pressing the vol down key

Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?

jordandroid64 said:
Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?
Click to expand...
Click to collapse
You need to delete file "recovery-from-boot.p" from system folder of your stock ROM and of port :good:
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
I ended again with black screen when porting cm12.1 from redmi note 2 Is it caused by another size of ram Because my device has 3gb ram and redmi note 2 has 2gb.

thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?

jordandroid64 said:
thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?
Click to expand...
Click to collapse
You need to extract system.img with ext4unpacker and then make it folder with ext2explore. You dont need recovery so delete it

I have already extract the img but with ext2explore only that will be good also?
thanks for your answer
edit: edit : on the port rom at the last when i search recovery that whow me that :
http://www.hostingpics.net/viewer.php?id=839697recovery.jpg

Help me with bootloop please
Hi sandeep.sethi!
Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop . I edited mount points and replaced all files as your guide says.
Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram All specs are same except the ram size.
Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?
Is this guide for same android version ex. 50.1 to 5.0.1?
Thanks in advance and have a good day

Ufoner said:
Hi sandeep.sethi!
Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop . I edited mount points and replaced all files as your guide says.
Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram All specs are same except the ram size.
Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?
Is this guide for same android version ex. 50.1 to 5.0.1?
Thanks in advance and have a good day
Click to expand...
Click to collapse
then try using his kernel in the boot.img with my roms' ramdisk

Thanks but i have problem
sandeep.sethi said:
then try using his kernel in the boot.img with my roms' ramdisk
Click to expand...
Click to collapse
Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.

Ufoner said:
Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.
Click to expand...
Click to collapse
what files did u replace from lib/hw and lib64/hw
or try taking cm12 of ur phone as base
Sent from my Lenovo K3 Note using Tapatalk

sandeep.sethi said:
what files did u replace from lib/hw and lib64/hw
or try taking cm12 of ur phone as base
Sent from my Lenovo K3 Note using Tapatalk
Click to expand...
Click to collapse
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files If you help me and rom will boot i will donate to you bro :good:

Help with porting
Hello! Thanks for this awesome tutorial!
But now i need some help with porting a ROM
I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!
when i install it with TWRP i get stuck in a bootloop
Can you please help me with this problem, i have followed the tutorial exactly as i should!¨
What should i do?
please help!
//AnStu00

AnStu00 said:
Hello! Thanks for this awesome tutorial!
But now i need some help with porting a ROM
I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!
when i install it with TWRP i get stuck in a bootloop
Can you please help me with this problem, i have followed the tutorial exactly as i should!¨
What should i do?
please help!
//AnStu00
Click to expand...
Click to collapse
I got bootloop too and sandeep.sethi told me how to fix it!
1. You need to change mount points in updater-script
2.Extract blisspop´s rom boot.img and extract boot.img from Elephone CM12.1 http://www.needrom.com/download/elephone-p7000-cyanogenmod-12-1/ and then copy blisspop rom ramdisk and copy it to cm12.1 boot.img and then repack it

Ufoner said:
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files If you help me and rom will boot i will donate to you bro :good:
Click to expand...
Click to collapse
okay try porting again and this tym in ramdisk replace factory rc files
Sent from my Lenovo K3 Note using Tapatalk