Database Info

NS4G modem patch on CM7/9/10 based roms, nightlies and previews- 2/12/13

Hi, I made this thread because people have been asking me what to do to make a ROM compatible with the Nexus S 4G modem and RIL, so I made a flashable zip so you can use the modem and RIL on any CM7 based ROM (like MIUI or JoyOS or whatever you fancy).
Note: If using a ROM not on this list, use the closest cm patch corresponding to the os and then download the phone and settings apks from the nexus s 4g Roms and either put them in the zip or push them. That way, roaming and update prl and profile will work.
I included the KL2 modem in each AIO zip. If you do not like it, or would like to try other modem files, try the flashable zips here: http://forum.xda-developers.com/showthread.php?t=1077168
CM7
just flash the zip below (made by nashdogg and I)
http://d-h.st/dGR
I added the nexus audio drivers in kernel and lib, and I also added voodoo color, voodoo sound, and Battery Life Extender.
Click to expand...
Click to collapse
CM9 (Roaming Fixed) Instructions:
Just flash this in CWM. Custom kernels are available in the 2nd post. http://d-h.st/U1L
AOKP ICS (by Nashdogg)
http://d-h.st/vVP
Jellybean patches thanks to dropple, nashdogg, andy_nu, and didhiy ( newest patch as of 12/5/12 with nitest didhiy 1124 kernel voodoo color)
PA 2.54 AIO ns4g modem patch- http://d-h.st/CQm
CM10 AIO ns4g modem patch- http://d-h.st/96W
AOKP-JB Build-4 AIO ns4g modem patch- http://d-h.st/t4n
CM10.1 http://d-h.st/i9s
Universal
Effsi said:
http://goo.im/devs/effsi/misc
these should allow you to switch back and forth between the epic modem and nexus modem.
what it does :
installs blobs related to the modem
edits build.prop lines to match the modem
-should- work with all current versions (2.3 through 4.2.2)
-should- work with all roms that support switching modems (aokp, cm, pa, pac, baked, hellybean, etc...)
what it doesn't do :
it does not install or change the actual modem itself.
it does not install or change the kernel.
it does not backup anything.
it does not replace any apks.
it does not perform any tweaks or extras of that sort.
it does not fix issues in the system ie if 4g isn't working in the kernel this installer won't magically fix it or inversely break it if it works.
so that means you will need to install the modem itself (through zip or the MORE RECOMMENDED METHOD OF ODIN)
and that you will need to make sure you are on a proper kernel that supports your modem of choice.
Ex... on stock aokp4.2.2 (which is epic modem by default) to switch to the nexus modem you would flash kernel of choice for nexus modem (didhiy/mine), then modem with recovery or odin, then flash swap2nexusmdm.zip
Ex2... on ck10.1 (which is nexus modem by default) to switch to the epic modem you would flash modem of choice with Odin or recovery, then any kernel that supports epic modem and then flash swap2epicmdm.zip
Note: These instructions are a bit different than effsi's as the order of flashing does matter when on an epic modem ROM and kernel as the modem flash is dependent on kernel drivers that are not present in epic modem kernels.
Click to expand...
Click to collapse
Any Nexus S 4G modem can be used but the one included is supposedly best. Try any other one and let me know if it works better
My kernel sources are at https://github.com/xboxfanj/android_kernel_samsung_victory in the gingerbread branch so if you want to make a kernel based on that or cherrypick the patches in my kernel into another kernel, you are welcome to.
Use my commits and bbelos' commits at https://github.com/nexussense4g/android_device_samsung_epicmtd in the crespo-modem branch to get GPS and modem working on any ROM.
Thank you to didhiy for adapting the patches that bbelos and I made. For support for Update PRL and Profile, you need to copy some of the overlays from the Nexus S 4G device sources.
Thank you to bbelos, coolya, the CM SGS team, CM Nexus S team, AOSP, Samsung, Google, and me for making this patch.

Custom CM9 Kernels (note these are not all in one zips, so if you choose to flash these, you must also flash the AIO if you haven't already, and each time you upgrade builds, you'll need to flash the aio and the custom kernel if you still want it):
Nyan:
http://marcusant.com/android/epic/nyan_CM9-CrpMdm.zip
Shadow: http://marcusant.com/android/epic/Shadow_CM9-CrpMdm.zip
Anyone is welcome to include this patch in their rom, just as long as you give all the contributors credit.
And also, if someone wants to make this for cm9, that'd be awesome. Use bbelos's crespo-modem branch in his device repo and use his crespo-modem branch in his vendor repo.
Then use my kernel patches at my github and make a full cm9 build and if it works, release that build and release a patch like mine with kernel, and ril bins, libs, and etc files, and build.prop and everything outside system like the mtd scripts and modify updaterscript so it works, or just use my metain folder
Sent from my SPH-D700 using Tapatalk 2

First! Sweet, I always wanted to do that. :- )
And thank you so much xboxfanj for continuing to make this the phone that might never die! You and all the other great devs are definitely making it easy to
wait to upgrade to a new phone. Keep up the good work, and thanks again.

itek said:
First! Sweet, I always wanted to do that. :- )
And thank you so much xboxfanj for continuing to make this the phone that might never die! You and all the other great devs are definitely making it easy to
wait to upgrade to a new phone. Keep up the good work, and thanks again.
Click to expand...
Click to collapse
No problem. Glad you enjoy it. If there's ever anything you would like for me to port or do, PM me and I will do whatever I can to make it happen.
Sent from my SPH-D700 using Tapatalk 2

I try to install this patch over cm7 stable & didn't work.. I think the format /system command on updater-script will erase all the previous rom
I'll try to fix it tomorrow on my free time, maybe with try find some commands to erase previous blob which unreplaceable with the patch like lib sec ril 40.so (or similar) and build.prop must be edited from the previous rom with changes on several lines.

didhiy said:
I try to install this patch over cm7 stable & didn't work.. I think the format /system command on updater-script will erase all the previous rom
I'll try to fix it tomorrow on my free time, maybe with try find some commands to erase previous blob which unreplaceable with the patch like lib sec ril 40.so (or similar) and build.prop must be edited from the previous rom with changes on several lines.
Click to expand...
Click to collapse
No need to delete libsecril-40. Thanks for letting me know that. Forgot to delete the format command. Got it now and the zip is updated, but at the same link.
Edit: and any CM7 ROM should be fine with CM7 build.prop AFAIK. It may not identify 100% correctly in settings>about phone, but good enough. TBH, I don't care if it says CM7 in settings while I run MIUI.

