Develop Bugs

[Q] 4G not working?

Hi guys,
Imported my M9+ from India, I'm currently using it in the UK on the O2 network, however I've yet to pick up any 4G signal, anyone shed any light into why this could be as the phone states it does support my carriers 4G signal band.
Cheers

lfcdanny said:
Hi guys,
Imported my M9+ from India, I'm currently using it in the UK on the O2 network, however I've yet to pick up any 4G signal, anyone shed any light into why this could be as the phone states it does support my carriers 4G signal band.
Cheers
Click to expand...
Click to collapse
According to HTC India, M9+ Only supports FDD: Bands 1,3,5,7,8,28. Whereas O2 LTE network in UK is using FDD band 20(800Mhz).
Hope this answered your queries.

xunus said:
According to HTC India, M9+ Only supports FDD: Bands 1,3,5,7,8,28. Whereas O2 LTE network in UK is using FDD band 20(800Mhz).
Hope this answered your queries.
Click to expand...
Click to collapse
I've checked some stuff, and I think that the radio firmware is inside the /system image and is not a separate partition.
Also I think they might use the same firmware as they are the same version in different full fimware zips system img part and radiversion.ini contains same version.
but the /system/build.prop differences might help with your issue.
Here's the Asia WWE build.prop part that might differ:
Code:
ro.ril.vmail.50502=+61411000321,YES OPTUS,+61411000212,Virgin Mobile
ro.ril.vmail.50503=+61411000121
ro.ril.vmail.50501=+61101
ro.ril.vmail.50506=+61430005333
ro.ril.vmail.53001=+6421700700,vodafone NZ,+64298500500,TelstraClear
ro.ril.vmail.53005=+6483083210
ro.ril.vmail.53024=+64222022002
ro.ril.vmail.51000=*88
ro.ril.vmail.51011=888
ro.ril.vmail.51089=222
ro.ril.vmail.51099=*922
ro.ril.vmail.51021=+62816122
ro.ril.vmail.51001=+62816122
ro.ril.vmail.51003=122
ro.ril.vmail.51007=*88
ro.ril.vmail.51010=222
ro.ril.vmail.51028=*88
ro.ril.vmail.51051=*88
ro.ril.vmail.51009=*88
ro.config.htc.enableCOTA=1
ro.ril.enable.sdr=1
ro.telephony.ipv6_capability=1
ro.ril.hsxpa=4
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.disable.cpc=1
Replace it with this in Europe:
Code:
ro.telephony.ipv6_capability=1
ro.apn.uservalue.protocol=IPV4V6
ro.product.model=HTC One M9PLUS
ro.ril.vmail.23415=1571,BT,121,VDF UK
ro.ril.vmail.27203=171
ro.ril.vmail.65502=181
ro.ril.vmail.27211=171
ro.ril.vmail.65510=100
ro.ril.vmail.22299=4133,3ITA
ro.ril.vmail.23410=901,O2 UK,905,TESCO,443,giffgaff
ro.ril.vmail.22201=41901,I TIM
ro.ril.vmail.22210=42020,Vodafone IT
ro.ril.vmail.22288=4200,I WIND
ro.ril.vmail.20801=888
ro.ril.vmail.20810=123
ro.ril.vmail.20826=777
ro.ril.vmail.42403=161
ro.config.htc.enableCOTA=1
ro.ril.enable.sdr=1
ro.ril.hsxpa=0
You will need to unlock the device and root it to do this in a root file manager and edit it somehow, or copy the build prop to the /sdcard/ copy it to PC, edit, copy back then:
copying file to sdcard on a rooted device from PC command line, :
Code:
adb shell
su
cp /system/build.prop /sdcard/build.prop
then reconnect the device and copy the build.prop to PC through mtp. There Edit file on PC then copying back to sdcard then from command line;
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/build.prop /system/build.prop
chmod 644 /system/build.prop
reboot and see if it works. report back if you try this.
It's absolutely not sure that it helps, so don't void your warranty if you were not planning on unlock and root

Stock Firmwares per region

