Develop Bugs

HOWTO: Install Windows 10 for Phones on Non-supported devices (and other hacks)

This is only confirmed working for the AT&T Lumia 1520 and may work as is for other phones but also might require tweaks to the XML (see below). It is very possible to brick your phone with this. Your mileage may vary!
From a high level this works by using FiddlerCore to intercept the traffic going to the Microsoft WPflights server that controls the Insider app and responds with our own custom data. The app accepts registry editing information from the web responses and acts upon that. This allows us to write stuff to select locations in the registry. In the case of the Windows 10 Preview, it appears to only look for your phone's PhoneManufacturerModelName to decide if it should be offered previews. Windows Update also checks this value. Other devices like Samsungs or HTCs may need different settings. My phone did revert to it's factory values after Windows 10 was installed (I actually think it might have done it after Windows 8.1 was installed but it continued with 10 nonetheless).
1. For the Lumia 1520 (and other phones?) reset your phone using the Windows Phone recovery tool. I recommend not logging in and setting everything up yet and just waiting til the end and doing a reset and letting it restore after you’re on Windows 10. This may not be required for your device but most likely is due to the space issue cited by Microsoft. You can see your available space in the About menu of the Windows Insiders app. Before resetting mine was ~200mb and after it was ~600mb. You can try without resetting but may get an error after it tries to download and install the update.
2. Install the [url=http://go.microsoft.com/fwlink/?LinkId=522524]Windows Insider app on your phone (you will need to have a store account configured)
3. Open the insiders app and go to the about options in the app bar and screenshot/make notes/email the settings to yourself. You may need this later.
4. Download and extract the WPInsidersHacks app (attached to this post) to your computer
5. Start the WPInsiderHacks app on pc, approve any firewall requests
6. Connect to the same WiFi that your PC is on. Edit the settings for the WiFi connection to turn on the Proxy and set it to use the PC’s IP address and enter 8877 for the port
7. Open Internet Explorer on your phone and navigate to http://[pc.ip.add.ress]:8877 where [pc.ip.add.ress] is the IP address of the PC running the WPInsidersHacks app
8. Tap on the link at the bottom to the fiddler root certificate
9. When prompted click open and then install to trust the cert and ok at the confirmation
10. Run the Windows Insider app and tap get preview builds
11. Tap on which custom action you’d like to perform. In my case I hit "Set to ATT Lumia 635" and click the arrow at the bottom
12. Accept the agreement and click the check mark at the bottom. the app will close
13. Now clear your proxy settings and run the insider app again
14. Tap get preview builds and login with your Microsoft account
15. Select the fast branch (if you’re reading this of course you want the fast branch) and click the arrow at the bottom
16. Go into the phone settings and check for updates. With any luck you should have Windows 10 there for you to install. On my AT&T 1520 it had to do 8.1 first but it kept going to 10 after 8.1 installed (had to check for updates again)
17. You’ll probably want to go into the settings and do another reset and then log into the phone and let it restore your previous data
The Windows Insider options are populated from the WPFlights.xml file. Feel free to edit/add stuff. I've experimented with writing to other keys but had mixed results. I wasn't able to write to the Software\Microsoft\Settings\{1DEF9B7D-2322-40eb-A007-16A75D5CDA6F} for example (seemed to not like the curly braces?). It should have all the same permissons as the preview for developers app. You'll just need to run the WPInsiderHacks app on your PC and point your phone's proxy settings to it if you want to go back and set something again (such as enabling tethering).

I just used this to install the TP on my Lumia 930 and .. it worked like a charm! phone is booting, OS is working! Thank you very much for the work you put into this! Really excited to try out the Preview now..
Edit: I did change the target device ID from ATT though.
Confirmed working for the Lumia 930
Confirmed working for the Lumia 920

I will try tomorrow on Lumia 520 and post result.

Not working on my Lumia 535
tried it on a Lumia 535. After Setting no proxy again the Windows Insider app shows that there is no update available.
the about-setting Shows RM-975 correctly instead of RM-1089, but I think the FW Version needs to be changed too.
Does anyone know a fix? Tried it several times by now.

LogString: DefaultCertMaker: GetRootCertificate() did not find the root in t
he Windows TrustStore.?

error0x0000034 said:
tried it on a Lumia 535. After Setting no proxy again the Windows Insider app shows that there is no update available.
the about-setting Shows RM-975 correctly instead of RM-1089, but I think the FW Version needs to be changed too.
Does anyone know a fix? Tried it several times by now.
Click to expand...
Click to collapse
Which carrier are you on? Sometimes you have to use device information for a phone on the same carrier as you're on for it to work.

I tried this with both a 520 and a 920. Everything works fine until I tap Get preview builds. I get the no builds message, but I know it's using the proxy because the WPInsiderHacks window gives this message:
** LogString: !SecureClientPipeDirect failed: System.IO.IOException Authenticati
on failed because the remote party has closed the transport stream. on pipe to (
CN=login.live.com, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.com)
** LogString: !SecureClientPipeDirect failed: System.IO.IOException Authenticati
on failed because the remote party has closed the transport stream. on pipe to (
CN=sn3301.storage.live.com, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.co
m)
Click to expand...
Click to collapse
Both devices get exactly the same result.
EDIT: I should clarify something: both the 920 and the 520 get this script. The 920 differs a bit on the device itself. Instead of going directly to the no builds page, an error pops up that says:
Server error
A connection error prevented us from downloading programs for you. Please check the date/time of your device and its network connection and try again.
Click to expand...
Click to collapse

Lumia 920
OK certificate installed
Windows insider no change ?

What would the registry entry for MOID be?
I have a non AT&T carrier, and I want to change that entry to be AT&T

Tried it on my Lumia 530 don't work i get we weren't able to find a preview build for you please confirm

Working fine on my 920 now.

I just installed. Working fine here on my Lumia 720.

For those asking, I've found you absolutely have to modify the WPFlights.xml PhoneManufacturerModelName to one that matches the carrier your device is from. In my case, I have a //Build/ (Rogers Canada) Lumia 920, and a Hong Kong unlocked 620 & 1520.
I managed to spoof the build check by using the following:
Unlocked/Hong Kong: RM-1027_1007
Rogers/Canada: RM-985_1004
http://twitter.com/stroughtonsmith/status/566460948291260417
Also, wiping the devices first /with the Windows Phone Recovery Tool/ (not Reset in Settings->About) for the most part isn't optional; only the 920 for me had enough space to install without doing that
Hope this helps

stroughtonsmith said:
For those asking, I've found you absolutely have to modify the WPFlights.xml PhoneManufacturerModelName to one that matches the carrier your device is from. In my case, I have a //Build/ (Rogers Canada) Lumia 920, and a Hong Kong unlocked 620 & 1520.
I managed to spoof the build check by using the following:
Unlocked/Hong Kong: RM-1027_1007
Rogers/Canada: RM-985_1004
http://twitter.com/stroughtonsmith/status/566460948291260417
Also, wiping the devices first /with the Windows Phone Recovery Tool/ (not Reset in Settings->About) for the most part isn't optional; only the 920 for me had enough space to install without doing that
Hope this helps
Click to expand...
Click to collapse
Hi, would you be able to upload your WPFlights.xml for me to have a look at what you have changed. For me it's not working. Cheers.

ajay003 said:
Hi, would you be able to upload your WPFlights.xml for me to have a look at what you have changed. For me it's not working. Cheers.
Click to expand...
Click to collapse
You just need to change the phonemanufacturermodel to whatever phone that supports windows 10 from your carrier/region.

ajay003 said:
Hi, would you be able to upload your WPFlights.xml for me to have a look at what you have changed. For me it's not working. Cheers.
Click to expand...
Click to collapse
The line in the screenshot is what you'd need to change; nothing too complicated, but finding a valid model for your phone's carrier is the hard part (took me a lot of Googling to find the two I needed), hence why I posted mine

stroughtonsmith said:
The line in the screenshot is what you'd need to change; nothing too complicated, but finding a valid model for your phone's carrier is the hard part (took me a lot of Googling to find the two I needed), hence why I posted mine
Click to expand...
Click to collapse
Not working for me. I'm having Lumia 920 and the carrier rom is RM-821_apac_australia_new_zealand_218. Here's my file attached. Am i doing something wrong?

What exactly did you google ? because the i am with is Telstra in Australia they have a prepaid Nokia Lumia 635 so where would i get the PhoneManufacturerModelName ?

German, Unlocked 830: RM-984_1002
For googling help: some forums automatically include the model variant in signatures of members, I just started with RM-984_10XX for 830 and tried increasing numbers for XX in order to find one that was posted a lot on german forums. Good luck!

ajay003 said:
Not working for me. I'm having Lumia 920 and the carrier rom is RM-821_apac_australia_new_zealand_218. Here's my file attached. Am i doing something wrong?
Click to expand...
Click to collapse
Yeah, you just placed RM-821_apac_australia_new_zealand_218 into the XML - that's your existing device. You need to use the correct form for a 63x/730/830 on same carrier, not your existing 920. That's the hard part to find.
My 1520 was "RM-937_apac_hong_kong_222", which I substituted for "RM-1027_1007" (a Hong Kong Lumia 636) - from what I could tell it doesn't need the "apac_hong_kong" part, but it needs the valid number at the end, and I don't know an easy way to find out what that should be (took me 50 mins of Googling to find that one).
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
th0mas96 said:
German, Unlocked 830: RM-984_1002
For googling help: some forums automatically include the model variant in signatures of members, I just started with RM-984_10XX for 830 and tried increasing numbers for XX in order to find one that was posted a lot on german forums. Good luck!
Click to expand...
Click to collapse
lmfao. I was far too lazy to try bruteforcing it, but again, that's why I posted my working ones!

Archos 50 Cesium/Bush Eluma B2 - any hope?

This is my first modern Windows Mobile (I used Windows Mobile 11 years a go) and it seems Microsoft was crippled the operating system.
Model: Bush Eluma, Windows 10 native (rebranded Archos 50 Cesium)
Specification:
Snapdragon 210
Adreno 304
1 GB RAM
16GB ROM
MicroSD support up to 128GB
5" 720x1280 IPS screen
4G LTE
WIFI/Bluetooth/GPS
8MP rear/2MP front with flash
2100mAh battery
Spec. Sheet: archos [dot] com/corporate/press/press_releases/EN_ARCHOS_50Cesium_50eHelium.pdf
What I'm trying to do: Interop-unlock
What I've managed to do: Deploy apps, such as Root Tool and vcREG
Where I'm stuck: Setting the value for my model of phone - I have no idea where to look
I hope I've provided information in a clear format. I'd very much appreciate some help or feedback in order to interop-unlock this model
System\Platform\DeviceTargetingInfo
PhoneManufacturer
Value = "True" (I think this used to just say "ARCHOS")
Thank you for reading.

Was there any progress made with this? Looking to interop unlock phone too so any help would be great

you tried this?
https://forum.xda-developers.com/windows-10-mobile/acer-liquid-jade-primo-upgrade-to-au-cu-t3589156

Worked a treat! Thanks a lot.

user154 said:
Sorry to kinda hijack this thread, but I have this device and struggling to find any other owners. My understanding is that the archos 50 cesium is the windows version of the 50e helium. I have an emmc dump of the 50e helium, if you cant already tell where im going with this, I want to flash this dump to my eluma b2 but cant get qfil or thor2 to do this. Can anyone help? or even know if this is possible?
Click to expand...
Click to collapse
I say just enjoy the W10 phone while you can, or if you really want Android, go buy that model online some where.
It is not as simple as it sounds. You would need at least a flash programmer for the SoC in that phone which usually the manufacturers never release. Depending on the format of the dump you might need other flashers or files to understand how the Archos 50 eMMC is structured or to utilize them in the flashing process. You would also want to be able to put the phone into EDL mode. If you can manage to even boot the flash programmer and initialize a flash of the phone there is also high risk of bricking it. Because you would be flashing partitions that were not signed for that phone/SoC. So I am not sure if you would also need to unlock the boot loader on it or not...sounds like you would. IMO it would be best to unlock the bootloader so you can backup the current layout of the phone. This as far as I know is not possible, so I would just stop there.
I know there are some threads in other forums where they are trying to do this with the IDOL 4s, and maybe a couple devices in the past have worked out to be able to do this. However it pretty much hinges on unlocking the boot loader. Also from what I know once you flash it like that and even if device survives (it boots, the IMEI is in tact, etc.) you cannot revert it back or it is pretty much impossible to go back without bricking it.

user154 said:
It doesnt really matter if the device is rendered unusable, it is quite a long way down the list of backup devices I have, it was more for the fun of trying to do it. The device is the exact same as its android counterpart (hardware wise) this is what made me think it should theoretically be possible. The dump I have was made with infinitybox, I have managed to create the required rawprogram.xml and patch.xml from the gpt binary contained within the dump. I have also found a couple of flash programmers for the soc (prog_emmc_firehose_8909.mbn, and a couple of manufacturer specific ones, pretty sure iv got the filename slightly wrong there). I have been able to boot the device to EDL mode using a cable, however sahara fails to load the flash programmer to the device. I didnt think the bootloader would need to be unlocked to flash the device seeing as the device is in EDL mode and what Im trying to flash is signed as is just the dump from the android counterpart. Maybe this is where im going wrong. Also Im working on the assumption the IMEI will be wiped as I plan to flash persist.img from dump too, I thought trying to keep the partition where it is stored in windows 10 and repartition the rest of the emmc to the same as the android counterpart might make things more complicated than they already are. Also IMEI can sometimes be quite simple to repair on certain devices (A lot more simple than what Im trying to acheieve here anyway). Can you point me in the right direction as to where I can find instructions to unlock the bootloader of this device? for some reason it doesnt get recognised by wpinternals (In any mode, EDL, standard flash mode, no idea what thats called on windows haha, or booted normally)
Click to expand...
Click to collapse
Sounds like you're on the right path. I'm not 100% sure you need to unlock the boot loader, however it would definitely make things easier as you could dump partitions from the phone as it is and even possibly enable mass storage mode. I am unsure where you would look to unlock that phones boot loader other than here. The flash programmers you have may not be built for the Windows Phone eMMC and why they are not booting.

Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?

JoachimP said:
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
Click to expand...
Click to collapse
If you have qpst/qfil installed on your PC, and have used them recently. The services might still be running. Just hunt for them in task manager and kill them and run thor2 again. See if that helps.

Worked a treat! Much obliged.

@nate0
Hi, thanks for your reply. I am nearly sure, I uninstalled QFIL and shutdown my pc after use, but I will check on it.

So I uninstalled QFIL and rebooted. This is the result:
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode list_connections
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode list_connections
Process started Wed Nov 14 08:48:16 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084816_ThreadId-4796.log
Debugging enabled for listconnections
WinUSB in use.
Connection list START
0.1A07:0004:0004 {71de994d-8b7c-43db-a27e-2ae7cd579a0c} Emergency mode connected
Connection list END
Exited with success
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
Process started Wed Nov 14 08:48:52 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084852_ThreadId-7500.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Message send failed with error code -1
Waiting connection to DLOAD: 2 of 2
Check if device in Dload
Message send failed with error code -1
Failed to connect to DLOAD mode
Make sure that the COM port is free. Close QPST.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 8.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_PROGRAMMER_SEND_FAILED
THOR2 1.8.2.18 exited with error code 85030 (0x14C26)
Any suggestions?

[Tweak] Fix MMS for the Open Market IDOL4s if using AT&T

Due to the mishap that happened on 6-1-2017 with inadvertent engineering builds going out to phones, some folks have opted to restore their open market Idol4s with the T-Mobile FW. They are finding themselves with issues sending MMS messages. Here is a reg file you can use to import that I know for sure works with AT&T. You need to edit it though and where it says REPLACE_WITH_YOUR_SIM_CARD_ID, you need to put the ICCID (SIM card number/ID) in place of that.
You can browse the registry using the Interop Tools app and view it (SIM card number/ID) and also import the registry file I attached with interop tools. It is located under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\ ]
Make sure you follow the directions here to install the app for editing the registry.
Some things about this reg file:
It enables SMS to SMTP Addressing with an AT&T short code
It enables show sending status
It enables automatic downloads for MMS
It uses a Lumia 950 User Agent Profile
You can edit or delete any of the strings out as needed, but I personally had no issues after importing it and then sending messages and mms on AT&T.
The reason I posted this, is due to Alcatel's lack of urgency in fixing the Open Market FFU that is currently unable to flash to the open market IDOL4s to restore it.
Let me know if there are any questions on this.

