Database Users

[Modems] Modem files for CWM and Odin

Hello friends,
as some of you will know, modem is that part of rom which is responsible for network communications. When people install custom roms, they are stuck on the modems which are included in the roms and i've seen many people asking how to change the modem to their locale. Below is the list of some modem files. I'll try to update the list as much as I can. Instructions on how to install will also follow soon.
Post 1- List of Modem files by country, version number and release date. You can decide what modem is best for you.
Post 2- Links of CWM flashable modem files.
Post 3- Links of Odin flashable modem files.
Post 4- Instructions on how to flash (both CWM and Odin)
S.no-----------------------------------------------Country---------------------------------------Modem Version--------------------Release Date
----ASIA----
1. ---------------------------------------------------India----------------------------------------------DDJV7-------------------------------March 2012
2.----------------------------------------------------India----------------------------------------------DDJV5-------------------------------June 2011
3.----------------------------------------------------India----------------------------------------------DDJV4-------------------------------May 2011
4.----------------------------------------------------India----------------------------------------------DDJP2-------------------------------Nov 2010

CWM Recovery Flashable Files
----Asia----
1. DDJV7
2. DDJV5

ODIN Flashable Files
----Asia----
1. DDJV7
2. DDJV5

Reserved for instructions

thanks for ddjv7. I will compare it with ddjv5 which suits me best so far

India-based DDJV7 modem/radio
RITZYtheDEVIL said:
CWM Recovery Flashable Files
----Asia----
1. URL="https://docs.google.com/file/d/0B_7EhmYHATX7QzVrVVZ3UjdFeFk/edit?usp=sharing"]DDJV7
2. URL="https://docs.google.com/file/d/0B_7EhmYHATX7cUNxaDRoc1h1bWc/edit?usp=sharing"]DDJV5
Click to expand...
Click to collapse
I'm trying to CWM flash DDJV7 on my old I9000 after a clean install of the latest CM11 snapshot & it failed, though the status was 0.
Just wanted to know if it's compatible with this CM version before I try to mess more with it?
If it is compatible, I'll try & capture a log of the failure next time I try it.
Current baseband is XXJVT which is the default from that ROM but I'm facing call drop & disconnection issues on long calls with this modem.
Wanted to try out DDJV7 since that was the last that Samsung provided for India on the I9000.
Understand that this is a very old thread but my issue is relevant to this thread to trying here 1st.
Thanks!

No, these files are old and were meant for cm 9, etc. CM11 is quiet different.

jaNgamdurvaani said:
I'm trying to CWM flash DDJV7 on my old I9000 after a clean install of the latest CM11 snapshot & it failed, though the status was 0.
Just wanted to know if it's compatible with this CM version before I try to mess more with it?
If it is compatible, I'll try & capture a log of the failure next time I try it.
Current baseband is XXJVT which is the default from that ROM but I'm facing call drop & disconnection issues on long calls with this modem.
Wanted to try out DDJV7 since that was the last that Samsung provided for India on the I9000.
Understand that this is a very old thread but my issue is relevant to this thread to trying here 1st.
Thanks!
Click to expand...
Click to collapse
No, these files are old and were meant for cm 9, etc. CM11 is quiet different. And I dont own the device anymore, so cant make cm11 flashable zips now.

DDJV7-I9000-JB-KK.zip

Thanks!
RITZYtheDEVIL said:
No, these files are old and were meant for cm 9, etc. CM11 is quiet different. And I dont own the device anymore, so cant make cm11 flashable zips now.
Click to expand...
Click to collapse
No worries, thanks for replying anyway, .
Even the thread is really old.
..::WD40::.. said:
URL=http//www48.zippyshare.com/v/u0S9MROP/file.html]DDJV7-I9000-JB-KK.zip
Click to expand...
Click to collapse
It worked! I dirty-flashed the .zip & it installed successfully.
The immediate change I observed was the stable full signal bars with signal fluctuations around -75dBm (screenshots attached).
With XXJVT the signal used to fluctuate a lot & around 85 - 90 dBm, sometimes remaining above -100 dBm.
So prima facie it looks like a definite improvement in the past 2 days. Will keep observing & report back in the next 3 - 4 weeks including call quality & battery performance (not much info available about DDJV7 it seems).
Also planning to do a clean install of everything this week (hopefully) & see how it goes (with a "de-bloated" CM11).

[Q] Support for LG G3 with Cyanogenmod 12?

Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.

Yup, i confirm, doesn't work on lg g3. Pitty.

joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
Sorry for my delay. I started a re-coding "marathon" on the weekend and it stretched for a week.
I intend to support the LG G3 as well as I possibly can, on any ROM. I have almost bought a G3 for testing a few times, but haven't gone through with it yet.
The CM12 kernel does not at present include the needed Qualcomm V4L FM radio "IRIS" driver.
I will try to submit the tiny 2 line config file change needed for that and see if they respond.
Someone built an FM friendly kernel and it worked, but there are/were still some audio issues. We can work around this with the new analog mode being added to Spirit2, and this should be properly resolved at some point.

Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide

joergherzinger said:
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
Click to expand...
Click to collapse
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.

WOW great news!!
Thank's very much :victory:

mikereidis said:
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
Click to expand...
Click to collapse
Great! I'm trying CM12 in my G3 and, despite some typical nightly bugs, it's working quite well. I only really miss FM radio! :fingers-crossed:

Any progress ?

ariek44 said:
Any progress ?
Click to expand...
Click to collapse
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901