Hi... maybe it would be the place to share what firmware (stock) you have in your Nova-Nova Plus...
Im in Quebec Canada with Rogers...
MLA-L03C654B130

Russia
Huawei Nova CAN-L11
CAN-L11C10B101
Huawei Nova CAZ-AL10 (full Netcom 4 GB ram/64 GB rom)
CAZ-AL10C00B130

with Fido (Rogers) in Canada. looks to be the same
Nova Plus MLA-L03
MLA-L03C654B130
looks like firmware build is Model# followed by C# and then B#

Following Huawei Firmware labeling traditions, we still have that something similar to this.
For example, doing getprop you will find:
Code:
# getprop |sort
...
[ro.build.cust.id]: [CAN-L11C432B100CUSTC432D004]
[ro.product.BaseVersion]: [CAN-L11C432B100]
[ro.product.fingerprintName]: [HUAWEI-MILAN]
[ro.product.CustCVersion]: [C432]
[ro.product.CustDVersion]: [D004]
[ro.product.board]: [CAN-L11]
[ro.product.hardwareversion]: [HL1CANL01M]
Thus we can guess that:
Code:
CAN = Refers to the Hardware Platform ("Cannes"?)
L11 = The device hardware model version ("Nova" is too general!)
B100 = Build Version (OTA released firmware)
C432 = The Customization Code version (region/country/service provider)
D004 = The Customization Debug version (patches and bug fixes)
So for example, in the Huawei Firmware Finder app, you can search for "CAN-L11" and you'll get a list of recent firmwares. The Changelog of one of these say:
Code:
Update from L11C432[COLOR=Red][B]B100[/B][/COLOR]CUSTC432[COLOR=DarkGreen][B]D004[/B][/COLOR] to L11C432[COLOR=Red][B]B140[/B][/COLOR]CUSTC432[B][COLOR=DarkGreen]D001[/COLOR][/B]

Nice post, what do you make of the China released CAZ versions?

wangdaning said:
Nice post, what do you make of the China released CAZ versions?
Click to expand...
Click to collapse
Don't know... Please post some more getprop info. I suspect its not even a Qualcomm based device, perhaps a HiSilicon?

Iraq
Huawei MLA-L11
MLA-L11C185B131

