Dear,
A few months ago, I've upgraded my Lumia 925 to Windows 10 (preview) using Windows Insider: it went smoothly.
I decided to go back to WP8.1 using the Lumia Recovery Tool.
Today, I tried to update (again) to one of the Windows 10 previews, but I'm unable to upgrade: no updates found.
I know MS decided to exclude Lumia 925 to Windows 10 final: but: is there any possibility to upgrade to one of the developer previews?
When I download Windows Insider, I select fast ring: no updates are found (my account is enabled for developer previews).
Is this normal behaviour? I also tried to edit the registry to get Windows 10 redstone: unable to update: Update is downloading but when I try to install: unable to open update it says.
Any thoughts?
Thanks!
Pieter
No one?
cyberbozzo said:
No one?
Click to expand...
Click to collapse
If I could help dude I would , recently moved from android to windows phone and can say the community bad, ignorance seems to be a major player. I can kinda see why the app developers don't want create any or port any over.
use release preview ring
Same problem here !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
cyberbozzo said:
Dear,
A few months ago, I've upgraded my Lumia 925 to Windows 10 (preview) using Windows Insider: it went smoothly.
I decided to go back to WP8.1 using the Lumia Recovery Tool.
Today, I tried to update (again) to one of the Windows 10 previews, but I'm unable to upgrade: no updates found.
I know MS decided to exclude Lumia 925 to Windows 10 final: but: is there any possibility to upgrade to one of the developer previews?
When I download Windows Insider, I select fast ring: no updates are found (my account is enabled for developer previews).
Is this normal behaviour? I also tried to edit the registry to get Windows 10 redstone: unable to update: Update is downloading but when I try to install: unable to open update it says.
Any thoughts?
Thanks!
Pieter
Click to expand...
Click to collapse
Same problem here !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I need help too, root tool and vcreg don't install for xap deployer (error menssage) CustomPFD need SD card, so this are hard to solve, I've used wpinternals too to edit the registre file !!!!!!!
Some one in this FORUM PLEASE HELP US !!!!!!!!!!!!!!
r_x4 said:
Same problem here !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I need help too, root tool and vcreg don't install for xap deployer (error menssage) CustomPFD need SD card, so this are hard to solve, I've used wpinternals too to edit the registre file !!!!!!!
Some one in this FORUM PLEASE HELP US !!!!!!!!!!!!!!
Click to expand...
Click to collapse
Hey out there !
Upgrading to W10M works actually !!
Yesterday i upgraded my 925 from 8.1 Denim to W10M 10.0.14393.89
In Short:
All you need is the same 8.1 Firmware (.ffu)-File as is installed on your Phone.
Grab your FW on lumiafirmware Site
You need WP Internals 1.2 to unlock Bootloader and enable the Root access.
-YOU DIDN´T need Root-Tool and vcreg and all the other Stuff, ONLY WP Internals !!
Reboot Phone
After that, you must Boot your Phone via WP Internals into the Storage Mode
On PC open regedit and point to your Phone, called MainOS
In Regedit, you load the Registry of your Phone and do some Hacks and write the registry back to Phone
Reboot your Phone, go to MS Store and download Windows Insider App, start it and register for the Insider programm.
All done, you can use the fast ring, Slow ring and Preview .
If you wish, i can do a complete tutorial here !
Cya
http://forum.xda-developers.com/win...le/installing-windows-10-mobile-tech-t3431454
visit this.
Broken phone
Ok people... Process failed after tried flashing the FFU and guess what? phone doesn't boot anymore, keeps on looping.. when i try the down and power botton and then down again, i get the gear screen but either it gets stuck there or it gives me a bad face.. non of the relative software (WPinternals - Windows Device Recovery) recongize the phone. I guess it's pretty dead, any ideas on what can i do??
aris7la said:
Ok people... Process failed after tried flashing the FFU and guess what? phone doesn't boot anymore, keeps on looping.. when i try the down and power botton and then down again, i get the gear screen but either it gets stuck there or it gives me a bad face.. non of the relative software (WPinternals - Windows Device Recovery) recongize the phone. I guess it's pretty dead, any ideas on what can i do??
Click to expand...
Click to collapse
With the phone turned off, press and hold "volume up" + "power". Keep pressing them until you see a lighting with a gear. From there, flash using "Windows Phone Image Designer".
Hi,
I just wanted to know if someone can help me out to upgrade Lumia 1020 to Windows 10 Mobile. I am currently on Wp 8.1 Lumia Denim.
same as it was done in 2016. flash the engineering bootloader, boot mass storage mode, load the reg hive into regedit, edit the device id and update
blue screen
tofuschnitte said:
same as it was done in 2016. flash the engineering bootloader, boot mass storage mode, load the reg hive into regedit, edit the device id and update
Click to expand...
Click to collapse
After flashing the engineering bootloader, a blue screen appears and the phone reboots again and again. I had to restore it using Windows Device recovery Tool.
If you just want the Threshold 2 (10586.xxx, latest is 10586.753) branch of Windows 10 Mobile which is/was semi-supported on the older Lumias, as opposed to the Redstone branch which was never supported at all and so may have more issues, you can easily upgrade to 10586.753 with no risky flashing/unlocking required - first upgrade from 8.1 to 10586.107 (https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340) and then change to Enterprise edition so that you get the latest 10586.753 update straight from Microsoft (https://forum.xda-developers.com/showpost.php?p=71029519&postcount=23). If you're upgrading from 8.1, a hard reset is recommended once you're finished to ensure you have a clean install of W10M.
WARNING: Trying this may brick your phone! DO IT AT YOUR OWN RISK!
I'll attach the package that you need to debrand your Lumia 1520 AT&T here.
The procedure is the same as Lumia 640 RM-1073, but use files for Lumia 1520 instead.
GUIDE: https://forum.xda-developers.com/windows-phone-8/general/brand-att-lumia-640-lte-t3294971
You must downgrade your phone to WP8.1 Stock. After you debrand your phone, you can flash your phone to RM-937/938/939.
Unfortunately, only RM-938 firmware tested and worked on Lumia 1520 RM-940, flashing RM-937 will get stuck in Flight Mode. I haven't tested the RM-939 firmware. Since I don't have a Lumia 1520 RM-940, I couldn't grab files that modify the PLAT ID back for RM-940.
As for Lumia 830 RM-983 and Lumia 640 XL RM-1062, I have no idea.
hikari_calyx said:
WARNING: Trying this may brick your phone! DO IT AT YOUR OWN RISK!
I'll attach the package that you need to debrand your Lumia 1520 AT&T here.
The procedure is the same as Lumia 640 RM-1073, but use files for Lumia 1520 instead.
GUIDE: https://forum.xda-developers.com/windows-phone-8/general/brand-att-lumia-640-lte-t3294971
You must downgrade your phone to WP8.1 Stock. After you debrand your phone, you can flash your phone to RM-937/938/939.
Unfortunately, only RM-938 firmware tested and worked on Lumia 1520 RM-940, flashing RM-937 will get stuck in Flight Mode. I haven't tested the RM-939 firmware. Since I don't have a Lumia 1520 RM-940, I couldn't grab files that modify the PLAT ID back for RM-940.
As for Lumia 830 RM-983 and Lumia 640 XL RM-1062, I have no idea.
Click to expand...
Click to collapse
I think I have been looking for this. Is this the plat/smbios files? I have branded a 32GB RM-937 to a RM-940 for testing LTE connectivity but could not locate the plat ID file to Unbrand it back...fyi I have the RM-940 Plat ID files.
Edit: Also you can take it out of flight mode (RM-940 unbranded) by loading back and updating its NVI settings via the modem configuration NVI files of the RM-940 FFU.
Attached are all the ATT platform cabs I had if anyone needs.
roll back to factory firmware with wdrt,
make a firmware dump using the desired platform id RM-XXX.FFU introduction of the following commands:
Code:
thor2 -mode ffureader -ffufile "RM-XXX.ffu" -dump_partitions -filedir c:\
to unlock the bootloader using wpinternals
switch the device to mass storage mode
using the EMMC raw tool (make a backup of all the mass storage partitions), write the plat.bin (if you do not know how to do it, it is better not to do it, if you want to ask me in a personal message)
restart your device and flash it using wpinternals: efiesp.bin, mainos.bin, data.bin.
Blue screen is not scary!(BSOD) flash with wpinternals RM-XXX.ffu!
EMMC raw tool can be used to format and unbrick EMMC ?
augustinionut said:
EMMC raw tool can be used to format and unbrick EMMC ?
Click to expand...
Click to collapse
Format using EMMCrawtool no, I described a method of substitution of partition of memory.
The program detects only Qualcomm MMC Storage devices in 9006 mode
A small instruction and the program itself on the Russian forum
Goodbye ATT
nate0 said:
I think I have been looking for this. Is this the plat/smbios files? I have branded a 32GB RM-937 to a RM-940 for testing LTE connectivity but could not locate the plat ID file to Unbrand it back...fyi I have the RM-940 Plat ID files.
Edit: Also you can take it out of flight mode (RM-940 unbranded) by loading back and updating its NVI settings via the modem configuration NVI files of the RM-940 FFU.
Attached are all the ATT platform cabs I had if anyone needs.
Click to expand...
Click to collapse
thankyou so much, I had given up hope of removing the rm-940 firmware until I saw these files. An hour later my beloved 1520 is a normal phone ...yipppeee thanks HEAPS!
Regards
Elmarko
hikari_calyx said:
WARNING: Trying this may brick your phone! DO IT AT YOUR OWN RISK!
I'll attach the package that you need to debrand your Lumia 1520 AT&T here.
The procedure is the same as Lumia 640 RM-1073, but use files for Lumia 1520 instead.
GUIDE: https://forum.xda-developers.com/windows-phone-8/general/brand-att-lumia-640-lte-t3294971
You must downgrade your phone to WP8.1 Stock. After you debrand your phone, you can flash your phone to RM-937/938/939.
Unfortunately, only RM-938 firmware tested and worked on Lumia 1520 RM-940, flashing RM-937 will get stuck in Flight Mode. I haven't tested the RM-939 firmware. Since I don't have a Lumia 1520 RM-940, I couldn't grab files that modify the PLAT ID back for RM-940.
As for Lumia 830 RM-983 and Lumia 640 XL RM-1062, I have no idea.
Click to expand...
Click to collapse
Hi hikari-calyx, I just recently picked up a Lumia 1520 for free. I followed the steps to debrand but then wanted to upgrade to WIN10 (well attemping to). Phone boots but is on Win8. Prior to this I unlocked bootloader and gained root access. However now when I use Windows Phone Internals, it tells me my phone is: RM-938_nam_canada_104, product code 059T5X8, firmware version 1028.3534.1343.0000. I apparently somehow relocked my bootloader during this process of de-branding. I get an error code in WPI stating error 0x1304:invalid platform. I am fine with staying on this Canadian/America's firmware but want to update to WIN10, if it is at all possible, and would love to have bootloader unlocked and root. I am very very new to WIN phone but have been rooting flashing custom roms on android for 10+ years. I am stumped as to what to do, if it possible to upgrade to WIN10 mobile as well as unlock bootloader. I realize I am asking a slew of questions, but I am stumped with this one. I have spent the last 8 hours reading up on getting the bootloader unlocked and root access and then hit this snag. Any help is greatly appreciated. Thank you
PS: I tried to push the original AT&T cab files from post 2 (thank you for providing those) in hopes I could then get my product ID and phone to match at RM-940 (currently it shows (RM-938 on Canada/Americas firmware) but it was a no go. In phone update (settings on phone) it shows updating but then gets an error code of ERROR: 0x80188306. I have tried several different attempts to reprogram the ATT cab files for RM-940 to no avail. Still stumped. Any suggestions or assistance is appreciated, thank you.
PS2: I have also tried to manually push the RM-940/1520 ffu file to the device under iutool -v -p 1520 (my folder with the firmware) and all a no go.
nate0 said:
I think I have been looking for this. Is this the plat/smbios files? I have branded a 32GB RM-937 to a RM-940 for testing LTE connectivity but could not locate the plat ID file to Unbrand it back...fyi I have the RM-940 Plat ID files.
Edit: Also you can take it out of flight mode (RM-940 unbranded) by loading back and updating its NVI settings via the modem configuration NVI files of the RM-940 FFU.
Attached are all the ATT platform cabs I had if anyone needs.
Click to expand...
Click to collapse
Hi Nate0, how do I go about loading back and updating its NVI settings via the modem configuration NVI files? Thank you
ozzmanj1 said:
Hi Nate0, how do I go about loading back and updating its NVI settings via the modem configuration NVI files? Thank you
Click to expand...
Click to collapse
There are a few ways. One is to use thor2 and send the json files manually. I have had mixed luck/reactions with devices by doing that. The Second way is to put the nvi files manually on the phone, but make the parent/master nvi file a version higher than stock firmware. Then simply use thor2 and the variant ffu you have to do an nviupdate skip flash. The other way only works in mass storage mode, but with Nokia/Microsoft/Lumia phones they went hardcore locking down the QC partitions so that only certain values can be touched by the nvupdater package at the OS level. So in order to update the nv settings using QPST or other modem modifying software you have to authenticate with the nvupdate api. This means someone would need to create a third party api to interface and bypass of trick the qpst software into authenticating or trick the phone into thinking it is being updated by the nvupdater package.
nate0 said:
There are a few ways. One is to use thor2 and send the json files manually. I have had mixed luck/reactions with devices by doing that. The Second way is to put the nvi files manually on the phone, but make the parent/master nvi file a version higher than stock firmware. Then simply use thor2 and the variant ffu you have to do an nviupdate skip flash. The other way only works in mass storage mode, but with Nokia/Microsoft/Lumia phones they went hardcore locking down the QC partitions so that only certain values can be touched by the nvupdater package at the OS level. So in order to update the nv settings using QPST or other modem modifying software you have to authenticate with the nvupdate api. This means someone would need to create a third party api to interface and bypass of trick the qpst software into authenticating or trick the phone into thinking it is being updated by the nvupdater package.
Click to expand...
Click to collapse
Gotcha. I am very new to Windows Phone. I was given a Lumia 1520 that is apparently got an issue. Its an AT&T RM-940, when I run WPI, it reads:
Lumia RM-938 - NAM CANADA 1040
Product Code: 059T5X8
I have tried several times to repair it but a lot of times get a Product ID mismatch. Phone is on W8, not 8.1. Version 8.0.10517.150. I am totally stumped with what I need to do to fix this. I was told that it was on US AT&T firmware 02540.00019.14484.37028, but was flashed with modded cabs for USA Tmobile. I did find the AT&T cabs and have attempted to push them but it fails every time. Is this phone toast, or is there any solution? I appreciate your help and time. Thank you
Edit, how difficult would it be to push the nvi file with a parent/master nvi file higher then the above firmware version? I have no clue on how to do that or what the commands would be. I am willing to totally give it a shot with the commands and how I would do that. Appreciate any insight, thank you in advance.
Edit : I am not sure if this is what I need to do, but this did not work for me:
thor2 -mode uefiflash -ffufile "C:\the place of the ffu\file name.ffu" -do_full_nvi_update -do_factory_reset
Edited to match what my file directory was, but got this error:
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
Resp from device
Json message GetVersion send/receive failed
isDeviceInNcsdMode is false
Device mode 1 Normal mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Device is not in Lumia UEFI mode
Device mode get failed, mode is 1
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 5.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Again, not sure what I am missing.
ozzmanj1 said:
Gotcha. I am very new to Windows Phone. I was given a Lumia 1520 that is apparently got an issue. Its an AT&T RM-940, when I run WPI, it reads:
Lumia RM-938 - NAM CANADA 1040
Product Code: 059T5X8
I have tried several times to repair it but a lot of times get a Product ID mismatch. Phone is on W8, not 8.1. Version 8.0.10517.150. I am totally stumped with what I need to do to fix this. I was told that it was on US AT&T firmware 02540.00019.14484.37028, but was flashed with modded cabs for USA Tmobile. I did find the AT&T cabs and have attempted to push them but it fails every time. Is this phone toast, or is there any solution? I appreciate your help and time. Thank you
Edit, how difficult would it be to push the nvi file with a parent/master nvi file higher then the above firmware version? I have no clue on how to do that or what the commands would be. I am willing to totally give it a shot with the commands and how I would do that. Appreciate any insight, thank you in advance.
Edit : I am not sure if this is what I need to do, but this did not work for me:
thor2 -mode uefiflash -ffufile "C:\the place of the ffu\file name.ffu" -do_full_nvi_update -do_factory_reset
Edited to match what my file directory was, but got this error:
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
Resp from device
Json message GetVersion send/receive failed
isDeviceInNcsdMode is false
Device mode 1 Normal mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Device is not in Lumia UEFI mode
Device mode get failed, mode is 1
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 5.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Again, not sure what I am missing.
Click to expand...
Click to collapse
Without knowing a whole lot about your situation and phone I would say yes It can be fixed. You can even get access to the PLAT partition mount it and edit the platform file that houses the identity so that it matches the correct model... However there is no real way to tell which model it is if it has both AT&T FW but identifies as the RM-038. What you should ask yourself is what do you want to do with the phone. If you want to use it on a carrier then decide which fw to go with after that. Pushing the cabs for the PLAT partition that have the AT&T product ID will work, but only if the firmware version you send is newer. You cannot roll back to earlier version. So it gets tricky with variant firmwares because their fw version numbers may vary slightly and if the vary a lot you are stuck doing things manually. To put the nvi files on the phone manually and update the NVI settings with thor2 is not completely simple. What I would do is flash it with WPInternals to whatever variant the PLAT ID identifies with (in the case RM-938) Let it boot up and use it that way, if you have issues you alter the PLAT ID again back to an AT&T model and flash that firmware back.
I had to dig up old info I had....
To flash a nvi json file would be like this below:
The nvi file is in json format and the version number is partial way down in the file something like line 80 or something, I cannot entirely remember but not all NVI files are the same.... You would need to find a copy of whatever variant you trying to send to to know what version number to start with so that you can alter the version number to be higher. So you are sending a local file from PC to the phone. The phone has to be booted in flash mode and this only works on Lumia phones.
Sends NVIs messages from nvi file to MMOS / label app:
thor2 -mode retail -nvifile "CustomerNvi.nvi"
Sends NVIs messages from nvi file to normal mode / NCSd:
thor2 -mode retail -nvifile "CustomerNvi.nvi -normalmode"
EDIT:
Sorry I pasted the above but there is also here the json file command to. Also I think one command tries to send the messages while the phone is booted and the other while in flash mode. I cannot entirely remember...
Sends JSON messages from JSON file to MMOS / label app:
thor2 -mode rnd -jsonfile "json_messages_file.json"
Sends JSON messages from JSON file to normal mode / NCSd:
thor2 -mode rnd -jsonfile "json_messages_file.json -normalmode"
ozzmanj1 said:
Gotcha. I am very new to Windows Phone. I was given a Lumia 1520 that is apparently got an issue. Its an AT&T RM-940, when I run WPI, it reads:
Lumia RM-938 - NAM CANADA 1040
Product Code: 059T5X8
I have tried several times to repair it but a lot of times get a Product ID mismatch. Phone is on W8, not 8.1. Version 8.0.10517.150. I am totally stumped with what I need to do to fix this. I was told that it was on US AT&T firmware 02540.00019.14484.37028, but was flashed with modded cabs for USA Tmobile. I did find the AT&T cabs and have attempted to push them but it fails every time. Is this phone toast, or is there any solution? I appreciate your help and time. Thank you
Click to expand...
Click to collapse
nate0 said:
I had to dig up old info I had....
To flash a nvi json file would be like this below:
The nvi file is in json format and the version number is partial way down in the file something like line 80 or something, I cannot entirely remember but not all NVI files are the same.... You would need to find a copy of whatever variant you trying to send to to know what version number to start with so that you can alter the version number to be higher. So you are sending a local file from PC to the phone. The phone has to be booted in flash mode and this only works on Lumia phones.
Sends NVIs messages from nvi file to MMOS / label app:
thor2 -mode retail -nvifile "CustomerNvi.nvi"
Sends NVIs messages from nvi file to normal mode / NCSd:
thor2 -mode retail -nvifile "CustomerNvi.nvi -normalmode"
EDIT:
Sorry I pasted the above but there is also here the json file command to. Also I think one command tries to send the messages while the phone is booted and the other while in flash mode. I cannot entirely remember...
Sends JSON messages from JSON file to MMOS / label app:
thor2 -mode rnd -jsonfile "json_messages_file.json"
Sends JSON messages from JSON file to normal mode / NCSd:
thor2 -mode rnd -jsonfile "json_messages_file.json -normalmode"
Click to expand...
Click to collapse
Thank you very much for all your time, I do appreciate it. The phone is on WP8.0. What I would like to ultimately do is have it back on AT&T stock firmware and then upgrade it to WP10. While I am on Tmo, that is fine, I do know the phone is sim unlocked as I put in my sim, and I get HSP+ (3.5G). But that is not a huge deal for me as I would not be using it as a daily phone. BUt yeah, I would like to simply be able to flash it back to full AT&T stock and then update to the latest WP10
I took some screenshots. When the phone is powered up and connected to WPI, it shows one model, but another when rebooted to "unlock bootloader". Please see attached to screenshots
ozzmanj1 said:
Thank you very much for all your time, I do appreciate it. The phone is on WP8.0. What I would like to ultimately do is have it back on AT&T stock firmware and then upgrade it to WP10. While I am on Tmo, that is fine, I do know the phone is sim unlocked as I put in my sim, and I get HSP+ (3.5G). But that is not a huge deal for me as I would not be using it as a daily phone. BUt yeah, I would like to simply be able to flash it back to full AT&T stock and then update to the latest WP10
I took some screenshots. When the phone is powered up and connected to WPI, it shows one model, but another when rebooted to "unlock bootloader". Please see attached to screenshots
Click to expand...
Click to collapse
Ah ok. I too use TMO. What I did with the 1520 while on TMO was I used the RM-938 Firmware. But the only RM-938 models I used were the 32GB models. With the RM-938 the Modem partitions are different and the firmware for that model of phone allowed me to configure NVI settings to that I at least got HD voice while on TMO. Wifi calling and VoLTE never seemed to actually work on W10M but HD voice did. I am not certain if I did or not but I thought I posted some place explaining how I used custom NVI settings in an attempt to get quality cellular usage out of the 1520...
nate0 said:
Ah ok. I too use TMO. What I did with the 1520 while on TMO was I used the RM-938 Firmware. But the only RM-938 models I used were the 32GB models. With the RM-938 the Modem partitions are different and the firmware for that model of phone allowed me to configure NVI settings to that I at least got HD voice while on TMO. Wifi calling and VoLTE never seemed to actually work on W10M but HD voice did. I am not certain if I did or not but I thought I posted some place explaining how I used custom NVI settings in an attempt to get quality cellular usage out of the 1520...
Click to expand...
Click to collapse
Also to note, that if this 1520 you own is indeed a RM-940 from birth even flashing the RM-938 fw won't allow any cool changes to the NV settings like I mentioned. There is a distinct difference in models at that SOC level where one has NVI settings that the other does not and even if you make them identical there are other Firmware level differences I think on the DPP partition or some other place that allowed the RM-938 only to get HD Voice.
nate0 said:
Also to note, that if this 1520 you own is indeed a RM-940 from birth even flashing the RM-938 fw won't allow any cool changes to the NV settings like I mentioned. There is a distinct difference in models at that SOC level where one has NVI settings that the other does not and even if you make them identical there are other Firmware level differences I think on the DPP partition or some other place that allowed the RM-938 only to get HD Voice.
nate0 said:
Also to note, that if this 1520 you own is indeed a RM-940 from birth even flashing the RM-938 fw won't allow any cool changes to the NV settings like I mentioned. There is a distinct difference in models at that SOC level where one has NVI settings that the other does not and even if you make them identical there are other Firmware level differences I think on the DPP partition or some other place that allowed the RM-938 only to get HD Voice.
Click to expand...
Click to collapse
I see. I went back and looked and the device was RM-940 "fro mbirth" and was flashed to RM-938. I am almost positive someone previously attempted to do what you did and it wonked it. Is it difficult to re-apply the AT&T stock firmware? At the moment I get the following errors when attempting to flash the ffu for AT&T RM940 with the emergency files and a "donor" ffu for RM-1085" The errors are, Product ID mismatch or Profile FFU has wrong platform id for connected phone.
Click to expand...
Click to collapse
@ozzmanj1 with regards to the WPI showing two different models, one shows the FW revision/OS level connected. The other shows the device configuration pulled from the Plat and DPP partitions.
I understand. I might have the cab files for the PLAT ID RM-938 that you can push to the phone to match the FW so you can at least upgrade it to WP10M, but I am unsure if that will work while on WP8. Have you tried that yet?
nate0 said:
I understand. I might have the cab files for the PLAT ID RM-938 that you can push to the phone to match the FW so you can at least upgrade it to WP10M, but I am unsure if that will work while on WP8. Have you tried that yet?
Click to expand...
Click to collapse
I have tried to push the plat files for the ATT plat RM940 files but it fails. I am very unfamiliar with thor2 and simply copying and pasting commands I am finding. Never knew about thor2 until the other day. Thank you very much for your help.
EDIT: I did find your post, guessing this is what you did.
**testing** Lumia 1520.3 ROM
I've been working on a custom ROM for the Lumia 1520.3 RM-938 32gb. The variant info for the model I'm working with is below. I wanted to know if there were any users out there US or non-US that would be wanting or willing to test a 1520.3 ROM...
forum.xda-developers.com
I did find the files for your model 32gb from the LumiaFirmware. Do I need to download the nvi files for this?
LumiaFirmware | Download all Lumia firmware And Emergency Files
Download all Lumia firmware!
www.lumiafirmware.com
Download - CustomerNvi_02540.00019.15236.45004_905_4718e5dc65cbeb980b32e2af22af2e1d.nvi
Download - RetailModeNvi_02540.00019.15236.45004_905_10b151222cbcc1dcefc95c481b4e6244.nvi
By the way, I never had a Windows Phone device before this phone. And man, this Lumia 1520 is awesome looking. I would have loved this phone I think back in 2013/2014. I always thought my Nexus 6 was the largest phone (outside the Sony Xperia Z Ultra), but nope, the 1520 is taller and ever so slightly wider.
ozzmanj1 said:
I have tried to push the plat files for the ATT plat RM940 files but it fails. I am very unfamiliar with thor2 and simply copying and pasting commands I am finding. Never knew about thor2 until the other day. Thank you very much for your help.
EDIT: I did find your post, guessing this is what you did.
**testing** Lumia 1520.3 ROM
I've been working on a custom ROM for the Lumia 1520.3 RM-938 32gb. The variant info for the model I'm working with is below. I wanted to know if there were any users out there US or non-US that would be wanting or willing to test a 1520.3 ROM...
forum.xda-developers.com
I did find the files for your model 32gb from the LumiaFirmware. Do I need to download the nvi files for this?
LumiaFirmware | Download all Lumia firmware And Emergency Files
Download all Lumia firmware!
www.lumiafirmware.com
Download - CustomerNvi_02540.00019.15236.45004_905_4718e5dc65cbeb980b32e2af22af2e1d.nvi
Download - RetailModeNvi_02540.00019.15236.45004_905_10b151222cbcc1dcefc95c481b4e6244.nvi
By the way, I never had a Windows Phone device before this phone. And man, this Lumia 1520 is awesome looking. I would have loved this phone I think back in 2013/2014. I always thought my Nexus 6 was the largest phone (outside the Sony Xperia Z Ultra), but nope, the 1520 is taller and ever so slightly wider.
Click to expand...
Click to collapse
By far the 1520 was light years beyond all smartphones back then in every way. Like up to 700nits almost in direct sunlight on the LCD. Color profile for complete LCD color control. Big 6in screen. Solid camera of course. One of THE most popular Lumias ever. One of my favorites too.
That post is me sharing Full OS ffu for the 1520.3 (RM-938). It won't work for your device. But nvi files can be pulled from any FFU. We can mount partitions from the FFU and pull whatever files we want from them. You need to get the PLAT ID to match the FW/OS version of your phone in order to move forward. I have had your scenario happen to me before, but it has been a while and I cannot remember exactly the best route to go so you can upgrade back to W10M...
What was the error you got when sending the cab file to the phone and can you list the exact cab files you sent? For Plat ID changes there is always 2 cab files that need to be sent....
Dear XDA developers,
I have successfully (?) installed Windows 10 ARM64 on my Lumia 950 (RM-1104_11210) using the WoA Deployer Lumia Edition. When the tool froze on me during flashing my phone's partitions were destroyed. So then I recovered my Lumia 950 using the official "Windows Device Recovery Tool". But now it is stuck on Windows 10 Mobile 10586 which is really out of date!
On a separate partition I have the Windows 10 ARM64 build 17736 installed. Of course not accessible if the boot loader has been relocked. But WoA does state that you can update Windows 10 Mobile if you relocked...
Does anyone have experience with a dual boot setup for Lumia 950? Do you still get updates for your Lumia 950? Did you recently factory reset your Lumia 950 and then update it to latest build? Does the integrity check require deletion of WoA? Do you have the same problem as me?
Please help.
Ive done it on my 950 no I cant update w10m anymore its a pain in the ass because I want to be able to use the latest update but cannot do this as windows phone internals does not support it
Hey, I was able to fix it by wiping away my Windows 10 ARM64 installation, removing the WoA deployer created partitions, regrowing the Windows 10 Mobile partitions to 32GB max size using Windows 10 partition manager, relocking the bootloader. Then after some time it suddenly started updating again. Pain in the ass but works.
Not to mention the frustration I had with bitlocker and the device skipping the flashing part. When wpinternals was waiting for a reboot, manually rebooting the phone did the trick.
But much has changed since April. The bootloader does not crash all the time anymore. GPU works (finally). Maybe Windows 10 will mature some day on Lumia 950? You can look for my YouTube channel "rplgn" if you want to find a showcase video.