Related
Hello all,
So after updating my Lumia 710 from Rogers, in the "About" screen of the Diagnostic Tool I see that I am on FW revision 1600.3007.7740.11465. This is a few versions behind what seems to be the latest version out there for unlocked variants of the phone...
So I found this page:
http://www.wpcentral.com/hack-t-mobile-lumia-710-flash-windows-phone-os-8107-new-firmware
Which claims that they have flashed the latest Indian firmware (8107.12070) for the RM-803 variant of the phone onto the T-Mobile (RM-809) version. However I am somewhat reluctant to try flashing an RM-803 image onto an RM-809, especially due to the fact that they support different 3G bands. What do you guys think?
Alternatively, I can see in Navifirm+ that the latest available image for the RM-809 is the Australian 8107.12050, so that might be a safer choice?
This will be the first time I try to manually update a Windows Phone... So what do you guys think? I really want to update it since there are some GMail syncing issues on the build that I'm running now.
I updated my lumia 710 from rogers (RM-809) with the RM-803 indian rom 12070 with no problems! Nothing is missing and it's now unbranded If you follow this guide it's really simple!
Thanks, Simon!
After reading your post, I gave it a shot and everything seems to be working fine I wonder if we should be seeing any battery life improvements like the Lumia 800 users?
Just something I should mention, though: I unlocked my phone so that I could use it on Wind Mobile, but after going through the flashing process, the phone became locked again so I had to re-enter my unlock code.
I didn't know that it was even possible for a phone to become locked again, after already having been unlocked...
I am thinking about getting a Lumia 710, and I am really surprised that you guys were able to flash a firmware from another RM-### without bricking the phone.
I currently own the X7 (RM659) from the Rogers and I was told not to flash the Belle firmware from the X& (RM707) since the phone will get bricked.
Nonetheless, thanks a lot for the info.
Which software do you use to flash? Phoenix or WP7 requires other tools? Never mind I found the post detailing how to debrand it.
The weird thing is... I tried to downgrade from the Indian (RM-803) 1070 build to the Australian (RM-809) 1050 build, and I wasn't able to...
It seems there is a small battery bug (Diagnostic tool doesn't display battery info) so that's why I tried to install the Australian one instead.
Whenever the next update comes along, I hope I'll be able to switch back to an RM-809 build... It seems like the safe way to go.
xsever said:
I currently own the X7 (RM659) from the Rogers and I was told not to flash the Belle firmware from the X& (RM707) since the phone will get bricked.
Click to expand...
Click to collapse
Normally you shouldn't... But the only reason I did it is because other people had successfully done it.
Also keep in mind that Symbian phones seem to be a little pickier - you can brick them just by trying to downgrade to the previous OS.
Edit: Well that's weird... My Battery Status randomly started working!
Edit #2: I just remembered I did a battery pull, so that may have had something to do with why it is fixed now...
I never knew it was possible to downgrade the OS for Nokia phones whether it is Symbian or WP.
Would an unlocked T-Mobile Lumia 710 work fine on the Rogers network? Do the GSM bands match?
It would indeed. The RM-809 model supports HSPA 850/1700/1900/2100. So it will work on any of the North American operators. (excluding the cdma operators like Verizon and Sprint, of course)
Actually, I bought my Lumia 710 from Rogers, unlocked it, and I am using it on Wind Mobile now (same hspa band as t-mobile).
Edit: I hope you're right about the downgrading thing, since that would mean that the reason I wasn't able to flash back to RM-809 was because of the fact that it's a downgrade, as opposed to something being messed up on the phone! I guess I'll find out when the next update comes along.
I am 100% sure you cannot downgrade Nokia firmwares without bricking the phone. I read about one method somewhere, but it was very complicated.
If I were you, I wouldn't be worried, now that you have the RM-803 firmware, next time there is an RM-803 update, you should be able to update via Zune/Nokia Suite without having to go through the method you used at the beginning of the post.
Now your phone is an RM-803 so Zune will recognize it as so and update it normally hence the beauty of debranding where you don't have to wait for operators.
Hello guys i'm new to the site.
I want it to ask if i could flash my lumia 710 (t-mobile US) with the RM-809 VAR T-MOBILE BLACK version that appears in navifirm.
my nokia is DLOAD. Would that be a problem?
kortvolker said:
Hello guys i'm new to the site.
I want it to ask if i could flash my lumia 710 (t-mobile US) with the RM-809 VAR T-MOBILE BLACK version that appears in navifirm.
my nokia is DLOAD. Would that be a problem?
Click to expand...
Click to collapse
I was wondering that too.
Also, there's two T_Mobile 8773 fw's listed for each color phone. One appears to have been released 06/04/12. The other 05/29 . What's the differences?
Ok I just got a really sweet deal
150$ brand new in box unlocked Lumia 900 Black... I LOVE IT!!!!!!!!!!!!
now the only thing is...its branded to TelCel mexico
Are the roms in the dev sectoin interchangeable?
Will flashing another rom re-lock my device?
Also any idea why LTE would not show up on my device...its marked 4G
I got the right sim from my provider, and I am in an LTE area
THank you all in advance if you can provide me any insight regarding these questions
rob243 said:
Ok I just got a really sweet deal
150$ brand new in box unlocked Lumia 900 Black... I LOVE IT!!!!!!!!!!!!
now the only thing is...its branded to TelCel mexico
Are the roms in the dev sectoin interchangeable?
Will flashing another rom re-lock my device?
Also any idea why LTE would not show up on my device...its marked 4G
I got the right sim from my provider, and I am in an LTE area
THank you all in advance if you can provide me any insight regarding these questions
Click to expand...
Click to collapse
Not sure about the interchangeable ROMs. But as far as I know Telcel don't sell Lumia 900s that supports LTE.
Heck, not even the iPhone 5 is LTE at the moment. However iPhone 5 can be upgraded to LTE with a software update.
Cheers,
Rayan
Sent from my GT-N7000 using Tapatalk
Ok I just got a really sweet deal
150$ brand new in box unlocked Lumia 900 Black... I LOVE IT!!!!!!!!!!!!
now the only thing is...its branded to TelCel mexico
Are the roms in the dev sectoin interchangeable?
Will flashing another rom re-lock my device?
Also any idea why LTE would not show up on my device...its marked 4G
I got the right sim from my provider, and I am in an LTE area
THank you all in advance if you can provide me any insight regarding these questions
Click to expand...
Click to collapse
If you have 4G on your screen it is LTE, if you see H is HSPA,
I have a Rogers Lumia 900 LTE from Canada, and I had a lot of connectivity issues, I loaded it with Telcel MX firmware and I can tell you its the best ROM available.
1.- Fixed all Connectivity issues
2.- APN settings, including MMS are automatically detected
3.- Removed all Rogers Branding (Rogers Lumia 900 doesn't have any branding on the exteriors, so after flashing with Telcel ROM its like a new factory unlocked device with no branding at all)
4.- Telcel ROM doesn't have any operator custom preloaded apps
5.- The only thing I was nervous was the disappearance on the LTE logo, but apparently they only replaced LTE and HSPA+II by 4G.
6.- Internet Sharing started working (Didn't work with Rogers Firmware with my current carrier CLARO)
There si another post that mention this:
http://forum.xda-developers.com/showthread.php?t=1905734&page=2
Bottom line, stay with it, it works great!!
thanks alot
Thanks alot for this, I did notice that the telcel rom has no carrier branding, and after reading all your points concerning rogers rom I am definately staying with this one "if its not broke - don't fix it" very helpful post mods feel free to close this thread.
When you changed ROMs, did you run into a signature error? How did you overcome that? It seems some handsets are tied to their specific carrier -- short of upgrading with a same carrier ROM, the update fails with message 'problem with file signature'. or something along those lines.
Cheers
aquanaut88 said:
When you changed ROMs, did you run into a signature error? How did you overcome that? It seems some handsets are tied to their specific carrier -- short of upgrading with a same carrier ROM, the update fails with message 'problem with file signature'. or something along those lines.
Cheers
Click to expand...
Click to collapse
I have a Rogers phone that is unlocked and being used on Bell and it is flashed with this rom as well. I used Nokia Care Suite and got the rom through the data package manager. It flashed without any problems. There haven't been any updates through Zune yet so I don't know what will happen when 7.8 is released. If it doesn't do the update automatically I'll just update it again through Nokia Care Suite.
aquanaut88 said:
When you changed ROMs, did you run into a signature error? How did you overcome that? It seems some handsets are tied to their specific carrier -- short of upgrading with a same carrier ROM, the update fails with message 'problem with file signature'. or something along those lines.
Cheers
Click to expand...
Click to collapse
Didn't happened anything like that to me, just looked for my RM in Data Package Manager downloaded the latest one and loaded it using Nokia Care Suite
Thanks... glad it at least works for the Rogers devices. I'm guessing there's something added to the AT&T versions which prevent swapping carrier ROMs, even within the same RM group.
I've tried modifying the product code both in the file names and within the files. Still fails with file signature error.
aquanaut88 said:
Thanks... glad it at least works for the Rogers devices. I'm guessing there's something added to the AT&T versions which prevent swapping carrier ROMs, even within the same RM group.
I've tried modifying the product code both in the file names and within the files. Still fails with file signature error.
Click to expand...
Click to collapse
I have the same issue, maybe try flashing it to an earlier ROM from AT&T that doesn't have that limitation?
Doing a field exercise with my unit so it may be awhile before I get to try it myself.
I actually tried that a week ago... rolled AT&T rom back to 8112 (nothing earlier available on NaviFirm list). Same complaint.
I could not find a thread to walk through being able to get my Dual Sim 950 to officially work on AT&T with VoLTE and other services (Enhanced LTE/HD Voice etc...). I searched many forums and threads to find a way to do this. I got tired of the lack of call quality and other quirks for my Lumia while on ATT. After accumulating several different pieces of information from multiple sources and places on the xda forum I was able to make it work. This is my first official post with the intention of it being a guide, offer tips if you want. Or if you see errors offer advice or suggestions if needed.
I am only posting this in the event someone else needs the information or wants to use it in some way. Messing with hidden partitions is risky and so if you brick your device using this thread, I'm sorry but I cannot help you. So if you choose to use these directions, use them at your own risk. I cannot be remote technical support. Thanks.
Here is how I got this to work.
Steps I used to convert NAM 950 DS RM-1118_13058 (059X5G2) to an ATT Lumia 950 (RM-1105_12716 059X4D9)
-1- First I flashed this specific original rom for my Dual Sim 950. I used the ffu located here.
-- thor2 -mode uefiflash -ffufile "RM1118_1078.0027.10586.13058.15358.030FF5_retail_ prod_signed.ffu"
-2- Second I manually pushed three cabs to my phone to alter the plat ID to Microsoft.MSM8992.P6218_ATT.1.0. All three were alone in the directory. Listed them below:
mmo.device_talkman_lte_americas.phone.plat_d20cefe ddb10fb6737b56fa966533783b1288e44.cab
mmo.base.variant.plat_55ce525fdf57ab0d614ada3517c3 4c84029f5437.cab
mmo.base.phone.plat_96ea6a2d24151eaf6299c342f81f49 997ca44137.cab
-- iutool.exe -v -p "C:\CABs\Your_Location-of-RM-1105_Plat-cabs"
-3- Third I did a full NVI flash and Reset with an ATT ROM. Link to location of ffu I used here.
FFU File used: RM1105_1078.0053.10586.13169.12716.035044_retail_ prod_signed.ffu
-- thor2 -mode uefiflash -ffufile "RM1105_1078.0053.10586.13169.12716.035044_retail_ prod_signed.ffu" -do_full_nvi_update -do_factory_reset
-4- Fourth I updated the product code. (Note: I never kept my phone on the ATT ROM long enough to see if this was really needed, but I suspected potentially an OTA update might revert it back to the Dual Sim variant.)
-- thor2 -mode uefiflash -ffufile RM1105_1078.0053.10586.13169.12716.035044_ret ail_prod_signed.ffu -productcodeupdate 059X4D9 -skip_flash
After it is finished while in this mode you can run thor2 -mode rnd -readdeviceinfo to check the device details also to verify the changes.
-5- Fifth I registered an imei of the att Lumia 950 I had to my ATT account to have ims registration complete.
Steps I used to convert back to NAM 950 DS RM-1118_13058 (059X5G2) from an ATT Lumia 950 (RM-1105_12716 059X4D9)
-1- First I flashed this specific ATT ROM. The one I used is located here.
-- thor2 -mode uefiflash -ffufile "RM1105_1078.0017.10586.13053.12716.02FBB4_retail_prod_signed.ffu"
-2- Second I manually pushed three cabs to my phone to alter the plat ID back to Microsoft.MSM8992.P6218.1.0. All three were alone in the directory. Listed them below:
mmo.base.phone.plat_8bab003dbd82a4acc5989f812a0dcd284eccfe43.cab
mmo.base.variant.plat_c7b2c481e64fe6a806f52df8f5f55c59fbb6a81e.cab
mmo.device_talkman_lte_row_dsds.phone.plat_d7303236cd88dda5a304701d5b59b0c2d5260d7c.cab
-- iutool.exe -v -p "C:\CABs\Your_Location-of-RM-1118_Plat-cabs"
-3- Third I did a full NVI flash and Reset with a NAM 950 DS ROM. Link to the ffu Iocation here.
FFU File used: RM1118_1078.0027.10586.13058.15358.030FF5_retail_prod_signed.ffu
-- thor2 -mode uefiflash -ffufile "RM1118_1078.0027.10586.13058.15358.030FF5_retail_prod_signed.ffu" -do_full_nvi_update -do_factory_reset
-4- Fourth I updated the product code back to the NAM Lumia 950 DS variant just in case.
-- thor2 -mode uefiflash -ffufile RM1118_1078.0027.10586.13058.15358.030FF5_retail_prod_signed.ffu" -productcodeupdate 059X5G2 -skip_flash
What helped immensely was being able to locate and find those cab files. They are added here for convenience. I found a thread posted here on the forums that helped a ton. Even if it was a cumulative effort, a thanks to @TristanLeBoss for posting it.
Thanks for your tutorial, OP.
In China most of us bought AT&T Variant Lumia 950 (RM-1105). However, the China Variant Firmware works best as far as I know.
Would you mind my repost it to Chinese Community?
hikari_calyx said:
Thanks for your tutorial, OP.
In China most of us bought AT&T Variant Lumia 950 (RM-1105). However, the China Variant Firmware works best as far as I know.
Would you mind my repost it to Chinese Community?
Click to expand...
Click to collapse
What model is the Chinese variant? Is it a RM-1104?
To delete.
In that case being both are dual sim, in theory these directions should work. But I'm not certain if the cabs are identical or if the directions could be improved for that model. In either case you're more than welcome to use what I found here.
Edit: Wait my mistake were talking about the lumia 950 here...RM-1116 Is the xl.
Update: If the Chinese model is also an RM-1118 I'm not sure how that will work since I converted my dual sim RM-1118 to the AT&T single sim. You need to go from an AT&T single sim to a dual sim ROM...I simply lost the ability to use my second sim slot.
To delete.
DilanChd said:
Not found a Chinese package for RM-1104 (Lumia 950) and for RM-1085 (Lumia 950 XL), even from multivariants packages. Just found for RM-1116 (Lumia 950 XL Dual SIM) and for RM-1118 (Lumia 950 Dual SIM). RM-1105 (Lumia 950) is excluded due to it's an exclusive AT&T hardware variant.
RM-1116 VAR APAC CN CV
059X4Z0 RM-1118 VAR APAC CN CV
In the past, I've flashed my Lumia 550 RM-1127 with a RM-1128 package (059X692 RM-1128 VAR NAM 4R CV) just with *.ffu file and full NVI update. So, flash *.cab files to modify Platform ID is specific to AT&T ?
Click to expand...
Click to collapse
Do the RM-1127 and RM-1128 have the same PlatformID?
The cab files in the RM-1105 folder allowed me to change the PlatformID of my Dual sim RM-1118 to match that of the AT&T variant. Only then I could flash the AT&T ROM to it.
To delete.
DilanChd said:
To be honnest, I hadn't carefull if the Platform ID matches beetween RM-1127 and RM-1128. But, I think they matches, because otherwise I would not have been able to flash so easily.
Yep, I know. You can see if Platform ID of RM-1118 matches with RM-1104 ?
Click to expand...
Click to collapse
I think the PlatformID matches between RM-1104 and RM-1118, but I'm not certain. Someone would need to verify that.
nate0 said:
I think the PlatformID matches between RM-1104 and RM-1118, but I'm not certain. Someone would need to verify that.
Click to expand...
Click to collapse
In Mainland China, Lumia 950 and 950 XL are RM-1118 and RM-1116. The code of 950 is 059X4Z0.
We have already tested RM-1116 China Variant Firmware on RM-1085 from Hong Kong or European countries even the prototype for Telstra in Australia, and RM-1118 China Variant Firmware Firmware on RM-1104 from Hong Kong and RM-1118 from US.
To delete.
I'll add also, that after flashing with the RM-1105 ROM I lost LTE band 17 but gained band 30.
The device also retained a device detail of TYPE being RM-1118 even though the product code and PlatformID were that of the RM-1105. You could see this using the device info command with thor2 or by going to Extras --> Advanced Info.
nate0 said:
I'll add also, that after flashing with the RM-1105 ROM I lost LTE band 17 but gained band 30.
The device also retained a device detail of TYPE being RM-1118 even though the product code and PlatformID were that of the RM-1105. You could see this using the device info command with thor2 or by going to Extras --> Advanced Info.
Click to expand...
Click to collapse
In China, we found it's possible to add another SIM slot on Lumia 950 RM-1104 and Lumia 950 XL RM-1085 bought from European countries or Hong Kong. After the modification and flash to China Variant Firmware, the second SIM slot works fine. The Typelabel is flashed along with VPL file, and the Typelabel doesn't change if you flash FFU only.
Because the China Variant Lumia 950/XL (RM-1118/1116) is much more expensive than other variant with only single SIM slot, Chinese resellers from Shenzhen have found a way to modify other variant of Lumia 950/XL into China Variant (RM-1105 AT&T Variant is not included right now).
BTW, my brand new Lumia 950 XL RM-1116 (Unlocked, Without Contract, China Variant) cost me 2,600 Chinese Yuan (About $376).
hikari_calyx said:
In China, we found it's possible to add another SIM slot on Lumia 950 RM-1104 and Lumia 950 XL RM-1085 bought from European countries or Hong Kong. After the modification and flash to China Variant Firmware, the second SIM slot works fine.
Click to expand...
Click to collapse
With this does that include a hardware modification?
Also, I'm curious and would like to know how popular Windows 10 Mobile is for China users?
Thanks.
nate0 said:
Whith this doess that include a hardware modification?
Also, I'm curious and would like to know how popular Windows 10 Mobile is for China users?
Thanks.
Click to expand...
Click to collapse
Yes it is. Here's how it works: http://bbs.wfun.com/thread-966790-1-1.html
You may need a translator, it's in Chinese but lots of pictures provided.
In China, only minor users use Windows 10 Mobile, most of users use Android Phone or iPhone. If I met someone who use Lumia Phone or other else (e.g. HTC One M8 for Windows, HP Elite x3), I'd get excited and talk to him or her.
Hey guys, glad to see someone released this. Just to add to the guide, I successfully did this a few months ago, however to add to the OPs offering, my initial findings also allows you to flash a single sim rom to a DS*phone, along with a DS rom to single sim phone, however the main problem is that most of the update settings will not take affect because of the modem flashing is done in a way that the phone retains it on a separate partition on the phone that we don't have access too. The nvi flashing from a rom that is not native to the phone doesn't seem to flash or retain onto the phone. However this will definitely enable users to get raid of the ATT stock stuff. Something to also be extremely cautious too is that when using WDRT it sometime will not recognize the phone product code to recover and/or it will reflash the "stock" product code rom that was on the original phone, even if you updated the productcode throught thor2.
anubis23 said:
Hey guys, glad to see someone released this. Just to add to the guide, I successfully did this a few months ago, however to add to the OPs offering, my initial findings also allows you to flash a single sim rom to a DS*phone, along with a DS rom to single sim phone, however the main problem is that most of the update settings will not take affect because of the modem flashing is done in a way that the phone retains it on a separate partition on the phone that we don't have access too. The nvi flashing from a rom that is not native to the phone doesn't seem to flash or retain onto the phone. However this will definitely enable users to get raid of the ATT stock stuff. Something to also be extremely cautious too is that when using WDRT it sometime will not recognize the phone product code to recover and/or it will reflash the "stock" product code rom that was on the original phone, even if you updated the productcode throught thor2.
Click to expand...
Click to collapse
I am now curious if this type of scenario of applying a PlatformID change works for the XL model Any thoughts?
The reason I bring this up, and also strike my curiosity would be all the *8994*.dll and other files included on the 950 FFUs along with the 8992 files. Is the common theme between the xl and non-xl model? If so what purpose does that serve? Thanks.
Hey guys, I want to do this with my Lumia 950 XL Dual Sim (059X4S4) en convert it to single sim (059X4X5). Does anyone have the .CAB files needed to change the Platform ID or know where I can get them? I can't find them anywhere.
JoostL said:
Hey guys, I want to do this with my Lumia 950 XL Dual Sim (059X4S4) en convert it to single sim (059X4X5). Does anyone have the .CAB files needed to change the Platform ID or know where I can get them? I can't find them anywhere.
Click to expand...
Click to collapse
Most if not all Lumia FW are stored here. The one I pasted includes ffu's for 059X4X5. The PLAT ID change is only needed for certain Carrier variant device ROMs. I do not think you need to change the Platform ID for moving from the 059X4S4 product ROM to the 059X4X5 SS product ROM.
Thanks! I did indeed come across that website but I thought I also needed to change the PLAT ID.
I successfully flashed my 950XL with the 059X4X5 ROM.
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.
Hi there,
Is there anyone on this forum that has an Xz2 COMPACT with the VoLTE enabled? If yes, can you please let us know which firmware are you using? Many Thanks
Riolo
riolo said:
Hi there,
Is there anyone on this forum that has an Xz2 COMPACT with the VoLTE enabled? If yes, can you please let us know which firmware are you using? Many Thanks
Riolo
Click to expand...
Click to collapse
The volte is enabled based on what network you are using. Tmobile has shunned our phone and its impossible to have VOLTE. The only network giving us an official blessing is VERIZON the volte works so good. Forget about sprint and ATT is not consistent with it's game right now either.
VoLTE activation
Hi,
I have XZ2 Compact (Locked Bootloader) and after few tries, I think I managed to get VoLTE working with my carrier 2 days ago on Oreo ROM.
Maybe this will help others
I bought H8324 (DualSIM) with Central Europe 1 (CE1, CDA 1313-3194) firmware in local store, my carrier is Vodafone Czech Republic and VoLTE did not work out of the box after VoLTE and VoWifi activation in My Vodafone.
There is no option to activate VoLTE switch, it is grayed out. (Hidden Settings -> RadioInfo -> VoLTE Provisioned).
My carrier sells just XZ2 single SIM phone.
After some attempts 2 months ago with different region firmwares, that offered VoLTE Provisioned switch to be enabled (e.g. DE, CDA 1313-6204) and did not work (when call started, it immediately dropped from LTE to 2G/3G ), I tried it again 2 days ago.
On XperiFirm I found Global Vodafone Oreo firmware for XZ2 (H8216) and after UNSIN of oem_X-*.sin and system_X-*.sin files and exploring these files, I found that CDA 1313-8220 is the right firmware for Vodafone Czech.
So after that I used Newflasher to flash "hybrid" ROM.
I used XZ2C German fw (DE, CDA 1313-6204, VoLTE Provisioned can be enabled) and OEM file from XZ2 Vodafone fw (CDA 1313-8220).
To the Newflasher folder:
I copied all (*.sin) files and two folders (boot and partition) from XZ2 Compact DE firmware (CDA 1313-6204),
deleted userdata_X-*.sin file (I did not want to wipe my data),
deleted original (XZ2C) oem_X-*.sin and replaced it for the oem_X-*.sin from XZ2 Vodafone,
entered fastboot mode on phone (Power on + hold Volume down)
and flashed "hybrid" ROM with Newflasher
After reboot and enabling VoLTE Provisioned, VoLTE (probably) started working as there is no 2G/3G on call but 4G+ (screenshots attached).
So far I did not noticed any real cons.
I found ONE BIG disadvantage, at least for me. The device has lost Play Protect certification, so I can not use Google Pay for paying in stores any more.
I just noticed changes in Service menu (*#*#7378423#*#*) :
Service Info -> Software Info
Customization Version -> 1313-8220_R14A
Current Modem Config -> euro/vodafone/vlvw/cz (used to be something like *general*)
Sidenote: German (DE) Oreo firmware was the only OREO firmware I still had on my computer beside CE1. Now there are almost just PIE on XperiFirm.
Can anyone try to apply the above solution to try to get volte on more carriers with our phone in USA? Thanks.
ehBrY said:
Can anyone try to apply the above solution to try to get volte on more carriers with our phone in USA? Thanks.
Click to expand...
Click to collapse
Hi,
To you and anyone reading this, I desperately followed exactly what rSG1t did after Verizon support failed to help me getting my xz2c working. I've got an unlocked H8314 (I'm in the US) that got data fine, but call and text were not functioning.
I did everything the same for except I just flashed the US firmware from XperiFirm. No replacing of any files or that stuff.
So to OP, yes I have an XZ2C with working VoLTE. My firmware is CDA 1313-0031 USA from XperiFirm. Also if it helps you, I have radio set to LTE only, and after flashing this particular firmware the VoLTE toggle in testing menu is enabled and not grayed out. After doing all of this, it finally works on Verizon with calling, data, and text all working beautifully.
mightymightyJR said:
Hi,
To you and anyone reading this, I desperately followed exactly what rSG1t did after Verizon support failed to help me getting my xz2c working. I've got an unlocked H8314 (I'm in the US) that got data fine, but call and text were not functioning.
I did everything the same for except I just flashed the US firmware from XperiFirm. No replacing of any files or that stuff.
So to OP, yes I have an XZ2C with working VoLTE. My firmware is CDA 1313-0031 USA from XperiFirm. Also if it helps you, I have radio set to LTE only, and after flashing this particular firmware the VoLTE toggle in testing menu is enabled and not grayed out. After doing all of this, it finally works on Verizon with calling, data, and text all working beautifully.
Click to expand...
Click to collapse
So your XZ2C initially had a US firmware, an you flashed the US firmware from XperiFirm to it, and then everything works?
I am asking so, because I am in a pretty similar situation, except that my carrier is AT&T
only possible on verz
I'm in Canada using Videotron on the H8324. I can confirm that VoLTE is working using the most recent unbranded customized DE Firmware 1313-6204 52.0.A.8.14 but with both oem_*.sin files from the branded Videotron H8314 firmware. You can simply flash only the OEM files using newflasher if you already have a VoLTE-provisioned (like the DE) firmware installed.
VoLTE
riolo said:
Hi there,
Is there anyone on this forum that has an Xz2 COMPACT with the VoLTE enabled? If yes, can you please let us know which firmware are you using? Many Thanks
Riolo
Click to expand...
Click to collapse
Everyone who is using the XZ2 Compact on USA Verizon is using VoLTE. This phone does not support CDMA, so the only way it can make/receive phone calls is with LTE. (I am on Verizon.) My build number is 52.0.A.71. You may get more suitable responses if you specify which Country/Carrier and model of XZ2 you have. (8134 vs. 8234).
riolo said:
Hi there,
Is there anyone on this forum that has an Xz2 COMPACT with the VoLTE enabled? If yes, can you please let us know which firmware are you using? Many Thanks
Riolo
Click to expand...
Click to collapse
Glad it isn't just me. I have xz2 factory unlocked and am unable to call whilst using data due to my being unable to use volte
Wifi Calling on unbranded H8324 with Orange France
@rSG1t just wanted to say thank you ! I had a slightly different problem :
In France Orange doesn't support Wifi Calling on unbranded (non Orange) XZ2 Compact. I do have the option activated on my plan, but don't have the option showing in the menu.
Another problem is that Xperifirm doesn't propose any Orange Rom for France for the H8324.
So I followed your procedure with DE stock + Orange MCV FR/ES/PL/SK/RO for H8216, and it worked !
I also have the VoLTE enabled in the hidden menu, but I don't think I have this option in my plan (and I don't see the option in the settings menu), so I assume it's not working (which is not a big deal as my main goal was to be able to place and receive calls in my countryside house where I have no cellular coverage).
Vinc1 said:
I'm in Canada using Videotron on the H8324. I can confirm that VoLTE is working using the most recent unbranded customized DE Firmware 1313-6204 52.0.A.8.14 but with both oem_*.sin files from the branded Videotron H8314 firmware. You can simply flash only the OEM files using newflasher if you already have a VoLTE-provisioned (like the DE) firmware installed.
Click to expand...
Click to collapse
Hi Vinc1,
Can you Share both oem_*.sin(from the branded Videotron H8314 firmware), because I tried a number of times to download firmware from Xperifirm but it got stuck, and I required only two files, please share it will help to me
Vinc1 said:
I'm in Canada using Videotron on the H8324. I can confirm that VoLTE is working using the most recent unbranded customized DE Firmware 1313-6204 52.0.A.8.14 but with both oem_*.sin files from the branded Videotron H8314 firmware. You can simply flash only the OEM files using newflasher if you already have a VoLTE-provisioned (like the DE) firmware installed.
Click to expand...
Click to collapse
Not working, Only Indian Firmware XZ2 OEM have capability to provide Volte & Wifi Calling both, whatever Firmware you have in Xz2 Compact, just Flash OEM
I will create thread for the same