xboxfanj said:
No need to delete libsecril-40. Thanks for letting me know that. Forgot to delete the format command. Got it now and the zip is updated, but at the same link.
Edit: and any CM7 ROM should be fine with CM7 build.prop AFAIK. It may not identify 100% correctly in settings>about phone, but good enough. TBH, I don't care if it says CM7 in settings while I run MIUI.
Click to expand...
Click to collapse
Fixed GPS as well, sorry about the first couple batches being wrong. This one should be good. If you downloaded before, DL again.

Modem works great but this breaks root for me.
Sent from my SPH-D700 using Tapatalk 2

Flint420 said:
Modem works great but this breaks root for me.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Weird not sure what I could've done that would've broken root. Does anyone else have this problem?
Sent from my SPH-D700 using Tapatalk 2

Not sure if it makes a difference but I flashed the modem through odin first then the patch. I'm on the newest cm7 nightly.
Sent from my SPH-D700 using Tapatalk 2

Flint420 said:
Not sure if it makes a difference but I flashed the modem through odin first then the patch. I'm on the newest cm7 nightly.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
That shouldn't matter.
Sent from my SPH-D700 using Tapatalk 2

xboxfanj said:
That shouldn't matter.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
I downloaded the newest one (not test yet) & think that this command
Code:
set_perm_recursive(0, 0, 0755, 0644, "/system");
will messed up the su permission that cause root access denied

didhiy said:
I downloaded the newest one (not test yet) & think that this command
Code:
set_perm_recursive(0, 0, 0755, 0644, "/system");
will messed up the su permission that cause root access denied
Click to expand...
Click to collapse
OK, I will just not change the permissions in any folder I haven't modified. Probably some of the xbin and bin stuff is at fault too.
Thank you didhiy for looking at my updaterscripts and pointing out what to fix.
Sent from my GT-P7510 using Tapatalk 2

What changes are needed in build.prop, if I was to try this on CM10?

sgtkwol said:
What changes are needed in build.prop, if I was to try this on CM10?
Click to expand...
Click to collapse
change libsecril-40 to libsec-ril, delete all the samsungril or samsungcdma or epicril stuff. Remember, you will need a fresh new kernel, with the modem patch.

sgtkwol said:
What changes are needed in build.prop, if I was to try this on CM10?
Click to expand...
Click to collapse
succesful run this patch on PA 1.99 and Kanged CM10 0808 too
thanks to marcusant, bbelos, noobl, xboxfanj, sgktwol, darkjje, epiccm team & all great dev on xda
all credits goes to them
me just mix & match, just have fun with all the great epic community
you can blame me if didn't work or have some nasty bugs... but hope other can fixed it for us
{
"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"
}
link for test or reference:
Patch for PA 1.99
Patch for CM10 0808
just flash from cwm or twrp, didn't need to wipe anything.. except an app was FC, try to clear that app data first before goes to wipe entire dalvik-cache, cache or data
don't forget to odined the crespo modem on OP

didhiy said:
succesful run this patch on PA 1.99
Click to expand...
Click to collapse
Sorry if I'm asking too much, but can you get a stock+backlight fixed version of the patch up and running? I'm sure others would like a Shadow version, too. Nyan never seemed to agree with me.

Is it stable? Copy the last two commits here to fix GPS and modem stability: https://github.com/NexusSense4G/android_device_samsung_epicmtd/commits/crespo-modem
Also, add gpsd from my CrespoModem CM7 ROM to vendor/samsung/epicmtd/vendor/bin to fix GPS.
Let me know after you apply these patches if modem works every boot (on some old ICS builds using this, modem didn't work every boot, so reboot at least 20 times and make sure the signal bars are there, not X'ed out). If so, go ahead and release, just give me and bbelos a shout out. If you want, create your own thread for it. If not, you can certainly use the CM10 Kang thread. Also, make a patch zip like mine here if you don't mind and I can post that here, or you can make your own thread.

added some of the xbin permissions stuff in here. Let me know if it fixed su. It's in the same link.

sgtkwol said:
Sorry if I'm asking too much, but can you get a stock+backlight fixed version of the patch up and running? I'm sure others would like a Shadow version, too. Nyan never seemed to agree with me.
Click to expand...
Click to collapse
I'll try another build with different source tomorrow.. my internet connection was so poor so I must edit the source manually
posted a link for reference if you want to test a kernel build too
xboxfanj said:
Is it stable? Copy the last two commits here to fix GPS and modem stability: https://github.com/NexusSense4G/android_device_samsung_epicmtd/commits/crespo-modem
Also, add gpsd from my CrespoModem CM7 ROM to vendor/samsung/epicmtd/vendor/bin to fix GPS.
Let me know after you apply these patches if modem works every boot (on some old ICS builds using this, modem didn't work every boot, so reboot at least 20 times and make sure the signal bars are there, not X'ed out). If so, go ahead and release, just give me and bbelos a shout out. If you want, create your own thread for it. If not, you can certainly use the CM10 Kang thread. Also, make a patch zip like mine here if you don't mind and I can post that here, or you can make your own thread.
Click to expand...
Click to collapse
just posted a link to test, it works fine after reboot (tested 3 times)
you can look over it, and if it goes fine.. maybe need to modify the build.prop for other cm10 build
just post on the OP if this tested working to other guys

[FIX] CM10 alpha 4 kernel - signal fix