nate0 said:
Due to the mishap that happened on 6-1-2017 with inadvertent engineering builds going out to phones, some folks have opted to restore their open market Idol4s with the T-Mobile FW. They are finding themselves with issues sending MMS messages. Here is a reg file you can use to import that I know for sure works with AT&T. You need to edit it though and where it says REPLACE_WITH_YOUR_SIM_CARD_ID, you need to put the ICCID (SIM card number/ID) in place of that.
You can browse the registry using the Interop Tools app and view it (SIM card number/ID) and also import the registry file I attached with interop tools. It is located under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\ ]
Make sure you follow the directions here to install the app for editing the registry.
Some things about this reg file:
It enables SMS to SMTP Addressing with an AT&T short code
It enables show sending status
It enables automatic downloads for MMS
It uses a Lumia 950 User Agent Profile
You can edit or delete any of the strings out as needed, but I personally had no issues after importing it and then sending messages and mms on AT&T.
The reason I posted this, is due to Alcatel's lack of urgency in fixing the Open Market FFU that is currently unable to flash to the open market IDOL4s to restore it.
Let me know if there are any questions on this.
Click to expand...
Click to collapse
Good afternoon, what do you know about flashing in the open market model? i have this issue, can´t flash open market whit ffu

@rjcs123
The open market FFU is different as far as the PLAT ID it is needing matched in order to flash the FFU and I did confirm. It is part of the series of checks the flashing does before loading the FW. My open market model IDOL 4s phone Plat ID is ALCATEL.8996.IDOL4S identified from a xml under an Image Update folder. Not sure why this scenario exists for the open market ffu but it does.
I have not figured out how to mount the PLAT partition from my phone as an MTP mount or some other way. If we could that is one way it could be changed. It looks like it resides in a SMBIOS.CFG file under PLAT:\SMBIOS\SMBIOS.CFG
Pushing a cab file to alter it would be a second method. But one does not exist yet. Ultimately the OEM needs to figure out what they need to do to fix it...
You can see the difference when comparing the T-Mo ffu with the open market, and this is why it fails.
I confirmed a dump from the FFUs below:
TMOUS PLAT ID identified in the FFU below:
Number of partitions found 34
Warning: RKH of SBL1 is missing from the FFU. Flashing the FFU may result non-booting device.
Warning: RKH of UEFI is missing from the FFU. Flashing the FFU may result non-booting device.
Platform ID: ALCATEL.8996.IDOL4S
Hi. index sector 40955648
Computing integrity of FFU. Please wait...
.............
FFU integrity OK.
Open Market FFU PLAT ID identified in the FFU below:
Number of partitions found 34
Warning: RKH of SBL1 is missing from the FFU. Flashing the FFU may result non-booting device.
Warning: RKH of UEFI is missing from the FFU. Flashing the FFU may result non-booting device.
Platform ID: ALCATEL.8996.IDOL4S.NA
Hi. index sector 40955648
Computing integrity of FFU. Please wait...
...............
FFU integrity OK.
Now, what does not make sense is that the PLAT partition extracted from the FFU of the OPEN market device is also listed with the same PLAT ID as everything else as ALCATEL.8996.IDOL4S. I think the OEM really messed up here honestly. It is a hex file and you can see it below. I am not sure if the FFUs are signed this way on purpose and the PLAT info was never updated or if something else is at fault here. Anyone else can chime in to add other info that would be great.
Cfg version, if the data layout changes ever, Ignore for now.
CFG:01.01
# Compatible SMBIOS versions, Ignore for now.
VER:02.03
VER:02.06
# Manufacturer
01,04,S,"ALCATEL"
# Family
01,1A,S,"8996"
# Product Name
01,05,S,"IDOL4S"
# Version
01,06,S,"1.0"
# Blank line needed after the last config

