Rom porting guides!!!

You tube is full of guides for porting roms with the same hardware specs but i cannot find any guides for porting roms between two different hardware specs.
Does anyone know of a guide that covers two different hardware specs ?

Help in Porting To Cyanogen

Hey, Guys
im a total noob in programming and stuff :silly:
but im very much interested in mobiles and technology
I wanted to port Cyanogenmod to my htc desire 826(only china and india release, so i figured there will be no further updates from htc :( )
I saw many guides for noobs :p but they said base rom shouldnt be stock, and please correct me if i am wrong that port rom should be pure
So if base rom shouldnt be stock then i cant use the rom in htcdev
and it is written any other rom(cyanogen?) for same soc(snapdragon 615) and resolution(1920X1080)
there is no rom available like that the closest i found was but the rom there itself is for both the 720p and 1080p resolution( project tomato just made the account so outside links restricted :p )
also different manufacturer
Please guys help me it will be much appreciated
Also too I have been following xda for a long time
Also which method should i follow??

P.S.
Guys i really like all this stuff can you please tell me where should i start learning it and to understand android code
Also built universal apps that run across all three platforms

Thanks guys your help will be much appreciated :) :fingers-crossed: :) :fingers-crossed:

Why only stock android based custom Roms? Why no porting??

While I really appreciate the work put in by the developers for Zenfone 2, I don't see any ported roms from other flagship devices like any Note Rom, Miui Rom, Sony etc. ?
If any of the developers is listening, please port some roms from other devices, it will be a good change and new experience for our amazing Z2. Thanks !!! :D

Help needed in porting stock 4.2.2 rom into stock 4.4 rom for mtk6572 !!!

Hi Friends,
I am pretty n00b in rom porting. I simply want to upgrade this Phone http://www.iball.co.in/Product/Andi-4-5z/578"]http://www.iball.co.in/Product/Andi-4-5z/578
IBall Andi 4.5Z having jellybean rom to any simply any Kitkat based rom.

I found out that this phone http://www.iball.co.in/Product/Andi4-5-K6/597 IBall Andi 4.5K6 has almost same specs and same mtk6572 chip.

I Downloaded both the stock roms so that I can try porting my self using porting guides.But most of the guides explain using folders but in these roms there are all .img files. Screenshots Below
[IMG="IBAll Andi 4.5K6+ Kitkat"][/IMG]


[IMG="IBall Andi 4.5Z JellyBean"][/IMG]

extracting them using winrar, 7zip , Uniextract failed. :eek:
What to do now ??:confused:
how to get these rom ported ? i Dont want much but to simply upgrade my phone to Kitkat whether be in stock or custom rom.

Links to roms are provided below.

http://www.androot.org/iball-stock-r...-firmware.html

http://www.androot.org/iball-stock-r...-firmware.html


Please Help me.

About porting camera.

Can we put Kitkat camera to 5.1.1 is it possible to port it? I don't like the camera on Lollipop. To blurry.

Porting without source

Hi guys
I have an android with kitkat (Not even stock roms available online for it), and I want to port lolipop to it. The trouble is, all the tutorials I see assume you have source to work from.
Now, I dont have source, But I have an entire bit for bit partition dump (dd). I cant access about half the partitions, but thats the least of my worries.
I'm not interested in installing a new radio, I only want the OS upgraded.
Any advice?

Vibe porting?

Sir I am trying to port vibe from over 2 weeks.... But I always get stuck on bootlogo... I don't know what to do... Plz someone shortly tell me how to do it...

My device is micromax a116 and I want to port vibe 2...
P.S: I have a good knowledge about porting... Just tell me shortly... I already ported a number of roma

Sent from my Nexus 5 using XDA Forums

Vibe UI 2 porting?

What are the steps for porting vibe rom... I have a good knowledge about porting... Just tell me shortly..

P.S: I have already ported 7 roms... Vibe Ui stuck on bootlogo...

Sent from my Nexus 5 using XDA Forums

LewaOS porting problem

Hi guys, have a problem porting Lewa OS on my phone (Samsung Galaxy Ace Plus). In short words the rom does not boot and it remains on bootanimation, i tried to copy files (libandroid_runtime, libandroid_servers and libmedia_jni) from port to my rom but the rom does not boot the same. Does anyone know how i can fix? (I port rom from LG Optimus L5)

I followed this guide -> http://forum.xda-developers.com/show....php?t=1623464

Porting Vibe

When porting VibeUi, do I have to take any specific step apart from ordinary Rom porting?

P.S: I have ported many Roms. Now porting vibe 2 from Lenovo s920 but not getting further from the boot logo.