will not start
mikereidis said:
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
Click to expand...
Click to collapse
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.

Phenax said:
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Click to expand...
Click to collapse
If you have the T-Mobile variant, I do not think FM can ever work for you.
As with the LG G2, only the Sprint and International variants have the FM antenna pin connected as needed to the headset jack for the antenna.
Other variants are purposely and permanently "broken" by shorting the pin to ground.
There was rumor here and there that other variants might work, but I think that was based on Spirit not showing a specific error at one point.
So, AFAICT, only the International D855 and Sprint's model.

joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
I have built a CM12 based kernel that I think should work.
I do not have a G3 so I can not test it.
I can not make any guarantees that it will boot and won't harm anything.
This is a boot.img file. Anyone flashing it should understand how to flash such a file so I won't explain.
I will submit the patches to CM once someone can verify.
md5sum ~/mikes_boot_fm_12-20150307-UNOFFICIAL-d855.img
d8080528d3f37448e57a6da84162d4df
Thanks !

Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...

joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
Click to expand...
Click to collapse
Great !
I did not touch the kernel config at all. I used this one, stock as of this morning, AFAICT: https://github.com/CyanogenMod/andr...0/arch/arm/configs/cyanogenmod_d855_defconfig
The config has this, unchanged:
Code:
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
All I did to patch/fix was this:
Code:
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris-transport.c kernel/lge/g3/drivers/media/radio/radio-iris-transport.c
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris.c kernel/lge/g3/drivers/media/radio/radio-iris.c
This copied the Qualcomm fix from the MotoG kernel source that allows radio-iris-transport to work built into the kernel, instead of only as a module.

joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Click to expand...
Click to collapse
Patch is here: http://review.cyanogenmod.org/#/c/90794/

I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.

joergherzinger said:
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
Click to expand...
Click to collapse
Maybe.
I've seen Settings crash on a few devices/ROMs.
Common AOSP Lollipop ROMs still have lots of problems.
They ALL have a nasty memory leak that gets bigger every time Spirit sends an RDS update to notification shade/remotes/lockscreen. I have to reboot my test phones every day or so to avoid unpredictable restarts when Android system_server fills its' internal table maxed at 51,200.
Stock Lollipop ROMs don't have this problem, so IMO must be some common bug in CM12 I think. (I could/should verify if Nexus/pure AOSP shares this.)

Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?