nate0 said:
@rjcs123
The open market FFU is different as far as the PLAT ID it is needing matched in order to flash the FFU and I did confirm. It is part of the series of checks the flashing does before loading the FW. My open market model IDOL 4s phone Plat ID is ALCATEL.8996.IDOL4S identified from a xml under an Image Update folder. Not sure why this scenario exists for the open market ffu but it does.
I have not figured out how to mount the PLAT partition from my phone as an MTP mount or some other way. If we could that is one way it could be changed. It looks like it resides in a SMBIOS.CFG file under PLAT:\SMBIOS\SMBIOS.CFG
Pushing a cab file to alter it would be a second method. But one does not exist yet. Ultimately the OEM needs to figure out what they need to do to fix it...
You can see the difference when comparing the T-Mo ffu with the open market, and this is why it fails.
I confirmed a dump from the FFUs below:
TMOUS PLAT ID identified in the FFU below:
Number of partitions found 34
Warning: RKH of SBL1 is missing from the FFU. Flashing the FFU may result non-booting device.
Warning: RKH of UEFI is missing from the FFU. Flashing the FFU may result non-booting device.
Platform ID: ALCATEL.8996.IDOL4S
Hi. index sector 40955648
Computing integrity of FFU. Please wait...
.............
FFU integrity OK.
Open Market FFU PLAT ID identified in the FFU below:
Number of partitions found 34
Warning: RKH of SBL1 is missing from the FFU. Flashing the FFU may result non-booting device.
Warning: RKH of UEFI is missing from the FFU. Flashing the FFU may result non-booting device.
Platform ID: ALCATEL.8996.IDOL4S.NA
Hi. index sector 40955648
Computing integrity of FFU. Please wait...
...............
FFU integrity OK.
Now, what does not make sense is that the PLAT partition extracted from the FFU of the OPEN market device is also listed with the same PLAT ID as everything else as ALCATEL.8996.IDOL4S. I think the OEM really messed up here honestly. It is a hex file and you can see it below. I am not sure if the FFUs are signed this way on purpose and the PLAT info was never updated or if something else is at fault here. Anyone else can chime in to add other info that would be great.
Cfg version, if the data layout changes ever, Ignore for now.
CFG:01.01
# Compatible SMBIOS versions, Ignore for now.
VER:02.03
VER:02.06
# Manufacturer
01,04,S,"ALCATEL"
# Family
01,1A,S,"8996"
# Product Name
01,05,S,"IDOL4S"
# Version
01,06,S,"1.0"
# Blank line needed after the last config
Click to expand...
Click to collapse
when i tray to flash cellphone dont no match FFU. the result is for t-mobile =ALCATEL.8996.IDOL4S.1.0 and open market=ALCATEL.8996.IDOL4S.NA.. I have another Alcatel idol 4s from t-mobile and I would like to unlock it . whats service recomend you? T-mobile does not want to unlock it because i not have an acountt .
Regards!