These kernels are for CyanogenMod 10 - Alpha 4.
The goal of these builds is to fix the issues with phone signal, which is not properly working with the stock kernel. Nothing was changes, no extra features, no nothing.
There won't be any more "development" now that the bug is fixed.
The experimental sync bug fix, as the name says, it's a new sync bug fix I was testing. It's here because it partially fixed the missing signal issue at first, but it's not the real fix.
Downloads:
kernel-cm-10-A4-signal_fix.zip: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-exp.zip: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore.zip: stock alpha 4 kernel.
Note: I forgot to change the "name" of the kernel, so you'll get [email protected]_CM9. Don't worry, it's for CM10
Even though I marked V2 as experimental build and I added it as alternative choice, it's the most downloaded version.
As I reported several time ago, mobile data is maybe less stable with it and I think it's because the PDA state is controlled with early suspend instead of the regulr suspend, as it was in the old Samsung releases. In case of problems, flash V1.
If you noticed anything, please report
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patches attached, applied as indicated above.
I verified that when a stock ROM is used, GPIO 126 is normally set to 0.
UPDATE
Click to expand...
Click to collapse
If you are stuck at Samsung splash screen and you are unable to reboot in recovery (I don't know why some users are facing this issue), so you are not able to flash another kernel or restore a backup, you can try to flash one of the kernels with ODIN.
Downloads:
kernel-cm-10-A4-signal_fix-ODIN.tar: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-ODIN-exp.tar: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore-ODIN.tar: stock alpha 4 kernel.
Reboot in Download mode and flash as PDA.
Kernel modules are not included in the PDA. They are not necessary if you were using dhiru's CM with no custom kernels. If you are not sure, do as follows:
Flash kernel as PDA with ODIN (assuming you are stuck at Samsung splash screen and can't reboot in recovery)
Reboot in recovery (pull the battery if nothing works and use the three-keys combo)
Flash CyanogenMod 10 zip (your data will be preserved)
Flash once again kernel as PDA with ODIN
_____
Older posts:
Update: Now I know what stock ROMs use (GPIO 126 = 0). I'll soon update the kernel.
I already wrote that this won't be a custom kernel, no extra features, overclock etc. I opened this thread simply to test a fix, that's why I opened it in the general section, even though the dev section would have been more appropriate.
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
Very old post:
Click to expand...
Click to collapse
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.

Question
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!

jsp1984 said:
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
Click to expand...
Click to collapse
I could, but I don't have LUBKPD modem.
All you have to do is to take modem.bin from the PDA of your ROM (as you may know, you can open it as a normal tar), copy it in /radio overwriting the existing one and reboot. Permissions will be automatically set on reboot.
If you want, here two (different) flashable zips I made for myself. You have to replace modem.bin inside of the zip with yours and then flash.
radio-cm-XXLE4-galaxysl-signed.zip (will erase /radio and then copy the modem)
radio-cm-KPU-galaxysl-noerase-signed.zip (will simply copy the modem)

Works perfectly. Thank you dear Sir :thumbup:
Sent from my GT-N8013 using xda app-developers app

Ok, I think I almost fixed the problem. sec_get_param_value is an exported symbol defined in param.ko (yeah, brilliant...), but we don't use that module anymore in alpha4. The consequence is that the function that turns on the modem is never executed completely.
It still needs some improvements. switch_sel is never set or initialized, but at least the connection is immediately enstablished now. The problem is that I'm not sure which is the best option, so I'll wait for more opinions about it.
In the meanwhile I built two new kernels:
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
V2 is a little bit more "experimental".
OP updated with the new patch.
__
Maybe this is not the right place for this thread, but I opened it here because there won't be any development.

I flashed the V2 and I got the signal instantly after flashing
Sent from my GT-I9003 using xda app-developers app

Thanks man it works great for me...flashed v2 and boom it turned on
Sent from my GT-I9003 using CM10 alpha4 Tapatalk 2

It works so good thank you so much I hope you will continue your very good job
Envoyé depuis mon GT-I9003 avec Tapatalk

Its working fine till now, Thanks alot!. I just wanted to say would you please add move governers in the subsequent release

This thread should be moved to development section.
So that people are aware of the fix.
And it works perfectly, thanks to losconsiuoto
Sent from my GT-I9003 using xda premium

hi
loSconosciuto said:
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Click to expand...
Click to collapse
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update

Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!

spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned

rahul_rocks3 said:
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
Click to expand...
Click to collapse
I wrote some of the original instructions on the i9003 forums, so procedure/method is not a problem here.
I think the issue is I flashed the v2 kernel over the ParanoidAndroid latest 2.54 Alpha4 assuming that as the base is this ROM, the kernel would work. But got a soft brick. Its all fine now, had to go through the whole KPE, LF2 process and now flashing CM10 Aplha4.
If you could just tell me if replacing the modem.bin from LF4 is enough for the signal issues or do I still need to flash the V2 kernel?
Thanks in advance!
EDIT: Flashed V2 but got a 2nd soft brick. Went through the whole process again () My signal and data are working but the indicator is greyed out.

resolved problems
I had problems relating to signal strength and storage.
Thanks and its now working perfectly.
---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------
rahul_rocks3 said:
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Click to expand...
Click to collapse
+1

Flashed V2... It's working great. Thanks.
Sent from my Nexus 7 using xda premium

Thanks works like a charm.

spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !

arindammanidas said:
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Click to expand...
Click to collapse
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.

spacebar2011 said:
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
Click to expand...
Click to collapse
I'm doin' good!
I'm still on CM9.... but v2 seems to work for some people including loSconosciuto himself....
Sent from my Samsung Galaxy SL on CyanogenMod 9 !

[ROM][4 May 2013] CM7 for HTC Merge/Lexikon [Kernel: msm7x30 CM]

I originally released this rom on 2fastforums.com (http://2fastroms.com/showthread.php?5435-WIP-18-Dec-2012-CM7-Kernel-CM-msm7x30) and now feel it is ready for release on XDA. (Site is currently down for unknown reasons)
CM7 for HTC Merge/Lexikon
Click to expand...
Click to collapse
Code:
Features:
-100% stock CM7 from source
What works:
Almost everything
Click to expand...
Click to collapse
What doesn't work:
MMS on USC?
Jittery Compass
Click to expand...
Click to collapse
Instructions
1) Flash recovery through bootloader or fastboot
2) Boot into recovery and factory reset, also go into mounts and format system
3) Flash Rom
4) Flash GApps
Click to expand...
Click to collapse
Downloads
Recovery: http://d-h.st/users/e334/?fld_id=6766 (Either one will work, I personally prefer v5.0.2.8 Capacitive Touch)
ROM: http://d-h.st/users/e334/?fld_id=6727
GApps: https://www.box.com/s/79bpq0ywdxcf4093t926 (thanks liamf1!)
Click to expand...
Click to collapse
Source
Kernel: https://github.com/jianC/htc-kernel-msm7x30
Lexikon Device Tree: https://github.com/jianC/android_device_htc_lexikon
Lexikon Proprietary Vendor Tree: https://github.com/jianC/android_vendor_htc
Click to expand...
Click to collapse
All my changes are documented on github.
Credits: Cyberblade (CDMA fix), liamf1 (beta tester/helpful feedback) 2fast4u88, Cyanogenmod & Team, Kali-, Neopeek & Team, UnitedDev & Team, and everyone else who contributed.
Please leave any feedback about bugs/problems/glitches/etc and I will try to fix them.

Thank you ;D
Sent from my HTC Merge using Tapatalk 2

faille13 said:
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you on here too

Lol yeah, I'm everywhere.
Sent from my HTC Merge using Tapatalk 2
---------- Post added at 01:34 PM ---------- Previous post was at 01:12 PM ----------
I don't get around here too often. I haven't seen a dedicated forum for my merge yet.
Sent from my HTC Merge using Tapatalk 2

GPS problem
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .

Gytixas said:
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Click to expand...
Click to collapse
Hmm.. i'll look into it.

I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks

Mistake
sorry sorry, GSM works perfect, Just needed to reboot. Thanks a lot. but Bluetooth and GPS doesn't work either. Plz fix these bugs ! Thanks

nikoloz995 said:
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Click to expand...
Click to collapse
+1
development of the firmware is?

Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.

