Need Help Porting Multirom

Hi all,
I'm going to port multirom on galaxy A5, but as you know, I have to patch the kernel before, with the "kexec hardboot" patch.
The problem is that there is to patch restart.c on mach-msm, but I havent got that file in my mach-msm folder, and when I try to add it to makefiles.... I get a lot of errors (I found that file on git google, so I don't know if it's for my device).
Please help me
Thanks in advance :)

Porting Recovery

Hello, i have a wiko darkmoon and i'm using twrp 2.8... want to flash rom+gapps with android 6, but it says that i don't have system space avaibable when i do.. I think that with twrp 3 i can flash them and gapps too ! The problem is that i try to port twrp 3 to my phone but my stock recovery misses some files that are on the porting guide... Can someone help me please ? Device: Wiko Darkmoon, mt6582
Thanks !

Porting a Custom Recovery to an Unsupported Device and Flashing

Hey XDA,

Finally took the leap and started doing a little developing. I have successfully setup Linux, a build environment, and compiled a custom CWM recovery for my device. I noticed some things along the way that made me very weary of actually flashing it.

Here is some of my output:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
CM_VERSION=10.1-20160720-UNOFFICIAL-q80
TARGET_PRODUCT=cm_q80
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-28-generic-x86_64-with-debian-stretch-sid
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39E
OUT_DIR=/home/lin/cm-10.1/out
============================================
Platform version = Android Version right? This is building for Kit-Kat so I cant use this on my device.? My Target_ARCH_Variant is armv7-a-neon is this okay to use with Krait?

Here is my target device specs:
MSM8974 Krait ARMv7
Android 6.0.1
ADB rooted, I’m having issue getting SU to work properly on the device.
Build Number says dev-keys at the end what does this mean?


I attempted to re-flash my clean stock recovery pulled from the device as a test run and can’t even get that to work. Since my build says dev-keys does that mean that the keys are located somewhere on the device so I can sign an update.zip that will flash through the stock recovery? AFAIK there is no ODIN-like tool or download mode I can get into. I have the flash_image binary on the device. When I run flash_image recovery /sdcard/recovery.img I get this message:
“Error scanning partitions: No such file or directory”

Are there any other options to flash my recovery.img? My recovery partition is located at mmcblk0p20. I have been out of the loop for a while now. Is CMW recovery dead these days? The guides I'm using are probably pretty old as well. Been having a lot of fun so far but I seem to have hit a wall. Any help would be appreciated.


Thanks!

Porting AOSP to OP2

Hi there,
I have recently been trying to learn and build custom ROMs for the OP2. I have successfully managed to build CM13 from source so I feel now is the time to face a bigger project.

I am attempting to port AOSP to the OP2 using the CM13 device tree found on github: https://github.com/CyanogenMod/andro...eplus_oneplus2 and the vendor files etc... I have repo sync'ed the AOSP source code into a directory and cloned the gits below into the directory as well:
https://github.com/HGT98/android_device_qcom_common
https://github.com/HGT98/android_dev...eplus_oneplus2
https://github.com/HGT98/proprietary_vendor_oneplus
https://github.com/HGT98/android_device_oppo_common
https://github.com/HGT98/android_kernel_oneplus_msm8994

The changes I have made so far to the device tree are as follows:

Added AndroidProducts.mk copied and changed from hammerhead
Added AndroidBoard.mk
Removed cm.mk
Removed cm.dependances
Renamed full_oneplus2.mk to oneplus2.mk and renamed instances of make file
Change Kernel DEFCONFIG and remove cm_ and change in kernel/arch/arm64/config cm_ removed

Added missing libraries throwing make errors from CyanogenMod github

liblight in hardware/qcom/display/msm8994/liblight/Android.mk was removed due to conflict with oneplus2 device specific code

Now I am facing an error about 'ninja'. I have copied in the whole command line into paste bin, but I feel the most important part is below:
http://pastebin.com/4fqyzq2U