Sent from my Nexus 5 using XDA Forums

Porting Air Command from Note 5 ..

Hey ..
i have been working on port Air Command from NOTE 5 to our S6E but unfortunately with no luck,
Actually its pop up but i cant click on any app with my finger because it need Spen which we dont have .. ( i have try the same thing on NOTE 5 and doesnt work with finger too)
I dont have much experience in developing or editing but i have edited many files but get the same result ..



So if there any developer can help us to get it work on our device send me a pm , i appreciate that :)

Greets

[Help] Camera App Porting Requested

Hello,
I've always loved to click pictures and never am I able to compromise on picture quality and enhancements. I've been using Cybershot Camera Mod from here
http://forum.xda-developers.com/xper...-auto-t2501740
But the thing is, that mod is available only for JB 4.2.2 and not for kitkat or lollipop. I've asked the developer for it but seems like he is not responding to any queries. I am still on stock JB for that camera only.
It would be very helpful if you could port that app. Any other camera app porting from latest xperia z series is also highly appreciated.
Thank you.

Porting CWM to ZTE MF97A livepro/spro (Need Help)

Hi Everyone, I am trying to port CWM to a ZTE Livepro (sprint) spro (ATT) and I am running into a small issue. I have rooted and unlocked the bootloader with relative ease. I have dumped the boot and recovery partition as well as system (just incase) I have pulled down CM 10.1 to work from. The stock rom on the device is jellybean 4.2.2 After unpacking the bootloader and getting the fstab and everything else needed I was able to build a recovery BUT thats only with the default vaules in the boardconfig.mk This is the defaults for this device:

Code:

---

USE_CAMERA_STUB := true  # inherit from the proprietary version -include vendor/zte/MF97A/BoardConfigVendor.mk  TARGET_ARCH := arm TARGET_NO_BOOTLOADER := true TARGET_BOARD_PLATFORM := unknown TARGET_CPU_ABI := armeabi-v7a TARGET_CPU_ABI2 := armeabi TARGET_ARCH_VARIANT := armv7-a-neon ARCH_ARM_HAVE_TLS_REGISTER := true  TARGET_BOOTLOADER_BOARD_NAME := MF97A  BOARD_KERNEL_CMDLINE := console=NULL androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 BOARD_KERNEL_BASE := 0x80200000 BOARD_KERNEL_PAGESIZE := 2048  # fix this up by examining /proc/mtd on a running device BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_FLASH_BLOCK_SIZE := 131072  TARGET_PREBUILT_KERNEL := device/zte/MF97A/kernel  BOARD_HAS_NO_SELECT_BUTTON := true

---

and here is the fstab I use from boot.img

Code:

---

# Copyright (c) 2011, The Linux Foundation. All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are # met: #    * Redistributions of source code must retain the above copyright #      notice, this list of conditions and the following disclaimer. #    * Redistributions in binary form must reproduce the above #      copyright notice, this list of conditions and the following #      disclaimer in the documentation and/or other materials provided #      with the distribution. #    * Neither the name of The Linux Foundation nor the names of its #      contributors may be used to endorse or promote products derived #      from this software without specific prior written permission. # # THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT # ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN # IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.  # mount point        fstype                device                        [device2] [length=]  /modem                emmc                /dev/block/platform/msm_sdcc.1/by-name/modem /sbl1                emmc                /dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl2                emmc                /dev/block/platform/msm_sdcc.1/by-name/sbl2 /sbl3                emmc                /dev/block/platform/msm_sdcc.1/by-name/sbl3 /tz                emmc                /dev/block/platform/msm_sdcc.1/by-name/tz /rpm                emmc                /dev/block/platform/msm_sdcc.1/by-name/rpm /emmcboot        emmc                /dev/block/platform/msm_sdcc.1/by-name/aboot /cefs                emmc                /dev/block/platform/msm_sdcc.1/by-name/modemst1 /cefs_tar      emmc            /dev/block/platform/msm_sdcc.1/by-name/fsg /splash                emmc                /dev/block/platform/msm_sdcc.1/by-name/splash /boot                emmc                /dev/block/platform/msm_sdcc.1/by-name/boot /cache                ext4                /dev/block/platform/msm_sdcc.1/by-name/cache /data                ext4                /dev/block/platform/msm_sdcc.1/by-name/userdata                length=-16384 /misc                emmc                /dev/block/platform/msm_sdcc.1/by-name/misc /recovery        emmc                /dev/block/platform/msm_sdcc.1/by-name/recovery /sdcard                vfat                /dev/block/mmcblk1p1        /dev/block/mmcblk1 /system                ext4                /dev/block/platform/msm_sdcc.1/by-name/system #/sdcarddata        ext4                /dev/block/platform/msm_sdcc.1/by-name/sdcarddata /carrier        ext4                /dev/block/platform/msm_sdcc.1/by-name/carrier