lexikonlover said:
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
Click to expand...
Click to collapse
APN backup and restore app worked for me on US Cellular (backup apn from stock install, then restore to CM7), though I had to switch to GoSMS as a messaging app for MMS to send properly (stock app would receive but not send MMS - SMS worked normally in both). I had no success manually entering the apn info - didn't seem to have any effect when I tried.
@JianC
I found an issue with the 20130121 version from Jan 21 you posted on 2fastroms: If the phone is left on the charger it will charge all the way up, then discharge all the way back to zero while still plugged in. It still displays that it is at 100%, but then abruptly drops to whatever the actual charge level is after a few minutes of use. I've tried wiping battery stats to no effect and it works properly in stock rom. This is the only bug I can't seem to work around... Any fix or suggestions for things to try would be most appreciated! Thanks again for your work on this ROM!

Fixed GPS (and other issues), please see OP!
EDIT: I'll look into the apns issue... I don't use my Merge on CDMA so it's a stab in the dark.

The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!

jianC said:
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
Click to expand...
Click to collapse
CM10.1 availible to test?

DJ_MiX said:
CM10.1 availible to test?
Click to expand...
Click to collapse
Nope, he working on kernel .
http://review.evervolv.com
Sent from my HTC Merge using xda premium

If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.

linuxsociety said:
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
Click to expand...
Click to collapse
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
@ everyone: CM9 for the htc merge is here!: http://forum.xda-developers.com/showthread.php?p=44487058#post44487058

jianC said:
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
Click to expand...
Click to collapse
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!

linuxsociety said:
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
Click to expand...
Click to collapse
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.

jianC said:
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
Click to expand...
Click to collapse
This sounds about like the exact same issues that was experienced when I was helping hashcode work on the original kindle fire device and getting it to work with ICS. I 'think' with the HTC it shouldn't be near as hard to resolve the issue to get full hw acceleration, memory mappings camera/gps and all the extra bells and whistles if we make an attempt at backporting the necessary support into the .35 kernel instead of trying to upgrade * to 3.x which will be adding to the work and break more things than it fixes. Since HTC apparently isn't going to be releasing any updates for the device it looks like it is going to be left all up to us to make one of two decisions:
1) backporting kernel - only the few things remaining needed for our current working GB kernel to have full support for ICS/JB roms
OR
2) updating to 3.x.x and merging HTC fixes and 3rd party patches -through several mainline kernel patches and keeping the proprietary htc addins compatible.
My opinion/suggestion:
I'd think of the two options that backporting would be the most logical answer to the equation since we are only missing support for few things and you already have everything working except the camera, ION, BINDER(?), and other >=3.0.0 android patches. Plus the device is pretty well coming to a good place to say cease development work and either enjoy the device or upgrade to something newer. So if we could get JB support or even just ICS working fully I think 99.99% of all owners/users would be more than 99.99% happy!! I know I would be very happy myself!

[Acer A210] CM10.2 and CM11 coming soon EDIT: Development stopped, device bricked

Sad News All,
Today I ended up with a brick in APX mode. It seems without the SBK code i cannot fix this, sending it back is impossible where i am, plus i think its out of warranty.
I will push what i have but now my development is over on this device.
Regards
darkspr1te
Hi all,
Some of you may know me from the Korean phones section where I was developing fixes for bricked phones, as I no longer have a bricked phone at the moment I moved on.
What I moved onto is opening the devices trees for the A210 tegra 3 based tablet from Acer.
yes I know there are already a few cm10 compiles out there for the Acer Axxx devices but the A210 seems to have only closed sources on the cm side and kernel, example kiwi++ based kernel/James ROMs, (if the kernel is public,then I stand corrected)
Anyway, moving on,
My current tree for cm10.2 is available on github and I will start posting compiled nightly builds as the project moves on. And develops.
For now my builds will include the cm kernel, based off kernel/acer/t30-common , mainly because I know little about kernel hacking and the goal was to get cm10.2/11 booting and usable.
Current status
CM10.2
1. WiFi working
2. Touch working
3. Sound fully working
4 no internal/external SD card yet
5 USB devices are working
6 display has flicker but otherwise fully working
7 cwm is working, touch to follow
8 PA-gapps / play store working
9 battery life untested yet
10 custom kernel/CPU gov's - not started yet
CM11
non-booting.
compiles ok but having issues with selinux
require EXT FS ext attrib also must be set in kernel
You can find my cm10.2 online on github, my cm11 tree is staying closed for now while I iron out some hectic bugs that have the potential to brick the device (so far I keep loosing touch and sound even across ROMs)
Anyway, onto the meat of it , if you want to compile yourself, pull the trees from here
https://github.com/darkspr1te
I also want to document some of the development process here too, time allowing (mods gods allowing)
Compiled builds to follow for now, enjoy the reading.
Darkspr1te
Sent from my A210 using Tapatalk

CM10.2 Beta available
Hi All
Here is working beta of CM 10.2.
So far its mostly stable
http://www.sendspace.com/file/e7dx2x

And Now Onto CM11
Current Status
We Can BOOT!!
{
"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"
}
A510 Thread Where i posted pictures of CM11 booting
Wifi starts up but cannot find any access points, camera working sometimes, no sound, sd card work, ext sd card is not, usb is not working.
sensors not working
Must say, its fast but that could be because i've not go other parts up and running.

hi OP
i have a acer s500 cloudmobile and we have been trying to get cm10.1/above o it but
we havent been able to boot
something with kernel or such
we have dmesg and logcat
if possible could you take a look?
thank u
Sent from my CloudMobile using xda app-developers app

SpaceCaker said:
hi OP
i have a acer s500 cloudmobile and we have been trying to get cm10.1/above o it but
we havent been able to boot
something with kernel or such
we have dmesg and logcat
if possible could you take a look?
thank u
Sent from my CloudMobile using xda app-developers app
Click to expand...
Click to collapse
Sure, no problem but use pastebin or code tags or attached as file.
I am personally not familiar with that device , what's its CPU / specs
Sent from my a210 using Tapatalk

darkspr1te said:
Sure, no problem but use pastebin or code tags or attached as file.
I am personally not familiar with that device , what's its CPU / specs
Sent from my a210 using Tapatalk
Click to expand...
Click to collapse
Here is the Dmesg http://pastebin.com/3Dc7nybL
and here the logcat
http://pastebin.com/cAQuVHXC
Our device configs we used ( github.com.vachounette )
Device specifications.
http://www.gsmarena.com/acer_cloudmobile_s500-4542.php
http://www.phonearena.com/phones/Acer-CloudMobile_id6926