[spoiler]
Starting build with ninja
ninja: Entering directory `.'
ninja: error: unknown target 'oneplus2'
build/core/ninja.mk:142: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

#### make failed to build some targets (41 seconds) ####
[/spoiler]

Thank you for any help or insight. PM me if you know any specifics. Thanks.

[ASK] custom rom like samsung s7/s7 edge porting.

there's cusrom like samsung s7 edge porting or touchwiz rom for redmi note 3 pro (KENZO) ?

Porting SystemUI

I am trying to port S6 Edge SystemUI to Note 4, after doing some modifications in framework-res.apk the SystemUI now boots, but after few seconds it FCs and becomes unusable.
I have taken logcat of it but not able to get anything fruitful out of it after trying many days, the fatal logcat is as follows,

07-17 17:24:49.682: E/AndroidRuntime(9998): FATAL EXCEPTION: main
07-17 17:24:49.682: E/AndroidRuntime(9998): Process: com.android.systemui, PID: 9998
07-17 17:24:49.682: E/AndroidRuntime(9998): android.view.InflateException: Binary XML file line #2: Binary XML file line #2: Error inflating class MenuItemView
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.view.LayoutInflater.inflate(LayoutInflater .java:551)
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.view.LayoutInflater.inflate(LayoutInflater .java:429)
07-17 17:24:49.682: E/AndroidRuntime(9998): at com.android.systemui.statusbar.BaseStatusBar.infla teViews(BaseStatusBar.java:2435)
07-17 17:24:49.682: E/AndroidRuntime(9998): at com.android.systemui.statusbar.BaseStatusBar.creat eNotificationViews(BaseStatusBar.java:3197)
07-17 17:24:49.682: E/AndroidRuntime(9998): at com.android.systemui.statusbar.phone.PhoneStatusBa r.addNotification(PhoneStatusBar.java:1884)
07-17 17:24:49.682: E/AndroidRuntime(9998): at com.android.systemui.statusbar.BaseStatusBar.r un(BaseStatusBar.java:1188)
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.os.Handler.handleCallback(Handler.java:739 )
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.os.Handler.dispatchMessage(Handler.java:95 )
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.os.Looper.loop(Looper.java:158)
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.app.ActivityThread.main(ActivityThread.jav a:7225)
07-17 17:24:49.682: E/AndroidRuntime(9998): at java.lang.reflect.Method.invoke(Native Method)
07-17 17:24:49.682: E/AndroidRuntime(9998): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:1230)
07-17 17:24:49.682: E/AndroidRuntime(9998): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:1120)
07-17 17:24:49.682: E/AndroidRuntime(9998): Caused by: android.view.InflateException: Binary XML file line #2: Error inflating class MenuItemView
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.view.LayoutInflater.createViewFromTag(Layo utInflater.java:788)
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.view.LayoutInflater.createViewFromTag(Layo utInflater.java:716)
07-17 17:24:49.682: E/AndroidRuntime(9998): at android.view.LayoutInflater.inflate(LayoutInflater .java:498)
07-17 17:24:49.682: E/AndroidRuntime(9998): ... 12 more
07-17 17:24:49.682: E/AndroidRuntime(9998): Caused by: java.lang.ClassNotFoundException: Didn't find class "android.view.MenuItemView" on path: DexPathList[[zip file "/system/framework/com.broadcom.bt.jar", zip file "/system/framework/secvisualeffect.jar", zip file "/system/priv-app/SystemUI/SystemUI.apk"],nativeLibraryDirectories=[/system/priv-app/SystemUI/lib/arm, /vendor/lib, /system/lib]]


I can upload full logcat also, please help in this regard, I have tried many ways but unsuccessful and now I am stuck at this


Thanks in advance

Porting AOSP

I want to start work on making a AOSP port for the honor 7. The last time i checked people were stuck making a device tree, Is that still the stage we are at? If we have got passed that could some one link it to me so i can get a head start? Thanks.

Lollipop and cross chipset porting

I am trying to understand more about android to be able to get MIUI running on my bullhead device.

How is google stopping us from running Lollipop on it and can it be bypassed?

Is it possible to port a for example SD 810 rom to our SD 808? I understand it might not be the easiest but I can't find any information at all about cross chipset porting, only for MTK chipsets.

I know that this is probably not any easy task and it would probably just be easier to buy a MI device, but I got nothing to do on my vacation so thought I would try and educate myself some.

Porting ROMs to Xiaomi Redmi 3 (Pro)

I want to port a ROM to Xiaomi Redmi 3 (Pro) by following this guide, so I downloaded the latest MIUI version from xiaomi.eu and extracted it to use it as base rom, but there is no system folder. So, I downloaded Cyanogenmod port for this device, and there is a system folder, but it contains build.prop only. What should I do to port a ROM to Xiaomi Redmi 3?

SailfishOS for Tiny210v2 - porting in process

I start porting SailfishOS to Tiny210v2 S5PV210 ARM Cortex-A8 Board

And i have error when SurfaceFlinger is start:

Code:

---

I/SurfaceFlinger(  212): SurfaceFlinger is starting
I/SurfaceFlinger(  212): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL  (  212): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL  (  212): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL  (  212): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
W/libEGL  (  212): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/hwcomposer(  212): int hwc_device_open(const hw_module_t*, const char*, hw_device_t**)::win-0 add[0] 3c330000
I/hwcomposer(  212): int hwc_device_open(const hw_module_t*, const char*, hw_device_t**)::win-0 add[1] 3c4a7000
I/hwcomposer(  212): int hwc_device_open(const hw_module_t*, const char*, hw_device_t**)::win-0 add[2] 3c61e000
E/hwcomposer(  212): int createFimc(s5p_fimc_t*)::Post processor open error (13)
E/hwcomposer(  212): int hwc_device_open(const hw_module_t*, const char*, hw_device_t**)::creatFimc() fail
E/SurfaceFlinger(  212): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger(  212): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc    (  212): Fatal signal 6 (SIGABRT) at 0x000000d4 (code=-6), thread 212 (surfaceflinger)

---

who can ask me - what is wrong ?

[GUIDE] Porting Between HTC MSM8974 Devices

This guide will explain to users on how to port from the HTC One M8, HTC One E8 and HTC Butterfly 2 roms to our beloved Desire EYE. The porting between these devices take little to no knowledge at all to do if you know how to logcat and read kernel last_kmsg.

In this guide i will explain how I've ported InsertCoin M8 to Desire EYE.. Should apply to all htc msm8974 devices.

Requirements :
- Developers Permission for the rom your porting if you plan to release
- Android Image Kitchen
- Basic knowledge on understanding my method of porting

InsertCoin ( Port )
Desire EYE Rom ( Base )

Step 1 : Fixing Camera
Each HTC MSM8974 devices have different camera modules thus need fixing
So take these similar libs from stock roms and place them into the rom your porting.

1. All /system/lib/libtuning** lib files from stock and place them in port in /system/lib/
2. All /system/vendor/lib/libchromatic** lib files from stock and place them in port in /system/vendor/lib/
3. Take /system/etc/res_ctrl** files from stock and place them in port in /system/etc/ ( fix camera resolution )

Step 2 : Fixing NFC

EYE, E8, and B2 all have same NFC driver. So this method will explain when porting from M8

Files to Delete from Port

Code:

---

- /system/app/Nfc
- /system/etc/nfcee_access.xml
- /system/lib/hw/nfc.qcom.so
- /system/lib/libnfc.so
- /system/lib/libnfc_jni.so
- /system/libnfc_ndef.so
- /system/vendor/firmware/libpn544_fw.so

---

Now add these from stock to port

Code:

---

- /system/app/NfcNciNxp/
- /system/etc/libnfc-brcm.conf
- /system/etc/libnfc-nxp.conf
- /system/etc/nfcee_access.xml
- /system/lib/hw/nfc_nci_pn547.defualt.so
- /system/lib/libnfc-nci-nxp.so
- /system/lib/libnfc_nci_nxp_jni.so
- /system/lib/libnfc_ndef.so
- /system/vendor/firmware/libpn547_fw.so

---

Kernel Side for NFC : Will edit later with indep fixing

Step 3 : Having Correct Kernel
Will post stock kernel ports soon with NFC ramdisk fixes.

Camera porting to k10? Any plans?

The camera is good but i dont like the Ui. No manual controls.

Resurrection Remix porting to the Z4 tab

Hey guys,

with RR being the rom i like best (mostly due to its insane custom features), and because i don't really know how to build from source, i attempted to port it by merging the RR of my 6p with the cyanogenmod for the z4 tab( following this guide: http://forum.xda-developers.com/chef...allow-t3283452 ) . I was expecting it to work without major issues due to the hardware of both devices being mostly the same, but on the first try i got a "systemUI has stopped" and nothing else. Then i replaced systemUI with the version of cyanogenmod and got it to show the navbar and notification bar but it reboots if i try to push any buttons (video: https://www.youtube.com/watch?v=64ez0TpIrf0). At this point i'm pretty much out of ideas, so if maybe some of you know about anything useful for such issues or maybe someone knows of a guide or some general directions for building roms from source i would be very happy. (BTW, tried running adb logcat with it plugged in and it doesn't find the device but i'm not sure if its the problem with android or my setup because i haven't tried with other devices)

SM-S820L Same SOC, different Model. Need Porting Help. Please

I have an sm-s820l, straight talk, and found out this phone and the grand prime have a lot in common. Same resolution, same processor, same soc, I just need someone to tell me how to go about porting the cyanogenmod for this device to the one I have. Any help would be appreciated!

Help porting S6 Framework

Grand 2 beloved developers:

I come from S3 Neo. We want a ROM that has S6 framework.
And development for our phone is compatible with yours must of the time, for example, Project Lucky by @Ciro.

Together we are stronger, that's why I'm asking for your help.

If you guys wanna/can help, join us on Telegram: https://telegram.me/joinchat/C6FjkAgEOw9YLHuUttdlwQ

Thank you, in advance!!

REQ : Tutorial on porting Xperia Z5 Rom

Hello All,

I gave lg l90 d405 rooted with custom recovery installed, I want to port xperia z5 rom to my phone, I saw many member like stryder 007 and others have done it successfully and I am asking if any one could help me how to port it to my phone pleazzzze :crying:

qeustions on porting twrp image to new phone

I acquired an lg g3 on 24b. I figured I would make it as a spare incase I lost or damaged my original and use it to test newer versions like marshmallow or nouget.
Here's what I did
1. I I restored factory image using lg flash tool .tot version back to 10b
2. stump rooted it.
3. installed earliey twrp from 2014 with flashify
4. installed twrp 3.0.0
5. did a twrp back up including EFS
6. restored my jasmine9.1 -35b image to it. with EFS checked
7. Noticed my modem/baseband version was "Unknown"
I was going to flash the 35b modem but before that I had some questions.

Questions.
1. what exactly is EFS? ( am asking because I included it when I went from 10b to jasmine9.1 35b I need to know if that's something you dont flash from one phone to another)
2. if I flash my modem file to 35b wil I be able to flip flop back and forth and upwith modem files.?
3. how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b.

I know enough to be dangerous so I'm asking cause I don't know enough! lol
thanks.

[Help Plz] Porting Stock ROM For Same But Deterrent Model Device

Sir I Tried To Port Stock Marshmallow ROM ...
I Tried By Every Methodes..
Some Time tar.md5 file Checksum Failed.
Some Time When Settled To Flash It Error With Updater Script..
My Device Ex; A900F not Received Marshmallow But A900H Received Marshmallow..when I Tried To Odin That A900H Firmware ...its Went A Fails Error..
So Please How Can I Do That Sir [emoji26] [emoji26] [emoji26]

Sent from my SM-J700F using XDA-Developers mobile app

Android porting

Hello. I have j700f with exynos octa 7580 processor. What base Rom and cm should chose to port to cm13.

Porting CM13 to Tegra Note

Recently Cyanogen released official CM13 nightly for Nvidia Shield Portable https://download.cyanogenmod.org/?device=roth.

Tegra note 7 and Shield portable got the same processor. So someone who got experience in porting kindly port the CM13 rom.