E:V:A said:
Don't know... Please post some more getprop info. I suspect its not even a Qualcomm based device, perhaps a HiSilicon?
Click to expand...
Click to collapse
Hi man!
I'm China device owner too, CAZ-TL10 to be more precise. The device is qualcomm based too, there is no difference (apart from baseband maybe).
Here follows its getprop:
Code:
[ro.build.display.id]: [CAZ-TL10C01B153]
[ro.build.id]: [HUAWEICAZ-TL10]
[ro.product.BaseVersion]: [CAZ-TL10C01B153]
[ro.product.CustCVersion]: [C01]
[ro.product.CustDVersion]: [D153]
[ro.product.board]: [CAZ-TL10]
[ro.product.fingerprintName]: [HUAWEI-MILAN]
[ro.product.hardwareversion]: [HL1CANAL10M]
[ro.board.platform]: [msm8953]
[ro.build.hide.matchers]: [Honor;msm8952;Adreno(TM)405;Qualcomm;HUAWEI CAN;HUAWEI CAZ;CAN;CAZ;]
Do you think that twrp for CAN made by @Xelfmade built will work for my CAZ? I can't test yet, couldn't get the unlock code yet (received my device yesterday, couldn't even apply for it yet).

The TWRP should work unless the partition layout is different. Just give it a try with "fastboot boot twrp.img" that way if it does not work your phone will still be ok.

Vinnom said:
Here follows its getprop:
Code:
[ro.board.platform]: [msm8953]
[ro.build.hide.matchers]: [Honor;msm8952;Adreno(TM)405;Qualcomm;HUAWEI CAN;HUAWEI CAZ;CAN;CAZ;]
Click to expand...
Click to collapse
Those two lines seem very suspicious as they seem contradictory. I doubt the partition layout is the same and therefore TWRP may not work... Different (?) processor, GPU, modem and connectivity.

wangdaning said:
The TWRP should work unless the partition layout is different. Just give it a try with "fastboot boot twrp.img" that way if it does not work your phone will still be ok.
Click to expand...
Click to collapse
For now, I can't :/ tried to apply for the unlock code and it seems I need to wait for 14 days until I can apply for it.
E:V:A said:
Those two lines seem very suspicious as they seem contradictory. I doubt the partition layout is the same and therefore TWRP may not work... Different (?) processor, GPU, modem and connectivity.
Click to expand...
Click to collapse
I found it strange too, butI don't now what ro.build.hide.matchers means.
ro.build.platform implies that it is msm8953, though.

Having MLA-L03
is it safe to root my device with Kingoroot or Rootkhp...or else ?
is it working ?
thanks

Belgium - Proximus
CAN-L01C02B130
CUSTC02D014

Poland
CAN-L11C432B140
CUSTC432D001

Germany
MLA-L11:good:

Wind Italy
Can-L01C113B130
CUSTC113B003

United Kingdom
CAN-L01C432B131
CUSTC432D001

Malaysia
MLA-L12
MLA-L12C636B130
CUSTC636D006
Anyone have the ROM for the model?

virusdunil said:
Hi... maybe it would be the place to share what firmware (stock) you have in your Nova-Nova Plus...
Im in Quebec Canada with Rogers...
MLA-L03C654B130
Click to expand...
Click to collapse
Same for me, Quebec with Videotron as a provider
MLA-L03C578B130

Salut...on est les pas chanceux dla gang...on a pas eu droit a une beta...

Modify Radio and Modem IMG for VoLTE

I would like to edit the Radio and Modem IMG files on the my Pixel XL 2 to enable VoLTE for my carrier which is not officially supporting VoLTE. I alrady know which files I have to edit (from the Pixel XL 1), but I don't know how to open and edit the IMG files, because for the Pixel XL 2 this is required.
Does anyone knwo how to do it?
Additonal Info:
There's a mcfg_sw.mbn file under /vendor/mbn/mcfg/configs/mcfg_sw/generic/common/WildCard/WildCard/mcfg_sw.mbn which inlcudes the Qualcomm NV Item settings which define the chipset settings which are loaded based on the inserted SIM. The default mcfg_sw.mbn file does not include VoLTE support, the mcfg_sw.mbn file for Deutsche Telekom, Vodafone UK & DE, T-Mobile US does. On the Pixel XL 1 it was enough to copy the Deutsche Telekom mcfg_sw.mbn file to the generic folder and VoLTE was working. On the Pixel XL 2 this is not working, because the mcfg_sw.mbn files are again copied from firmware/images at every boot and therefore the generic folder is overwritten. Now I'm looking for a way to bypass this. Contact me at [email protected] if you like to work on this with me.
Btw: I'm a VoLTE / IMS engineer with dedicated knowhow.

devsx said:
I would like to edit the Radio and Modem IMG files on the my Pixel XL 2 to enable VoLTE for my carrier which is not officially supporting VoLTE. I alrady know which files I have to edit (from the Pixel XL 1), but I don't know how to open and edit the IMG files, because for the Pixel XL 2 this is required.
Does anyone knwo how to do it?
Click to expand...
Click to collapse
I have no idea how to do what your are asking but one thing I would do is research if the files are encrypted and or signed in a way that might destroy them if messed with. Hopefully they would just fail to flash but what if they don't fail but cause an UNfixable bootloop or whatever... again I have no idea at all but my paranoia dictates finding out more before trying it. Lol

devsx said:
I would like to edit the Radio and Modem IMG files on the my Pixel XL 2 to enable VoLTE for my carrier which is not officially supporting VoLTE. I alrady know which files I have to edit (from the Pixel XL 1), but I don't know how to open and edit the IMG files, because for the Pixel XL 2 this is required.
Does anyone knwo how to do it?
Click to expand...
Click to collapse
You can't. Changing the Modem partitions on any QCOM device (except HTC devices that are S-OFF) will result in a permanent brick regardless of their unlock status.
Don't do it.

I don't think that there's a high risk to brick the phone with just modding the radio and modem partition. Because the radio was once notbworking on my Pixel XL 2, because I edited some files with es file explorer and after that I just flashed the radio and modem again and it was working fine again.

Can be removed!

I'd wait for a userdebug rom for the phone and then poke around in QPST/QXDM. Replacing and editing files at the filesystem level won't work.

Did you find anything about this?

unfortunately not..

Mod the /firmware/radio folder directly. This didn't cause any problem on my Pixel 1 XL if flashed the factory image again.
EDIT: I don't have a Pixel 2 so I don't know where modem is mounted. Please search for it by yourself

Dario, I think I figuru d wifi calling out via an xda thread. I was wondering if this would work on pixel to allow 4g+?
https://forum.xda-developers.com/showpost.php?p=74573146&postcount=3

devsx said:
I would like to edit the Radio and Modem IMG files on the my Pixel XL 2 to enable VoLTE for my carrier which is not officially supporting VoLTE. I alrady know which files I have to edit (from the Pixel XL 1), but I don't know how to open and edit the IMG files, because for the Pixel XL 2 this is required.
Does anyone knwo how to do it?
Additonal Info:
There's a mcfg_sw.mbn file under /vendor/mbn/mcfg/configs/mcfg_sw/generic/common/WildCard/WildCard/mcfg_sw.mbn which inlcudes the Qualcomm NV Item settings which define the chipset settings which are loaded based on the inserted SIM. The default mcfg_sw.mbn file does not include VoLTE support, the mcfg_sw.mbn file for Deutsche Telekom, Vodafone UK & DE, T-Mobile US does. On the Pixel XL 1 it was enough to copy the Deutsche Telekom mcfg_sw.mbn file to the generic folder and VoLTE was working. On the Pixel XL 2 this is not working, because the mcfg_sw.mbn files are again copied from firmware/images at every boot and therefore the generic folder is overwritten. Now I'm looking for a way to bypass this. Contact me at [email protected] if you like to work on this with me.
Btw: I'm a VoLTE / IMS engineer with dedicated knowhow.
Click to expand...
Click to collapse
So lets start with this. Does your carriers VoLTE use bands that aren't available on the pixel 2? If the answer to that is no, which it probably is, then you dont have to do to modify the radio or modem. You will either need a custom ROM, an OMS overlay, or magisk to do this. VoLTE assigment isnt done by the radio or modem, it is done by the CarrierConfig app. You can use magisk and get the VoEnabler module (or use root to force enable VoLTE with the same props), you can follow https://github.com/CarbonBeta/android_device_google_wahoo/commit/0e38da5af4a93be834347bfe535ae231154530df and force enable it for your carrier (find the config that matches the MCC and MNC of your carrier) and build your own custom rom with the change, or submit it to lineage/carbon/whatever and they will probably merge it. You can also change this value by creating an OMS overlay (formerly RRO, the backend that substratum uses), and install it on any rom, however this may or may not work as android blocks overlays with signatures that don't match the system platform.

Hi, How to enable qam256, can flashing modem or radio solve this

trignogd said:
Hi, How to enable qam256, can flashing modem or radio solve this
Click to expand...
Click to collapse
This is a chipset setting (nv item), which can be changed with QXDM.

devsx said:
This is a chipset setting (nv item), which can be changed with QXDM.
Click to expand...
Click to collapse
Hi, plz can u tell me how to proceed

devsx said:
I would like to edit the Radio and Modem IMG files on the my Pixel XL 2 to enable VoLTE for my carrier which is not officially supporting VoLTE. I alrady know which files I have to edit (from the Pixel XL 1), but I don't know how to open and edit the IMG files, because for the Pixel XL 2 this is required.
Does anyone knwo how to do it?
Additonal Info:
There's a mcfg_sw.mbn file under /vendor/mbn/mcfg/configs/mcfg_sw/generic/common/WildCard/WildCard/mcfg_sw.mbn which inlcudes the Qualcomm NV Item settings which define the chipset settings which are loaded based on the inserted SIM. The default mcfg_sw.mbn file does not include VoLTE support, the mcfg_sw.mbn file for Deutsche Telekom, Vodafone UK & DE, T-Mobile US does. On the Pixel XL 1 it was enough to copy the Deutsche Telekom mcfg_sw.mbn file to the generic folder and VoLTE was working. On the Pixel XL 2 this is not working, because the mcfg_sw.mbn files are again copied from firmware/images at every boot and therefore the generic folder is overwritten. Now I'm looking for a way to bypass this. Contact me at [email protected] if you like to work on this with me.
Btw: I'm a VoLTE / IMS engineer with dedicated knowhow.
Click to expand...
Click to collapse
I have tried editing Verizon's .mbn file with a hex editor and used Magisk to replace the file at boot time to enable WiFi Preferred Calling, it doesn't work. I also took out my SIM card, activated fi, then put my SIM back in, that didn't work (with the file edited).
So, if you spot something in QPST, please let me know, I really would like to figure this out for the community and myself.
What did you use to extract the img? I would love to do it at a radio level instead. F-Verizon!
Sent from my Pixel 3 XL using Tapatalk

I need volte profile for China Unicom too.Ims status is not registered.
Just add a specific profile or parameters like at&t's ?

I tried the mbn trick but it doesn't works on my Pixel xl. I even tried to remove entire mcfg_sw folder under /data and /firmware, but the LTE still works. BTW I sent you an email months ago but no reply
---------- Post added at 05:31 PM ---------- Previous post was at 05:27 PM ----------
seardna said:
I need volte profile for China Unicom too.Ims status is not registered.
Just add a specific profile or parameters like at&t's ?
Click to expand...
Click to collapse
You need to get one from any Chinese phones which supports CU VoLTE. Apart from this, you need to call 10010 to activate VoLTE for your SIM card. At last, you need to comfirm the city you live have VoLTE coverage.

Xdevillived666 said:
Dario, I think I figuru d wifi calling out via an xda thread. I was wondering if this would work on pixel to allow 4g+?
https://forum.xda-developers.com/showpost.php?p=74573146&postcount=3
Click to expand...
Click to collapse
unfortunately, it does not work on Pixel 2XL 'cause it is not able to opne the port of QPST

raphael韬 said:
unfortunately, it does not work on Pixel 2XL 'cause it is not able to opne the port of QPST
Click to expand...
Click to collapse
****

Can someone help me to get VoLTE work on my Pixel XL ?? I have VoLTE working fine with my mobile number (works fine on a Xiaomi Mi A2 Lite and on a Nokia 6.1), but can't seem to work on my Pixel XL, even after trying almost (except modifying radio/modem for example) anything, magisk buildprop etc... my IMS status is not registered.

Question OOS 11.2.5.5BA/NA 5G/Dual Sim?

Hi all, I think I already know the answer to my question.... I just want to be 100% sure as my searches are not quite revealing my answer.
Like many...when I received my NA OP9Pro I was disappointed to notice it wasn't dual SIM. Sent it back and still waiting for a refund for almost 2 months now. (That's a frustration with OP in itself...makes me want to go back to Samsung....UGH!) Anyways, I currently have an LE2120 (Chinese Model) running OOS 1.2.5.5BA (European version) and I am well aware that out of the box the NA version does not come with Dual SIM hardware.
The question that I am not 100% sure of is would the software build still allow dual SIM? My gut strongly tells me no..
The reason why I ask is that currently I don't have access to 5G. I thought it was because my work SIM didn't have 5G enabled on the carrier, I was incorrect. I still don't have access to a 5G, just shows 2G/3G/4G. I thought maybe it is because I am using a EU build here in Canada where maybe the bands don't line up...I have done searches on why 5G isn't available but nothing seems to fix it.
Just a shot in the dark...for people much smarter than I am!