I answered what I could for you in your thread about unlocking the T-Mobile model. Please keep those questions for that thread over there, so not to take this one off topic.

Hi, could you explain more about your post?
I have L630 ds , can I try this??

mirasal2 said:
Hi, could you explain more about your post?
I have L630 ds , can I try this??
Click to expand...
Click to collapse
It could be used if MMS is not working on your Lumia if you wanted to try it. This is occurring for the T-Mobile version of the IDOL4s while using it unlocked on AT&T.
What seems to be your issue?

nate0 said:
It could be used if MMS is not working on your Lumia if you wanted to try it. This is occurring for the T-Mobile version of the IDOL4s while using it unlocked on AT&T.
What seems to be your issue?
Click to expand...
Click to collapse
My mobile phone doesn't send or receive mms what ever I do, I had visited my cellphone carier with no results ?

nate0 said:
Due to the mishap that happened on 6-1-2017 with inadvertent engineering builds going out to phones, some folks have opted to restore their open market Idol4s with the T-Mobile FW. They are finding themselves with issues sending MMS messages. Here is a reg file you can use to import that I know for sure works with AT&T. You need to edit it though and where it says REPLACE_WITH_YOUR_SIM_CARD_ID, you need to put the ICCID (SIM card number/ID) in place of that.
You can browse the registry using the Interop Tools app and view it (SIM card number/ID) and also import the registry file I attached with interop tools. It is located under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\ ]
Make sure you follow the directions here to install the app for editing the registry.
Some things about this reg file:
It enables SMS to SMTP Addressing with an AT&T short code
It enables show sending status
It enables automatic downloads for MMS
It uses a Lumia 950 User Agent Profile
You can edit or delete any of the strings out as needed, but I personally had no issues after importing it and then sending messages and mms on AT&T.
The reason I posted this, is due to Alcatel's lack of urgency in fixing the Open Market FFU that is currently unable to flash to the open market IDOL4s to restore it.
Let me know if there are any questions on this.
Click to expand...
Click to collapse
Hello,
I've just bought an Idol 4S on Microsoft Store US to use it in France and it works well except MMS.
I can send MMS if I set a blank name for the SIM Card (one space in fact to enable saving) and use some APN settings found on the Internet.
But I can't receive MMS and my carrier (Bouygues Telecom) can't (or doesn't want to) help me.
So, I've tried to import your reg file, but I still have the problem for receiving MMS.
And I've noticed a mistake maybe:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cellular\SMS]
"MsgQueuSize"=dword:00000400
or
"MsgQueueSize"=dword:00000400
Thanks for your help.

Looks like its queue, but I am not using the IDOL for what is below, it is from a 950 XL on T-Mobile. let me check the reg file...
{
"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"
}

martzelx said:
Hello,
I've just bought an Idol 4S on Microsoft Store US to use it in France and it works well except MMS.
I can send MMS if I set a blank name for the SIM Card (one space in fact to enable saving) and use some APN settings found on the Internet.
But I can't receive MMS and my carrier (Bouygues Telecom) can't (or doesn't want to) help me.
So, I've tried to import your reg file, but I still have the problem for receiving MMS.
And I've noticed a mistake maybe:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cellular\SMS]
"MsgQueuSize"=dword:00000400
or
"MsgQueueSize"=dword:00000400
Thanks for your help.
Click to expand...
Click to collapse
So my current phone has it a totally different location ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cellular\SMS\Store] "MsgQueueSize"=dword:00000400)
I am not certain if that is an error on my part or if Microsoft changed its path. Either way I will upload a new reg file for that.

nate0 said:
So my current phone has it a totally different location ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cellular\SMS\Store] "MsgQueueSize"=dword:00000400)
I am not certain if that is an error on my part or if Microsoft changed its path. Either way I will upload a new reg file for that.
Click to expand...
Click to collapse
Thanks for the new reg file.
I have test it but it is the same.
My phone can send but not receive MMS.
How can I be certain that the phone reads the new registry keys ?
I have tried to add some toggles to check but without effect:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\*MY ICCID*]
"ShowAutomaticallyDownloadMMSToggle"=dword:00000001
"ShowRequiredMonthlyTest"=dword:00000001
Thanks.

martzelx said:
Thanks for the new reg file.
I have test it but it is the same.
My phone can send but not receive MMS.
How can I be certain that the phone reads the new registry keys ?
I have tried to add some toggles to check but without effect:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\*MY ICCID*]
"ShowAutomaticallyDownloadMMSToggle"=dword:00000001
"ShowRequiredMonthlyTest"=dword:00000001
Thanks.
Click to expand...
Click to collapse
Are you even using AT&T? The keys here in the first post were meant to help people correct an MMS issue on AT&T because of being forced to use T-Mobile firmware.

nate0 said:
Are you even using AT&T? The keys here in the first post were meant to help people correct an MMS issue on AT&T because of being forced to use T-Mobile firmware.
Click to expand...
Click to collapse
Hi nate0,
No, I'm not using AT&T but I have modified the reg file for my carrier.
I got values from my oldies Lumia 930 and Lumia 950 that were working perfectly.
But, it seems that adding or changing registry keys has no effect.
That's why I 'm looking for a registry key that has a visual effect.
Xavier