SpaceCaker said:
Here is the Dmesg http://pastebin.com/3Dc7nybL
and here the logcat
http://pastebin.com/cAQuVHXC
Our device configs we used ( github.com.vachounette )
Device specifications.
http://www.gsmarena.com/acer_cloudmobile_s500-4542.php
http://www.phonearena.com/phones/Acer-CloudMobile_id6926
Click to expand...
Click to collapse
On initial look it's more like a issue with blobs, but there are a fw other errors i can help with
Code:
D/TelephonyManager( 1060): No /proc/cmdline exception=java.io.FileNotFoundException: /proc/cmdline: open failed: EACCES (Permission denied)
This is a permissions error , in your init.device.rc file you need
Code:
chown radio radio /proc/cmdline
chmod 0777 /proc/cmdline
it should be around the insmod statements or other chmod statements
Looking at the device trees and prop files i can see some of the file are not blobs but are built by cm at build time, example is power.default.so, they should not be included in the prop file AFAIK, but i could be wrong.
i am no expert, i am still learning this myself (spent 3 days chasing a wifi bug only to realize i forgot setup the mac address) anyway my feeling is blobs, have a look at similar msm8960/8660 devices and see how minimal their prop files are,
is can see surfaceflinger dying, on my devices i get that when i get wrong blobs in place, i copy across .so lib files that are built by cm or if my blobs are way off.
are you getting bootlogo ?
darkspr1te

i got the Kernel bootlogo (acer) but then its just blackscreen
will check the stuffindeed
but also when compiling we have tons of errors witg files like
camera.msm and hw.msm etc
Sent from my CloudMobile using xda app-developers app

I am soooo excited to see this!
Might even be conjoled into assisting with development
Sent from my GT-I9505G using Tapatalk

SpaceCaker said:
i got the Kernel bootlogo (acer) but then its just blackscreen
will check the stuffindeed
but also when compiling we have tons of errors witg files like
camera.msm and hw.msm etc
Sent from my CloudMobile using xda app-developers app
Click to expand...
Click to collapse
Black screen is because surfaceflinger has not come up, I get that always with blob issues, concentrate on the blobs in lib/ego and lib/hw,
For my device I ended up using blobs from a random source just to get the egl gfx started and in turn surface flinger.
Sent from my a210 using Tapatalk

Sc4ryB3ar said:
I am soooo excited to see this!
Might even be conjoled into assisting with development
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Just a quick update on cm11 status :-
WiFi working
gfx working
Bluetooth working (profiles need updating, audio only at moment)
Audio working
Sdcard correct mounting
Sensors and camera are still a issue.
USB working
Joypads working
USB network/WiFi/3g working mostly
Google play/gapps from PA reported for 4.4 is working
Am currently writing this from cm11 so its stable for the time being. Going to run for a few days to test.
Darkspr1te
Sent from my a210 using Tapatalk

Just a FYI... online nandroid and nandroid manager now compatible with a210.
Took some digging but found and got devblock info to app developer
Sent from my GT-I9505G using Tapatalk

Sc4ryB3ar said:
Just a FYI... online nandroid and nandroid manager now compatible with a210.
Took some digging but found and got devblock info to app developer
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up, that will be handy.
Sent from my a210 using Tapatalk

CM11 Beta test ##WARNING - DEVS ONLY ##
Hi All,
I though i would post one of my early beta's of cm11.
sensors still not working, camera also , sdcard1 having issues at random times too. Wifi, bluetooth and audio work,
Remember this is a work in progress.
CM11 beta
and a recovery image compatible with cm11 set metadata kernel ext4 FS security thingy
recovery.img
this is not intended as a daily use nor intended for general public, it has a chance to brick your device if not carefull or you dont know what you are doing, it's a development release , i need to clean up my commits and push them back then the tree should be able to build without issue.
once ive cleaned up my code and changes i will return to debugging.
please no filling up the thread with install noob Q's, legit bug reports, logcats etc only.
darkspr1te

darkspr1te said:
Hi All,
I though i would post one of my early beta's of cm11.
sensors still not working, camera also , sdcard1 having issues at random times too. Wifi, bluetooth and audio work,
Remember this is a work in progress.
CM11 beta
and a recovery image compatible with cm11 set metadata kernel ext4 FS security thingy
recovery.img
this is not intended as a daily use nor intended for general public, it has a chance to brick your device if not carefull or you dont know what you are doing, it's a development release , i need to clean up my commits and push them back then the tree should be able to build without issue.
once ive cleaned up my code and changes i will return to debugging.
please no filling up the thread with install noob Q's, legit bug reports, logcats etc only.
darkspr1te
Click to expand...
Click to collapse
btw
does gps work in ur builds ?
on mine not :/ (cm10)
this is log
Sent from my CloudMobile using xda app-developers app

SpaceCaker said:
btw
does gps work in ur builds ?
on mine not :/ (cm10)
this is log
Sent from my CloudMobile using xda app-developers app
Click to expand...
Click to collapse
hi,
No gps also not functioning yet, but i am not sure what is causing the issue as even in factory rom it's not working, it's on the list though.
darkspr1te

hmm in a factory rom not working thats bad
in my factory rom gps works fine xD
only in cm10 not
Sent from my CloudMobile using xda app-developers app

Anyone looking for a ROM for Acer A210..........SEE BELOW
FYI
IF YOU DECIDE TO TRY THIS, BE SURE TO READ ALL THE STEPS A COUPLE OF TIME. BOTH HERE AND ON THE FORUM
I HAD NO PROBLEM BUT AS ALWAYS I CAN NOT BE RESPONSIBLE!!!!! I HAVE ONLY INSTALLED 1 TIME. I ALSO HAD NOTHING TO DO WITH THIS ROM. I only found it while looking for an A210 ROM, there is an A210 and an A211 ROM so make sure you get the 1 you need.
there is a an Omnirom 4.4.2 in a German forum, the ROM is in English and if you go to the forum with Google Chrome. Chrome will ask you if you want to translate to English. I have just downloaded and install the Omnirom about 5 hours ago and so far all is working great, think I saw where NFC is not working but haven't tried NFC. You will have to download the omnirom, kiwi recovery(by cwm), supersu and 4.4 gapps. If you have quickboot app from Play, you can do it all without a PC,by downloading all to your device and move to ext sd. Boot to recovery with quickboot, do a backup,then install kiwi recovery and go into Advance and reboot recovery, you will then be in kiwi recovery, wipe/factory reset, Advanced wipe all but ext SD. Once that is done and before rebooting system do a wipe/factory reset, then before rebooting still flash supersu and 4..4.2 gapps. I haven't tried restoring my backup with Kiwi, so I would have the cwm recovery.zip on your extsd card also. Also I have had problems connecting to a PC with USB, since I installed this omnirom 4,4,2 but haven't tried to long as of yet.
Here's the forum link
http://www.android-hilfe.de/custom-r...stone-1-a.html
Sent from my A210 using XDA Premium 4 mobile app