No, simply running EU rom on NA hardware does not enable dsds. You can setprop for dsds but it doesn't work properly, seems to wire the first sim card into both slots and cause a conflict

Maybe I didn't word my question in the correct fashion.
I have dual SIM hardware, in my case it is the Chinese Version but I'm told the hardware doesn't differ as it still a Global Version.
The question is NA ROM, on Dual SIM hardware. If the rom itself supports it. I would just try it, but then I have to wait for the next update.

If you have LE2120, then the EU build should get you dual sim

I have LE2120 and I'm switch to Oxygen OS and trying build AA/BA/DA all working with sim dual
About 5g .. i have same your problem no option 5g only 2g/3g/4g
First check your country bands support
First try:
*#*#4636#*#* and choose NR/LTE/CDMA/EvDo/GSM/WCDMA if not fix 5g
Another way to fix:
I'm fixed 5g same steps its was on op8p
Sorry about english

KTFA said:
I have LE2120 and I'm switch to Oxygen OS and trying build AA/BA/DA all working with sim dual
About 5g .. i have same your problem no option 5g only 2g/3g/4g
First check your country bands support
First try:
*#*#4636#*#* and choose NR/LTE/CDMA/EvDo/GSM/WCDMA if not fix 5g
Another way to fix:
I'm fixed 5g same steps its was on op8p
Sorry about english
Click to expand...
Click to collapse
So you have tried your LE2120 on AA? Dual SIM is all working ok?
I feel like switching to AA would get me unto the proper bands here in my country, but leary to do it because then I have to wait to the next build. Unless I decide to go root/magisk.
I did try the *#*# method, but that doesn't do anything. I have tried several different dialers and it never brings up this menu everyone talks about.