---

When I build the recovery with that it doesnt have an issue, but when running fastboot boot recovery.img I get 4 distorted pinguins and the device goes black and hanges. This is obviously because the:

Code:

---

BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_FLASH_BLOCK_SIZE := 131072

---

is incorrect. There is no /proc/mtd /proc/emmc /proc/dumchar_info Here is the partition map:

Code:

---

lrwxrwxrwx root    root              1970-01-11 07:55 aboot -> /dev/block/mmcblk0p5 lrwxrwxrwx root    root              1970-01-11 07:55 boot -> /dev/block/mmcblk0p7 lrwxrwxrwx root    root              1970-01-11 07:55 cache -> /dev/block/mmcblk0p17 lrwxrwxrwx root    root              1970-01-11 07:55 carrier -> /dev/block/mmcblk0p15 lrwxrwxrwx root    root              1970-01-11 07:55 fsg -> /dev/block/mmcblk0p20 lrwxrwxrwx root    root              1970-01-11 07:55 misc -> /dev/block/mmcblk0p18 lrwxrwxrwx root    root              1970-01-11 07:55 modem -> /dev/block/mmcblk0p1 lrwxrwxrwx root    root              1970-01-11 07:55 modemst1 -> /dev/block/mmcblk0p11 lrwxrwxrwx root    root              1970-01-11 07:55 modemst2 -> /dev/block/mmcblk0p12 lrwxrwxrwx root    root              1970-01-11 07:55 persist -> /dev/block/mmcblk0p9 lrwxrwxrwx root    root              1970-01-11 07:55 recovery -> /dev/block/mmcblk0p19 lrwxrwxrwx root    root              1970-01-11 07:55 rpm -> /dev/block/mmcblk0p6 lrwxrwxrwx root    root              1970-01-11 07:55 sbl1 -> /dev/block/mmcblk0p2 lrwxrwxrwx root    root              1970-01-11 07:55 sbl2 -> /dev/block/mmcblk0p3 lrwxrwxrwx root    root              1970-01-11 07:55 sbl3 -> /dev/block/mmcblk0p4 lrwxrwxrwx root    root              1970-01-11 07:55 splash -> /dev/block/mmcblk0p16 lrwxrwxrwx root    root              1970-01-11 07:55 ssd -> /dev/block/mmcblk0p21 lrwxrwxrwx root    root              1970-01-11 07:55 system -> /dev/block/mmcblk0p13 lrwxrwxrwx root    root              1970-01-11 07:55 tz -> /dev/block/mmcblk0p8 lrwxrwxrwx root    root              1970-01-11 07:55 userdata -> /dev/block/mmcblk0p14 lrwxrwxrwx root    root              1970-01-11 07:55 ztecfg -> /dev/block/mmcblk0p10

---

Partition sizes:

Code:

---

cat /proc/partitions                                          major minor  #blocks  name  179        0    3866624 mmcblk0  179        1      73728 mmcblk0p1  179        2      8192 mmcblk0p2  179        3      8192 mmcblk0p3  179        4      8192 mmcblk0p4  179        5      8192 mmcblk0p5  179        6      16384 mmcblk0p6  179        7      16384 mmcblk0p7  179        8      49152 mmcblk0p8  179        9      16384 mmcblk0p9  179      10      8192 mmcblk0p10  179      11      8192 mmcblk0p11  179      12      32768 mmcblk0p12  179      13    1056768 mmcblk0p13  179      14    1892352 mmcblk0p14  179      15      57344 mmcblk0p15  179      16      16384 mmcblk0p16  179      17    311296 mmcblk0p17  179      18      8192 mmcblk0p18  179      19      16384 mmcblk0p19  179      20      8192 mmcblk0p20  179      21      8192 mmcblk0p21

---

Shows the boot and recovery being 16mb So heres the boardconfig.mk I came up with:

Code:

---

