Develop Bugs

[minnow for whale]USB Video Out Dev&Dig (Status:success)

We all remember at the MIX10 Joe Belfiore projects his phone onto the big screen. Even on the recent XBOX show he did that again.
http://www.youtube.com/watch?v=9IA28wRWAI8
http://www.youtube.com/watch?v=uCDXaJh4bwE
this kind of video out is through micro-usb, normal type one. You can find Joe is using a Lumia 800 in his hand in the XBOX video.
I asked him through twitter and received an answer of "Special Software build".
I did some research and dig into the register keys. Found something.
This is a special driver that only shared inside the MS and normally won't be out anytime soon.
...
（Deleted because they are no longer of any means）
...
----Update on 2012.Feb 9 China Time----
marsrogers said:
Big Step Forward, since the DFT Rom released, the exe can be run in WP7.
One thing I need now is if someone can build an app for me, which calls the changeusbprofile.exe under /windows
Things here is I'm using the Opera mini launcher to call it, but the path is under /application, not under /Windows, and the result is my computer can not detect the phone when the phone reboots. I think this may relates to the path I call.
I'm not a typical tech-man, so I need help here. Thanks!
Click to expand...
Click to collapse
----Update on 2012.Feb 9 23:00 China Shanghai Time----
Today I really thank @GoodDayToDie and @ultrashot for helping so many.
@ultrashot sent me a xap app that does the job, calling the changusbprofile.exe in Windows folder. Although result is the same with yesterday, but now I am more sure that we are one more step closer to our destination. I'll wait my new micro usb cables to arrive and then I'll make a second try. Thank you again!!! Can't reach here without you kind people~~~
----Update on 2012.Feb 10 19:22 China Shanghai Time----
I removed the attachments because the project is now on special stage. I will put them back after the feature works, or after I can't make it work. Either way, I will put them back~~~Don't worry.
----Update on 2012.Feb 12 15:22 China Shanghai Time----
Complete failure....
New cable arrived and still my computer can't recognize the phone in usb video out mode...I changed a computer and till the same...
Will think about next steps...if I can't make figure it out next week, I shall put everything at present stage onto here.
----Update on 2012.Feb 14 10:22 China Shanghai Time----
Think it over, and think there is still a hill in front of us. The changeusbprofile.exe seems just to be a toggle, like a shortcut. But the real port of usb video out hasn't been enabled. On my samsung focus, I checked the *#7284# in Diagnosis Mode before and after I ran the changeusbprofile. The thing changes from Zun to Tethering, while it's not the real tethering mode. I think the changeusbprofile is just doing a job like changing usb mode from zune to tethering or to Diag mode. So that's to say, we haven't really seen the iceberg yet. I'll keep finding and hoping that anyone can get any help on this. This may requires me to dig some post in Windows Mobile age, since some parts between the two system are same.
And I contacted the kind secret person, and get the news that the usb cable doesn't really matters. Any short cables should serve the job. So our attention should move back onto the phone again.
----Update on 2012.Feb 15 15:13 China Shanghai Time----
I figured it out~The changeusbprofile changes the value in Registry Local_Machine/Drivers/USB/FunctionDrivers, DefaultClientDriver=CompositeFn to UFN_VIDSTREAM_CLASS. Every value change here points to a folder in FunctionDrivers.
in Samsung Focus, it is like below:
/CompositeFn;
/CompositeFn_QCOM;
/CompositeFn_SAMSUNG;(This is the one when we choose Diag Mode in Diagnosis App *#7284#)
/MtpClientDrvUsb;
/Samsung_USBSER_Modemlink;
/Serial_Class;
/Serial_Class_Diag_Qcom;
/Serial_Class_Nmea_Qcom;
/Serial_Class_Trace_Qcom;
/USBSER_Class;
/USBSER_Modemlink_Qcom;
There is no UFN_VIDSTREAM_CLASS folder here, so that explains why the changeusbprofile works well while it is no use at all...
Next step, I will try looking for the Setting in Asus E600, if I can find someone who has this device. Maybe Samsung Taylor will do the same.
If you can help, don't hesitate~~
----Update on 2012.Mar 3 15:13 China Shanghai Time----
marsrogers said:
Updated some info
I looked into the Key name, UFN_VIDSTREAM_CLASS, which is very unique way to name.
This belongs to a USB function Driver, and the only thing I saw similar is a UFN_PRINTER_CLASS, which is in Wince 6.0
http://msdn.microsoft.com/en-us/library/ee483856(v=winembedded.60).aspx
And you may check this
http://msdn.microsoft.com/en-us/library/ee485691(v=winembedded.60).aspx
So I'm still waiting for somebody who can offer any help on this. I talked with Mr. Yang Zhongke, who invented RecX prototype, fiinix optimized that, but not the inventor.
His way is not quite efficient and seems can't go further. But he will do some work for this in a foreseeable future.
Any one has a Asus E600, plz contact me, will keep your name secret.
Thanks!~
Click to expand...
Click to collapse
----Update on 2012.Mar 6 1:02 China Shanghai Time----
Project suspended, cuz according to a source, WP8 will have Remote desktop support.
"The ability to take screenshots (via Remote Desktop, no less) will be a feature of Windows Phone 8. I don't see anything changing before that."
Click to expand...
Click to collapse
"Only that you will be able to remote desktop into the Phone, which should allow you to create videos and/or screenshots from a PC."
Click to expand...
Click to collapse
The source is quite trustful, and I have no reason to doubt that.
So just be patient, and it will come. No need for this project to keep going.
At last, use my words in the email I talked with the source.
Me:Really puzzled why MS doesn't release such a cool and convenient feature. Haven't they realized that when people use this feature, they are promoting WP7 for free...(Actually I've promoted in this way for Android as a "side effect" in the company I work in for three months and as a result more than 20 Samsung Galaxy SII were added during this period. Google and Samsung should thank me...)
Click to expand...
Click to collapse
---Update on 2012.August 17 14:21 China Shanghai Time---
A very kind man has sent me the 7003 LG Panther ROM, which has the necessary file, and we successfully got them out. But I just lost my sell phone, so it may take some time to buy a new WP7 Samsung focus. Maybe next week. Very close to the final line. God bless us. Cheers.
Click to expand...
Click to collapse
Good luck!~
--Update on 2012.August 20 22:37 China Shanghai Time--
I tried to make it work while it still failed. The computer recognised my cellphone as WM7VIDSTREAM while the PC side app still does n't work.
I think this could be related to that the PC side app is for mango and the cellphone side is grabbed from 7003. I uploaded the VSD folder which contains what I think are the everything we need for now.
If anyone wants to build an rom, now it's the time.
Click to expand...
Click to collapse
--Update on 2012.August 23 17:42 China Shanghai Time--
One friend, who you will know someday later, gave me a home-make cab which includes the pkg file from Microsoft. Right now it is not for public for now. But it is successful.
Although I started this project, but as it always be, not a technique project but a sociology one. So there are many things and many people's benefit to consider. So just wait for some time, it is there when it is there.
For technique part, the pkg file includes as same as the VSD.rar in the attachment.
Cheers
Click to expand...
Click to collapse
--Update on 2012.August 28 19:43 China Shanghai Time--
Check here, you have what you want. http://forum.xda-developers.com/showthread.php?t=1856509
This is a long story, and finally it ended beautifully.
"Always be closing"--Glengarry Glen Ross (1992)
To me? Yeah, this project closed.
Regards,
marsrogers
Click to expand...
Click to collapse

Well, I can tell you a little about the thing you found (good investigation, by the way!)
First off, that's a module - it's kind of like a file (and shows up in the filesystem) but is baked into the ROM and can't be opened, much less modified, like a normal file.
There are tools that are supposed to be able to re-assemble modules, such as recmod. I haven't been able to get them to work, but maybe I'm just doing it wrong. In theory, it should be possible to create a "normal" DLL out of the components of a module.
The next trick is getting that rebuilt DLL onto the phone. This can be done pretty easily on Samsung, and is possible on interop-unlocked HTC, but on LG/Toshiba/Fujitsu/Dell/Nokia we don't currently have a way.
After that, you'll need to "install" the driver. Now, there's a registry entry for doing this. The problem is, I only know that the entry is required - I don't know if it's sufficient, or if there's also a database or something that must be updated. In any case, any phone where we can put a file into the Windows folder, we can also do registry editing.
Then there's the thing of actually getting the UI for this feature (the Settings "app" to control it). It's vaguely possible that the retail ROMs include it, but this is doubtful, so you'll probably need to pull it out of that old ROM. It's probably an EXE, so it's unlokely you can make a XAP for it - instead, you'll need to install it into the phone directly, including putting in the registry entried to launch it (this is a guess, I've never tried).
It's worth noting here that it's probably *WAY* easier to just pull that feature out of your old ROM and bake it into a custom ROM. This should be pretty straightforward, however, then it's only useful on custom ROMs, which in turn are only possible on HTC phones (right now).

GoodDayToDie said:
Well, I can tell you a little about the thing you found (good investigation, by the way!)
First off, that's a module - it's kind of like a file ...
Click to expand...
Click to collapse
Thanks for your reply. I did something with the recmod, but the dll it packed is only 1kb, apparently it's not useful. I guess it is because there is no imageinfo.bin inside the dll folder. I used some tools recommended by Da_G who started to try modding WP7 on the first day. Like nbsplit.exe to creat a IMGFS.bin, and use xidump to dump it. Just like what they have done before, I got the dll folders as same as I got at the beginning.
You may be right for the part that it's rather easier to build a new rom. There are tools to repack the whole IMGFS from files while I didn't find any good ways to pack a specific folder.
May ask more people all over the world (thx to the internet) cuz I just moved from android. In android, I use cygwin to pack the Odin Tar files, but it's totally different of course.
Anyway, doing this research is just for fun~ All is because MS is moving too slow...not to mention the NFC function I already have for a year on my Nexus S~~
Thank U again!~

This would be awesome good luck

Really a good find! Found that reg entry some time ago but I didn't care about it...Now that you bring up that thing again I also think that this could be very useful (even if you want it just for fun and not for business purposes). But note that the DLL file doesn't have to be in the /windows folder. It could be somewhere different, too.

@-WP7User-: That's an interesting idea, and might enable this to work on LG phones (where we have registry but not filesystem control). The registry value that speicies the path to the driver binary only ever gives the file name (example:
[HKLM\Drivers\Builtin\HTCFileUtility]
Dll="HTCFileUtility.dll")
However, it might work to specify a full path instead of just a relative one (relative to the \Windows folder, one must assume, since that's where the files in question are located).
However, there's still the issue of actually getting the phone to load the driver correctly. Just adding or editing the registry value for Drivers\Builtin didn't work for me - it did something (the driver stopped working when I chancged the value for an existing driver) - I wasn't able to make a user-added DLL work (even a different version of an official driver).

any news on this?

The old Recmod doesn't work on WP7 files. I believe there is a patched version for WP7 floating around XDA somewhere. Have to check my files, could of swore I downloaded it once.
EDIT: Here you go.

I have get the source code for creating the dcTNONE_ANALOGTV.dll, they are .c file and .def file.
My Problem is I don't know how to build them.
And I have got the changeusbmode.exe and the xml file with it. Figuring an idea to put them in.

marsrogers said:
I have get the source code for creating the dcTNONE_ANALOGTV.dll, they are .c file and .def file.
My Problem is I don't know how to build them.
And I have got the changeusbmode.exe and the xml file with it. Figuring an idea to put them in.
Click to expand...
Click to collapse
Download the FixRecMod.exe above I posted. Drag the dctNONE_analogtv.dll folder with the "s000 s001 s002 s003 s004" files in it over the exe. Now you'll find the actual DLL file inside the folder. Any problems, just upload the folder & I'll do it for you.

drkfngthdragnlrd said:
Download the FixRecMod.exe above I posted. Drag the dctNONE_analogtv.dll folder with the "s000 s001 s002 s003 s004" files in it over the exe. Now you'll find the actual DLL file inside the folder. Any problems, just upload the folder & I'll do it for you.
Click to expand...
Click to collapse
I have made the dll successfully. But when I put the dll into the /Windows folder in my Samsung Focus, nothing happened even after a reboot.
And another interesting thing is in WP7 Root Tools, when exploring the /Windows folder, all single file has a "ROM Module" or "ROM File" written blew, but the files I moved in has nothing written under it.
I tried to check the usb mode in diagnosis *#7248#, still there are three options to choose, nothing new.
I personally don't see the future of this project for now.
However, You have done a lot to help, it's very kind of you, thank you so much!

marsrogers said:
I have made the dll successfully. But when I put the dll into the /Windows folder in my Samsung Focus, nothing happened even after a reboot.
And another interesting thing is in WP7 Root Tools, when exploring the /Windows folder, all single file has a "ROM Module" or "ROM File" written blew, but the files I moved in has nothing written under it.
I tried to check the usb mode in diagnosis *#7248#, still there are three options to choose, nothing new.
I personally don't see the future of this project for now.
However, You have done a lot to help, it's very kind of you, thank you so much!
Click to expand...
Click to collapse
It wouldn't have ROM FILE/MODULE under it as it wasn't cooked in. You probably need some registry for it to work. Also, try opening the DLL in PEexplorer & checking to see it it has a cert attached.
Example of a DLL/EXE with a cert;

Gonna cook it into my rom and try it out...Do you have an idea which reg entry it could need?
I think of something for the settings page. Because if you haven't got a settings page for it, how can you activate it?
And maybe another entry which points it to the DLL file...?

-WP7User- said:
Gonna cook it into my rom and try it out...Do you have an idea which reg entry it could need?
I think of something for the settings page. Because if you haven't got a settings page for it, how can you activate it?
And maybe another entry which points it to the DLL file...?
Click to expand...
Click to collapse
Next weekend I may upload the dcTNONE_ANALOGTV.dll folder which I found in the leaked ROM for HTC Surround even before the WP7 was officially to public, the source code which is .c and .def for it, which is to remove some limits for QSD8250 CPU, and the changeusbprofile.exe and changeusbprofile.xml from Asus E600 (the only dev phone has the display mirror feather in 7720 for now)someone Mr X, who I am very grateful to gave me.
I ain't major in this level of computing techs, so I think in order to make the project alive, it's better to share what I have to those who has the ability to do it. Let them holding in my hand is a great waste at present stage.
The QSD8250 is a very old cpu, so there should be no problem with NDA.
P.S
There should be a manual installed usb driver on PC and a client application on PC but I don't have them right now. If you have friends or friend's friend who is a dev, holding a e600 dev phone, try ask them to share something, appreciated.

drkfngthdragnlrd said:
It wouldn't have ROM FILE/MODULE under it as it wasn't cooked in. You probably need some registry for it to work. Also, try opening the DLL in PEexplorer & checking to see it it has a cert attached.
Example of a DLL/EXE with a cert;
http://i105.photobucket.com/albums/m240/drkfngthdragnlrd/Untitled-31.png
Click to expand...
Click to collapse
I've uploaded all my files so you can make the check yourself.
After all I'm major in management not IT techniques so I don't want to pull the path down.
Thank You for the help you offered!~~~

Thanks for uploading your files. But it seems like I can't find the reg key...
There isn't a single reg entry which points to the uploaded .dll. At least not in the official Mango Update for the HD7.
But if you post the whole entry, I could try to cook the .dll into my rom and see what happens.

-WP7User- said:
Thanks for uploading your files. But it seems like I can't find the reg key...
There isn't a single reg entry which points to the uploaded .dll. At least not in the official Mango Update for the HD7.
But if you post the whole entry, I could try to cook the .dll into my rom and see what happens.
Click to expand...
Click to collapse
has this registry something to do With that ? :
Local Machine\Drivers\Display\TV\
PanelDLL=string:"dcTNONE_ANALOGTV.dll"

-WP7User- said:
Thanks for uploading your files. But it seems like I can't find the reg key...
There isn't a single reg entry which points to the uploaded .dll. At least not in the official Mango Update for the HD7.
But if you post the whole entry, I could try to cook the .dll into my rom and see what happens.
Click to expand...
Click to collapse
Just like @tessut posted. It's it. And I think you'd better try to build the dcTNONE_ANALOGTV.dll yourself from the source, it should be more reliable than using fixedRecmod. I can't do that cuz there seems to need many head files that do not exist in computer even I have vs2010...
Sent from my SGH-i937 using XDA Windows Phone 7 App

Okay, if someone wants to try that, too: The exact reg key (just copy and paste) is
[HKEY_LOCAL_MACHINE\Drivers\Display\TV]
"PanelDLL"=string:"dcTNONE_ANALOGTV.dll"
Didn't flash the rom on my device yet, but that's soon going to happen
The dctNONE_analogtv.dll is in the windows folder, the changeusbprofile.exe and .xml are in there, too. I hope it works!
EDIT: Didn't work at all...The ChangeUSBProfile.exe didn't get installed (although I'm 100% sure that it is there and of course in the right folder). Wasn't there a license xml around or something? Because normally a Windows Phone 7 App needs a license file to get installed when starting the phone for the first time. Don't know if this applies to .exe files though.
Has someone got an idea?

-WP7User- said:
EDIT: Didn't work at all...The ChangeUSBProfile.exe didn't get installed (although I'm 100% sure that it is there and of course in the right folder). Wasn't there a license xml around or something? Because normally a Windows Phone 7 App needs a license file to get installed when starting the phone for the first time. Don't know if this applies to .exe files though.
Has someone got an idea?
Click to expand...
Click to collapse
Thanks for the work! Is it possible if we extract the official .cab update file to get a licence and patch it to the exe?
I used a PE Explorer to open the changusbprofile.exe and found a license called"Windows Mobile TCB signing cert" in it.
Another thing is I used a way to open .exe in IE (use IE in WP7 to open this thread and download the usbvideoout.zip and you can have the chance to open changeusbprofile.exe directly) but it failed in Mango. Maybe we should try this in 7004 because this is really an old file. Or we should find a .cab file that contains a exe file in it and this .cab must be announced after mango update.

Interop Tools Appx for Windows 10 Mobile - registry editor

Interop Tools is a brand new registry editor that works on Windows 10 Mobile, It allows you to View, Browse and Edit of registry entries. Great news is that this tool doesn’t need your device to be interop-unlocked for this. The tool has been developed by Gustave M, who is a well-known Windows enthusiast and developer.
How to Download & Install Interop Tools on Windows 10 Mobile:
1. Download the Interop tools Appx file from attachment, unzip
2. Now all you need to do is to turn on the developer option by going to Settings—>Update & Security–>For Developer–>Select Developer Mode and select “yes” when prompted. This enables side-loading of apps.
You should be now able to install “Interop Tools” by tapping on the Appx that you have downloaded in first step.
3. You should be ready to have some fun, though be careful before editing registry unless you know what you are doing.
4. Once installed, the app appears under installed apps
The tool is not Lumia-specific but seems access to restricted keys is only for Lumias.
Source
http://www.windowscentral.com/interop-tools-windows-10-mobile
edit: if you have problem with newer version, simple uninstall app from storage, restart phone and install again.
Interop Tools Beta 1.7.157.0 (fbl_release(gustavem).160621-0900) changelog:
+ New helper runtime component, all core registry editing functionality have been migrated to registryhelper.winmd, as such, there might be new bugs, especially in the registry browser. Please report them if you find any.
+ WinPRTUtil is now also used in the browser and in registry value deleting operations.
~ Fixed an ux issue with light theme enabled.
~ Fixed an issue where HKD would be incorrectly named in certain areas.
~ Fixed an issue where the tool would incorrectly report the state of offline charging when loading the page.
Click to expand...
Click to collapse
Official download location: http://bit.ly/InteropTools
NOTICE: ARM for mobile, x86/x64 for PC

Now if we could only use a similar method to get an Adblocker on the 950/950XL...

jhoff80 said:
Now if we could only use a similar method to get an Adblocker on the 950/950XL...
Click to expand...
Click to collapse
you cant. this is only for WP8.1 devices with W10M... not for native W10M devices (550, 650, 950, 950XL)... you can install on Lumia 950/950XL and change some registry values but you cant access to MTP to use adblock (change hosts file)

Can this be uninstalled from the phone?
EDIT: nvm. I got it. Disable developer mode, try to open app, get error, uninstall

The file works perfectly in nokia lumia 520 windows 10 mobile build 10586.242
but I have a question
which is the benefit of this application?
I have a nokia lumia 520 with windows 10 mobile build 10586,242
but still not unlocked for use XAP files and appx
so this application can give me those benefits?
I would like to know more about how to install files with this application appx
thank you ... is great news for our lumias

dxdy said:
you cant. this is only for WP8.1 devices with W10M... not for native W10M devices (550, 650, 950, 950XL)... you can install on Lumia 950/950XL and change some registry values but you cant access to MTP to use adblock (change hosts file)
Click to expand...
Click to collapse
Yeah, I know, that's what I meant- This is great progress from the old way of getting access to these things, but what would really be nice is something similar that allowed adblock.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
DLS123 said:
Can this be uninstalled from the phone?
EDIT: nvm. I got it. Disable developer mode, try to open app, get error, uninstall
Click to expand...
Click to collapse
You can also uninstall from the Storage page in System.

thank you . Awesome Tool

Hi
I tried changing the video resolution (VideoResolution) registry value from 3 to 4. This opens 4k recording resolutions in camera app on my LUMIA 730 dual sim and also the SLOW MOTION option in video recording. But when recording is pressed it shows the device can't save the video. Im new to this, so if anyone can help to find me any turnarounds or is this due to hardware limitations. Thanks

Looks like file explorer. A search button can.t be aded?

Just saying
OP,
You copied all the content from Nokiapoweruser article and gave source link to WindowsCentral. Try to be fair!!

seems to be a nice little tool
but anyone knows what i have to use for sftp accesss as username and passwort when using winscp to connect?

Read this
http://forum.xda-developers.com/windows-10/windows-10-mobile/guide-filesystem-access-sftp-windows-10-t3185766

yes did that, but made a two mistakes figured it out with the dev of the tool, btw he released a new version a few hours ago
https://mega.nz/#!eZNRFRJB!ZszQcU1lAAQhbj14y4E70wIQhbDqWNIvZ0CmCcKHUWY
few bugfixes for th2 branch
finally again full fs access to the public apps folder (had problems with that before with interop unlock)

KNM_THe1 said:
OP,
You copied all the content from Nokiapoweruser article and gave source link to WindowsCentral. Try to be fair!!
Click to expand...
Click to collapse
i not open NPU for months, WC is only WP blog which one i read.... but this one first i see it on one pirate site, but link there lead to WC not NPU

And for those wondering what sort of hacks/tweaks they can do using this prog/tool, there's a thread for that:
http://forum.xda-developers.com/showthread.php?t=2434959&page=41

Has anyone found a key to enable call recording on older phones?

Aj6627 said:
Has anyone found a key to enable call recording on older phones?
Click to expand...
Click to collapse
this not possible via registry.... is already discussed on forum...

The author of Interop Tools is gus33000 aka Gustave M.
Official source links:
https://twitter.com/gus33000/statuses/731780368853041152
https://mega.nz/#F!iZMhSSzI!sGQy4V12ubfvT8Abm2Uo1g
----------
Interop Tools beta 1.2
Changelog:
+ The registry browser value editing dialog now displays the value type and name.
+ The registry browser now correctly handles write errors and will display them to you.
+ The registry editor now saves the history and has a new clear all button to clear all of them.
+ You can now tap a history item in the registry editor and it will fill all fields for you.
~ Improved the Registry browser ui again.
~ The app is now a regular app and not a settings app as there was many requests for this.
~ New icon for the app.
~ Small ui changes on the welcome page.
~ Bug fixes.
Known issues:
* It appears there is an editing issue for the pagingfiles on redstone, where the value is not set, this might be due to the key being reverted automatically. This is under inspection.
? It appears there is an editing issue for the pagingfiles on threshold, where some ";" appears instead of spaces, I can't reproduce it on my side, so if you could confirm or not confirm that to me on twitter that would be great.
Side notes:
* I know I need to add a way to alert from the app of new updates, this is under consideration.
* A small tweak page is in the works, if you have tweak ideas please tweet me them with the page where you found them or yourself if you found it, so I can properly credit peoples.

You may ad poweroff charging. Sure will be a huge succes.

Hi. I am unable to install it. It just closes when tapping from device and confirming install. When in AppDeploy app, I got this error "Error - There is an error in XML document (18, 15)." I'm using Nokia 925 Windows 10 10586.318. Please help what am I missing here?

(Petition) Find a way to get updated to W10M RS1 On 512MB devices

Hello guys, today I just figure out a way to get redstone on 512mb devices, this is not an tutorial, its a petition for windows phone users who have an official eligible lumia device for Windows 10 Mobile to share a real important data from their official windows devices.
In this case I need some screenshots from a device updated with upgrade advisor and not via windows insider, needs to be on TH2 of course, I'm trying to bypass MS hardware verification process. this process block our devices with 512mb to be connected througth Windows Insider Server.
Things I need to setup a working method for upgrade our devices to RS1:
1- Official eligible Lumia device for Windows 10 Mobile
2- Device updated througth Upgrade Advisor
3- screenshots> 1 with default W10m Extras&info outdated and other with Extras&info updated.
4- install interop tools.
5- Navigate for the followings strings:
(Instead of /OEM/NOKIA can be /OEM/Microsoft or /OEM/MicrosoftMDG)
HKLM/SOFTWARE/OEM/Nokia/Variant/BSPRelease
HKLM/SOFTWARE/OEM/Nokia/Variant/ConfigurationID
HKLM/SOFTWARE/OEM/Nokia/Variant/labelID
HKLM/SYSTEM/Platform/DeviceTargetingInfo/ < here I need all the strings stored for example: "PhoneManufacturer" "PhoneManufacturerModelName" "PhoneModelName" "PhoneHardwareVariant" and more.
6- Shared all these info from your device here + screenshots and let call it a day, redstone is waiting for us guys! ​

Do you know a way to get WM10 on 512 mb device right now? I''m stuck and unable to update since MS change the release preview ring to the redstone build.

a registry edit is not enough, if you managed to install RS1 your phone will simply bootloop, there are missing files that are related to that continuum hack and cant be shared at the moment, so please just be patient, whenever they can share the procedure they will make it available, asking a bazillion times wont change a thing

EspHack2 said:
a registry edit is not enough, if you managed to install RS1 your phone will simply bootloop, there are missing files that are related to that continuum hack and cant be shared at the moment, so please just be patient, whenever they can share the procedure they will make it available, asking a bazillion times wont change a thing
Click to expand...
Click to collapse
this is not just a registry edit, Im not asking about a way to get redstone on my 512mb device, I made this post with one a mission of gather important data and make my own "method"

wiien said:
Do you know a way to get WM10 on 512 mb device right now? I''m stuck and unable to update since MS change the release preview ring to the redstone build.
Click to expand...
Click to collapse
sure, are you stuck at Windows 8.1 ?

sorry to crush your dreams but that data you requested are not enough and will not be and you dont even need to collect them cause you find enough on the net.long story short: what esphack2 said is right, dont waste your time cause i assume you dont even know what you are doing

tofuschnitte said:
sorry to crush your dreams but that data you requested are not enough and will not be and you dont even need to collect them cause you find enough on the net.long story short: what esphack2 said is right, dont waste your time cause i assume you dont even know what you are doing
Click to expand...
Click to collapse
I know what I do, i just need these data. btw I brick any phone everyday and that makes me enjoy cause I enjoy play with some hard stuff, anyway here is a petition, not a dreambreaker post

http://forum.xda-developers.com/win...grade-advisor-redstone-lumias-t3434774/page10
Just change your keys with a supported device and upgrade using the upgrade advisor.

thanks to @BlueTR my 512mb lumia 635 is getting the update 10.0.14393.67
here's how to grab the update:
http://forum.xda-developers.com/win...-redstone-lumias-t3434774/page14#post68220276

No tienes problemas de bootloop?
Translation:
You not have problems with bootloop?

MrCego said:
No tienes problemas de bootloop?
Click to expand...
Click to collapse
No but there is a rendering issue (on devices with virtual keys) which causes apps not to fit to the screen. Normally, you hide the nav bar and it is fixed but 630 doesnt have that hiding option.

New version of DHT UpgradeAdvisor released and should be allow you to upgrade your phones . http://forum.xda-developers.com/win...-dht-upgrade-advisor-redstone-lumias-t3434774
Check OP or #2 post

BlueTR said:
No but there is a rendering issue (on devices with virtual keys) which causes apps not to fit to the screen. Normally, you hide the nav bar and it is fixed but 630 doesnt have that hiding option.
Click to expand...
Click to collapse
I have the same issue on where some apps not fit, but lumia 635 and 636 have the same screen resolution so I think updating to the new release preview cummulative update will fit again

BlueTR said:
No but there is a rendering issue (on devices with virtual keys) which causes apps not to fit to the screen. Normally, you hide the nav bar and it is fixed but 630 doesnt have that hiding option.
Click to expand...
Click to collapse
So no problem in my L620. That's a great news, dude!

Thread closed at OP request.

[GUIDE] Win10 Mobile (Semi-)Offline Update Project 10586.107 [UPDATED V5.3 beta6]

So few years after it's released, Windows Phone will finally end it's life.
It's time to update Win10 Mobile Offline Update Package to V5.2 (still beta5), then a next step - Semi-Offline Update Package V5.3 beta 6, or "WXM-SOUP".
I'm not going to fix the bug of Windows 10 Mobile Offline Update V5.3b6 now.
This project will not update again and placed there, and no technical issue will be answered. I've stopped using Windows Phone and shifted to HMD Nokia developement since 2017.
告中国用户：严禁转载本教程到智机网！
Click to expand...
Click to collapse
- I merged every packages that need to be pushed into one.
- I created a tool to allow us analyze the phone, target packages and push them.
- Because of that, you will not encounter keyboard issue like before, but we still recommend you to remove lockscreen password before you proceed.
Just a little warning:
I've noticed someone in China is reselling this package to others for a pretty unreasonable price. To prevent this happen in V5.2 release, we added server-side checksum verification.
You can still use it even you don't have Internet connection or my server down in the future.
Win10 Offline Update Package Project is never meant for sale - if you bought this from someone, you've been scammed and you must request refund or report the seller who sold you this.
Chinese translation of the warning above:
最近，我注意到在中国，有人正在以非常不合理的价格出售Win10 Mobile离线更新包项目。为了防止这个事情在本次版本发生，我们添加了服务端校验检查，以确保工具确实是我们提供的正确版本。
即便没有网络连接或者未来服务器宕机，你也可以使用，但是我们无法保证文件的正确性。
Win10 Mobile离线更新包项目不可转卖——如果你从他人手中购买了这份更新包，你应当立即申请退款或者是向平台举报卖家。
Click to expand...
Click to collapse
Known unsupported Models:
All 4GB ROM models, e.g: Nokia Lumia 530, HTC 8S, Huawei Ascend W1, Hisense E260T+, K-Touch E8
HTC 8X
Cancelled 5th Generation Lumia prototypes, e.g. Honjo
RX-130 (Hapanero)
Then you tell me.
How to use?
Video demonstration: https://www.youtube.com/watch?v=g2pCzz5_znY
1. The OS Version of your phone must be at least 8.10.14219.341. If it's older than 8.10.14219.341, update it before you use the package. Most of phones should be able to search updates.
Samsung ATIV S and ATIV SE users can download required packages from "WP8.1_Offline_Specific_Models.txt" in attachment below.
2. Download Win10 Mobile Semi-Offline Update Package V5.3 beta 6 from the attachment (HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z) below.
Existing beta 2 to beta 5 owners can also download it and overwrite all the files.
What's new in V5.3 beta 6?
- Download amounts reduced as much as possible.
- Now it will download necessary packages from Microsoft server automatically.
- Allow end-users to provide detailed error reports if error appears.
What's new in Beta 5?
- Replace buggy timestamp acquiring method.
To use this new method, your PC must have PowerShell enabled, which I think Windows 7 or newer OS should have that enabled by default.
This will also make the tool usable in 2020.
If no more bugs, this will become into the final version.
What's new in Beta 4?
- Add Simplified Chinese translation of main executable (win10oup_cn.exe) .
- Ignore the "MMOSLOADER" file to prevent the executable itself.
- Change the logic of judging if WDRT installed.
- Fix the FC issue of beta 3.
- Now it can be used if the path contains space.
- Administrator previleges no longer required.
Click to expand...
Click to collapse
3. You must have WDRT and required all the Microsoft Visual C++ Redistributable Runtimes installed, otherwise it will not run as expect. All Visual C++ Redistributable Runtimes can be downloaded here:
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
4. Extract the package and open "run_en.cmd" (Simplified Chinese users can run "run_cn.cmd" instead).
5. Follow the procedure the wxmsoup told you.
6. A "Device and Printers" window will appear. Disconnect (if connected) and remove your phone inside of it.
7. Get back to win10oup, press any key, and connect your phone to PC. Wait 10 seconds then press enter to detect your phone by using getdulogs.
8. If you see your phone listed, input "yes" (without quotes, lower case) and press enter. Input others will let getdulogs detect again, in case it's not listed.
9. Getdulogs will now grab the log and analyze it, after analyze complete, it will copy packages from repo directory to pkgs directory automatically. You may see few "System cannot find the file specified" prompts which expected (usually MMOS related). It can be still done even if your battery capacity is lower than 40%, but we still recommend you to fully recharge the battery.
10. Wait for the procedure complete, you may need to wait up to 40 minutes to get to Windows 10 Mobile 10586.107.
11. After 10586.107 installed, you can now use Interop Tools to hack the model to get further updates. Registry files are placed at "regs" directory, and Interop Tools 1.9.400 (known working version) can be downloaded from:
https://forum.xda-developers.com/showpost.php?p=70457420&postcount=550
12. The packages that pushed to your phone is located at "pkgs" directory - you can push it manually when you flash your phone back to WP8.1 and want to update to W10M next time.
Following Content is now archived to users who still want to use old packages themselves.
Translation of this guide
简体中文: http://www.ithome.com/html/win10/295565.htm
Deutsche: http://wpvision.de/windows-phone-hacking/9090-windows10mobile-offline-installation-per-iutools.html
Click to expand...
Click to collapse
Recently, Microsoft released Over-the-Cable Updater for Windows Phone. However, it still can't update unsupported devices to W10M directly, for supported devices they will start from 10586.107 first. Continue to use my offline update package.
But OTC Updater can be used as your alternative choice for further update, after you modified the model.
Click to expand...
Click to collapse
PLEASE DOWNLOAD V4.1 instead of V3/V4. V4.1 added support for LG Lancet and any other devices that has Snapdragon 410 Processor and fixed issues for several Snapdragon 800 Devices - Especially Nokia Lumia 1520 and Samsung ATIV SE.
To Lumia 810 Users: Now you can update to WP8.1GDR1 with Offline Update Packages. I knew how painful update to WP8.1 GDR1 on Lumia 810.
Push these packages from PART1 to PART4.
Is there any Huawei Ascend W2 users want a full offline update package to WP8.1 GDR1?
Click to expand...
Click to collapse
In August 2016, I released Win10 Mobile Offline Update Package for old models that can't get to Windows 10 right now in several communities in China.
Today, I'd like to present this package to everyone in XDA.
[NOW UPDATED TO V4.1]
It supports these models:
*Microsoft Lumia 430/435
Nokia Lumia 520/520T/521/525/526
*Microsoft Lumia 532
*Microsoft Lumia 535
*Microsoft Lumia 540
Nokia Lumia 620
Nokia Lumia 625/625H
Nokia Lumia 630
Nokia Lumia 635 (RM-974/RM-975/RM-1078)
*Nokia Lumia 636 (RM-1027)
*Nokia Lumia 638 (RM-1010)
*Microsoft Lumia 640
*Microsoft Lumia 640 XL
Nokia Lumia 720/720T
*Nokia Lumia 730/735
*Microsoft Lumia 735 (Verizon RM-1041)
Nokia Lumia 810 (T-Mobile US RM-878)
Nokia Lumia 820
Nokia Lumia 822 (Verizon RM-845)
*Nokia Lumia 830
Nokia Lumia 920/920T (RM-820/RM-821/RM-822/RM-867)
Nokia Lumia 925/925T (RM-892/RM-893/RM-910)
Nokia Lumia 928
*Nokia Lumia 929 Icon
*Nokia Lumia 930
Nokia Lumia McLaren (id315-x)
Nokia Lumia 1020
Nokia Lumia 1320
*Nokia Lumia 1520
Samsung ATIV S
Samsung ATIV S Neo
Samsung ATIV SE
HTC One M8 for Windows (AT&T, T-Mobile and Verizon variants are supported)
BLU WIN HD/LTE
LG Lancet VW820
MCJ Madosma Q501
MICROMAX W092
MICROMAX W121
HUAWEI Ascend W2
Acer Liquid M220
RAMOS Q7 (Prototype Only)
Panasonic Toughpad FZ-E1
TrekStor WinPhone 4.7
- Models with * are supported by Upgrade Advisor, these models are NOT RECOMMENDED to use this offline update package.
Need feedbacks from these models:
- Samsung ATIV S (SGH-T899M)
- Samsung ATIV S Neo (SGH-I187)
- Samsung ATIV Odyssey (SCH-I930)
- HTC One M8 for Windows (T-Mobile, 0P6B140)
To do that, you must be familiar with how to roll back your phone to Windows Phone 8.1. Windows Device Recovery Tool is necessary.
Instruction:
1. Make backup for your phone, for example, copy data to your PC. And make sure the OS of your PC must be at least Windows 7 Service Pack 1. Windows 8/8.1/10 are also acceptable, but you must install every Visual C++ Redistributable Runtime and Windows Device Recovery Tool.
2. Check your OS version in about phone. The OS version must be at least 8.10.14219.341 or newer. If the version is lower than required, please update it. You may want to use Windows Insider app from Windows Store. REMOVE YOUR PIN LOCK to prevent from some unknown issues after an upgrade.
3. Download and open the package by 7-Zip. Choose your model and extract the exact folder from it. For example, Nokia Lumia 820 should extract 480x800 folder from 2nd Generation folder. DO NOT EXTRACT cabs in that folder.
4. Press Win(Command)+R, in run command dialog, type "control printers" and run. Unplug your phone and remove your phone in Device and Printers window.
5. Extract iutool package attached below, and open a command prompt window with Administrator privilege. Change working directory to iutool.exe's location.
6. Plug your phone to your PC, then type this command:
iutool -l
7. If your phone is shown in command prompt window, then type this command:
iutool -V -p D:\480x800
(For example I have extracted this folder in Drive D)
8. Wait for about 40 minutes, then your phone will be in Win10 Mobile 10586.107.
9. Open Developer mode in "For Developers" option, then deploy tools that could modify phone's model to your phone.
10. Use any method that you know to modify your model, for example, I modified model to Microsoft RM-1116 (Lumia 950 XL Dual SIM). If you are going to use VCreg or Interop Tools, you needn't to Restore NDTKSvc.
The recommended version of Interop Tools can be downloaded here: http://forum.xda-developers.com/showpost.php?p=68322071&postcount=550
Click to expand...
Click to collapse
11. Check update, and you will receive another update to Win10 Mobile 14393 or later stable builds. Update to this build will fix critical issues you met.
12. After the update to another build, I recommended you to perform a hard reset to your phone. That would make the phone works at the best state.
Here's the demostration of upgrade Nokia Lumia 1020 (Hong Kong Variant) to W10M 10586.107:
https://www.youtube.com/watch?v=Ozt4QuQJj5U
How to choose the folder:
Lumia 52X, 62X, 720/T, 810, 820, 822, HUAWEI W2: 2nd Generation\480x800
Lumia 1320: 2nd Generation\720x1280
Lumia 920/T, 925/T, 928, 1020: 2nd Generation\768x1280
Lumia 1520: 2nd Generation\1520
Lumia 43X/532: 3rd Generation\43X-532
Lumia 535: 3rd Generation\535
Lumia 63X: 3rd Generation\63X
Lumia 73X: 3rd Generation\73X
Lumia 830: 3rd Generation\830
Samsung ATIV S/Neo: 2nd Generation\I8750
Lumia 929 Icon/930, Samsung ATIV SE: 3rd Generation\929-930-ATIVSE
HTC M8 for Windows (AT&T Variant): 3rd Generation\M8ATT
HTC M8 for Windows (Verizon Variant): 3rd Generation\M8Verizon
HTC M8 for Windows (T-Mobile Variant): 3rd Generation\M8TMobile
Lumia 540, TrekStor WinPhone 4.7: 4th Generation\540
Lumia 640/XL: 4th Generation\640-XL
Lumia McLaren/Goldfinger: 3rd Generation\McLaren-Goldfinger
BLU WIN HD LTE, MCJ Madosma Q501: 4th Generation\BLUWINHDLTE-MADOSMAQ501
Micromax W092: 4th Generation\MICROMAXW092
BLU WIN HD, Micromax W121, RAMOS Q7: 4th Generation\MICROMAXW121-BLUWINHD-RAMOSQ7
LG Lancet VW820: 4th Generation\VW820
Known issues:
- If the pre-installed default IME doesn't include English (United States), after an upgrade by this offline update package, pre-installed IME won't work. Please make sure your firmware's pre-installed IME included English (United States). However, if you modify your model by using Interop Tools by gus33000 then perform another update, IME issue will be fixed. Because this update package is made for Chinese users and China variant firmware at first, I couldn't take care of every variants. Sorry for that.
- To HTC 8X/8XT users: I'm sorry for the promise I made, but the packages doesn't work on HTC 8X/8XT because the MainOS partition is too small to upgrade. That's HTC's mistake.
- To Nokia Lumia 638 users: Please flash the latest China Variant Firmware (India Variant is not as stable as China Variant) to make sure the phone works at the best state, then download Upgrade Advisor from Windows Store to upgrade.
- To Prototype model users especially the cancelled model: Please make a full backup of phone first by using WinHex or something else. If you didn't do that, unbrick the prototype model is almost impossible.
- Because phones with 4GB ROM aren't capable for these package such as Nokia Lumia 530 and HTC 8S, this update package is not suitable for these models.
- To Nokia Lumia 1020 users: Update to Windows 10 Mobile will reduce the performance of precious 41MP Camera. If your Nokia Lumia 1020 is used for photography, DO NOT UPGRADE.
- Glance screen feature will be lost after another update to 14393 or later build, but it's possible to fix by using Interop Tools by gus33000.
- To Samsung ATIV S (GT-I8750) and ATIV SE users: Offline Update Packages to WP8.1GDR1 or GDR2 is available now. Now you can update to WP8.1GDR1 or GDR2 without using SDK Deployment.
- To Samsung ATIV S (GT-I8750) users: make sure you are using XXDOC2 firmware before update.
If your phone's pre-installed keyboard is neither English (United States) nor Chinese (Simplified, PRC), you'll meet a problem that your default keyboard doesn't work. To fix it:
1. Download the Internal IME Fix Package from the link below.
2. Extract your keyboard layout with your language code, for example, if you are using English (United Kingdom), extract the cab with en-gb from that package to the root of drive D, and rename it to 123.cab.
3. Open a command prompt window with administrator previlege, and change working directory to where iutool is, type this command:
iutool -l
4. Make sure your phone is listed in the output. Then type this command:
iutool -V -p D:\123.cab
5. You will encounter an error with code 8024a110, do not panic, the phone is still working with that package. The phone will reboot soon and perform another update to fix your keyboard.
6. After the update, you're able to use your keyboard. Modify phone model with VCreg or Interop Tools, and search for another update, remaining keyboard layout and pre-installed speech package will be fixed along with that update.
Here's some of the possible used language code in case you don't know how to choose:
de-de: German
en-au: English (Australia)
en-ca: English (Canada)
en-gb: English (United Kingdom)
en-ie: English (Ireland)
en-in: English (India)
fr-ca: French (Canada)
fr-fr: French (France)
ja-jp: Japanese
ko-kr: Korean
zh-hk: Chinese (Traditional, Hong Kong)
zh-tw: Chinese (Traditional, Taiwan)
You can also enable Mobile Enterprise on your phone. Just extract MobileEnterprise.ppkg from Enterprise_Configuration_File_for_TH2_Builds folder, and copy it to your phone, then tap "Yes, add it" on your phone. Soon your phone will become into Windows 10 Mobile Enterprise. Reboot your phone, Settings - Phone Update, Advanced options, and there's a "Defer Upgrade" available, now check it, then search update. If you still can't get any update, please modify your model and search update again.
Thanks for the collection here: http://forum.xda-developers.com/win...m-builds-update-links-collection-cab-t3234805 , and now it's possible to upgrade old models without Unlock Bootloader and Interop Unlock with SD card and WP8 SDK.
P.S. Only V4 and V3 set available here. V1 and V2 are deprecated and archived in Chinese Community.
Little hints:
- If your Lumia 830's navigation keys aren't responsible, you can push packages for Lumia 73X or Lumia 640/XL.
- If your Lumia 1520's navigation keys aren't responsible, you can push packages for McLaren.
- The directory catagory is depended on resolution, SoC, Virtual Navigation Bar availability, stock language packages included in firmware, etc.
- DO NOT USE Interop Tools provided in Windows Store.
In case that I can't give you help in time, here's some troubleshooting info for you:
IUTool Command Error Codes List: https://msdn.microsoft.com/en-us/library/windows/hardware/mt131833(v=vs.85).aspx
Also, if you encounter a error, don't unplug your phone, type command "getdulogs -o 123.cab" and waiting for Device Update Logs output. Open the 123.cab and open ImgUpd.log to get some hints. If you are a developer, you should be sensitive to error code lines.
Or, just attach the 123.cab to here.
Special Thanks:
@gus33000 for his Interop Tools
@zephray for LG Lancet W10M Update Package grabbing
DPMason, Ren, Max for provide devices to grab packages
Deprecated version download counts:
V3: at least 25,406 downloads
V4: at least 10,478 downloads
GNU components used:
- gawk
- wget
- aria2c

hikari_calyx said:
- Because phones with 4GB ROM aren't capable for these package such as Nokia Lumia 520/520T/521/530 and HTC 8S, this update package is not suitable for these models.
Click to expand...
Click to collapse
520/520T/521 has 8gb ROM.
Sent from my a3300-hv using XDA-Developers mobile app

Start digging after file explorer...... the one with C:/ acces.

I am not able to download!
This page can’t be displayed
•Make sure the web address https://dl-1.va.us.xda-developers.com is correct.
•Look for the page with your search engine.
•Refresh the page in a few minutes.

Download link does not work, can you upload it on another server?
(Edit: it's working fine now, updating my L720 )

are dual sims supported? for example lumia 630 dual sim.

I try on Ativ S it`s work but ... after uptade this offline package i must do hard reset (problem with keyboard).Then I change model name etc. download update 14393.576,device restart I get black screen with ;-( and start bootloop.............

Lumia 810
I was able to install 10586.107 on my Lumia 810 with out any problem!
Thank you!
Now my Lumia is on 14393.576 some how I did....
https://forum.xda-developers.com/wi...-dht-upgrade-advisor-redstone-lumias-t3434774

vuvkar said:
are dual sims supported? for example lumia 630 dual sim.
Click to expand...
Click to collapse
Yes you can. It doesn't matter if you are using Single SIM or Dual SIM or Operator Variants.

This is amazing work, OP, well done!
It's really useful to know that there's a way back from WP8.1 that doesn't involve risky flashing with WP Internals.
You mention that photography is downgraded for 1020, but my 1020 seems to produce good images still on W10M if I use Lumia Camera rather than the Windows Camera app. What's your experience?

GeoffreyK said:
This is amazing work, OP, well done!
It's really useful to know that there's a way back from WP8.1 that doesn't involve risky flashing with WP Internals.
You mention that photography is downgraded for 1020, but my 1020 seems to produce good images still on W10M if I use Lumia Camera rather than the Windows Camera app. What's your experience?
Click to expand...
Click to collapse
When upgraded to 14393.576, Lumia Camera works slower than that in WP8.1. I have two Lumia 1020 with yellow color to make comparison. Also, I'm using Nokia Camera Pro (pre-installed on Cyan), not the upgraded Lumia Camera by Microsoft Mobile.
Another alternative choice is using ProShot (ProShot Classic for W10M 10586.XXX or WP8.1) from Windows Store.
But upgrade 1020 to W10M is still not recommended.

got 1020 updated to 14393.576 (changed to 950 xl and enrolled to preview for developpers)
All is working well, even luminosity toggle (manual-automatic). Glance is back with the reg edting solution.
P.S. if cortana crash on listening try choosing another voice assistent (e.g. Microsoft Elsa Mobile).

Volpenger said:
got 1020 updated to 14393.576 (changed to 950 xl and enrolled to preview for developpers)
All is working well, even luminosity toggle (manual-automatic). Glance is back with the reg edting solution.
P.S. if cortana crash on listening try choosing another voice assistent (e.g. Microsoft Elsa Mobile).
Click to expand...
Click to collapse
Hi can you post a link which solution you used for Glance.
Thank you.

https://forum.xda-developers.com/showpost.php?p=68647224&postcount=1256
I've used vcREG to enable the Full FS Access and copy the files needed into the correct path.
You can import the attached reg files .
don't forget to reboot!

Lumia 925
I updated my mobile from 8.1 to windows 10 by using this method, it loaded fine (no errors). Just that when I tried to type anything it wouldn't type. So I couldn't use interop tools to be able to update if from W10M 10586.107. I have managed to downgrade again to 8.1. But I don't know why the keyboard didn't work. I even download different keyboard languages, but they showed as being downloaded but the keyboard still wouldn't work. The keyboard would show up, but that's all.
Any idea's ?

ryu35 said:
I updated my mobile from 8.1 to windows 10 by using this method, it loaded fine (no errors). Just that when I tried to type anything it wouldn't type. So I couldn't use interop tools to be able to update if from W10M 10586.107. I have managed to downgrade again to 8.1. But I don't know why the keyboard didn't work. I even download different keyboard languages, but they showed as being downloaded but the keyboard still wouldn't work. The keyboard would show up, but that's all.
Any idea's ?
Click to expand...
Click to collapse
many problems hard rest can fix it I am not saying in yours situation will fix but....
did you installed?
DHT Upgrade Advisor
https://forum.xda-developers.com/wi...-dht-upgrade-advisor-redstone-lumias-t3434774

TulakChoco said:
many problems hard rest can fix it I am not saying in yours situation will fix but....
did you installed?
DHT Upgrade Advisor
https://forum.xda-developers.com/wi...-dht-upgrade-advisor-redstone-lumias-t3434774
Click to expand...
Click to collapse
I did do a hard reset after I upgraded to win 10. That's when I realised my keyboard wasn't working. I couldn't change my phone values on interop tools to be able to get any more updates.

ryu35 said:
I updated my mobile from 8.1 to windows 10 by using this method, it loaded fine (no errors). Just that when I tried to type anything it wouldn't type. So I couldn't use interop tools to be able to update if from W10M 10586.107. I have managed to downgrade again to 8.1. But I don't know why the keyboard didn't work. I even download different keyboard languages, but they showed as being downloaded but the keyboard still wouldn't work. The keyboard would show up, but that's all.
Any idea's ?
Click to expand...
Click to collapse
This offline update package only considered keyboard of English (United States) and Simplified Chinese. If your default keyboard is not English (United States), for example English (India), you may need to push another keyboard package by using iutool.
I'll host the internal keyboard fix up package to mega soon.

ryu35 said:
I did do a hard reset after I upgraded to win 10. That's when I realised my keyboard wasn't working. I couldn't change my phone values on interop tools to be able to get any more updates.
Click to expand...
Click to collapse
I have released another package to fix this problem. Plz check it out

hikari_calyx said:
I have released another package to fix this problem. Plz check it out
Click to expand...
Click to collapse
I tried to add the keyboard using iutool but got an error command failed (HRESULT = 0x80070002)
update
I fixed my keyboard issue. what I did was I made a folder and named it 123 and put the keyboard cab that I named 123.cab inside. Then on iutool I put iutool -v -p C:\123 (this time I put little v instead off big V) I did get an error but my phone still updated itself and went to the spinning cogs and updated. So thanks for the help and now my mobile is on windows 10.

W10M Windows Update Issue (Error: 0x80070273)

Hey guys,
I have a Lumia 920 spoofed as a Lumia 950 XL and it successfully updated to the Creators Update (15063.2). But I am not able to download any of the cumulative updates beyond this in any of the Insider rings. The phone searches for the update but throws an error 0x80070273. I even tried enabling full file system access via Interop tools and clearing the SoftwareDistribution folder just like we do to troubleshoot desktop Windows Update issues but in vain. Any idea on how to fix this error will be much appreciated. Thanks. Here's the screenshot of the error. You can view the screenshot at imgur (dot) com/6KJiFzP

This is an issue with most of the x20 series phones. No one has been able to get it fixed so far.

извиняюсь что пишу на русском языке, нужно перепрошить ваш телефон под ваш регион и данная ошибка исчезнет.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
level143 said:
Hey guys,
I have a Lumia 920 spoofed as a Lumia 950 XL and it successfully updated to the Creators Update (15063.2). But I am not able to download any of the cumulative updates beyond this in any of the Insider rings. The phone searches for the update but throws an error 0x80070273. I even tried enabling full file system access via Interop tools and clearing the SoftwareDistribution folder just like we do to troubleshoot desktop Windows Update issues but in vain. Any idea on how to fix this error will be much appreciated. Thanks. Here's the screenshot of the error. You can view the screenshot at imgur (dot) com/6KJiFzP
Click to expand...
Click to collapse
http://www.lumiafirmware.com/info найди на этом сайте свою модель под свой регион и прошивай телефон согласно инструкции на сайте, бояться кирпича не стоит

level143 said:
Hey guys,
I have a Lumia 920 spoofed as a Lumia 950 XL and it successfully updated to the Creators Update (15063.2). But I am not able to download any of the cumulative updates beyond this in any of the Insider rings. The phone searches for the update but throws an error 0x80070273. I even tried enabling full file system access via Interop tools and clearing the SoftwareDistribution folder just like we do to troubleshoot desktop Windows Update issues but in vain. Any idea on how to fix this error will be much appreciated. Thanks. Here's the screenshot of the error. You can view the screenshot at imgur (dot) com/6KJiFzP
Click to expand...
Click to collapse
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it on my 1020 and another 925 which were stuck in the CU build .297 with success.
Keep in mind that the parameters that I will use are specific to these phone models and if you have a different model you need to find the requested parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do before a proper backup.
Let's start.
The problem appears because during update phase the oeminput.xml file becomes corrupted: as far as I know it happens only for some x20 model, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it is oeminput.xml. Save it with notepad.
Now modify the file
<SOC>{PROCESSOR_NAME}</SOC>
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you unlocked also system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Let me know if you have problems or need more informations...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide

sigfrid696 said:
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it on my 1020 and another 925 which were stuck in the CU build .297 with success.
Keep in mynd that the parameters that I will use are specific to these phone models and if you have a different model you need to find the requested parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do before a proper backup.
Let's start.
The problem appears because during update phase the oeminput.xml file becomes corrupted: as far as I know it happens only for some x20 model, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it is oeminput.xml. Save it with notepad.
Now modify the file
<SOC>{PROCESSOR_NAME}</SOC>
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you unlocked also system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Let me know if you have problems or need more informations...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
Click to expand...
Click to collapse
Nice guide! You should post it in a separate topic

Nightsteed said:
Nice guide! You should post it in a separate topic
Click to expand...
Click to collapse
good idea!! Done!

I have a similar problem I have Lumia 1020 10,0,15063,297 wanting to update me it pulls error 0x800f8003

I had the same error 0x80070273 on my Lumia 1520, RM-938. It was impossible to update its OS. It was stuck on the 10.0.15063.2 OS version.
I followed all the steps outlined here how to replace the corrupted OEMInput.xml file.
I am rocking 10.0.15063.674 OS version now.
Thanks a lot.

Dear all, have the same Error code: 0x80070273.
Because I am new to win10 mobile, I don't know how to manipulate the file OEMInput.xml inside my German Lumina 1520.
Is there someone arround who can write a detailed Manual what to do on PC and on the Phone?
Thanks a lot.

sigfrid696 said:
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone...
Click to expand...
Click to collapse
Yay, this worked perfectly on my Lumia 1020. Now Windows Update thinks it's a 950XL, and I've got the latest 2018-01 Update for arm-based devices. Very cool. Thank you so much to you and Antonio!

- Do the 2 en-US below also have to be changed to the phone's language ? :
<BootUILanguage>en-US</BootUILanguage>
<BootLocale>en-US</BootLocale>
- My USB port is broken ... so i cannot connect the phone to the PC
Is it possible to go to phone\windows\imageupdate and overwrite it with a oeminput.xml file from the sd card ?
- "after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools"
Even uninstalling InteropTools, Full filesystem access remains ON ?? Does a factory reset desactivate full file system access ?

i have been trying for many days to fix this error problem Windows Phone Update Error 0x80070273 .. I understand all about the solution in this page but the problem is when I apply full access on interop it show system files of the phone but all are protected as read only . so I can't replace or modify any files .. what to do to remove this read only protection on phone system files ?

oemimput.xml backup
I'm just leaving it here as a backup because who knows, when MS will get rid of this code from their servers. Today i have noticed, that Windows Device Recovery Tool is no longer working. Thanks a LOT for helping me resolve the problem using oemimput.xml re-build.
<?xml version="1.0" encoding="utf-8" ?>
<OEMInput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
<Description>Test FFU generation for {SOC TYPE} with build number XXXXX</Description>
<SOC>{PROCESSOR_NAME}</SOC>
<SV>{SV_NAME}</SV>
<Device>{DEVICE_NAME}</Device>
<ReleaseType>Test</ReleaseType>
<BuildType>fre</BuildType>
<SupportedLanguages>
<UserInterface>
<Language>en-US</Language>
</UserInterface>
<Keyboard>
<Language>en-US</Language>
</Keyboard>
<Speech>
<Language>en-US</Language>
</Speech>
</SupportedLanguages>
<BootUILanguage>en-US</BootUILanguage>
<BootLocale>en-US</BootLocale>
<Resolutions>
<Resolution>480x800</Resolution>
</Resolutions>
<AdditionalFMs>
<AdditionalFM>%WPDKCONTENTROOT%\FMFiles\MSOptionalFeatures.xml</AdditionalFM>
<!-- Add OEM FM files here -->
</AdditionalFMs>
<Features>
<Microsoft>
<Feature>CODEINTEGRITY_TEST</Feature>
<Feature>PRODUCTION_CORE</Feature>
<Feature>BOOTKEYACTIONS_RETAIL</Feature>
</Microsoft>
<!-- Insert OEM\SOC features here
<OEM>
<Feature>xxx</Feature>
</OEM>
-->
</Features>
</OEMInput>

Nice guide works perfect on Lumia 925 spoofed to 950 XL.

I've made the changes to the oeminput.xml that are shown here, for my Lumia 1520. Now when I run Phone Update, it briefly shows that updates are available for Windows 1703 (the updates are dated 2019 04), then displays an error message code 0x80070002. This has only happened since I changed the oeminput file, so I think I may have some value or other within it set incorrectly. I've got my language and time locales set to my region. For the other variables I used:
<SOC>MSM8974</SOC>
<Resolution>1080x1920</Resolution>
Are these correct for the 1520? Is there something else I should be looking at to get the updates to work? Many thanks in advance for any help with this.

2019 and it still works
thank you

I have used Nokia 920 and sat 950xl name ...but when I download the update than server say Error code: 0x80070273...so How can I solve it please help me? How I solve

I get an error trying to copy oeminput.xml to the destination directory on the phone. Something I need to do to grant permissions? Or use some tool other than Windows Explorer on the PC? I can navigate to that directory and view contents.
[edit]: found solution, just needed to turn on a couple more switches in the Unlock portion of the Interop Tools app, then it worked.

bigomod said:
Nice guide works perfect on Lumia 925 spoofed to 950 XL.
Click to expand...
Click to collapse
Hi, are you on 1703 or 1709 or did you dump your nokia phone...
I have a Nokia 925 and I try this guide
I changed the OEMInput.xml and could replace it on the filesystem
I am already on 1703, but then i get this Windows Phone Update Error 0x80070273
I have set 4 Registry fake Keys.
PhoneManufacturerModelName RM-1085_11302
PhoneManufacturer MicrosoftMDG
PhoneModelName Lumia 950 XL
PhoneHardwareVariant RM-1085

ant0nwax said:
Hi, are you on 1703 or 1709 or did you dump your nokia phone...
I have a Nokia 925 and I try this guide
I changed the OEMInput.xml and could replace it on the filesystem
I am already on 1703, but then i get this Windows Phone Update Error 0x80070273
I have set 4 Registry fake Keys.
PhoneManufacturerModelName RM-1085_11302
PhoneManufacturer MicrosoftMDG
PhoneModelName Lumia 950 XL
PhoneHardwareVariant RM-1085
Click to expand...
Click to collapse
Resetted Phone:
Nokia Lumia 925
Windows 10 Mobile 1703
Update 2019-06B for 1703 arrives and still get 0x80070273
Planned steps:
- Interop Tools and Dependencies Installation
- changing Registry to Nokia Luima 950 etc.
- checking XML File maybe correct
- trying Update agian