KTFA said:
I have LE2120 and I'm switch to Oxygen OS and trying build AA/BA/DA all working with sim dual
About 5g .. i have same your problem no option 5g only 2g/3g/4g
First check your country bands support
First try:
*#*#4636#*#* and choose NR/LTE/CDMA/EvDo/GSM/WCDMA if not fix 5g
Another way to fix:
I'm fixed 5g same steps its was on op8p
Sorry about english
Click to expand...
Click to collapse
Any status on AA working with dual sim? I see that you never responded. I have the new .7 OTA update, but still hesitant to put it on if I loose dual sim

Question WiFi Calling and VoLTE on OOS 12.0.0.0

After updating to OOS 12.0.0.0 WiFi Calling and VoLTE are gone. Does anyone also have this problem? has someone been able to fix it?

I feel differently - WiFi calling and volte started working after update (EU version). I did factory reset after update.

HubertGT said:
After updating to OOS 12.0.0.0 WiFi Calling and VoLTE are gone. Does anyone also have this problem? has someone been able to fix it?
Click to expand...
Click to collapse
this is a known problem

For me, VoWifi is working but VoLTE and 5G is not.
OnePlus logkit is not working anymore.
*#*#4636#*#* is not working either.

Since codebase merged with ColorOS, EngineeringMode is changed to *#899# but it has limitation (login required) now.
Maybe we can open it with setprop persist.sys.adb.engineermode 1 but root is required.
5G test switch is *#54794824#