OK, I'll see where I can help. Have you checked the APN settings? Never mind I see that in one of your posts you set the APN manually. The only issue is that you can't receive mms correct?

nate0 said:
OK, I'll see where I can help. Have you checked the APN settings? Never mind I see that in one of your posts you set the APN manually. The only issue is that you can't receive mms correct?
Click to expand...
Click to collapse
Yes, I can send MMS but I can't receive MMS.
APN Settings have been checked with the carrier support and it is OK, but they can't (don't want to) help me further because it is a US phone.
But, the weird thing is that I can only send MMS when the "SIM Card name" is blank (with a space).
If I put the real name of my carrier, sendind (and also receiving) does'nt work.

Manually setting an mms APN will override certain key values and settings under HKLM\SOFTWARE\Microsoft\Messaging\. It sets value under SOFTWARE\Microsoft\Messaging\PerProviderSettings\ to use the provided apn profile. Did you try removing the mms APN to see how it performs? Could you share what keys values you changed?

nate0 said:
Manually setting an mms APN will override certain key values and settings under HKLM\SOFTWARE\Microsoft\Messaging\. It sets value under SOFTWARE\Microsoft\Messaging\PerProviderSettings\ to use the provided apn profile. Did you try removing the mms APN to see how it performs? Could you share what keys values you changed?
Click to expand...
Click to collapse
If I remove my custom profiles (Internet and MMS), Nothing works because the phone has not the default settings of european carriers in the FFU.
But, if I well understand what you replied yesterday, it is normal that "PerSIMSettings" changes have not effect, because I use custom APN settings stored in the HKML\SOFTWARE\Microsoft\Messaging\PerProviderSettings key.
Is it correct ?
And here's my keys values:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\@[email protected]]
"ADDR"="http://mms.bouyguestelecom.fr/mms/wapenc"
"TO-NAPID"="Bouygues MMS_m"
"TO-PROXY"="Bouygues MMS_m-PRXY"
"MS"=dword:00000258
"ConnectionNameSuffix"="WAP"
"AllowSelectAllContacts"=dword:00000001
"MaxRetryCount"=dword:00000003
"RetrySize"=dword:0000012c
"TargetVideoFormat"=dword:00000000
"UseUTF8ForUnspecifiedCharset"=dword:00000001
"UAProf"="http://useragentprofile.microsoft.com/uaprof/Lumia950r100.xml"
"UserAgentString"="WindowsPhoneMMS/1.0 WindowsPhoneOS/10.0-13333 MICROSOFT-Lumia 950"
"ShowAutomaticallyDownloadMMSToggle"=dword:00000001
"MMSGroupText"=dword:0000000
"DeliveryNotifySupported"=dword:0000001
"SMSDeliveryNotify"=dword:0000000
Thanks for spending time on my problem.

I am not certain which key values get overridden when you enter an APN manually...
What I would do is start over, because what you really need is to either defer to someone from your region with a working device....or maybe even export all the keys from [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\] and [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cellular\] from one of your working devices, and compare and contrast. It is a pain to do but it is hard to tell what key(s) that you imported are causing the problem from my end. There is a key you can add that generates and error code, in the app whenever there is an error that you could try....Maybe it could help
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\REPLACE_WITH_YOUR_SIM_CARD_ID]
"ErrorCodeEnabled"=dword:00000001
Here are some other keys that you could try too that I do not see in what you pasted.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\REPLACE_WITH_YOUR_SIM_CARD_ID]
"AutomaticallyDownload"=dword:00000001
"AutoRetryDownload"=dword:0000001
"MMSLimitAttachments"=dword:00000005

nate0 said:
I am not certain which key values get overridden when you enter an APN manually...
What I would do is start over, because what you really need is to either defer to someone from your region with a working device....or maybe even export all the keys from [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\] and [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cellular\] from one of your working devices, and compare and contrast. It is a pain to do but it is hard to tell what key(s) that you imported are causing the problem from my end. There is a key you can add that generates and error code, in the app whenever there is an error that you could try....Maybe it could help
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\REPLACE_WITH_YOUR_SIM_CARD_ID]
"ErrorCodeEnabled"=dword:00000001
Here are some other keys that you could try too that I do not see in what you pasted.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Messaging\PerSimSettings\REPLACE_WITH_YOUR_SIM_CARD_ID]
"AutomaticallyDownload"=dword:00000001
"AutoRetryDownload"=dword:0000001
"MMSLimitAttachments"=dword:00000005
Click to expand...
Click to collapse
Thanks for your reply.
I have already test these keys, specially the ErrorCodeEnabled, but I never got an error code.
That's the problem, it seems to have no effect.

[Guide] Enable AT&T US HD Voice/VoLTE on non-supported W10M phones

This is how I enabled AT&T US HD Voice/VoLTE on the Lumia 950 XL Dual sim and the factory Unlocked Alcatel IDOL 4s. It should work on the Lumia 950 Dual sim too, but I have not tested this method on it yet.
*Requires full file system access with MTP or SFTP using Interop tools
*All the files attached were taken from the latest AT&T Lumia 950 FFU (01078.00053.16236.35035 - OS 10.0.10586.318)
*To reset everything back to original factory settings requires either a re-flash or you can take the files you backed up before hand and replace them back.
**The one caveat to this is you need to use an AT&T Lumia 950 imei to register to your ICCID (sim card ID) with AT&T customer support to enable the hd voice/ims registration to come online. It might work with a Lumia 830 imei for AT&T too.
***There was mention of AT&T possibly whitelisting your device. This would allow IMS provisioning to complete without the need to have AT&T update your IMEI with that of a AT&T branded one. Seems even though you can ask AT&T to do this, it has not actually been proven to work. The only for sure way is to use a AT& branded Lumia 950 IMEI.
Update 7/20/2017: Updated files attached to include the specific ATT-US files from the 950 XL rom RM-1085_15919 (product: 059X7S5). The modem file is slightly different as it provisions with the same bands that come default already on the 950XL, it will not remove band 17 like the 950 ATT modemconfiguration.cab file does. The modem files as far as I know only work on the x50 Lumia models and not OEM models.
Install Interop Tools
- Here is the link. I used version InteropTools_1.9.437.0_arm_RC3.
Install Swish
- This sftp client found here (needed for Lumia 950/XL) for explorer sftp support. For the IDOL 4s enable Full file system access via MTP with read write access in Interop Tools under the Unlock options/settings.
Gain access to the file systems using Interop Tools app.
- In Interop Tools go the SSH--Account Manager and add an account. The account user name should be System.
- Tap the account System so it is highlighted and then tap templates to use.
- Tap enable full file system access with sftp. Then go to the template options and hit the authentication drop down setting it to password.
- Add the password (4 digit pin of your choice).
- Once your phone is on wifi, add an SFTP Connection under Swish. Set the user to system. Set the path to /c/. Once added double click it and login with the pin you set. Explorer will open with your phones files. There is a guide in more detail on sftp file system access made by snickler if you need to see more details about this method.
For the Lumia 950/XL do the below:
- Copy and back up all files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM.
- Then Copy and replace the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM with the files of the zip file titled ADC.zip
- Copy and backup the file under C:\Programs\CommonFiles\OEM\Public\MMO\Multivariant.
- Then Copy and replace the file under C:\Programs\CommonFiles\OEM\Public\MMO\Multivariant with the contents of the zip file titled modemconfiguration.zip
- From there do a hard reset.
For the Alcatel IDOL 4s do the below using full file system access with MTP:
- Copy and backup all the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM.
- Then Copy and replace the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM with the contents of the zip file titled ADC.zip
- From there do a hard reset.
When the OOBE setup returns after hard reset, you may have a light blue/cyan theme and the display/dpi/font size may be a bit different too. This is due to the packages used from the AT&T 950. Go through the normal setup and let it fully boot to the start screen. Wait for the prompt to tell you to reboot your phone for settings/sim card settings to change/update.
Alternatively you can add the two files in the zip file titled MO_VoLTE_1117.zip to the c:\windows\system32. This will replace the MO_VoLTE_Label_1117.dll and MO_VoLTE_Description_1117.dll details found near the volte toggle under Sim settings with the proper descriptions.
To reset everything back to original factory settings requires either a re-flash or you can take the files you backed up prior and replace them back.
Thanks to the creator of interop tools @gus33000. Without access to that tool/app this and other things like this would not be possible. To @snickler for finding and explaining the sftp file system access in a guide to help others like me use that method.