USE_CAMERA_STUB := true  # inherit from the proprietary version -include vendor/zte/MF97A/BoardConfigVendor.mk  TARGET_ARCH := arm TARGET_NO_BOOTLOADER := true TARGET_BOARD_PLATFORM := unknown TARGET_CPU_ABI := armeabi-v7a TARGET_CPU_ABI2 := armeabi TARGET_ARCH_VARIANT := armv7-a-neon ARCH_ARM_HAVE_TLS_REGISTER := true  TARGET_BOOTLOADER_BOARD_NAME := MF97A  BOARD_KERNEL_CMDLINE := console=NULL androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 BOARD_KERNEL_BASE := 0x80200000 BOARD_KERNEL_PAGESIZE := 2048  # fix this up by examining /proc/mtd on a running device BOARD_BOOTIMAGE_PARTITION_SIZE := 16384 BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16384 BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1056768 BOARD_USERDATAIMAGE_PARTITION_SIZE := 1892352 BOARD_FLASH_BLOCK_SIZE := 4096  TARGET_PREBUILT_KERNEL := device/zte/MF97A/kernel  BOARD_HAS_NO_SELECT_BUTTON := true

---

After building with the modded boardconfig.mk I get an error at the very end of building CWM saying filesize too big. I have also used different flash block size to no avail. I have been scratching my head about this for about a week already trying to get it to work with lots of reading. I dont know if the boardconfig.mk needs a hex value for the partition sizes? If it does how can I go about getting it? Here is the error I get:

Code:

---

----- Making recovery image ------ /home/android/cm-10.1/out/target/product/MF97A/recovery.img maxsize=8448 blocksize=4224 total=8294400 reserve=8448 error: /home/android/cm-10.1/out/target/product/MF97A/recovery.img too large (8294400 > [16896 - 8448]) build/core/Makefile:769: recipe for target '/home/android/cm-10.1/out/target/product/MF97A/recovery.img' failed make: *** [/home/android/cm-10.1/out/target/product/MF97A/recovery.img] Error 1 make: *** Deleting file '/home/android/cm-10.1/out/target/product/MF97A/recovery.img' build error!

---

Rom porting- paranoid android to huawei mediapad t1 s8-701u

Hi all,,
I am using an s8-701u Huawei Mediapad t1 8.0 honor,, with rooted stock jellybean 4.3 rom (emui 1.6) and bootloader unlocked. I want to make a custom rom or use ""paranoid android" or PAC man rom on this device.
I tried to port PA 3.99 of google nexus 2013, but cant do that because i dont have a base custom rom, so i tried to cook one with android kitchen by dsixda but no luck because my device doesn't have support. So i tried to add support by ""edify" but mount points from recovery.fstab doesnt have valid mount points and i dont know what are param1 and param2 in edify,,
i am this far from porting,, please help me or i can use one of the roms available for my device with you,, if anyone have any rom for this mediapad t1 please give that to me
thanks to you all.. hoping for advice and help

[R&D] Porting G925F or any (version) Roms to Sprint.

Hello (I have nothing):eek:

This is to discuss Sprint porting/ Introducing myself/ A few questions
Please don't reject this (my) project. I will reject my project if I find out it's impossible or absolutely not worth it.. Please also don't tell me to just do it, I would need more research time.

Of course this would be great. Any request for Sprint support posted in other models Rom sections get rejected quickly. But it's been done. Not with this phone, but anyway...
About me:
I had built an AOSP Rom for A Virgin Mobile HTC Desire 816.. And coded A few Apps, so I know A bit around the Android system. Different hardware, I know. With that phone I could just flash A universal APN fix that fixed mobile network when using any rom for any world model. There are close to 20 or more variants. I'd like to create A flashable fix like this. Virgin Mobile uses the Sprint Network.
I have A github (same username), and A fast ((can use over 500GB RAM!)) Microsoft Azure remote server (Ubuntu Server, Windows, free for me) which I use for development which I may be able to "donate" access to for A few people.
I'm new to Knox systems

A few questions:
It's really that secure?!?! I can't even directly "sudo" in A rooted Linux install on the S6 edge. I've been searching the internet everyday for A Samsung Pay workaround/alternative use for the magstripe. But I highly doubt Samsung will open an SDK/API for the Magstripe.

This is possible right, simple porting procedure? Though I've been unsucessful with porting since Lollipop.

I plan to link resourses such as [Guides] from the Galaxy S5, S4 for reference.
Anyone working on this, knows what to change, or has more resources than incompatible guides please let me know.


Not much is happening with the S6 not even with AOSP teams. I see that all the news was the way to go and NOT root it because people want Samsung Pay.



//joke\While nothing is happening, who needs A Calculator (like NOW) but just can't find one on any store?
"Material Calculator"
Outdated, Unscaled for UHD, Unaligned, Unfinished. Works though.
https://onedrive.live.com/redir?resi...int=file%2capk

[Miui7] [Porting request] for Moto E

Anybody please port Miui7 for moto E. Its a very nice looking ROM. [emoji7] [emoji7]

Sent from my Moto E using Tapatalk