In NL I got the following results upgrading from OOS 11 to 12 without factory reset:
* OOS11:
5G for both KPN and Vodafone NL
VoLTE+VoWiFi for both KPN and Vodafone NL
* OOS12:
VoWiFi for Vodafone NL
VoLTE for both KPN and Vodafone NL
VoWiFi for KPN
5G, also both KPN and Vodafone NL

AndroPlus said:
Since codebase merged with ColorOS, EngineeringMode is changed to *#899# but it has limitation (login required) now.
Maybe we can open it with setprop persist.sys.adb.engineermode 1 but root is required.
5G test switch is *#54794824#
Click to expand...
Click to collapse
I didn't find a way for direct contact, so I reply you here. Do you now any way to use qpsp on op9 pro? I just moved from color os to oxygen (after doing it the other way around) and I just have asian bands, so I want to re enable the ones I lost during the change (and enable 5G also)

here i´m to wait for this..

is there any way to activate volte provision (grey out) on OOS12/ColorOS12? tried installing the old logkit apk but it says conflict with an existing package and reboot to FTM does only reboot to the OS.

Was anyone able to do this without factory reset? I don't want to loose everything

zeitos said:
Was anyone able to do this without factory reset? I don't want to loose everything
Click to expand...
Click to collapse
only solution right now for A12 for carriers with Volte not working by default is to root the device and flash a module to activate the Volte.