nate0 said:
This is how I enabled AT&T US HD Voice/VoLTE on the Lumia 950 XL Dual sim and the factory Unlocked Alcatel IDOL 4s. It should work on the Lumia 950 Dual sim too, but I have not tested this method on it yet.
*Requires full file system access with MTP or SFTP using Interop tools
*All the files attached were taken from the latest AT&T Lumia 950 FFU (01078.00053.16236.35035 - OS 10.0.10586.318)
*To reset everything back to original factory settings requires either a re-flash or you can take the files you backed up before hand and replace them back.
**The one caveat to this is you need to use an AT&T Lumia 950 imei to register to your ICCID (sim card ID) with AT&T customer support to enable the hd voice/ims registration to come online. It may work with lets say a Lumia 830 imei for AT&T too. I do not have one anymore to test though.
Install Interop Tools
- Here is the link. I used version InteropTools_1.9.437.0_arm_RC3.
Install Swish
- This sftp client found here (needed for Lumia 950/XL) for explorer sftp support. For the IDOL 4s enable Full file system access via MTP with read write access in Interop Tools under the Unlock options/settings.
Gain access to the file systems using Interop Tools app.
- In Interop Tools go the SSH--Account Manager and add an account. The account user name should be System.
- Tap the account System so it is highlighted and then tap templates to use.
- Tap enable full file system access with sftp. Then go to the template options and hit the authentication drop down setting it to password.
- Add the password (4 digit pin of your choice).
- Once your phone is on wifi, add an SFTP Connection under Swish. Set the user to system. Set the path to /c/. Once added double click it and login with the pin you set. Explorer will open with your phones files. There is a guide in more detail on sftp file system access made by snickler if you need to see more details about this method.
For the Lumia 950/XL do the below:
- Copy and back up all files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM.
- Then Copy and replace the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM with the files of the zip file titled ADC.zip
- Copy and backup the file under C:\Programs\CommonFiles\OEM\Public\MMO\Multivariant.
- Then Copy and replace the file under C:\Programs\CommonFiles\OEM\Public\MMO\Multivariant with the contents of the zip file titled modemconfiguration.zip
- From there do a hard reset.
For the Alcatel IDOL 4s do the below using full file system access with MTP:
- Copy and backup all the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM.
- Then Copy and replace the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM with the contents of the zip file titled ADC.zip
- From there do a hard reset.
When the OOBE setup returns after hard reset, you may have a light blue/cyan theme and the display/dpi/font size may be a bit different too. This is due to the packages used from the AT&T 950. Go through the normal setup and let it fully boot to the start screen. Wait for the prompt to tell you to reboot your phone for settings/sim card settings to change/update.
Alternatively you can add the two files in the zip file titled MO_VoLTE_1117.zip to the c:\windows\system32. This will replace the MO_VoLTE_Label_1117.dll and MO_VoLTE_Description_1117.dll details found near the volte toggle under Sim settings with the proper descriptions.
To reset everything back to original factory settings requires either a re-flash or you can take the files you backed up prior and replace them back.
Thanks to the creator of interop tools @gus33000. Without access to that tool/app this and other things like this would not be possible. To @snickler for finding and explaining the sftp file system access in a guide to help others like me use that method.
Click to expand...
Click to collapse
Should i try it in lumia 930

subhamnayan said:
Should i try it in lumia 930
Click to expand...
Click to collapse
Phones that came with WP8/8.1 are set up differently and may not provision files the same way during a hard reset. But if you want to try it and just see if it contains the same file/directory structure you can. I only test this officially on the 950 XL and factory unlocked NA IDOL4s.

nate0 said:
Phones that came with WP8/8.1 are set up differently and may not provision files the same way during a hard reset. But if you want to try it and just see if it contains the same file/directory structure you can. I only test this officially on the 950 XL and factory unlocked NA IDOL4s.
Click to expand...
Click to collapse
No it does not contains same directory

subhamnayan said:
No it does not contains same directory
Click to expand...
Click to collapse
It is up to you then. It might be a waste of time or if it could work it would require more than what I have shared.

@subhamnayan
The Nokia phones use individual NVI files that are not rolled up in a modemconfiguration.cab file. See this other post I made about enabling additional bands on the 1520. You might be able to use some of the info there to get what you are looking for (https://forums.windowscentral.com/search.php?searchid=34263546)

nate0 said:
This is how I enabled AT&T US HD Voice/VoLTE on the Lumia 950 XL Dual sim and the factory Unlocked Alcatel IDOL 4s. It should work on the Lumia 950 Dual sim too, but I have not tested this method on it yet.
*Requires full file system access with MTP or SFTP using Interop tools
*All the files attached were taken from the latest AT&T Lumia 950 FFU (01078.00053.16236.35035 - OS 10.0.10586.318)
*To reset everything back to original factory settings requires either a re-flash or you can take the files you backed up before hand and replace them back.
**The one caveat to this is you need to use an AT&T Lumia 950 imei to register to your ICCID (sim card ID) with AT&T customer support to enable the hd voice/ims registration to come online. It may work with lets say a Lumia 830 imei for AT&T too. I do not have one anymore to test though.
Update 7/20/2017: Updated files attached to include the specific ATT-US files from the 950 XL rom RM-1085_15919 (product: 059X7S5). The modem file is slightly different as it provisions with the same bands that come default already on the 950XL, it will not remove band 17 like the 950 ATT modemconfiguration.cab file does. The modem files as far as I know only work on the x50 Lumia models and not OEM models.
Install Interop Tools
- Here is the link. I used version InteropTools_1.9.437.0_arm_RC3.
Install Swish
- This sftp client found here (needed for Lumia 950/XL) for explorer sftp support. For the IDOL 4s enable Full file system access via MTP with read write access in Interop Tools under the Unlock options/settings.
Gain access to the file systems using Interop Tools app.
- In Interop Tools go the SSH--Account Manager and add an account. The account user name should be System.
- Tap the account System so it is highlighted and then tap templates to use.
- Tap enable full file system access with sftp. Then go to the template options and hit the authentication drop down setting it to password.
- Add the password (4 digit pin of your choice).
- Once your phone is on wifi, add an SFTP Connection under Swish. Set the user to system. Set the path to /c/. Once added double click it and login with the pin you set. Explorer will open with your phones files. There is a guide in more detail on sftp file system access made by snickler if you need to see more details about this method.
For the Lumia 950/XL do the below:
- Copy and back up all files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM.
- Then Copy and replace the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM with the files of the zip file titled ADC.zip
- Copy and backup the file under C:\Programs\CommonFiles\OEM\Public\MMO\Multivariant.
- Then Copy and replace the file under C:\Programs\CommonFiles\OEM\Public\MMO\Multivariant with the contents of the zip file titled modemconfiguration.zip
- From there do a hard reset.
For the Alcatel IDOL 4s do the below using full file system access with MTP:
- Copy and backup all the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM.
- Then Copy and replace the files under C:\Programs\CommonFiles\ADC\Microsoft and C:\Programs\CommonFiles\ADC\OEM with the contents of the zip file titled ADC.zip
- From there do a hard reset.
When the OOBE setup returns after hard reset, you may have a light blue/cyan theme and the display/dpi/font size may be a bit different too. This is due to the packages used from the AT&T 950. Go through the normal setup and let it fully boot to the start screen. Wait for the prompt to tell you to reboot your phone for settings/sim card settings to change/update.
Alternatively you can add the two files in the zip file titled MO_VoLTE_1117.zip to the c:\windows\system32. This will replace the MO_VoLTE_Label_1117.dll and MO_VoLTE_Description_1117.dll details found near the volte toggle under Sim settings with the proper descriptions.
To reset everything back to original factory settings requires either a re-flash or you can take the files you backed up prior and replace them back.
Thanks to the creator of interop tools @gus33000. Without access to that tool/app this and other things like this would not be possible. To @snickler for finding and explaining the sftp file system access in a guide to help others like me use that method.
Click to expand...
Click to collapse
It worked on my Lumia 950 XL
Look on LumiaFirmware.com for an FFU from your provider (in my case the Lumia 950) mount it with ImgMount and extract the files mentioned above.
for me no reset was necessary, as soon as I pasted the files in the ADC folder I got a message that "SIM settings have been changed please restart" and IMS registration was on
That's my findings so far

Flavius Etius said:
It worked on my Lumia 950 XL
Look on LumiaFirmware.com for an FFU from your provider (in my case the Lumia 950) mount it with ImgMount and extract the files mentioned above.
for me no reset was necessary, as soon as I pasted the files in the ADC folder I got a message that "SIM settings have been changed please restart" and IMS registration was on
That's my findings so far
Click to expand...
Click to collapse
Is yours a DualSIM 950XL?
I am trying to bring up my 059X523 RM-1116 VAR EURO A6 CV BLACK (Lumia 950XLDS) on T-Mobile Germany to register for VoLTE.
My 950XL (059X4V3 RM-1085 VAR EURO 1X CV BLACK) is working fine in VoLTE, the 950XLDS is not allowed in the Network.

@goreng
I think there is only one TMO firmware for the 950 XL and it is for the dual sim. Not sure what regions it is open to but here are the details
Phone model: Lumia 950 XL Dual SIM
PackageTitle: RM-1116 VAR EURO PL TMO BLACK
Product Code: 059X502
manufacturerHardwareModel: RM-1116
Last Firmware: 01078.00053.16236.35012
OperatorName: TMO-PL,
I am from the US so I am not familiar with the regions/carriers of there. Might be worth a look though.

goreng said:
Is yours a DualSIM 950XL?
I am trying to bring up my 059X523 RM-1116 VAR EURO A6 CV BLACK (Lumia 950XLDS) on T-Mobile Germany to register for VoLTE.
My 950XL (059X4V3 RM-1085 VAR EURO 1X CV BLACK) is working fine in VoLTE, the 950XLDS is not allowed in the Network.
Click to expand...
Click to collapse
My Lumia 950 XL is single SIM. SO far I do not know if it's possible to get it work on a Dual SIM (without disabling the second SIM slot)

Can it be used for other carriers???
Sorry for noob question.

It is. I switched to T-Mobile US and it is actually easier to do this (enabling VoLTE/HD Voice/VoWiFi) than on AT&T...which I kind of expected. It may be possible to do this on other carriers in other regions too, but it largely depends a lot on the device itself. For T-Mobile it is possible to configure VoLTE/HD Voice/VoWiFi for the IDOL 4s Open market variant and Lumia 950 XL RM-1085, 830 (VoLTE/HD Voice), 650 RM-1150 (VoLTE/HD Voice), 640 XL RM-1063 (VoLTE/HD Voice) and there may be others. The 930/929 and 1520 are unusual in that I never could figure out how to enabled any features like this for any carriers on them.

Help
nate0 said:
It is. I switched to T-Mobile US and it is actually easier to do this (enabling VoLTE/HD Voice/VoWiFi) than on AT&T...which I kind of expected. It may be possible to do this on other carriers in other regions too, but it largely depends a lot on the device itself. For T-Mobile it is possible to configure VoLTE/HD Voice/VoWiFi for the IDOL 4s Open market variant and Lumia 950 XL RM-1085, 830 (VoLTE/HD Voice), 650 RM-1150 (VoLTE/HD Voice), 640 XL RM-1063 (VoLTE/HD Voice) and there may be others. The 930/929 and 1520 are unusual in that I never could figure out how to enabled any features like this for any carriers on them.
Click to expand...
Click to collapse
I want to enable it for "Jio" a carrier in INDIA that provides VoLTE services but only android and ios users are able to use it and they donot sell a specific lumia with VoLTE services or there carrier name on it.
*I am using L950XL DS Indian Variant.
*Is this possible??? If yes can you guide me how to edit configuration files to do this.

subhamnayan said:
I want to enable it for "Jio" a carrier in INDIA that provides VoLTE services but only android and ios users are able to use it and they donot sell a specific lumia with VoLTE services or there carrier name on it.
*I am using L950XL DS Indian Variant.
*Is this possible??? If yes can you guide me how to edit configuration files to do this.
Click to expand...
Click to collapse
I was mainly referring to US carriers. You would need to get a hold of a Windows 10 Mobile handset that supports VoLTE on Jio and build new nvi file entries for the Lumia. I don't know of a model that would support Jio VoLTE except maybe the IDOL 4s Pro model that support European Countries. Once you find a Windows 10 Mobile phone that supports VoLTE on that carrier you a starting point.

nate0 said:
I was mainly referring to US carriers. You would need to get a hold of a Windows 10 Mobile handset that supports VoLTE on Jio and build new nvi file entries for the Lumia. I don't know of a model that would support Jio VoLTE except maybe the IDOL 4s Pro model that support European Countries. Once you find a Windows 10 Mobile phone that supports VoLTE on that carrier you a starting point.
Click to expand...
Click to collapse
There aren't any WP that supports jio VoLTE

nate0 said:
**The one caveat to this is you need to use an AT&T Lumia 950 imei to register to your ICCID (sim card ID) with AT&T customer support to enable the hd voice/ims registration to come online.
Click to expand...
Click to collapse
Thanks for the guide! I completed the steps on my 950xl and HD voice works, but I'm having trouble getting IMS to stay registered.
I have a new SIM being shipped to me and plan on registering it with an at&t branded 950 IMEI. When you did yours, was the SIM in the 950 or the 950 XL when you called and registered? If it was the 950, then I guess I need to buy one, but if just the IMEI is needed, then I just need the number, right? Did you call or do it online?

Notyours said:
Thanks for the guide! I completed the steps on my 950xl and HD voice works, but I'm having trouble getting IMS to stay registered.
I have a new SIM being shipped to me and plan on registering it with an at&t branded 950 IMEI. When you did yours, was the SIM in the 950 or the 950 XL when you called and registered? If it was the 950, then I guess I need to buy one, but if just the IMEI is needed, then I just need the number, right? Did you call or do it online?
Click to expand...
Click to collapse
I only used the 950 imei. I also had this happen once where my SIM went bad and ims and LTE were broken. I could not lock LTE bands therefore ims would fail. Might not be similar to your situation though.
Also you can do it online with support.

Just a follow up for anyone else following this thread. I figured out why my IMS registration kept unregistering.
I got it registered by putting my existing SIM into an at&t branded 950. The IMS registered and I was able to make HD calls. I put in back into my modified 950xl and the IMS would stay registered only for a few minutes. I was being greedy. I wanted WiFi calling in addition to HD Voice. After turning off WiFi calling my IMS has been registered for over 24 hours now.

I am having really bad luck with this process. First time my 950xl DS couldn't recognize either SIM slot, now there is only one SIM being recognized but it is not reading the sim card. It is a functioning card. I wonder if I'm missing something or putting in the wrong files from the zip? I assume this is a modem issue...

spe317 said:
I am having really bad luck with this process. First time my 950xl DS couldn't recognize either SIM slot, now there is only one SIM being recognized but it is not reading the sim card. It is a functioning card. I wonder if I'm missing something or putting in the wrong files from the zip? I assume this is a modem issue...
Click to expand...
Click to collapse
What files did you use and where did you place them?
Did you run any thor2 commands?

Dumped RDC file from a RM-1063 prototype

I was able to dump the RDC that is provisioned to my 640 XL prototype. I dumped it and renamed it with a .bin extension. Have a couple of questions for those that know more about as I currently know little.
1. What is the RDC file, meaning what does it consist of? Or how is it used?
2. Where is it written when writing it from thor2? Or where is it stored on the phone?
3. Can it be re-used or is it good only for the one device it is provisioned to?
So, I am not sure if "dump" is the correct term to use here, as the command from thor2 would include the option -readrdc which sends it to a file that you choose...So it is reading something from the phone and generating a file...
I opened the file in hex editor but see little about its contents. It is small in size, about 804 bytes. I tried to write it to a different device same model but it failed with a specific error "Certificate error 25 (0x19) (0)"
Thanks.

Where to get prototypes phone?

nate0 said:
I was able to dump the RDC that is provisioned to my 640 XL prototype. I dumped it and renamed it with a .bin extension. Have a couple of questions for those that know more about as I currently know little.
1. What is the RDC file, meaning what does it consist of? Or how is it used?
2. Where is it written when writing it from thor2? Or where is it stored on the phone?
3. Can it be re-used or is it good only for the one device it is provisioned to?
So, I am not sure if "dump" is the correct term to use here, as the command from thor2 would include the option -readrdc which sends it to a file that you choose...So it is reading something from the phone and generating a file...
I opened the file in hex editor but see little about its contents. It is small in size, about 804 bytes. I tried to write it to a different device same model but it failed with a specific error "Certificate error 25 (0x19) (0)"
Thanks.
Click to expand...
Click to collapse
A RDC file is a research and development certificate tied to the device hardware it came with, it will only work on the device it was shipped with, having the same IMEI, hardware serial number and everything unique, you can't use them with other devices at all.

@gus33000
I was almost certain it was unique to the device it was installed in. Does it reside on the boot partition? Thanks for sharing.

nate0 said:
@gus33000
I was almost certain it was unique to the device it was installed in. Does it reside on the boot partition? Thanks for sharing.
Click to expand...
Click to collapse
It's in DPP along with all other provisioned data specific to the phone, you won't be able to do anything with it, just abort, you'll loose time and you'll most likely brick devices.

Was only wanting to know more about it. Thanks again.

nate0 said:
Was only wanting to know more about it. Thanks again.
Click to expand...
Click to collapse
Also as a tip, never overwrite MODEM*, SSD, and DPP with the ones from another phone, it will be destructive for prototypes. I advise you make a full backup of the prototype emmc first, before doing anything, (even if it's just reflashing with a ffu, it's very important to back everything up in mass storage using something like Win32 disk imager), if you however for some reason ever end up with wrong MODEM*, DPP and/or SSD, boot to flash app, switch to download mode, send the emergency payloads for that device RM, and write the rdc, writing it without DLOAD won't work.

DPP is the one nice to work with but never copy and replace, delete and eventually copy over onto it

I need this file

Can you help

Kidsnet said:
I need this file
Click to expand...
Click to collapse
I sold this phone along with dozens of other Lumias and Windows Phones over 2 years ago. I do not own the phone anymore, and I unlikely will find that RDC file if I even backed it up. It would be almost to you unless you are the new owner of this exact device that I dumped it from. Are you planning to use the file for any other reason?

I got a refurbished mobile came locked so i have to fl it since its demanding protection key so i need help
nate0 said:
I sold this phone along with dozens of other Lumias and Windows Phones over 2 years ago. I do not own the phone anymore, and I unlikely will find that RDC file if I even backed it up. It would be almost to you unless you are the new owner of this exact device that I dumped it from. Are you planning to use the file for any other reason
Click to expand...
Click to collapse

Kidsnet said:
I got a refurbished mobile came locked so i have to fl it since its demanding protection key so i need help
Click to expand...
Click to collapse
They are coming already locked, or if there's any tool i can download so that it will vo well with m

Sounds like the lock you are seeing is like a safety net lock. Someone must have had windows on it but had logged in with their account in Windows 10 mobile and set up the Reset protection with their Microsoft account. There is a method to remove that but it is quite dangerous and could ruin the phone.
There is a way to by pass it though as a work around so that you can use the phone but every time you hard reset it it will always lock back.

nate0 said:
Sounds like the lock you are seeing is like a safety net lock. Someone must have had windows on it but had logged in with their account in Windows 10 mobile and set up the Reset protection with their Microsoft account. There is a method to remove that but it is quite dangerous and could ruin the phone.
There is a way to by pass it though as a work around so that you can use the phone but every time you hard reset it it will always lock back.
Click to expand...
Click to collapse
@Kidsnet this is especially a problem for a lumia 640/640 xl. Because what happens is that if they upgraded it to Windows 10 mobile and enabled the protection but you reflash it back to Windows phone 8 you will unlikely set yourself up to not even get a workaround to get in the phone. Since the provisioning of W10M and WP8 are completely different.