joergherzinger said:
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
Click to expand...
Click to collapse
Yes, I think so, it's just taking me a long time to do it.
The patches I provided WORK. The complaint was that IF they re-configure the kernel to use modules, then the kernel will not build and he did not like that.
Many kernels have removed modules now and it is rare to go back to modules, so I find this a bit strange, but I am not the one maintaining kernels.
The patches were not really "developed" by me. I just grabbed the very similar files from the MotoG CM12 kernel thinking they would not complain; it was just aligning the code between CM12 kernels.
My plan since the patches were rejected is to use the files from (I think) a Sony CM12 kernel that I think should work with or without modules.
But I have had a LOT of trouble getting d855 kernels and ROMs to build since my initial changes that worked AND it can take hours to build a new ROM and I still have not figured out how to build just the kernel, which is much faster.
This is the problem I had last night and the night before and I am not a ROM dev so it takes time for me to figure out what is wrong or how to fix (maybe a "make clean" or similar"):
creating userdata.img...
Running: mkf2fsuserimg.sh /tmp/tmpqdNGFw 12297699328
in mkf2fsuserimg.sh PATH=/home/m/android/system/out/host/linux-x86/bin:/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin:/home/m/android/system/out/host/linux-x86/bin:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin:/home/m/android/system/prebuilts/gcc/linux-x86/:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:/home/m/android/system/development/scripts:/home/m/android/system/prebuilts/devtools/tools:/home/m/android/system/prebuilts/android-emulator/linux-x86_64:/home/m/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/jdk1.8.0_25/bin:/home/m/b:/home/m/b/android-studio//bin/:/home/m/b/android-sdk//platform-tools/:/home/m/b/android-sdk//tools/:/home/m/b/android-sdk//build-tools/21.1.2/:/home/m/b/android-ndk-r10//build/tools/:/home/m/b/android-ndk-r10//
make_f2fs -l 12297699328 /tmp/tmpqdNGFw
/home/m/android/system/out/host/linux-x86/bin/mkf2fsuserimg.sh: line 31: 23180 Segmentation fault $MAKE_F2FS_CMD
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 261, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 255, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 241, in AddImagesToTargetFiles
AddUserdata(output_zip)
File "./build/tools/releasetools/add_img_to_target_files", line 156, in AddUserdata
assert succ, "build userdata.img image failed"
AssertionError: build userdata.img image failed
make: *** [/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip] Error 1
make: *** Deleting file `/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip'
Click to expand...
Click to collapse
With troubles like these, and ROM builds taking hours and my lack of a G3 to test, this is moving slowly.
Add the fact that I am exhausted from the last few months of MORE major changes to Spirit2, some time spent with my family and looking into Android Auto and things move even more slowly.
...And the build guide for G3 seems to have disappeared too: http://wiki.cyanogenmod.org/w/Build_Guides#vendor=%22LG%22;
...And... any chance you know the OFFICIAL CM12 way of switching between module and non-module kernels ? I know the defconfig "CONFIG_MODULES=y" thing, but I'm not sure if other changes are needed. I can do a "make menuconfig" but I'm not sure if I should write .config to the defconfig. "make config" gives a million options; I tried that and produced a kernel that probably won't even boot on a G3.
Perhaps I should post in a G3 forum section asking for help.
I posted on that patch now: http://review.cyanogenmod.org/#/c/90794/

Hi, I don't understand half you are talking about
I'm just an user who wants CM12 and FmRadio.
That being said, I can read this changelog in 777 kernel thread (http://forum.xda-developers.com/lg-g3/development/kernel-777-kernel-t3003115). Did anyone try this "radio" builds?
02/08/15
- R6
- Fix Powersuspend
- CM kernel updates
- Synaptic touch firmware update
- Separate d855 builds with fm radio module
Click to expand...
Click to collapse
(EDIT: Tried by myself. Radio works with 777 kernel. However, audio quality is quite bad.)
Second, I would like to test any beta kernels, spirit app, or whatever in my G3 D855, in order to help making it work. Please tell me how can I do it.
Thank you very much!

[HELP] thread for custom ROMs

Hello everyone.
This is a
HELP thread
for asking questions regarding custom ROMs and the issues that you might have with them for this device. Before you post, please read the FAQs at the bottom, and then proceed to ask your question.
Note - the members may or may not provide you a step by step solution, and will provide you links, please check those links carefully, and if you still do not understand, ask your question again.​
If the community notices real issues (which are different from the usual "Does this work, does this not?" questions), it will be forwarded to the respective ROM thread (or we'll request you to forward).​
Help us in keeping the custom ROM threads clean and help the developers to focus on important issues.​

Device Specific Information
Codename athene in development circles. Here, we often use G4 and G4 Plus interchangeably with athene. That's why ROM titles have the word ATHENE in them. Don't be confused.
Device names according to manufacturer - XT16xx. The xx in the end changes as per region. For instance the Indian version is XT1643.
For more information regarding the device, and the availability of ROMs, etc, go to this [INDEX] thread.
Yes, the INDEX thread is mine, I'm not self promoting, I'm linking this because the older one has not been updated in a long time, and no amount of messages to moderators seems to have any effect. If you wouldn't mind, please send a message to the moderator to make this the sticky INDEX thread to help Moto G4 Plus users.
​

Note: this information is out of date.
Common bugs
Fingerprint enrollment issues. Flash Nougat to resolve this. No, you have to flash, if you don't want to, please do not post bug reports. Follow this guide by @rahulsnair to update your phone to Nougat soak test. We have a soak test because the release version has not yet been captured for us to use. You can also (although the developer still won't accept bug reports) rename the fingerprints to add more (credits @mason2smart). Also, try this as mentioned by @__Maddy.
Camera/Video recording issues. Use the built in camera, NOT Moto Camera (the camera you had on stock ROM) as your camera. You can also use any other recording app (Cameringo, Motorola Camera, Google Camera all work just fine). And yes, Motorola Camera is different from Moto Camera. Camera issues are being sorted out by the CyanogenMod team (and will reflect on all ROMs that are based on CM), and only once those issues are sorted can the developers for this device sort any issues with ATHENE out. Note that for Moto Camera to work, you need to set the DPI (Settings > Display > Display Size) to the default one.
Video playback issues. Please use this thread by @strongst for providing logs and other details. The only OS that doesn't seem to be affected by this is Vanir.
Unable to share images/screenshots from gallery or filemanager. Sort this one out by formatting your internal storage. Credits @smitharro, here.
Chop-Chop/ Torch issues. Do a reboot. It should work then.
VoLTE issues. Follow the instructions on this thread, if that doesn't help we need logs, or we really can't help.
Mobile data intermittently stops working. See this post.
CyanMod/RR bugs​
Camera issues. Update in next build.
CypherOS bugs​
Video Recording doesn't work. Use Footej/Cameringo Lite for now.
External SD read error in inbuilt file manager. Use another file manager.

LOGS
(and why we keep asking for it.)
Imagine you make a cake. And you give it to a person, who says he doesn't like it. And then leaves. You have no idea what went wrong with your food, why that person doesn't like it, what that person would see as an improvement in your cake. You eventually go mad as more people keep saying they don't like your cake, and leave without further information.
This is exactly what happens when you state your bug (that the developer cannot easily reproduce) and then leave it at that. The developer cannot figure out what went wrong. So, to find out what could possibly have gone wrong, (s)he requires a log. The log tells the developer what all errors have occurred, and what could be done to possibly fix them.
Logs are also known as logcat (and other types). Find a helpful tutorial on how to take logs here.
Best way to present logs is to either upload the file to a hosting site, or paste the contents on pastebin, or hastebin, and share the link here.​​

How to report issues here​The aim of this thread is to become a source for all members to ask questions on issues they face in all ROMs. So report your bug after specifying the ROM, and the build date. For instance, if I am using CyanMod from Silesh.Nair, which he uploaded for use on 21st April 2016, then I start my issue as
CyanMod 20160421
and we'll help you sort out your issues as much as we can, and if we are stumped, the developers will help you out. ​​

Okay, last one, stop.

Solution For Single FP over MM baseband
If anyone don't want to Flash Nougat Soak or Modem, follow this procedure ( I'm using 5 FP over MM baseband )
** Firstly you will need Fresh start **
On fresh start complete setup wizard process, DON'T add security and FP when asked..
After seting up device go to
settings > security
Add your preferable unlocking option,
Now for FP,
Add your 1st FP, it will get successfully enrolled,
And now you have 4 FP left to add..
** Follow common procedure for remaining 4 FP **
Now add next FP ( add one FP only)
Obviously you will get "Enrollment Error" on any next FP..
After every Enrollment Error Close Setting app completely ( Force stop is preferable, or better do reboot)
Now open Setting again and do same...
*** Note ***
Don't add next FP directly without closing Setting app otherwise you will get "GHOST FP"
You will be not able to remove those FP unless getting Fresh Start again...!!
Count how many FP you have added, i haven't tried adding 6th FP, so better to count 5 FP only..

__Madddy said:
I have solution for Fingerprint over MM baseband if anyone dont want to update to nougat soak or modem,
Will edit this post with it, let me correct my english... Lol...
Click to expand...
Click to collapse
Much appreciated. Please do.

When I disconnect from WiFi after extended use on CM 14 my phone tells me I'm offline. I have to reboot to use network even though it was still connected... On xt1644...
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
__Madddy said:
I have solution for Fingerprint over MM baseband if anyone dont want to update to nougat soak or modem,
Will edit this post with it, let me correct my english... Lol...
Click to expand...
Click to collapse
If you rename each fingerprint after adding then you can add more than one

zeomal said:
Common Custom ROM bugs
Fingerprint enrollment issues. Flash Nougat to resolve this. No, you have to flash, if you don't want to, please do not post bug reports. Follow this guide by @rahulsnair to update your phone to Nougat soak test. We have a soak test because the release version has not yet been captured for us to use.
Camera/Video recording issues. Use the built in camera, NOT Moto Camera (the camera you had on stock ROM) as your camera. You can also use any other recording app (Cameringo, Motorola Camera, Google Camera all work just fine). And yes, Motorola Camera is different from Moto Camera. Camera issues are being sorted out by the CyanogenMod team (and will reflect on all ROMs that are based on CM), and only once those issues are sorted can the developers for this device sort any issues with ATHENE out. Note that for Moto Camera to work, you need to set the DPI (Settings → Display → Display Size) to the default one.
Unable to share images/screenshots from gallery or filemanager. Sort this one out by formatting your internal storage.
Chop-Chop/ Torch issues. Do a reboot. It should work then.
Click to expand...
Click to collapse
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....

swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
Click to expand...
Click to collapse
I'm no expert, but to the best of my knowledge, these will be upstream bugs, so devs will have to wait for CyanogenMod team to fix them, before they can implement the fix.

zeomal said:
I'm no expert, but to the best of my knowledge, these will be upstream bugs, so devs will have to wait for CyanogenMod team to fix them, before they can implement the fix.
Click to expand...
Click to collapse
In 20161117 It's Work Perfectly

@mason2smart updated my post with long procedure, will try your suggestion and add to my post...?
Sent from my Moto G4 Plus using XDA-Developers mobile app

swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
Click to expand...
Click to collapse
https://github.com/sileshn/android_frameworks_base/commit/70e87cfd06759768d451a8057522faba3922e415
2g issue, i'll take a look. Maybe some change from me botched it.
Is 2g working on other roms or is it a problem only on CyanMOD?

mason2smart said:
If you rename each fingerprint after adding then you can add more than one
Click to expand...
Click to collapse
Tried and had issue that i described in my post "GHOST FP" ...!
For that procedure i described for remaining FP must be followed...?

swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
Click to expand...
Click to collapse
About your second question: I can't reproduce that.
{
"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"
}
Are you sure you're on the latest (N) baseband?
Sent from my XT1642 using Tapatalk on CyanogenMod 14.1 (dualboot)

smitharro said:
About your second question: I can't reproduce that.
Are you sure you're on the latest (N) baseband?
Click to expand...
Click to collapse
N baseband does not work with custom roms. At least not for me.I installed soak test N and I stopped being able to make calls when I installed the roms. I suppose they only work with the MM baseband.

velosa said:
N baseband does not work with custom roms. At least not for me.I installed soak test N and I stopped being able to make calls when I installed the roms. I suppose they only work with the MM baseband.
Click to expand...
Click to collapse
Well then you supposed wrong! Moreover it's a NEED for a proper use of all functions of all 7.1 custom roms!
Sent from my XT1642 using Tapatalk on CyanogenMod 14.1 (dualboot)

Silesh.Nair said:
https://github.com/sileshn/android_frameworks_base/commit/70e87cfd06759768d451a8057522faba3922e415
2g issue, i'll take a look. Maybe some change from me botched it.
Is 2g working on other roms or is it a problem only on CyanMOD?
Click to expand...
Click to collapse
I'm Only Use Cm14.1 , Not Try other roms

smitharro said:
Well then you supposed wrong! Moreover it's a NEED for a proper use of all functions of all 7.1 custom roms!
Click to expand...
Click to collapse
You are right, but I install everything as it should be and even when I restart the device not to the sign of the sim card.I'll try again and see if it's some mistake I made.

Is my axon 7 the global or chinese version?

I have just received my new Axon 7 which is currently running stock 6.0.1. So I thought I would try to update as I already know nougat is available. There are no available OTA's showing though. Of course AxonToolkit needs the variant if I want to root etc...
Hoping someone can shine a light on it for me as according to the model number it's the Chinese variant but the spec is 64gb/4gb. I thought the Chinese version only came with 128gb storage!
Any ideas folks?
{
"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"
}
Sent from my ZTE A2017 using Tapatalk

beastobadness said:
I have just received my new Axon 7 which is currently running stock 6.0.1. So I thought I would try to update as I already know nougat is available. There are no available OTA's showing though. Of course AxonToolkit needs the variant if I want to root etc...
Hoping someone can shine a light on it for me as according to the model number it's the Chinese variant but the spec is 64gb/4gb. I thought the Chinese version only came with 128gb storage!
Any ideas folks? View attachment 4392763
Sent from my ZTE A2017 using Tapatalk
Click to expand...
Click to collapse
From what I understand you have the Chinese version according to that screenshot.
A2017G = European / Global
A2017U = US
A2017 = China
The Way to be certain is to check the back of the phone as it should be printed there.
I also found a page that referred to a 64GB Chinese version too, just uncommon

This is what I've got for my G model.
Envoyé de mon ZTE A2017G en utilisant Tapatalk

Yes, seems it's definitely a 64gb Chinese version as on the back of the phone is printed 'ZTE A2017', not what I was expecting.
So can I change the region using AxonToolkit and flashing an alternative rom?
Sent from my ZTE A2017 using Tapatalk

I don't know if it's possible, but I think you should have a problem with the radio baseband.
Envoyé de mon ZTE A2017G en utilisant Tapatalk

beastobadness said:
Yes, seems it's definitely a 64gb Chinese version as on the back of the phone is printed 'ZTE A2017', not what I was expecting.
So can I change the region using AxonToolkit and flashing an alternative rom?
Click to expand...
Click to collapse
You can flash any firmware on any device. I am having A2017 and using A2017U Software.
Use MiFlash thread to flash
Instructions : Download both the EDL packages and extract and copy and replace the Modem Elf file from Chinese to US ROm and just flash US ROM. Good To go

satish.yarramsetti said:
You can flash any firmware on any device. I am having A2017 and using A2017U Software.
Use MiFlash thread to flash
Instructions : Download both the EDL packages and extract and copy and replace the Modem Elf file from Chinese to US ROm and just flash US ROM. Good To go
Click to expand...
Click to collapse
Thanks for that. I am having to learn everything again coming from an S4 and LG G3 but that info is something I may use in the future.
In the end I took the simple route and used AxonToolkit to unlock the bootloader, flash twrp and root. Went custom with RR which I have used for years on and off. Just flashed the universal bootloader and modem along side the rom. Apart from losing some stock functionality like the camera, my Axon 7 is running absolutely fine.
Edit...actually reading the MiFlash thread that seems just as simple if I ever get the itch to go back to stock rom
Sent from my ZTE A2017U using Tapatalk

beastobadness said:
Thanks for that. I am having to learn everything again coming from an S4 and LG G3 but that info is something I may use in the future.
In the end I took the simple route and used AxonToolkit to unlock the bootloader, flash twrp and root. Went custom with RR which I have used for years on and off. Just flashed the universal bootloader and modem along side the rom. Apart from losing some stock functionality like the camera, my Axon 7 is running absolutely fine.
Edit...actually reading the MiFlash thread that seems just as simple if I ever get the itch to go back to stock rom
Click to expand...
Click to collapse
If you want the stock camera just go to the stock camera thread on Themes, Apps and Mods, download the B13V2 camera, flash it. You'll get the latest and greatest MiFavor 5.0 camera
To flash any ROM you have to flash the A2017 modem file. And probably an universal bootstack. If you wanted to switch to a G ROM (say, slim⁴) you can just follow the instructions. But it basically js flashing a bootstack, a modem, then the ROM.
And if you want to go back to stock you can just install one of the MiFavor 5 ROMs, they are basically stock for the A2017. I think there's a flashable one, and there's an older one which is just a TWRP backup.
I always thought MiFlash was more like the last thing to do, but you might as well use it. I wouldn't like to know what would happen if there was a power surge in the middle of a flash.

Choose an username... said:
If you want the stock camera just go to the stock camera thread on Themes, Apps and Mods, download the B13V2 camera, flash it. You'll get the latest and greatest MiFavor 5.0 camera
To flash any ROM you have to flash the A2017 modem file. And probably an universal bootstack. If you wanted to switch to a G ROM (say, slim⁴) you can just follow the instructions. But it basically js flashing a bootstack, a modem, then the ROM.
And if you want to go back to stock you can just install one of the MiFavor 5 ROMs, they are basically stock for the A2017. I think there's a flashable one, and there's an older one which is just a TWRP backup.
I always thought MiFlash was more like the last thing to do, but you might as well use it. I wouldn't like to know what would happen if there was a power surge in the middle of a flash.
Click to expand...
Click to collapse
Yeah I have to say I have always been a one for flashing from recovery...it just feels safer to me.
The B13V2 cam file is actually already sitting on my Ax7, I have just never got around to flashing it yet lol
Only thing that I thought would really bother me was the lack of hi-res DAC support on LOS/custom based ROMs but I now have RR with V4A running on it and it sounds great...far cry from the clicks, stutters and hiss I was getting on my S4 and G3
Sent from my ZTE A2017U using Tapatalk

beastobadness said:
Yeah I have to say I have always been a one for flashing from recovery...it just feels safer to me.
The B13V2 cam file is actually already sitting on my Ax7, I have just never got around to flashing it yet lol
Only thing that I thought would really bother me was the lack of hi-res DAC support on LOS/custom based ROMs but I now have RR with V4A running on it and it sounds great...far cry from the clicks, stutters and hiss I was getting on my S4 and G3
Click to expand...
Click to collapse
Actually I believe sound is better on LOS after the AK4490 patch... With it you can get 192KHz/24bit on Neutron, so yeah, there is hi-res on LOS roms. Flash it just in case, but I think that it has already been integrated

Choose an username... said:
Actually I believe sound is better on LOS after the AK4490 patch... With it you can get 192KHz/24bit on Neutron, so yeah, there is hi-res on LOS roms. Flash it just in case, but I think that it has already been integrated
Click to expand...
Click to collapse
I went away from Neutron a couple of years ago because of the janky UI, damn good player for sound though. Might have to give it another go later. Does Neutron not force out 32bit?...I am sure there is a switch in settings which forces 32bit.
Shame that Max can't get the hi-res working natively on Poweramp though...I am a big fan of that player even though the next version has been in beta for ever.
Sent from my ZTE A2017U using Tapatalk

beastobadness said:
I went away from Neutron a couple of years ago because of the janky UI, damn good player for sound though. Might have to give it another go later. Does Neutron not force out 32bit?...I am sure there is a switch in settings which forces 32bit.
Shame that Max can't get the hi-res working natively on Poweramp though...I am a big fan of that player even though the next version has been in beta for ever.
Click to expand...
Click to collapse
I absolutely despise Neutron, but the hi-res thing is a fact. I use Poweramp 704
Why would you force 32 bit when the DAC only processes up to 24? Even if you toggle that switch the output will be 24.

Choose an username... said:
I absolutely despise Neutron, but the hi-res thing is a fact. I use Poweramp 704
Why would you force 32 bit when the DAC only processes up to 24? Even if you toggle that switch the output will be 24.
Click to expand...
Click to collapse
I thought I had read the DAC had a max bit rate of 32 bit...oh well, no need then! lol
Same here Poweramp 704
Edit...OK did some reading up on the DAC... Bit of a heated subject that one! So the DAC itself is a 32bit chip but it is limited to 24bit by android itself...I mean WTF lol!
Sent from my ZTE A2017U using Tapatalk

Can't Install Every Rom for this Phone? (XT1575)

The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R

LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.

aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Thanks I thought that it was the marshmallow as I seen a thread that said it was the marshmallow baseband

aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Is there a way to get The Marshmallow BaseBand?

LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
To answer your question without you going into a Blackhole in having to know more about your device in getting it back to good ground - I OFFER THIS-
Only way I know is to buy a XT1575 device that's never taken the servers Nougat OTA or has been ADB flashed to Nougat OS...
This as in ADB flashed questioned basically being understood by the device still having the bootloader status to LOCKED - as DEVICE LOCKED, the STATUS will still show 0, and it's software status of OFFICIAL.
Note: The Status Code will always show 2 = (relocked) or 3 = (unlocked), and it can never go back to 0 = (device locked), if it's ever been unlocked by a Motorola token code obtained from their site.
Otherwise you need an image of the Bootloader screen of the device up for sale.
THAT'S THE ONLY WAYS TO KNOW AND A SELLER SHOULD SUPPLY THIS AS A GUARANTEE AND/OR AN IMAGE SHOWING YOU FIRST...
OR YOU BUYING FROM A SITE AND ASKING THESE QUESTION OF THE XT1575 SELLER FIRST BEFORE THE PURCHASE AND THE SITE (LIKE EBAY) HAS A GUARANTEE IN THAT AD - TO FALL BACK ON...
To check this yourself-
1. Using (vol down + power button) put the device in bootloader mode where all of this is visible / should read as follows - see images also.
(A) - totally Stock non-rooted Marshmallow Baseband should read as - M8992_1255331.29.01.88.02R SUPER_NA
as taken from my Marshmallow XT1575 build MPHS24.49-18-16 devices Bootloader.
(B) - Shows the very same thing with device from the ABOUT PHONE in settings.
(C) - Rooted Custom Rom Nougat Baseband M8992_1255331.29.01.88.09R - from the ABOUT PHONE in settings / using the NuclearROM.
(D) - M8992_1255331.29.01.88.09R SUPER_NA - from the Bootloader Mode on same device - using the NuclearROM.
PS: I'm thinking, changing to a different Android build changes the Baseband build as well being applicable to the OS build version.
Warning:::
No don't ever do a complete ADB MM downgrade flash - if wanting to OTA back up to Nougat at some future point after already being on the Nougat OS.
To be clear "It's not recommended to downgrade" and allow a Moto X Pure device in taking the Nougat OTA again.
Once bootloader.img and gpt.bin are updated, there is no reverting back without the serious and the likely risk of a hard-bricked device. Only remedy at this time is a mainboard replacement. Confirmed in this threads post #75 .
A COUPLE POINTS - I'd like to make:
I've always clean flashed my XT1575 in custom roms and to going back in a stock Nougat OS - point being, I have never had any problems thereafter...
Another thing I'm thinking with an LOS based ROM - writes / changes some partitions parts that only with your ADB flashing back to the factory Official Stock Nougat can fix - changing everything back to an original partition structure.
- TWRP only backups a few partitions on the device, so partitions out of it's reach never gets restored back to an original stock environment with a TWRP backup when you do a restore using it/one made thereafter.
OTHER Reading you might want to do:
#30
#61
#73
#147
#179
#184
Baseband
I'm far from being a real practical experienced user in a XT1575 device but, I share in what I've taken a grasp of.
Hope this helps
{
"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"
}

LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Sorry I never got around to replying. @ResistanceIsFutile did a pretty good job explaining things as far as I can see. I just flashed stock Nougat within the last month with the intention of staying on stock rooted. I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.

LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
As @aybarrap1 has pointed out already, you are running a stock Nougat baseband,
Meaning you've also upgraded fully to the Nougat OS on your device.
Possibly, for someone new to the XT1575 on Nougat OS it's a good place to stay and get acquainted.
There's nothing wrong with Nougat. Root and TWRP are possible, as well advancing us further than what the Marshmallow OS offered.
I can understand Custom Rom wise, your wanting to "Is there a way to get The Marshmallow BaseBand?" but, consider that's just water under the bridge now - never to be the same for you. In anything you'd do to achieve this would just put your device in a Mixed-State, and where an advanced user would be better adapted of dealing with that.
That's why in my 1st. post to you I was trying to encourage you to read more, let it go awhile and sink-in, and read some more getting a mental picture as you understand the depth of everything related.
Or simply sell off your now XT1575 Nougat OS device and what to look for in a stock-locked bootloader of a Marshmallow OS XT1575 device and stay there not taking an OTA of Nougat.
Even in some Custom Rom's built for a Stock Nougat Kernel and Modem there have been changes related to the TWRP version needed to be used of them.
Here gives abit about that information.
I use the NucleaROM on one XT1575 and kind of bias towards it as I've stayed with it in my first flashing of a custom rom when OTAing up to Nougat that is after failing with LOS of the jumbled up thread for clark it uses.
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark)
Trying to decipher this LOS thread posts of Official versus Unofficial builds, versus using Modems of MM and Nougat and talking about LOS 14.1 and 15.1 builds along the way and all the different involved posts of each Official - Unofficial unlabeled subjects there of all the posts.
It's no place for an inexperienced user to go and easily understand it.
These are the posts https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303%22]https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303 that clearly pointed out the specific information in details that helped me to know of the differences to the posts while I was active in that thread.
I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever, play store is not a concern for me to use - there are other less invasive places that don't have the requirements Googles PS imposes. (F-Droid)
Even running a root file explorer I don't see anything Google related - with the way I've installed NR
Besides running an apk through Virus Total gives me peace of mind.
Android is by Google and that's were G stops with me...
NucleaROM - (root - g-apps), all are optional for the two NucleaROM builds out.
Note:It's the wakeblock app or it's folder that is mandatory to do something with in NucleaROM.
In disabling it's app in phone settings (Apps) after 1st. boot, or removing it's folder in NucleaROM's root directory via TWRP before your very 1st boot into OS where you initially setup the OS.
Did any of this help?

aybarrap1 said:
I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.
Click to expand...
Click to collapse
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow base that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risk to having a hard-bricked device. You'd need to skip those parts in the downgrade commands used of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...

ResistanceIsFutile said:
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risking to having a hard-bricked device. You'd need to skip those parts in the downgrade commands of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...
Click to expand...
Click to collapse
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.

There's a change in the wind with Oreo...
aybarrap1 said:
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.
Click to expand...
Click to collapse
Your happy with the stock Nougat - as I've said there's nothing wrong with it.
I get it and respect your decision to do just that in staying with a stock Nougat.
Custom ROMs aren't merely for customization's, back in the day especially with the array of cheaper devices it was the norm though. To make it in ones liking of a polished look or for performance enhancements.
The added themes and applications preinstalled by a manufacturer were reduced to almost nothing. This saved a lot of memory space and increased the device's performance, then with being able address the questionable UI design decisions that a manufacturer had made.
Besides with the XT1575 Moto X Pure, you needn't worry much about Motorola's manufacturers bloat and being skinned to something hideous and repulsive. By that, I mean your not dealing with and like the other manufacturers (tweaking Androids OS) add/remove/change the interface and apps to make it their own highly styled branded system.
Customization's was a way to truly make a phone your own and still is...
After installing a Custom ROM on Android you are the Admin of your Device which means no Objections, no Restrictions, and basically nothing hampering you as your free to do anything with your Android device.
But, customization's is only one facet in the equation to consider with a custom rom.
Taking a view of all devices in the realm of Custom ROM's offered to each (not just an MXP), there's something more also to be gained.
Updates:
One of the most frustrating things about owning an Android device is waiting for your manufacturer to push an update to your phone, so you can get the latest features. The newer versions of Android are not only interesting because they bring new features but, also because they fill security gaps.
Often times manufacturers will even cut support for your device entirely (thinking of Motorola's support for the MXP). This leaves you stuck with a phone on an older version of Android and less secure. The solution is a custom ROM on the newest or a newer Android version for it.
Privacy and Security:
The recent alarming News surrounding data collected by OnePlus devices (along with a second claim that the company has denied), having highlighted the amount of trust we have to place in our phones by the manufacturer itself now.
This doesn't apply more to budget phones in that they may have security problems. And even the world’s second largest smartphone manufacturer, Huawei, has recently found its US ambitions blocked by US security agencies over concerns about it's spying.
And even once you get past this, every Android user is handing over vast amounts of personal data to Google and others (App's) every single day.
[[Like I pointed out in post #7, I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever.]]
Lineage OS has numerous privacy controls built in, including a Privacy Guard that restricts how apps can use your data. Plus, you can use it without Google apps if you prefer !
A custom ROM can help address your security and privacy concerns. ROMs are, or should be open source. The code is available for anyone to scrutinize. Even if you don’t have the skills to analyze it yourself, you can be assured someone will flag any privacy concerns to it's custom rom using community.
Other Benefits:
Then one can benefit possibly with Performance, Battery Life. In some cases, you might even be able to unlock new functions or find features from newer flagships ported back to older devices. These are the types of phones that rarely get updated, and are often not as well optimized as their higher end siblings.
Disadvantages:
Sure Custom ROMs have their own, it's not going to be a sunny days walk in the park everyday. Expect some rain too, like in adding an app, tweaking hidden settings of the Android's OS and like-
"many phone cameras have dual lens setups nowadays, fancy HDR effects, and high frame rate 4K video. They all need special tools to drive them, and these are all part of the phone’s manufacturers firmware. There’s no one app that you can simply lift and install on another device. Nor can you replace all of the cameras functionality with a third-party camera app."
Closing thoughts:
One of the biggest draws of custom ROMs used to be that you could install the stock Android experience on any device. You could replace the bloated software from Samsung, Huawei, or HTC and other manufacturers with a ROM based on the open source version of Android. Throw in the suite of Google apps, and you’d have something akin to a pure Android device. This is the principle around which Google’s Nexus phones were built. {In reality, Android is but one of the parts of your phone's software today, not the total sum of those parts as manufacturers hardware needs it's own drivers to function.}
But, that makes the stock Android no longer the best version of Android, even Google admits this. The best parts of the company’s Pixel phones aren’t Android. The camera app, Google Assistant, and the fast streamlined launcher are all proprietary software. They’re developed and owned by Google. In fact, on the product pages for the Pixel phones, Android barely even gets a mention there.
Custom ROMs can be wonderful for older devices but, before you decide to change your device's original manufacturers firmware you should familiarize yourself with the disadvantages of the process.
Custom ROMs are perfect for those who love a good challenge. But if this doesn't sound like you then you won't like custom ROMs. Between the devices need for security updates that custom roms can offer. Comes a need to unlock the bootloader, install a custom recovery, gain system root and dealing with unstable versions being pushed to a device, and having an active ROM maintainer.
Those are some of the things where your patience could reach its limits fast.
Not forgetting, third-party firmware (as in custom roms) comes with very few or no Google apps. The Play Store application has to be installed again if you use that source for you add-on apps.
Then hardware specific software (drivers) to make a devices hardware function properly.
So is it Your device because you've paid for it, or is it a manufacturers device with their own branded apps, style and the flair they choose for you of the price you've paid for it.
It's Your choice and decision to change it or not... :good:
PS: Devices that started to ship with OREO installed will change the custom rom landscape.
There's a change in the wind with Oreo...
Project Treble has some interesting implications for the revival of the custom ROM scene.
XDA community members are excited about the prospect that we may be edging closer to a time where Android software can be easily ported across a range of devices.
Other developers have also already shown off a single system image capable of booting on different devices with different processors.

ResistanceIsFutile said:
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
Click to expand...
Click to collapse
Not much to add - I share @ResistanceIsFutile comment - once you have updated - don't try to go back to earlier modem / baseband on this phone
Here is another collection that gives you choices and very clear which version to use for
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
Personally - I flashed the stock ROM that is here ( make sure you have correct variant before doing ) :
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
to move from Marshmellow modem - as noted above ; much more development on the original modem -- but I had a nagging issue with the Fly Delta app that could be duplicated but not something developers of custom ROMs should have spent time on - going to Nougat stock cleared it - then I went to NucleaROM almost immediately and everything worked fine
I have never tried - but , by searching xda-- you will find many active developers noting it is a good way to brick the phone .. I do not pretend to fully understand -- but have learned long ago to do research , carefully read OPs and safest to follow instructions of those who have much greater knowledge than me .
The phone is still my daily driver - I am currently on rooted stock that was installed by the method noted in the thread above. I have been on NucleaROM as DD and a good ROM ..and have flashed many posted by obsolete1. I have found with many back to back clean flashes - reflashing stock can eliminate issues that you might run into ( don't remember them all - but do recall having an issue wiping phone once )
Also - check carefully what TWRP to use - some of the ones using the Nougat modem require the unofficial TWRP that Hashbang developed for the earliest ROMs that worked on it.
We had a pretty good run on this phone and it appears there still might be a few developers looking at it .. but I understand ; most of them have moved on to other phones or the reality of life has required them to leave development for awhile
Regards

@ResistanceIsFutile
Thanks for the run down and I'm quite aware of many of these things. The MXPE in itself is a great phone with the few added features for Moto being actually somewhat useful.
I am not overly concerned with updates. If I were I would get a pixel or Android one phone.
Prior to the MXPE I had carrier branded phones and found custom ROMs to be quite useful in terms of bloat and better performance.

@aybarrap1
Only meant it peaceably - didn't mean by steps on any toes or persuade - crowd you or anyone at all.
The Moto X style/pure devices age has probably 3rd, 4th even 5th generation owners by now that have no ideal what we're talking about at times.
I then see it as a funneling effect, when I answer one it spreads out to others not knowing, especially in a threads topic as this. If you prefer I'll answer generally and not address anymore to you - I'm easy and would like to make friends on XDA - not loose any prospects.
I like and see your posts as helpful as I hope mine are, and it's encouraged to answer if you can at any experience level on XDA. So please forgive any misunderstanding or intentions on my part.
Thank you.
Everything is beneficial but not useful to all

@ResistanceIsFutile
Thanks. Reading back I see how the "tone" came across. I'm good and only intended to put out my reasons. I do have to say it is good you post this info as it was posts like yours that helped me a lot when I first started looking into rooting and custom ROMs some many years ago (LOL...7 or 8 years only but in terms of phone tech that is a very long time).