OmniRom 4.4.2
Also in Developer Option, you can add boot to Recovery to the Reboot menu.
Sent from my A210 using XDA Premium 4 mobile app

[HOW TO][4.2.2+] Port Custom Roms From Other OMAP 4 Devices (REVAMPED!)

Introduction​Greetings Atrix 2 community! I'm here to guide you the best I can to being able to port custom (not stock) roms that aren't available for the Atrix 2 from other Mototrola OMAP 4 devices, such as the Droid RAZR, Droid 4, etc. It may not be limited to only Motorola phones, but rule #1 of porting is that the CPU HAS TO BE THE SAME OR VERY SIMILAR! Rule #2 is that you can ONLY port from the same android custom rom version, e.g. 4.2.2 - 4.2.2, not 4.3 to 4.2.2, etc. due to major file differences in most cases. (More rules are mentioned within the linked guides) Rule #3 is that they have to either be GSM band or be able to completely convert from CDMA to GSM though patch.
Wait a sec, what do you mean by "porting roms"??? This link will help you get started on knowing what you'll be learning to do here. The top benefit to all of this is to provide yourself with roms from other compatible devices as well as learn what happens behind the scenes in a custom rom. I recommend that you try porting GSM Droid Razr/UMTS_Spyder roms to get yourself into it before attempting any other device.
Now that's out of the way, in this tutorial/guide, I'll be making a lot of reference links to save some time explaining certain steps since that's where I learned how to do this. I take no credit for each OP's guide and all credit goes to them and others who assisted, I'm just sharing. If you want to see a successfully ported example, go to page 2 of this thread.
"ENOUGH TALK, LET'S DO THIS!!!" ...is what all will be saying while reading my boring intro, but the next section is something you need to read, don't say I didn't warn you!
Disclaimer and Precautions​>This is a risk YOU are taking, you will be possibly voiding YOUR warranty and may even brick YOUR phone due to lack of instruction following
>I am not a developer, just a normal user who wants to share something useful.
>I am not responsible for whatever happens during your port projects, nor are any of the other guide OPs and so on. MAKE BACKUPS!!!
>This is a choice, your choice, I'm not forcing anyone to do this so please use your head when you want to blame.
>USE BOOT MENU MANAGER (by Team Lens from the play store), NOT ATRIX 2 BOOTSTRAP PLEASE!!!!!!!!!!!
>After installing and setting up BMM, MAKE SYSTEM PARTITIONS (3-6) AND USE ONLY THEM FOR FLASHING WHILE TESTING, i.e. DO NOT FLASH ON SYSTEM 1 (in case of bootloop or worse).
>Do not flash with JBX kernel until you are able to get your ported kexec rom at least 95% functional. You may test it afterwards.
>Ported roms will have the same bugs as they had for their corresponding device and they won't fix any of our bugs (maybe).
>Some roms require more specific actions to successfully port them with everything working (MIUI, PA, etc.) and from other devices outiside your own.
Porting Tools Needed
1. A Brain with an open mind (CRUCIAL)
2. Time and patience for trial and error (VERY CRUCIAL, so if you don't have enough, try again when you do)
3. A Good amount of disk space, so if you have less than 1gb available, DELETE SOME OF THAT PORN!!!:laugh:
4. A file comparison tool; use WinMerge for Windows or Meld for Ubuntu
5. A compression tool such as WinRar, 7zip, or any other that can make .zip files (typical rom extension)
6. Notepad++ (for editing file scripts)
7. A rooted Atrix 2 that is on at least 4.04 ICS stock kernel, NOT GB!
8. Boot Menu Manager Recovery with an unused System set up for testing your port
NOW we're ready to begin Porting!​There are many ways to port roms, however there are 2 main categories of porting methods:
The Basic Porting Method - Using the Base (Previously known as Method 1)
Basically follow all the instructions in this thread for using the working base rom. I highly recommend using the port rom's corresponding base (CM, AOKP, PA, etc), unless you're porting a rom that we already have but want to update it. This is another good guide that has similar instructions.
*NOTE*: This method rarely ever works for our OMAP devices, but other device users might benefit from it.:good:
The Actually Working Porting Methods - Using the Port itself (Previously known as Method 2)
This style of porting has proven to work for all the roms the A2EPT has ported thus far for all Moto OMAP4 android versions. However, for the sake of organization I will outline furter devisions in the methods used for general and specific cases. These methods will be called the Motorola Porting Methods (MPM), but can be useful to any other device based on recent feedback.
Motorola Porting Method 1 (MPM1) - This will outline the surefire steps that will usually port roms from our Moto OMAP cousins with everything functional!:good:
These steps below involve a lot of copy and paste using your comparison tool of choice: ('unique'=files on either left or right alone)
>Start off with the updater script, compare the ones for your base and port and copy only the single line differences from base to port.
>After you copy everything except those consecutive lines to the port's updater_script, now go to system/etc and copy apns_config, mkshrc, firmware folder and all unique items from base to port.
>Next, head on over bin and copy over all unique unique bin files over to your port, then copy rild.bin over as well and that's all.
>Next victim is the most influential one; LIB FOLDER! Starting off with the hw folder, copy all the edison.so files over to you port rom.
>Afterwards, replace the entire modules folder and copied over all unique lib*.so from base to port.
>Locate all libs with ril in their names and replace the ones in your port
>Now head onto the xbin folder, and copy over all unique files from base to port.
>That should do it for xbin, so now head on back to /sysem and copy the entire vendor folder, then do the same for usr.
>Finally, build.prop is your last stop and to make it simple for everyone, download and use this sample build.prop as a guide for what lines you should always replace: Sample build.prop
Motorola Porting Method 2 (MPM2) - This is specifically for all Moto OMAP 4.3/4.3.1/4.4+ roms and others that need to replace the storage_list.xml such as the Droid 4 and Droid Bionic (previously called Method 2.5 behind the scenes ):
>Perform all the steps in MPM1 on the desired 4.3 or whatever rom that needs the replacement.
>In a working 4.3/4.3.1/etc. rom for the A2, open system/framework/framework-res.apk with winrar or any other file compression tool.
>Look for the storage_list.xml file in /res/xml and extract it to your Desktop (or wherever you want)
>Now open your corresponding 4.3+/etc. port rom and navigate all the way to the /xml folder in framework-res.apk
>Take your extracted storage_list file and replace the one in the port with it, AND THAT'S IT!!
>Test to see if it is actually booting and as long as you can get to the setup screen without bootlooping, you are home-free!
!NEW UPDATE VIDEO!: I received a suggestion to actually show how to do the above Moto porting methods, now that I got the time, I have done just that for all those who were having a hard time with following my steps! Here it is for all who are interested:Turorial Video, it's 27 minutes of hearing my boring voice so prepare yourselves!:laugh:
Common Challenges with Porting (experiences may vary)​
This sorta depends on which method you used to port you rom, but I'll list all the typical expected problems I at least faced and (possible) solutions:
Issues Faced with Both Methods:
1. The rom doesn't boot past the boot animation - this may be due to the updater script's permissions and/or build.prop mistakes, so make sure everything is in place according to the instructions.
2. It boots to the setup screen but there are numerous crashes, then it bootloops - this is a system/app, /lib or /etc problem and you may have to try replacing the android_server.so and media_jni.so from the ported rom, but a logcat may be needed.
3. "YIPPEE, IT BOOTED PAST SETUP, but where is my signal?" - Baseband issues *sigh*, its very tricky to get this part so you may either need to move signal and modem-related files from your base to your port and check build.prop
4. "My SD card won't mount?! D:" - This can be fixed by going into your ported rom and opening system/framework/framework-res.apk with WinRar/7zip then go to res/xml/storage_list.xml and open it. Then go to vold.fstab in system/etc and make sure that the 'sdcard' numbers are the same, e.g. sdcard0, sdcard1, etc.
5. "WTF, I'm not rooted/ " - LOL, I experienced this in porting the kitkat rom below using the 1st Method. xD If that's the case, you need to copy these files from /lib in port to base: libandroid_runtime.so, libcutils.so, libbinder.so, libutils.so, libsqlite.so and libsqlite_jni.so.
6. "Ok, I have signal and most things working but x always FCs"- at this point, you're a bit better off and that can be solvable if you specify what it is in this thread.
All other problems may need logcat, but before posting them here, search in this thread yet again to see if they were solved.
Credits are Needed!!!
Credits go to the OP's of these guide threads
XDA and Google search for when I was lost as a lamb xD
qkdxorjs1002 for his Carbon Rom 4.4.1 kitkat (below)
alteredlikeness, Ravikirancg, deveshmanish, dtrail1, all Motorola OMAP 4 developers and rom maintainers/porters.
Respective custom rom developers; CM, PA, PACMan, AOKP, Carbon Rom, Liquid Smooth, etc.
My curiosity and stubbornness (LOL, kidding).
And last but not least, the Atrix 2 community for providing a noob like me with the best first android experiences I never expected!

Proof!!!
Screenshots
{
"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"
}
Examples
Currently I could only upload this due to slow bandwidth, but I will upload the Non-kexec Liquid Smooth another time (I can re-kexec it on request).:good:
Carbon 4.4.1 Using the Atrix 2 CM 11 as a Base rom (Update on trying this out - it works ok enough but has some issues if you reboot it sometimes so don't use it as a daily driver, just a reference point!)
~UPDATE~: Alrighty, I managed to upload the ported 4.2.2 Liquid Smooth v2.9 that I made using the 2nd Method. It's my current daily driver as it's really stable for the most part, it has new transition animations and it's non-kexec so it has very good battery life! :good: (Note: Do not flash JBX kernel with this, it won't work!)
Liquid Smooth v2.9 using the 2nd Conversion Method, grab it and enjoy!
[Small Backstory]Just last week, I became curious in wanting to know how to port a rom after learning how to de-kexec them thanks to our own alteredlikeness and Ravikirancg. So most of last week I went about trying to port the last 4.2.2 version of Liquid Smooth v2.9 rom since our original porter, deveshmanish, can no longer do so. So since we had LS v2.8, I felt it wouldn't hurt to try, but it was much more challenging than I thought! But I continued to persevere and eventually I successfully ported it which will be shared in this tutorial. [/Small Backstory]
Click to expand...
Click to collapse

Samsung Galxay Roms Incoming!
Reserved for anything else I need to add!:laugh: ~New Update, now I have something to add~
Samsung Galaxy OMAP 4 Porting (Galaxy S2-I9100G and the Galaxy Nexus - all variants!)
In this post, I'll be Introducing the porting methods me and my team have made for porting roms from these two S. Galaxy phone series. The methods are basically the ones used for the Moto OMAP phones as well but with additional steps that are needed for full/almost full functionality.:good: (NBnly rom versions up to 4.3.1 can be ported with methods 2 and 3, 4.4+ roms cannot be ported at this time).
Notes about Samsung Galaxy ROMS:
Porting from these two phones has a higher difficulty than Moto phones in some cases, so patience is NEEDED!
On startup they will have all sound options enabled
The Galaxy Nexus-based roms will have the Nav bar on startup
Their battery charging lights are always enabled (should be able to turn that off in Settings)
Samsung-unique features don't work on our phone (duh)
On some roms, the lcd density will be high (large screen items) but they have dpi settings so don't panic lol
Only a few roms still don't have the 1% battery hack, so if you don't mind that then great!
Samsung Galaxy Porting Method 1 (SGPM1) - The "Preview Method".:cyclops:
I'll write this and the other methods in more detail when I revamp my thread in the coming month. But basically this can be done by doing the same steps in the 2nd Porting Method along with the additional steps I stated for getting 4.3/4.3.1 roms to boot (replacing the storage list). It is HIGHLY recommended that you use bases from our phone that are most compatible with the rom you want to port based on their sources.
Why is it called the "Preview Method"? Simple, because you won't be able to use the rom with some of our components working like audio, camera and wifi. However, if you want to get wifi working then replace these additional files after you've replaced the ones above:
In /system/bin, replace the two wpa binaries
In /system/etc, replace the entire wifi folder
And in /system/lib, replace lbhardware_legacy.so and libwpa_client.so
This method is applicable for all android versions based on our tests, but not all roms will boot even with this method, so keep that in mind. My personal advice is to test your port first without gapps to see if it boots and see what it has since gapps are pointless without wifi and audio.
Samsung Galaxy Porting Method 2 (SGPM2)- The "Lucky Porter".:fingers-crossed:
In this method for SG roms, the same steps for SGPM1 are involved except for further replacements that fully ports your SG rom with whatever is working in your base. This works for some roms but not all, so if it doesn't work for you then refer to SGPM3 below.
+Start off with modifying the updater script and build prop based these examples:
+After performing all the steps of SGPM1, go inside your system folder and replace the entire bin folder
+Afterwards, go inside the lib folder and replace everything except libandroid runtime, libandroid servers and libmedia jni.
+Make sure that the build.prop and updater script have everything in place, then you can zip the META_INF and system folders into a new rom zip and test away!
+If you're lucky enough to have it boot and the charging LED changes colour then you're at least very close to fully porting it if it didn't already do so!:good:
Samsung Galaxy Porting Method 3 (SGPM3) - The "Advanced Porter".
This advanced method is for porting SG roms that would otherwise not works as desired with SGPM2 by either bootlooping, booting with endless FCs, etc.
#Alrighty, go to the app folder where the only thing you copy over is OMAP 4 parts.apk from your your base (and any other app you wish to add).
#Now onto the bin folder, in there you will copy over all unique files from the your base and these specific ones; adb, app process, atrace, dalvikvm, dbus-daemon (if present), mediaserver, rild, sensorservice, tfdaemon and the two wpa binaries.
#Next in the etc folder, you will copy over all unique files and folders except the entire permission folder, dhcpcd, security, updatecmds and ppp. Then go and copy the unique files inside the permissions and in init.d folders. Also if there's a paranoid folder present, use one of our pacman roms to replace it in there so that there are no dpi issues.
#Back in system folder, replace the entire usr and vendor folder, then go to framework to replace the storage list.xml in framework-res.apk/res/xml with the one in your base.
#Finally in the lib folder, replace all of the folders inside lib, then libaudio ext, libaudioflinger, libaudioeffect jni, libaudioutils, libbinder, libc, libcamera client, libcutils, libdl, libdomx, libexif, libhardware and hardware legacy, libjpeg, liblog, libmedia, libmm osal, all of the libOMX files, libril files, libsensorservice, libstagefrighthw, libutils, libwpa client and libz. For making non-kexec 4.2.2 roms, delete libedid.so and libselinux.so as well.
#Make sure that the build.prop and updater script have everything in place, then you can zip the META_INF and system folders into a new rom zip and test away!
#If it boots, has wifi and camera working but still no audio, then go back to your port folder, open system/lib and replace everything except libandroid runtime, libandroid servers and libmedia jni.
That's all for now, stay tuned for more from the A2EPT!

nice .... will give a shot in free tym ....
thanks a lot :good:

shardul.phatak said:
nice .... will give a shot in free tym ....
thanks a lot :good:
Click to expand...
Click to collapse
No problem, I hope this will help liven up the place by giving people something to do while they wait on updates.

Awesome!!!
Sent from my MB865 using Tapatalk 2

Been up all night porting. Cant get past boot animation D: but its a WIP for me lol great guide!

i had been working on porting for a while,
thanks ace, this guide really helped me a lot. and pointed out where i went wrong.
I have successfully ported ROM "X" i shall not name it yet , i'll keep it a suspense until i get the devs permission.
it's just a start for many things, right now i'm working on a few bugs.
thanks again ace for taking your time to share us your knowledge.

Uzayr said:
i had been working on porting for a while,
thanks ace, this guide really helped me a lot. and pointed out where i went wrong.
I have successfully ported ROM "X" i shall not name it yet , i'll keep it a suspense until i get the devs permission.
it's just a start for many things, right now i'm working on a few bugs.
thanks again ace for taking your time to share us your knowledge.
Click to expand...
Click to collapse
You're welcome Uza and I'm very happy to hear that! Looking forward to what it is and I'll continue to help where this is concerned. :thumbup:
Sent from the Ace's MB865 using xda-developers app

GJ awsm Guide..............

atrix2man said:
Been up all night porting. Cant get past boot animation D: but its a WIP for me lol great guide!
Click to expand...
Click to collapse
Thanks man! Which rom are you trying to port and which method have you used to do it?

i got baseband issues. could you point out where exactly are the baseband related files located?
Sent from my Edison powered by Magical Unicorn bytes

Uzayr said:
i got baseband issues. could you point out where exactly are the baseband related files located?
Sent from my Edison powered by Magical Unicorn bytes
Click to expand...
Click to collapse
The baseband related files are typically located in primarily system/lib and rild.bin system/bin. Which rom exactly are you trying to port and what method are you using to port it?

i ported a KK rom using slimkat as base. everything works fine and perfect. just rrying to figure out the baseband issue.
i used the second method btw.
Sent from my Edison powered by Magical Unicorn bytes

Uzayr said:
i ported a KK rom using slimkat as base. everything works fine and perfect. just rrying to figure out the baseband issue.
i used the second method btw.
Sent from my Edison powered by Magical Unicorn bytes
Click to expand...
Click to collapse
Ahh, well that's the thing about method 2; it can usually get almost everything working except baseband, which I could never get with Carbon KK :/. I highly recommend trying method 1 as well to see what works/doesn't work, but if Method 2 is really that good reread the Step 4 and 5 to make sure you got everything including what's in the build.prop. Good luck and report back whenever possible!:good:

method 1 gives bootloops, everytime. i tried it with the one im working and my previous projects.
if i found out a way past the bootloops that would be a progress

Updated the OP and uploaded my first ported Liquid Smooth v2.9 (found on page 2 under Examples)!

Aceofzeroz said:
Updated the OP and uploaded my first ported Liquid Smooth v2.9 (found on page 2 under Examples)!
Click to expand...
Click to collapse
Thank you so much Ace for the non-kexec Liquid Smooth ROM, it was my favorite ROM until SlimROM 4.3 showed up . I am downloading now and hopefully use it as my daily as the battery life on these non-kexec are way too cool. Just a request Ace, any chance of you doing a non-kexec on SlimROM 4.3?
Keep up the good work and thanks for the Porting guide.:good:

minhajlk said:
Thank you so much Ace for the non-kexec Liquid Smooth ROM, it was my favorite ROM until SlimROM 4.3 showed up . I am downloading now and hopefully use it as my daily as the battery life on these non-kexec are way too cool. Just a request Ace, any chance of you doing a non-kexec on SlimROM 4.3?
Keep up the good work and thanks for the Porting guide.:good:
Click to expand...
Click to collapse
You're welcome minh! I'd love to de-kexec 4.3 roms and above, but I'm afraid I can only do 4.2.2 since I use other non-kexec roms to do it and they all stopped at that version.
I'm not entirely sure since altered taught me, but it's because 4.3+ would probably use more updated file structures. Don't fret, I'll still give it a shot and let everyone know if it's doable.
Sent from the Ace's MB865 using xda-developers app

Aceofzeroz said:
You're welcome minh! I'd love to de-kexec 4.3 roms and above, but I'm afraid I can only do 4.2.2 since I use other non-kexec roms to do it and they all stopped at that version.
I'm not entirely sure since altered taught me, but it's because 4.3+ would probably use more updated file structures. Don't fret, I'll still give it a shot and let everyone know if it's doable.
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
Thanks Ace. I am running no-kexec LiquidRom on system 4, the only problem I encountered so for is I can't install XDA Developer's app. I think it is something to do with external memory, other than that its great . I'll run it for a couple of days and see for battery performance, usually no-kexec gives pretty good battery performance. I get about 2 days with moderate to heavy use, on Alt-CM10.1. :good: