Windows RT 8.1 IR5 Media Builder - Windows RT General

Windows RT 8.1 IR5 Media Builder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​This media builder will download Windows RT 8.1 IR5, download and integrate selected Windows Updates, integrate drivers and generate custom installation media ready for use on the selected device.
Mainstream support for Windows RT 8.1 ended January 9, 2018, and extended support for Windows RT 8.1 will end on January 10, 2023.
The use of this media builder or the media it produces is entirely at your own risk.
User Guide
- Device Support
- Known Issues
- Version History
10/05/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4j.zip
- Tegra Jailbreak USB updated to v1.6.
- Office 2013 RT Home & Student Plus update lists updated to May 2023.
Download: Open-RT / Archive.org
27/04/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4i.zip
- Minor fixes.
15/04/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4h.zip
- Minor correction to Office 2013 RT removal option.
- DISM now uses the Media Builder temporary folder for scratch space where possible.
- Added check to prevent Media Builder from offering any of the drive(s) it is using from being offered as an output destination.
- Added file system check.
- Minor fixes.
19/03/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4g.zip
- Corrected an issue which caused the output for ASUS VivoTab RT to be unbootable.
- ASUS VivoTab RT driver pack updated.
- Office 2013 RT Home & Student Plus update lists updated to March 2023.
20/02/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4f.zip
- Possible workaround to the issue of hanging on the UEFI boot logo when attempting to install Windows using Windows Media Builder output on the Surface 2.
15/02/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4e.zip
- Windows Update lists updated to February 2023.
- Office 2013 RT Home & Student Plus update lists updated to February 2023.
- Nokia Lumia 2520 driver pack updated.
10/01/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4d.zip
- Windows Update lists updated to January 2023.
- Office 2013 RT Home & Student Plus update lists updated to January 2023.
- Surface RT & 2 Jailbreak USB updated to v1.5b.
- Minor fixes.
29/12/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4c.zip
- Windows Update lists updated to December 2022.
- Minor fixes.
20/11/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4b.zip
- Windows Update lists updated to November 2022.
- Office 2013 RT Home & Student Plus update lists updated to November 2022.
13/10/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4a.zip
- Windows Update lists updated to October 2022.
- Office 2013 RT Home & Student Plus update lists updated to October 2022.
- Surface RT & 2 Jailbreak USB updated to v1.5a.
17/09/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4.zip
- Added option to create a "Windows To Go" bootable USB drive. ^
- Added option to remove Office 2013 RT. ^^
- Windows Update lists updated to September 2022.
- Office 2013 RT Home & Student Plus update lists updated to September 2022.
- DISM logs are now being saved correctly.
- Minor fixes.
^ This isn't real Windows To Go but it will write a USB with a bootable installation of Windows. The option is disabled by default and has to be enabled from Media Builder Settings if required. If enabled this option will be offered either after creating an image or when writing an existing one. There are no guarantees that this is stable but it might be useful if you want to test something without touching the local installation.
I have only tested this on a Surface 2 and cannot predict how or even if it will work on other devices, in the test I have done the installation was usable when installed to a USB 2 Western Digital 250GB conventional hard drive. If a drive with inadequate performance is used then at best the installation will take an hour or two or in the worst case the installation will fail. For Windows RT 8.1 this option requires a USB drive that reports as "fixed", it will not work on a "removable" device.
^^ Based on Microsoft instructions for manual removal of Office and it might not be perfect.
Click to expand...
Click to collapse
​

Hello,
Could you explain how to use your file?
Thank you

xenis said:
Hello,
Could you explain how to use your file?
Thank you
Click to expand...
Click to collapse
Download and extract the zip file then run Build.cmd as administrator. Once Build opens select your device by typing the number corresponding to your device and pressing enter. After that no interaction will be required for a while, it will download Windows RT 8.1 IR5 and the updates for Windows directly from Microsoft, integrate them, add drivers for your device and then produce a folder ready to be copied to USB for installation on your device. Optionally an ISO can be created for archival purposes, you will be prompted for this towards the end of the run.
On an old test box I've found the process to take around 50 minutes including download time. I've attached some pictures of it running start to finish in first post.

I have an error message
«*this application cannot run on you computer*»
«*To find applications for this pc, open windows store*»
Do you know what’s happen?

xenis said:
I have an error message
«*this application cannot run on you computer*»
«*To find applications for this pc, open windows store*»
Do you know what’s happen?
Click to expand...
Click to collapse
What are you running it on? This is run on a normal x86/x64 PC, the media prepared here can then be used on your RT device. It could be made to work on an RT device but I imagine it would be incredibly slow to produce the updated installation source.
EDIT: I have updated the download, it will show an error if you are running on an unsupported architecture.

Can I grab iso my language different than en-us?

hooddy said:
Can I grab iso my language different than en-us?
Click to expand...
Click to collapse
Yes, you should just need to edit "\Download_Lists\Windows.txt" and replace the link with one of these.
ar-sa: http://vg.dl.ws.microsoft.com/dl/co..._343214DC5C52DBA99F34B9196A6ACBDD0BE53505.esd
bg-bg: http://vg.dl.ws.microsoft.com/dl/co..._307C20D50B8EC7CE3C8A8AE3E087E211A3BED662.esd
cs-cz: http://vg.dl.ws.microsoft.com/dl/co..._8D39E5906B750806CA68802DF1F79A2AF81B9FD5.esd
da-dk: http://vg.dl.ws.microsoft.com/dl/co..._62A6E28F1679CB64726655EF928936BFDF8F9FF4.esd
de-de: http://vg.dl.ws.microsoft.com/dl/co..._AD36CA5F9F8D384187EAB1583C71E7979357B63D.esd
el-gr: http://vg.dl.ws.microsoft.com/dl/co..._6813245AFCC99B8F84CC63B72FA082CCE8CE1AC4.esd
en-gb: http://vg.dl.ws.microsoft.com/dl/co..._410B5AE61DE3EA349F61BB8ACC3F3CB0681B1DCF.esd
es-es: http://vg.dl.ws.microsoft.com/dl/co..._45C90FB10612AF9C4AE7795623129AB9950FE655.esd
et-ee: http://vg.dl.ws.microsoft.com/dl/co..._516956ECB25C4B480489F820E4C780214F9551BE.esd
fi-fi: http://vg.dl.ws.microsoft.com/dl/co..._6CBAF4362316241EF87D5EF9B80CB7F1F37EDBED.esd
fr-fr: http://vg.dl.ws.microsoft.com/dl/co..._1EF69BB926B9A0742A093854DF82ABFF2E995F23.esd
he-il: http://vg.dl.ws.microsoft.com/dl/co..._11CB81D14F847684BD193BEB50BC3C4E408FF34C.esd
hr-hr: http://vg.dl.ws.microsoft.com/dl/co..._48FC1DABE3D0A1B88E0E68FD083381E99A24516E.esd
hu-hu: http://vg.dl.ws.microsoft.com/dl/co..._182ECAEBB0E738B165924C8F99B89A696F4FCADA.esd
it-it: http://vg.dl.ws.microsoft.com/dl/co..._D942BBC8808E629681CC21E1BD77A15E4396AF9C.esd
ja-jp: http://vg.dl.ws.microsoft.com/dl/co..._B788FF2B21517E2E555F8037A806A55ED967D8EB.esd
ko-kr: http://vg.dl.ws.microsoft.com/dl/co..._CB3FE5FBBEEDC1A7C15BC7906853663AFE853B98.esd
lt-lt: http://vg.dl.ws.microsoft.com/dl/co..._CE7A71D3FA5F56F58E2D6ACD9BB645725C04FB0E.esd
lv-lv: http://vg.dl.ws.microsoft.com/dl/co..._21ADAE9C229741CAE4C249125D03060410A864B6.esd
nb-no: http://vg.dl.ws.microsoft.com/dl/co..._7C750ADB12C6AAEA12D4A8D951D6E5386D984181.esd
nl-nl: http://vg.dl.ws.microsoft.com/dl/co..._7A1963FF85610217CA3B0DEF2C35B266BCABAD0D.esd
pl-pl: http://vg.dl.ws.microsoft.com/dl/co..._81EB4062960D6A3461A1564094A8EB00AE9685BF.esd
pt-br: http://vg.dl.ws.microsoft.com/dl/co..._409716869AA521EF41B7D86333B77088EDD73334.esd
pt-pt: http://vg.dl.ws.microsoft.com/dl/co..._3182A88D293A37AAF7418BF896DFDF19F5A4818D.esd
ro-ro: http://vg.dl.ws.microsoft.com/dl/co..._967EB013E8C52BA0B2A7C1F9BE3A474EE2402ECF.esd
ru-ru: http://vg.dl.ws.microsoft.com/dl/co..._FBE42B32AB8B8A8D0F84FEBEB95099EC5DA1EEF8.esd
sk-sk: http://vg.dl.ws.microsoft.com/dl/co..._A0CBCFCD2B80D22AFC1C8403ACDBA62C4E9BA635.esd
sl-si: http://vg.dl.ws.microsoft.com/dl/co..._78571325C1D8395436A6630E31EBC4FE2CFD8C91.esd
sr-latn-rs: http://vg.dl.ws.microsoft.com/dl/co..._18FED3F95C86CB7B1E3BA6A669F73B5218501125.esd
sv-se: http://vg.dl.ws.microsoft.com/dl/co..._2EE5CDE96856C69021B643825BE26C04B59E3331.esd
th-th: http://vg.dl.ws.microsoft.com/dl/co..._76873E5D21F711EEB31239479B215868AC779F78.esd
tr-tr: http://vg.dl.ws.microsoft.com/dl/co..._86C5586E947025AEC939F2D0A7B2B52E0760B744.esd
uk-ua: http://vg.dl.ws.microsoft.com/dl/co..._F4D7A99684BE4B7AA01D37E14377B1786FD24C4E.esd
zh-cn: http://vg.dl.ws.microsoft.com/dl/co..._36BE8400D2BDA3C3BEBE8A51F0859090C1C27C76.esd
zh-hk: http://vg.dl.ws.microsoft.com/dl/co..._89FE5E0F6173EE16806482C4884E32E5535193BB.esd
zh-tw: http://vg.dl.ws.microsoft.com/dl/co..._AA6F117073060E944950AD4081F178C126145C26.esd
Click to expand...
Click to collapse

jwa4 said:
Yes, you should just need to edit "\Download_Lists\Windows.txt" and replace the link with one of these.
Code:
ar-sa: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ar-sa-IR5_CCSA_WOAFRER_AR-SA_ESD_343214DC5C52DBA99F34B9196A6ACBDD0BE53505.esd
bg-bg: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_bg-bg-IR5_CCSA_WOAFRER_BG-BG_ESD_307C20D50B8EC7CE3C8A8AE3E087E211A3BED662.esd
cs-cz: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_cs-cz-IR5_CCSA_WOAFRER_CS-CZ_ESD_8D39E5906B750806CA68802DF1F79A2AF81B9FD5.esd
da-dk: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_da-dk-IR5_CCSA_WOAFRER_DA-DK_ESD_62A6E28F1679CB64726655EF928936BFDF8F9FF4.esd
de-de: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_de-de-IR5_CCSA_WOAFRER_DE-DE_ESD_AD36CA5F9F8D384187EAB1583C71E7979357B63D.esd
el-gr: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_el-gr-IR5_CCSA_WOAFRER_EL-GR_ESD_6813245AFCC99B8F84CC63B72FA082CCE8CE1AC4.esd
en-gb: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_en-gb-IR5_CCSA_WOAFRER_EN-GB_ESD_410B5AE61DE3EA349F61BB8ACC3F3CB0681B1DCF.esd
es-es: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_es-es-IR5_CCSA_WOAFRER_ES-ES_ESD_45C90FB10612AF9C4AE7795623129AB9950FE655.esd
et-ee: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_et-ee-IR5_CCSA_WOAFRER_ET-EE_ESD_516956ECB25C4B480489F820E4C780214F9551BE.esd
fi-fi: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_fi-fi-IR5_CCSA_WOAFRER_FI-FI_ESD_6CBAF4362316241EF87D5EF9B80CB7F1F37EDBED.esd
fr-fr: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_fr-fr-IR5_CCSA_WOAFRER_FR-FR_ESD_1EF69BB926B9A0742A093854DF82ABFF2E995F23.esd
he-il: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_he-il-IR5_CCSA_WOAFRER_HE-IL_ESD_11CB81D14F847684BD193BEB50BC3C4E408FF34C.esd
hr-hr: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_hr-hr-IR5_CCSA_WOAFRER_HR-HR_ESD_48FC1DABE3D0A1B88E0E68FD083381E99A24516E.esd
hu-hu: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_hu-hu-IR5_CCSA_WOAFRER_HU-HU_ESD_182ECAEBB0E738B165924C8F99B89A696F4FCADA.esd
it-it: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_it-it-IR5_CCSA_WOAFRER_IT-IT_ESD_D942BBC8808E629681CC21E1BD77A15E4396AF9C.esd
ja-jp: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ja-jp-IR5_CCSA_WOAFRER_JA-JP_ESD_B788FF2B21517E2E555F8037A806A55ED967D8EB.esd
ko-kr: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ko-kr-IR5_CCSA_WOAFRER_KO-KR_ESD_CB3FE5FBBEEDC1A7C15BC7906853663AFE853B98.esd
lt-lt: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_lt-lt-IR5_CCSA_WOAFRER_LT-LT_ESD_CE7A71D3FA5F56F58E2D6ACD9BB645725C04FB0E.esd
lv-lv: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_lv-lv-IR5_CCSA_WOAFRER_LV-LV_ESD_21ADAE9C229741CAE4C249125D03060410A864B6.esd
nb-no: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_nb-no-IR5_CCSA_WOAFRER_NB-NO_ESD_7C750ADB12C6AAEA12D4A8D951D6E5386D984181.esd
nl-nl: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_nl-nl-IR5_CCSA_WOAFRER_NL-NL_ESD_7A1963FF85610217CA3B0DEF2C35B266BCABAD0D.esd
pl-pl: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_pl-pl-IR5_CCSA_WOAFRER_PL-PL_ESD_81EB4062960D6A3461A1564094A8EB00AE9685BF.esd
pt-br: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_pt-br-IR5_CCSA_WOAFRER_PT-BR_ESD_409716869AA521EF41B7D86333B77088EDD73334.esd
pt-pt: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_pt-pt-IR5_CCSA_WOAFRER_PT-PT_ESD_3182A88D293A37AAF7418BF896DFDF19F5A4818D.esd
ro-ro: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ro-ro-IR5_CCSA_WOAFRER_RO-RO_ESD_967EB013E8C52BA0B2A7C1F9BE3A474EE2402ECF.esd
ru-ru: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ru-ru-IR5_CCSA_WOAFRER_RU-RU_ESD_FBE42B32AB8B8A8D0F84FEBEB95099EC5DA1EEF8.esd
sk-sk: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sk-sk-IR5_CCSA_WOAFRER_SK-SK_ESD_A0CBCFCD2B80D22AFC1C8403ACDBA62C4E9BA635.esd
sl-si: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sl-si-IR5_CCSA_WOAFRER_SL-SI_ESD_78571325C1D8395436A6630E31EBC4FE2CFD8C91.esd
sr-latn-rs: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sr-latn-rs-IR5_CCSA_WOAFRER_SR-LATN-RS_ESD_18FED3F95C86CB7B1E3BA6A669F73B5218501125.esd
sv-se: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sv-se-IR5_CCSA_WOAFRER_SV-SE_ESD_2EE5CDE96856C69021B643825BE26C04B59E3331.esd
th-th: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_th-th-IR5_CCSA_WOAFRER_TH-TH_ESD_76873E5D21F711EEB31239479B215868AC779F78.esd
tr-tr: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_tr-tr-IR5_CCSA_WOAFRER_TR-TR_ESD_86C5586E947025AEC939F2D0A7B2B52E0760B744.esd
uk-ua: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_uk-ua-IR5_CCSA_WOAFRER_UK-UA_ESD_F4D7A99684BE4B7AA01D37E14377B1786FD24C4E.esd
zh-cn: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_zh-cn-IR5_CCSA_WOAFRER_ZH-CN_ESD_36BE8400D2BDA3C3BEBE8A51F0859090C1C27C76.esd
zh-hk: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_zh-hk-IR5_CCSA_WOAFRER_ZH-HK_ESD_89FE5E0F6173EE16806482C4884E32E5535193BB.esd
zh-tw: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_zh-tw-IR5_CCSA_WOAFRER_ZH-TW_ESD_AA6F117073060E944950AD4081F178C126145C26.esd
Click to expand...
Click to collapse
Oh thats cool. Btw why did you hide Lumia drivers? I have Lenovo one to add into.

hooddy said:
Oh thats cool. Btw why did you hide Lumia drivers? I have Lenovo one to add into.
Click to expand...
Click to collapse
It's not hidden as such (I haven't added the drivers) but I'm not sure how to safely approach Lumia 2520 yet, I will look into it at the weekend. Once certain updates are applied to Lumia 2520 they can't ever be jailbroken again whereas on Surface we can just format them or remove the jailbreak blocking updates.
I'm also not sure what the jailbreak situation is on other RT devices so I need to try and found out if any of them are in the same boat as the Lumia 2520 before adding driver packs for them all. I suspect its going to end up having two update lists, the full one used in the existing release and a jailbreak friendly one.
I will also try to add language selection to avoid having the manually change it.

jwa4 said:
It's not hidden as such (I haven't added the drivers) but I'm not sure how to safely approach Lumia 2520 yet, I will look into it at the weekend. Once certain updates are applied to Lumia 2520 they can't ever be jailbroken again whereas on Surface we can just format them or remove the jailbreak blocking updates.
I'm also not sure what the jailbreak situation is on other RT devices so I need to try and found out if any of them are in the same boat as the Lumia 2520 before adding driver packs for them all. I suspect its going to end up having two update lists, the full one used in the existing release and a jailbreak friendly one.
I will also try to add language selection to avoid having the manually change it.
Click to expand...
Click to collapse
Lenovo is easily jailbreaked like Surface.
It is good to have multilang.

hooddy said:
Lenovo is easily jailbreaked like Surface.
Click to expand...
Click to collapse
Yea, I had a quick look and as I understand it all the Tegra devices can't be permanently blocked from being Jailbroken. It's just all the Qualcomm devices like the 2520 that are out of luck, these devices might get an alternative safe update list.
hooddy said:
It is good to have multilang.
Click to expand...
Click to collapse
I've got to do a quick test wim build tonight but the language selection is done, picture attached.

hooddy said:
It is good to have multilang.
Click to expand...
Click to collapse
I've updated the link, v1.3 will hopefully let you pick a language without editing anything. I have only tested this with Chinese, Dutch, English & French IR5 sources.
The optional Appx pack remains unchanged.

jwa4 said:
I've updated the link, v1.3 will hopefully let you pick a language without editing anything. I have only tested this with Chinese, Dutch, English & French IR5 sources.
The optional Appx pack remains unchanged.
Click to expand...
Click to collapse
I will check it. Btw I do not get what to do with appx pack... Unpack it into appx folder?

It is seems working. Add lenovo drivers please. I can share it if any.

hooddy said:
I will check it. Btw I do not get what to do with appx pack... Unpack it into appx folder?
Click to expand...
Click to collapse
Yep, extract to Appx folder so it looks like the attached image and once the pack is present Build.cmd will ask if you want to update the Appx or not.
hooddy said:
It is seems working. Add lenovo drivers please. I can share it if any.
Click to expand...
Click to collapse
I will try to take a look tonight. Do you have an RT 8.1 recovery image for the device? I wonder how close they are to the Surface RT ones.

hooddy said:
It is seems working. Add lenovo drivers please. I can share it if any.
Click to expand...
Click to collapse
This one contains the Lenovo drivers, just a test for now because I don't have a Yoga 11 to test it on. Assuming this works please check device manager,check all drivers are present and let me know the result.
Download: EDIT: Main link updated to v1.4
Thanks to lgibson02 for the drivers and testing!

28/11/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.5.zip
- Added UNTESTED support for ASUS VivoTab RT, Dell XPS 10, Nokia Lumia 2520 & Samsung Ativ Tab.
- Added Update List selection, choice of update lists - All Updates for Windows (Including "Jailbreak Killers"), Longhorn Jailbreak Safe & Myriachan Jailbreak Safe.

17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6.zip
17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6_Appx.zip
- Added three additional update modes (None, Service Stack Only & Service Stack and Update 3 Only).
- Added warning for languages that do not currently support App updates.
- Added warning if an unmodified IR5 image is going to be created.
- Removed Start Menu Update Discoverability notification if Update 3 is installed and Start Menu is enabled by default.
During testing I found that trying to update provisioned apps in Windows RT 8.1 IR5 for Saudi Arabia, Bulgaria, Germany, Croatia, Hungary, Russia and Slovakia results in the following error:
App packages (.appx) cannot be serviced on an offline image after a user has logged into the image.
Click to expand...
Click to collapse
I will try to find what causes this but for the moment these will be excluded from attempting app updates.
At this time I don't think there is going to be a solution for adding updates for Office 2013 RT offline.

hi I have installed all the windows update, everything perfect
I would like to know how to install the jailbreak and if you have to compile from the surface directly or from another pc.
thanks

ivanothai said:
hi I have installed all the windows update, everything perfect
I would like to know how to install the jailbreak and if you have to compile from the surface directly or from another pc.
thanks
Click to expand...
Click to collapse
Another thread might be best suited for jailbreak discussion but there are a few options. There are methods from Myriachan, Never_Released / black_bob and imbushuo.

Does myriachan jailbreak automatically with this program? What does it consist of? Should it be done? Can I put a newer browser? Thank you

Related

[CustomROM] FunkyROM v2.0 - Lumia 900 RM-823 - All official lang [updated 20.03.2013]

Hello people!
I proudly present FunkyROM v2.0 for the Nokia Lumia 900!
But first of all:
I would like to say a huge thank you to everyone who made this rom possible!
Rataplan: Thank you buddy! I've learned so much from you!! Thank you for your friendship!!
-=Barin=-: for giving us the heart of rom-cooking: OsBuilder!
ultrashot: for all your amazing stuff you did for WP7 community!
dewe: for your LumiaDownloader, it's awesome, i didn't have to reboot to ubuntu for everytime flashing the rom!
Heathcliff74: for your WP7 root tools!
Jaxbot: for all your amazing stuff on windowsphonehacker.com!
everyone else i didn't mention by name, but used stuff from!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshots were taken using USB Video Out.
Changelog v2.0:
- included MS os updates 7.10.8860.142 and 7.10.8862.144 --> live tile fix!
- added full CAB update support to cab updates signed by: lordmaxey (me ), ultrashot, XBmod-Yuki, Rataplan, CeesHeim, pdaimatejam, voluptuary
- of course everything else from v1.0
Click to expand...
Click to collapse
Changelog v1.0:
Basic rom: RM-823 2175.2907.8858.13030 - MX Country Variant
Languages: all official languages, set 0809 (eng-GB) as default
Added:
- Full Unlock v4
- Root Manager --> Settings
- XapDeployer --> Settings
- customizable SearchKey --> Settings
- Wmdc
- Bazaar
- Camera Extras
- Flashlight
- KeepWifi Alive
- Program Manager --> Settings
- Screen Capturer
- WP7 RootTools
- WPH Tweaks
- USB Video Out
- Tile World Clock
- Colors Start Menu
- GSensor Switch --> Settings
- "Custom Blue" Theme --> set as default
Removed:
- preinstalled AppHighlights
- preinstalled ESPN
- VolumeLimit
Else:
- modified Internet Explorer Favourites
- modified Phone Info/about
Click to expand...
Click to collapse
Please note, you can only flash this ROM when your Lumia 900 is QUALCOMM.
and you're using this ROM at your OWN RISK.
one last thing: I hope you can enjoy your Lumia 900 device even more with my rom.
Download:
FunkyROM v2.0 for Lumia900 RM-823
Mirror @ 4shared
useful stuff
Dewe's Nokia Lumia Downloader 0.5
I attached the Nokia Lumia Downloader 0.5 for flashing your Lumia 900 easily in Windows.
Thx to dewe for his great work!
How to use USB Video Out:
As it seems to be a little "difficult" to use the usb video out package, here's what you have to do (this is a copy out of the readme file of the package):
You can download the needed files here:
USB-Video-Out.rar
Mirror @4shared
Enabling USB video out on the phone (ON THE PHONE)
- From Start Menu swipe over to the application list and run "USB Video Out"
- Answer Yes to enable USB Video out. This is a toggle.
- When the phone boots up it is in Zune Mode which enables it to sync data with Zune Client software on the PC. You will need to toggle this to Video mode using the above steps to get video out.
- Note: Toggling between Zune mode and Video mode requires the phone to reboot each time.
Setting up driver on the desktop (one time)
- Make sure Zune is not running.
- Your Phone must be flashed with a ROM that has video out bits on it, they must be enabled, and the phone must be on and plugged into your PC to continue. When the phone boots up the default setting is OFF for the video output.
- Start -> Right click on Computer, select Manage
- In "Computer Management" click on the Device Manager
- Under "Other Devices"
- Within the list of drivers Right Click on WM7VIDSTREAM driver, select "Update Driver Software..."
- Choose Browse and point Windows to appropriate driver folder.
- Approve the Unsigned Driver installation.
Starting application
- Launch VidStream.exe.
- This application does support disconnect & reconnecting of the phone's USB cable.
- If a previous instance of VidStream.exe was running with the device connected, you will need to simply unplug and replug the phone's USB cable.
- Press ESC to exit the PC Client application.
Re-enabling MTPz USB sync (Zune Mode)
- Open "USB Video Out"
- Answer Yes to enable MTPz
- The device will reboot to make the changes effective.
Click to expand...
Click to collapse
Update to 8860 and 8862 successful
Hi there,
just a quick information:
I successfully updated to the Microsoft OS Updates 8860 and 8862 via Zune.
Unlock is still ok, also the qualcomm bootloader was not overwritten :good:
The only thing it "killed" so far, is the information of my Custom Rom in settings --> about.
It changed firmware revision number from "FunkyROM v1.0 - xda-developers" back to "2175.2907.8858.13030"
cheers
Will this work with AT&T Nokia Lumia 900?
Hi lordmaxey,
Last week I downloaded this rom 2175.2907.8858.13030 from navifirm then flashed it using the NCS. No problem when flashing it. But my concern is the battery drain. So I decided to go back to 2175.2905.8858.12480 (variant finland). Actually im not sure if my qualcom is unlock. My question is can I use this rom same process to flash it by using NCS? thanks
AW: [Custom ROM] FunkyROM v1.0 - Lumia 900 RM-823 - All official languages
kunalsethi50 said:
Will this work with AT&T Nokia Lumia 900?
Click to expand...
Click to collapse
i'm not sure, because i haven't tested. But probably not.
kookook said:
Hi lordmaxey,
Last week I downloaded this rom 2175.2907.8858.13030 from navifirm then flashed it using the NCS. No problem when flashing it. But my concern is the battery drain. So I decided to go back to 2175.2905.8858.12480 (variant finland). Actually im not sure if my qualcom is unlock. My question is can I use this rom same process to flash it by using NCS? thanks
Click to expand...
Click to collapse
no, you need to have an unlocked bootloader, to flash this rom. You can not flash it using NCS.
However Nokia want to sell her phones or atf boxes? ) Why write that stupid nokia bootloader? I read forums and see peoples buying Atf box for flashing phones.
updated to v2.0
Hi there,
just updated first post to FunkyROM v2.0.
Changelog v2.0:
- included MS os updates 7.10.8860.142 and 7.10.8862.144 --> live tile fix!
- added full CAB update support to cab updates signed by: lordmaxey (me ), ultrashot, XBmod-Yuki, Rataplan, CeesHeim, pdaimatejam, voluptuary
- of course everything else from v1.0
Click to expand...
Click to collapse
Enjoy.
please how to flash it
do I need any other device or just a software
please give me the light
Abd654 said:
please how to flash it
do I need any other device or just a software
please give me the light
Click to expand...
Click to collapse
guys, did you do any searching?? any??
http://forum.xda-developers.com/showpost.php?p=38774062&postcount=12
lordmaxey said:
guys, did you do any searching?? any??
http://forum.xda-developers.com/showpost.php?p=38774062&postcount=12
Click to expand...
Click to collapse
one fast question , i belive not stupid , if i use this rom , i will be able to find some extra apps here or on the internet , or only marketplace and the preinstalled ?
i ask this , because i dont have something like this before ...
Santoman7 said:
one fast question , i belive not stupid , if i use this rom , i will be able to find some extra apps here or on the internet , or only marketplace and the preinstalled ?
i ask this , because i dont have something like this before ...
Click to expand...
Click to collapse
because this rom is fully unlocked, you can install every xap (apps) you can find on the internet or in preinstalled programm bazaar.
lordmaxey said:
guys, did you do any searching?? any??
http://forum.xda-developers.com/showpost.php?p=38774062&postcount=12
Click to expand...
Click to collapse
I find a store which can unlock my phone but hasn't atf box , but another flasher for lumia phones , will it work ok ;
I told this because if i have understand well , i want only the Qualcomm bootloader , so is it possible ;
And finally if i get the bootloader , i then go home and put the rom or rom want the box to get installed ;
Thanx for your time ...
Santoman7 said:
I find a store which can unlock my phone but hasn't atf box , but another flasher for lumia phones , will it work ok ;
I told this because if i have understand well , i want only the Qualcomm bootloader , so is it possible ;
And finally if i get the bootloader , i then go home and put the rom or rom want the box to get installed ;
Thanx for your time ...
Click to expand...
Click to collapse
?
as far as i know, ONLY ATF can replace dload with qualcomm bootloader.
If that store does NOT have an ATF, i think they were lying an cheating to you! be careful!
Yes, once you've got the qualcomm bootloader, you can go home and flash my rom using dewe's Lumia Downloader 0.5.
I recommend you reading this thread: http://forum.xda-developers.com/showthread.php?t=2204994
lordmaxey said:
?
as far as i know, ONLY ATF can replace dload with qualcomm bootloader.
If that store does NOT have an ATF, i think they were lying an cheating to you! be careful!
Yes, once you've got the qualcomm bootloader, you can go home and flash my rom using dewe's Lumia Downloader 0.5.
I recommend you reading this thread: http://forum.xda-developers.com/showthread.php?t=2204994
Click to expand...
Click to collapse
http://gsmserver.com/shop/gsm/cyclone_box.php
this is the box i found ...
Santoman7 said:
http://gsmserver.com/shop/gsm/cyclone_box.php
this is the box i found ...
Click to expand...
Click to collapse
No, this box can not flash qualcomm to you Lumia!!
A Lumia phone is NOT a BB5 phone!!! Totally different!
lordmaxey said:
No, this box can not flash qualcomm to you Lumia!!
A Lumia phone is NOT a BB5 phone!!! Totally different!
Click to expand...
Click to collapse
so , I give up ..... None can help me ... And I don't give so much money to buy a flashing machine for just one phone update .... Will may be another way someday ? Or Its finally this way ?
USB Tether
Guys, apologies if this has been covered before. I'd love to share the internet connection via usb to avoid battery drain with wifi sharing. Do any of the custom ROMs allow/enable this? Seems to have been made possible with some of the Samsung Windows Phones but I find the network performance to be phenomenal on the 900 - even better than the 920 I own (looks like this is nowhere near possible on the newer 920). Was hoping the issue had been cracked on the older hardware/software!
@lordmaxey this ROM is amazing :victory: Thank you very much!
there is posible one problem: IE often crashs (I mean that IE automatically exits ) when I watch some websites that contains lots of pictures It does not happen in the original ROM.
But I'm uploading your ROM again and hard reset my phone. Perhaps the problem will disapear
steviesteve78 said:
Guys, apologies if this has been covered before. I'd love to share the internet connection via usb to avoid battery drain with wifi sharing. Do any of the custom ROMs allow/enable this? Seems to have been made possible with some of the Samsung Windows Phones but I find the network performance to be phenomenal on the 900 - even better than the 920 I own (looks like this is nowhere near possible on the newer 920). Was hoping the issue had been cracked on the older hardware/software!
Click to expand...
Click to collapse
No It isn't possible to share Internet connection via USB in Windows Phone
thangvh said:
No It isn't possible to share Internet connection via USB in Windows Phone
Click to expand...
Click to collapse
Yes it is...
Search for "enable USB Tethering with Windows Phone"

Boot Windows RT 8.1 installation PE on DragonBoard 410c

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Actually, it is far more easier to boot Windows RT 8.1 PE on Dragonboard 410c compared to Lumia 520. DB410c is shipped without RPMB provisioned, Secure Boot is off, no Secure Boot keys are provisioned, nor Secure Boot Policy, and almost all UEFI settings are accessible. You need to patch nothing with Windows kernel itself on DB410c.
1. Some preparation
Flash Windows 10 IoT to have UEFI. Access Microsoft's IoT page for details.
On the back of the board, switch USB HOST to on, other switches remain OFF.
In BDS menu, switch Secure Boot off. (It should shipped with Secure Boot off)
2. Windows RT installation disk prepartion
Extract HalExtQCTimer.dll and HalExtQCWdogTimer.dll from Lumia 640XL firmware. Other Windows Phone 8.1 devices with Snapdragon 400/410/801 should work too (not S4, Qualcomm changed hardware design), but I have not tested yet.
PS. If anyone have LG Lancet Windows Phone 8.1 firmware, that's better. Reply or PM me for more if you have one.
Inject HAL extensions:
Mount boot.wim index #1.
Put the two files metioned before to \Windows\System32.
Mount \Windows\system32\config\SYSTEM registry, import HAL extension configuration, like this:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\WinRTSYSTEM\ControlSet001\Control\OSExtensionDatabase]
[HKEY_LOCAL_MACHINE\WinRTSYSTEM\ControlSet001\Control\OSExtensionDatabase\VEN_QCOM&DEV_100A]
"HalExtension"="\SystemRoot\System32\HalExtQCTimer.dll"
[HKEY_LOCAL_MACHINE\WinRTSYSTEM\ControlSet001\Control\OSExtensionDatabase\VEN_QCOM&DEV_100B]
"HalExtension"="\SystemRoot\System32\HalExtQCWdogTimer.dll"
Repeat the operation for boot.wim image #2. Commit changes and unmount boot.wim
I haven't modified install.wim yet. You still need to inject these HAL extensions if you want to install it.
Copy files to a USB key. Modify BCD configuration:
You need boot param passed to kernel:
/REDIRECT /NOVGA /TESTSIGNING
Replace bootmgr.efi, bootarm.efi, bootmgfw.efi with Windows 10 IoT's. I am not sure whether original version will work.
3. Boot
DO NOT BOOT IT FROM UEFI SHELL. I believe there's a bug in Qualcomm's firmware. If you boot any Windows OS in UEFI shell, bootmgfw.efi will work fine, but HAL initialization will certainly fail with error code 0x5c, even Windows 10 IoT. I don't why yet.
Insert USB key to Dragonboard, plug in power supply, press Volume- button until your USB key's LED light indicates there is I/O operation.
It should boot. Ignore the other two options in the picture. I am testing HAL extensions with them.
4. Issues
No drivers are injected yet. I need to inject drivers in order to make USB and other devices work. I will try that after my final test. I think LG Lancet Windows Phone 8.1 firmware is the best driver source for DB410c as they MSM8916 and APQ8016 are similar.
I am not sure if Windows RT's kernel will accept a Windows Phone signed HAL extension without TESTSIGNING option. They have the same Root Certificate though in Windows RT 8.1/Windows Phone 8.1.
DB410c has only 8GB eMMC, if you want to install it on board, storage space will be a problem.
DO NOT BOOT IT FROM UEFI SHELL. I believe there's a bug in Qualcomm's firmware. If you boot any Windows OS in UEFI shell, bootmgfw.efi will work fine, but HAL initialization will certainly fail with error code 0x5c, even Windows 10 IoT. I don't why yet.
You can download FFU file for LG Lancet with WP 8.10.15148.160 here: http://cellomania.com/ffu/product_codes/VW820.html
Here is the list of all the files from Qualcomm packages contained in the LG Lancet ROM.
All files under "\Windows\Packages" are GZipped. Also *.rga files are REG files.
Edit: Edited the attachment to group files by package.
Ok, here is the list of all the packages (sorted alphabetically) with their files.
I discovered that 2 files (MainOS\Windows\Packages\RegistryFilesLGE.BASE.Phone.MainOS.reg & MainOS\Windows\Packages\RegistryFiles\LGE.BASE.Variant.MainOS.reg) contained registry entries for other packages so I made a small script to extract them (you will find them in the attached reg.zip file) and to link them back with their corresponding package.
So, in the packages.txt file, if a reg file has no path, it means you will find it in the reg.zip file
The Windows.zip file contains all the files from MainOS\Windows\Packages ready to be read (no more gzipped).
Hope it helps you
TristanLeBoss said:
Ok, here is the list of all the packages (sorted alphabetically) with their files.
I discovered that 2 files (MainOS\Windows\Packages\RegistryFilesLGE.BASE.Phone.MainOS.reg & MainOS\Windows\Packages\RegistryFiles\LGE.BASE.Variant.MainOS.reg) contained registry entries for other packages so I made a small script to extract them (you will find them in the attached reg.zip file) and to link them back with their corresponding package.
So, in the packages.txt file, if a reg file has no path, it means you will find it in the reg.zip file
The Windows.zip file contains all the files from MainOS\Windows\Packages ready to be read (no more gzipped).
Hope it helps you
Click to expand...
Click to collapse
Much thanks. The major issue now is, Dragonboard uses a Chipidea dual-role USB controller, which might not have propitiate driver support on Windows 8.1. I checked LG Lancet, its USB directly connects to Chipidea USB controller(not dual role). Since they both use 8x16, I believe there is someway to switch it.
imbushuo said:
Much thanks. The major issue now is, Dragonboard uses a Chipidea dual-role USB controller, which might not have propitiate driver support on Windows 8.1. I checked LG Lancet, its USB directly connects to Chipidea USB controller(not dual role). Since they both use 8x16, I believe there is someway to switch it.
Click to expand...
Click to collapse
More phones which use MSM8916 SoC:
- Mouse Computer MADOSMA Q501: http://www.mouse-jp.co.jp/phone/madosma/
- Blu X150Q Win HD LTE Dual SIM
- Blu X130Q Win Jr LTE Dual SIM
- KAZAM Thunder 450WL LTE
Unfortunately, none of them seems to have USB OTG.
---------- Post added at 04:09 AM ---------- Previous post was at 03:58 AM ----------
Btw, did you find out which package from the LG controls USB?
Also, do you have a VID/PID (or any type of applicable identifier) for the USB controller?
You may want to try the Windows 10 drivers... I don't think the BSP offered by Qualcomm is different if you use Windows Mobile 8.10 or 10 (When a phone is upgraded from 8.1 to 10, the drivers are not updated). The inf file may not be working but the sys/dll may work. It's worth the try.
TristanLeBoss said:
More phones which use MSM8916 SoC:
- Mouse Computer MADOSMA Q501: http://www.mouse-jp.co.jp/phone/madosma/
- Blu X150Q Win HD LTE Dual SIM
- Blu X130Q Win Jr LTE Dual SIM
- KAZAM Thunder 450WL LTE
Unfortunately, none of them seems to have USB OTG.
---------- Post added at 04:09 AM ---------- Previous post was at 03:58 AM ----------
Btw, did you find out which package from the LG controls USB?
Also, do you have a VID/PID (or any type of applicable identifier) for the USB controller?
You may want to try the Windows 10 drivers... I don't think the BSP offered by Qualcomm is different if you use Windows Mobile 8.10 or 10 (When a phone is upgraded from 8.1 to 10, the drivers are not updated). The inf file may not be working but the sys/dll may work. It's worth the try.
Click to expand...
Click to collapse
Yeah, their ACPI tree structure is:
- USB Controller
-- USBFn extensions #1
-- USBFn extensions #2
-- ....
I am installing Ubuntu to see how it deals with 410c.
imbushuo said:
Yeah, their ACPI tree structure is:
- USB Controller
-- USBFn extensions #1
-- USBFn extensions #2
-- ....
I am installing Ubuntu to see how it deals with 410c.
Click to expand...
Click to collapse
More info page 10 and 12 of this PDF: http://static.chip1stop.com/pdf/liblary/ARRD/dragonboard_hardwaremanual_v4.1.pdf
You may want to try Windows 10 IoT USB drivers with Windows 8.1 RT... they may work.
Linux support was added in 2015: https://lkml.org/lkml/2015/7/8/702
TristanLeBoss said:
More phones which use MSM8916 SoC:
- Mouse Computer MADOSMA Q501: http://www.mouse-jp.co.jp/phone/madosma/
- Blu X150Q Win HD LTE Dual SIM
- Blu X130Q Win Jr LTE Dual SIM
- KAZAM Thunder 450WL LTE
Unfortunately, none of them seems to have USB OTG.
---------- Post added at 04:09 AM ---------- Previous post was at 03:58 AM ----------
Btw, did you find out which package from the LG controls USB?
Also, do you have a VID/PID (or any type of applicable identifier) for the USB controller?
You may want to try the Windows 10 drivers... I don't think the BSP offered by Qualcomm is different if you use Windows Mobile 8.10 or 10 (When a phone is upgraded from 8.1 to 10, the drivers are not updated). The inf file may not be working but the sys/dll may work. It's worth the try.
Click to expand...
Click to collapse
I didn't find which package, but the ID is ACPI\QCOM2488, it is a USBFN device, located in \\_SB.UFN1 (in dsdt), while DB410c has \\_SB.URS0.USB0 and \\_SB.URS0.UFN0.
imbushuo said:
I didn't find which package, but the ID is ACPI\QCOM2488, it is a USBFN device, located in \\_SB.UFN1 (in dsdt), while DB410c has \\_SB.URS0.USB0 and \\_SB.URS0.UFN0.
Click to expand...
Click to collapse
Ok, if I understand, for LG Lancet :
ACPI\QCOM2488
-> \\_SB.UFN1
For 410c:
ACPI\QCOM2488
-> \\_SB.URS0.USB0
-> \\_SB.URS0.UFN0
If you look at the packages.txt file, there is a package named "Microsoft.Drivers.UfxChipIdea" and one named "Microsoft.Drivers.UsbFnChipIdea". It seems they hold the driver for the Chipidea chip. I don't know if they support OTG but you should try.
I attached a small packages_usb.txt with updated packages files for the USB packages and new reg files for those packages (which were inside Microsoft.MainOS.Production.reg).
These drivers are also part of Windows 10 so maybe the one from Windows 10 IoT are backward compatible?
I am wondering if the OTG support is built inside these drivers, part of another driver or part of the OS?
https://msdn.microsoft.com/en-us/library/windows/hardware/dn957036(v=vs.85).aspx
"The Microsoft USB Role Switch (URS) driver allows a system implementer to take advantage of the dual-role USB capability of their platform."
"These drivers are provided by Microsoft as in-box drivers. Chipidea High-Speed USB OTG Controller. Inbox INF: UrsChipidea.inf."
"URS0 is the ACPI definition for the USB dual-role controller. This is the ACPI device on which the URS driver will load.
USB0 and UFN0 are child devices inside the scope of URS0. USB0 and UFN0 represent the two child stacks that will be enumerated by the URS driver, and the host and function stacks respectively. Note that _ADR is the means by which ACPI matches these device definitions with the device objects that the URS driver creates."
"On a system that has a USB micro-AB connector, the driver makes use of hardware interrupts that indicates the state of the ID pin on the connector. This pin is used to detect whether the controller needs to assume the host role or the function role in a connection."
"Driver installation packages:
If you're an IHV or an OEM and you're thinking of providing your own driver package, here are some things to consider:
-> URS driver package
It is expected that the Hardware ID for the dual-role controller on each platform will be added to the inbox INF for URS. However, if for some reason the ID cannot be added, the IHV/OEM may provide a driver package with an INF that Needs/Includes the inbox INF and matches their Hardware ID.
This is necessary in the case where the IHV/OEM requires a filter driver to be present in the driver stack.
-> Host driver package.
An IHV/OEM-provided driver package that Needs/Includes the inbox usbxhci.inf and matches the host device Hardware ID is required. The Hardware ID match would be based on the scheme described in the preceding section.
This is necessary in the case where the IHV/OEM requires a filter driver to be present in the driver stack.
There is work in progress to make URS driver assign the XHCI Compatible ID for the host device.
-> Function driver package
An IHV/OEM-provided driver package that Needs/Includes the inbox Ufxsynopsys.inf and matches the peripheral device Hardware ID is required. The Hardware ID match would be based on the scheme described in the preceding section.
The IHV/OEM can also include a filter driver in the driver package."
This page is for WIndows 10 and it's not sure that Windows 8.1 supported dual-role drivers... because I found nothing on Google.
TristanLeBoss said:
Ok, if I understand, for LG Lancet :
ACPI\QCOM2488
-> \\_SB.UFN1
For 410c:
ACPI\QCOM2488
-> \\_SB.URS0.USB0
-> \\_SB.URS0.UFN0
If you look at the packages.txt file, there is a package named "Microsoft.Drivers.UfxChipIdea" and one named "Microsoft.Drivers.UsbFnChipIdea". It seems they hold the driver for the Chipidea chip. I don't know if they support OTG but you should try.
I attached a small packages_usb.txt with updated packages files for the USB packages and new reg files for those packages (which were inside Microsoft.MainOS.Production.reg).
These drivers are also part of Windows 10 so maybe the one from Windows 10 IoT are backward compatible?
I am wondering if the OTG support is built inside these drivers, part of another driver or part of the OS?
Click to expand...
Click to collapse
I don't think it has built-in support. I checked MSDN, USB role switch is a new feature introduced in Windows 10. And these USBFn drivers are used for USB device support, not USB host support.
Another Windows Embedded 8.1 Handheld device, Panasonic FZ-E1, has built-in USB OTG support in 8.1. I don't know how Panasonic implemented that yet.
imbushuo said:
I don't think it has built-in support. I checked MSDN, USB role switch is a new feature introduced in Windows 10. And these USBFn drivers are used for USB device support, not USB host support.
Another Windows Embedded 8.1 Handheld device, Panasonic FZ-E1, has built-in USB OTG support in 8.1. I don't know how Panasonic implemented that yet.
Click to expand...
Click to collapse
There is also an app which claims OTG support on Windows Phone 8.1: https://www.microsoft.com/fr-fr/store/apps/ninko-wp/9wzdncrdg98s
I have no Windows Phone so I can't poke inside... (I have the XAP file but it's encrypted and the only way to decrypt it is to install it on a WIndows Phone device).
---------- Post added at 06:11 PM ---------- Previous post was at 06:06 PM ----------
https://blogs.msdn.microsoft.com/wi...manufacturing-sdk-is-now-generally-available/
"What is new in Windows Embedded 8.1 Handheld?" "Support for USB Host"
So, it seems USB OTG is part of the Embedded version. We just need to hunt for a rom
---------- Post added at 06:16 PM ---------- Previous post was at 06:11 PM ----------
https://blogs.msdn.microsoft.com/ms...xperience-with-windows-embedded-handheld-8-1/
"Right now Microsoft is working with 5 OEMs that are bringing awesome devices like the Pidion one, those OEMs right now are:
Ingenico
Panasonic
Motorola
Intermec
Bluebird"
Did you find a ROM with Windows Embedded 8.1 Handheld? I searched but found nothing. You may want to ask in this forum if someone as one...
The only thing I found is the WE8.1H SDK which contains an emulator image (ffu). Unfortunately, like all the official emulators (Hololens, Windows Phone, Windows Phone), it's an x86 compilation of WE8.1H but it can help understand: only the files can't be used on an ARM devices.
https://www.microsoft.com/en-us/download/details.aspx?id=43677
TristanLeBoss said:
Did you find a ROM with Windows Embedded 8.1 Handheld? I searched but found nothing. You may want to ask in this forum if someone as one...
The only thing I found is the WE8.1H SDK which contains an emulator image (ffu). Unfortunately, like all the official emulators (Hololens, Windows Phone, Windows Phone), it's an x86 compilation of WE8.1H but it can help understand: only the files can't be used on an ARM devices.
https://www.microsoft.com/en-us/download/details.aspx?id=43677
Click to expand...
Click to collapse
Just contacted someone who owned a Panasonic FZ-E1. This device has two USB channels, one for USB device and another for USB host. This explains why it supports USB host mode in Windows Embedded 8.1 Handheld.
For the app, it said it used something not related to USB OTG.
I think you should have to add intermediate certificate to the store.
One is Microsoft Windows Phone Production 2012 for WP8.1 & Before.
Another is Microsoft Windows Mobile 2014 for W10M and later. That would be amazing. Universal ROM lol
imbushuo said:
Actually, it is far more easier to boot Windows RT 8.1 PE on Dragonboard 410c compared to Lumia 520. DB410c is shipped without RPMB provisioned, Secure Boot is off, no Secure Boot keys are provisioned, nor Secure Boot Policy, and almost all UEFI settings are accessible. You need to patch nothing with Windows kernel itself on DB410c.
1. Some preparation
Flash Windows 10 IoT to have UEFI. Access Microsoft's IoT page for details.
On the back of the board, switch USB HOST to on, other switches remain OFF.
In BDS menu, switch Secure Boot off. (It should shipped with Secure Boot off)
2. Windows RT installation disk prepartion
Extract HalExtQCTimer.dll and HalExtQCWdogTimer.dll from Lumia 640XL firmware. Other Windows Phone 8.1 devices with Snapdragon 400/410/801 should work too (not S4, Qualcomm changed hardware design), but I have not tested yet.
PS. If anyone have LG Lancet Windows Phone 8.1 firmware, that's better. Reply or PM me for more if you have one.
Inject HAL extensions:
Mount boot.wim index #1.
Put the two files metioned before to \Windows\System32.
Mount \Windows\system32\config\SYSTEM registry, import HAL extension configuration, like this:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\WinRTSYSTEM\ControlSet001\Control\OSExtensionDatabase]
[HKEY_LOCAL_MACHINE\WinRTSYSTEM\ControlSet001\Control\OSExtensionDatabase\VEN_QCOM&DEV_100A]
"HalExtension"="\SystemRoot\System32\HalExtQCTimer.dll"
[HKEY_LOCAL_MACHINE\WinRTSYSTEM\ControlSet001\Control\OSExtensionDatabase\VEN_QCOM&DEV_100B]
"HalExtension"="\SystemRoot\System32\HalExtQCWdogTimer.dll"
Repeat the operation for boot.wim image #2. Commit changes and unmount boot.wim
I haven't modified install.wim yet. You still need to inject these HAL extensions if you want to install it.
Copy files to a USB key. Modify BCD configuration:
You need boot param passed to kernel:
/REDIRECT /NOVGA /TESTSIGNING
Replace bootmgr.efi, bootarm.efi, bootmgfw.efi with Windows 10 IoT's. I am not sure whether original version will work.
3. Boot
DO NOT BOOT IT FROM UEFI SHELL. I believe there's a bug in Qualcomm's firmware. If you boot any Windows OS in UEFI shell, bootmgfw.efi will work fine, but HAL initialization will certainly fail with error code 0x5c, even Windows 10 IoT. I don't why yet.
Insert USB key to Dragonboard, plug in power supply, press Volume- button until your USB key's LED light indicates there is I/O operation.
It should boot. Ignore the other two options in the picture. I am testing HAL extensions with them.
4. Issues
No drivers are injected yet. I need to inject drivers in order to make USB and other devices work. I will try that after my final test. I think LG Lancet Windows Phone 8.1 firmware is the best driver source for DB410c as they MSM8916 and APQ8016 are similar.
I am not sure if Windows RT's kernel will accept a Windows Phone signed HAL extension without TESTSIGNING option. They have the same Root Certificate though in Windows RT 8.1/Windows Phone 8.1.
DB410c has only 8GB eMMC, if you want to install it on board, storage space will be a problem.
DO NOT BOOT IT FROM UEFI SHELL. I believe there's a bug in Qualcomm's firmware. If you boot any Windows OS in UEFI shell, bootmgfw.efi will work fine, but HAL initialization will certainly fail with error code 0x5c, even Windows 10 IoT. I don't why yet.
Click to expand...
Click to collapse
you don't need a halext to boot RT 8.1 on DB410c.

How to: use WSUS (Windows Server Update Services) to update Windows 10 Mobile devices

I've written this up in case of interest - reasons you might want to use WSUS include if you want to manage or update multiple Windows 10 Mobile devices or if you want complete control over what build you update to and when (rather than just getting the latest supported one when MS decide is time).
Also I suspect the "defer upgrades" trick to get Threshold 2 (10586.xxx) updates on the older unsupported Lumias may stop working once Redstone 1 makes its way down to the Current Branch for Business later this year, so I was keen to test this out to be sure that it will still be possible to update a device from Windows Phone 8.1 or Windows 10 Mobile 10586.xxx to the latest 10586.xxx build (currently 10586.839 - March 2017) perpetually, whatever Microsoft do (the iutool method of installing the update never worked for me - it works for getting the initial 10586.107 upgrade from 8.1 though).
If WSUS is for you, here's what you need to do:
(1) I will assume you are starting with a fresh copy of Windows Server 2012 R2 as this is what I used - other versions of Windows Server will be similar and can also be used though. Just download the trial version from Microsoft if you don't have a licence key for a suitable version of Windows Server, and install it in a VM.
(2) Open Server Manager (Control Panel > Administrative Tools > Server Manager) - in there choose Manage > Add Roles and Features from the top-right menus. Click Next until you reach a list of available roles; tick "Windows Server Update Services" and accept the prompt to add required dependencies if it appears. Continue to click Next to complete the wizard and install the WSUS role. The default settings are all fine if you will be using the Windows Internal Database. Ensure that you choose the option to download updates locally and enter a suitable folder path for these to be saved to (otherwise if MS ever remove the updates from Windows Update, your WSUS server will be useless!)
(3) Once it has finished installing, open Control Panel > Administrative Tools > Windows Server Update Services. This will complete the post-installation configuration the first time it is run. Click through the initial wizard - again all the default options should be fine. Click "Start connecting" when prompted and wait for it to download all the information about the available updates from Windows Update, this seems to take quite a while so be patient! Once the Next button is no longer greyed out, click it.
(4) Next you have to choose what products and languages your WSUS server will be used for. I don't think this actually matters as Windows 10 Mobile updates don't seem to be an option here anyway and we will instead be importing the relevant update(s) from the Microsoft Update Catalogue later on - I chose English, Windows 10, and all types of updates here.
(5) Choose whether to synchronise the details of available updates manually or automatically - I chose manually given that we will be manually adding the update from the Microsoft Update Catalogue anyway.
(6) The WSUS server is now ready so we now need to create a provisioning package to configure your phone(s) to use it when checking for updates, rather than Microsoft's servers. https://blogs.technet.microsoft.com...ge-to-upgrade-to-windows-10-mobile-enterprise covers doing this, you can either use the same package as your one to upgrade to Enterprise edition (WSUS can only be used with Windows 10 Mobile Enterprise) or a separate one. Essentially to create the package you need to install the Windows Imaging and Configuration Designer (download from https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx#adkwin10 - I'm using the 1511/Threshold 2 version), tick just the ICD part and allow it to select the prerequisite parts:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once installed, run Windows Kits > Windows Imaging and Configuration Designer from the Start Menu, select "New Provisioning Package" from the opening screen, and enter a name for it (I called mine "WSUS"). Select "Common to all Windows mobile editions" on the next screen, then on the next screen click Finish without importing anything.
Once the empty package has been created,in the left-hand tree expand Runtime Settings > Policies > Update, and select "UpdateServiceUrl". In the centre pane, enter http:// followed by your WSUS server's name and port number - in this example the server is called VM-WSUS and the port number is the default WSUS port of 8530:
View attachment 4078601
Once you have added all of the customisations that you want, go to Export > Provisioning Package at the top and save the package (again I just called it "WSUS").
(7) Copy the resulting package(s) to your phone e.g. via USB cable (any location is fine, I chose the Downloads folder), and select the prompt that appears to apply it. Note that you must do the Enterprise upgrade one first if you were not already running Enterprise edition, and you only need the .ppkg file, not the .cat file that it also creates.
(8) Once it has been applied, on the phone go to Settings > Update and Security > Phone Update. If you are on the Threshold 2 branch you must tick the "Defer upgrades" box under "advanced options", the more recent Threshold 2 updates (i.e. those released since Redstone) will only install on devices where this is set. Then press the button to check for updates. To check it is connecting to your WSUS server and not to Microsoft's servers, ensure you see the tickbox to check with Microsoft instead - this confirms it is configured to use WSUS (like how when a desktop PC is configured to use WSUS). At this stage it should say no updates are available as we haven't yet added any relevant updates to WSUS. If it says it "can't connect to the update service" or you don't see the box to check online instead, then something has gone wrong with the above steps.
Just ensure this box is there; don't tick it if you want to get your updates from your WSUS server!
The phone should also appear under Computers on the WSUS server once it has checked in for the first time.
(9) Next we need to add the update(s) that we want - back on your WSUS server, continuing in Control Panel > Administrative Tools > Windows Server Update Services, click "Updates" in the left-hand tree and then click "Import updates" in the right-hand Actions" pane. This opens Internet Explorer and prompts you to install an ActiveX control. Once done, search for the update you want - they can be tricky to find, generally searching for "xxx mobile" where xxx is the part of the build number after 10.0.10586 will get you the more recent Threshold 2 updates; you will need to do your own research if you want a different update. I don't know why they have a different main build number rather than 10586.
For example:
10.0.10586.839 (March 2017 cumulative update for W10M, Threshold 2 branch): https://www.catalog.update.microsoft.com/Search.aspx?q=839 mobile
Click "Add" next to the larger update, then click "View basket" at the top - then click "Import". This will add the update to WSUS but won't actually download the files for it yet.
(10) Once it says it has finished, go back to Control Panel > Administrative Tools > Windows Server Update Services, select Updates > All Updates in the left-hand tree and change the filter at the top to a status of "Any", then click Refresh. Your update should be shown - click on it, then in the right-hand Actions pane click "Approve". Click the "no" symbol to the left of "All Computers" and select "Approved for Install" - the "no" symbols should change to ticks:
(you will see that you can check the "correct" build number of the update in the Description section towards the bottom of the window - highlighted above)
(11) Wait for the update (around 2.5 GB as it is cumulative and contains the files for all mobile devices) to be downloaded into WSUS - you can see how it is doing by clicking on the name of your WSUS server in the left-hand tree view. If it is very slow you may want to change the settings in gpedit.msc under Computer Configuration > Administrative Templates > Network > Background Intelligent Transfer Service > Limit the maximum network bandwidth for BITS Background Transfers.
(12) Once it is fully downloaded, check for updates on your phone again. With any luck, you will see the update begin to download from your WSUS server!
Hope this helps and/or is interesting, feel free to post below how you get on! I've tested updating a Lumia 625 straight from 10586.107 all the way to 10586.839 with this, you only need the one update as they are cumulative.
Why not post spkg file?
augustinionut said:
Why not post spkg file?
Click to expand...
Click to collapse
The WSUS .ppkg file contains the name of your WSUS server, so it will be specific to your setup! There is a copy of the one to upgrade to Enterprise edition (prerequisite for using WSUS) in the other thread (https://forum.xda-developers.com/showpost.php?p=71091803&postcount=25).
This is really interesting!
I went searching for the latest windows mobile 10 version (on lumia 920, pretending to be a 950xl) and I cannot find any updates since 2018, but my phone did an update with a very happy result
The update was at the end of April/begining of May 2019
I am on the tech preview/insider fast ring on the phone.
Here are some details if anyone wants to go looking
Version 1709
Os Build 10.0.15254.566
Firmware rev #:3051.50009.1451.1009
The phone model reads: MicrosoftMDG Lumia 950 XL
So when the update read "We promise it will be worth the wait" microsoft did not lie!
The update fixed the issue with my bluetooth (because it was running 950 updates using 920 hardware I assume the driver could not launch in past builds) and improved my battery life.
I think it would be really nice to get the latest build downloaded and see if there is anything out there that is above 15254.566 (what I am allowed to get) and test to see if it will run on the Lumia 950 XL or other phones.
...and I think you are right, use a server and get all the updates downloaded for those of us who are tinkering around, so that we can have a play, and even roll back builds to get access to astoria.
Maybe someone can find a way to port project Astoria to the latest build/update so that we can hang on to these devices a while longer?!

[New Version][V3.0] AEM Store - A program to sideload Windows Store apps

AEM Store
A alternative place to download and sideload Windows Store apps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. find your app (Make sure you are on the app page)
2. Click on the download button at the top right corner
3. Find the appropriate package containing either _arm_ or _neutral_ in the filename and .appx or .appxbundle in the file extension
(Download any dependencies if required)
4. Download the files
(some might not have the extension anymore, so add it back)
5. Run the .appx/.appxbundle files and click on install
Websites used in this program:
Microsoft Store: https://www.microsoft.com/en-us/store/b/home
MStoreLinkGenLite: https://github.com/alexenferman/MStoreLinkGenLite
Source code (Coming soon. Need to clean the code)
https://github.com/alexenferman/AEM-Store
This Software along with MStoreLinkGen are licensed under the GNU General Public License v3.0
https://github.com/alexenferman/AEM-Store/blob/main/LICENSE
In addition to this license, you are NOT allowed to sell this software, alone or in a bundle.
Download the latest version
New Version! [v3.0 / 2020-11-27]
Changelog:
New logo
New download section
New Design
Consumes less RAM (Around 60MB)
Now open source
problem certificate 0
Hi thanks for this program but i have a problem when i click for download the application there is an error of certificate (not be connect to the page of alternative store certificate 0). how can i solve it? thank for any response
diablojet said:
Hi thanks for this program but i have a problem when i click for download the application there is an error of certificate (not be connect to the page of alternative store certificate 0). how can i solve it? thank for any response
Click to expand...
Click to collapse
Can you more specific about the error you are getting?
If you meant that one of the websites are not loading because of the certificate problem, then the website has to renew their certificate. I checked on march 31st and it appears that it works. If you still get this error try to go on the windows store website and on the https://store.rg-adguard.net/ website on the edge browser to see if you get the same error.
Also when you download an app DO NOT click on Get. Always click on the download icon at the bottom right corner.
Thank you
Now it work sorry
Hi thanks for the reply and I apologize in advance for making you waste time now I don't know why it works. Thanks again.
alexenferman said:
Since the store started to not work on my surface RT, I decided to develop a program that makes it easier to sideload apps from the Microsoft Store and allows you to install them manually.
ARM RT App-Store
How to install apps using this program: (It might seem like a long process but it's not)
1. find your app (Make sure you are on the app page)
2. Click on the download button at the bottom right corner
3. You will be at a different page, so click on the check mark button
4. Find the appropriate package containing either _arm_ or _neutral_ in the filename and .appx or .appxbundle in the file extension
(Download any dependencies if required)
5. Download the files
(some might not have the extension anymore, so add it back)
6. Run the .appx/.appxbundle files and click on install
Issues:
The program uses around 100MB of RAM
It requires a lot of steps
It needs a better name
Some apps, such as Microsoft games, do not open because they are not added to your account
Some apps, need a modified manifest to install
Websites used in this program
Microsoft Store: https://www.microsoft.com/en-us/store/b/home
Microsoft Store link generator: https://store.rg-adguard.net/
Note:
Make sure you have the .NET Runtime packages
You can also use this program on a x86 computer
Terms and conditions:
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Click to expand...
Click to collapse
Hey want to try this out but when I select the file to download, the download dialogue opens but it never starts to download. Just sits there. Any idea why?
Thanks
dk1keith said:
Hey want to try this out but when I select the file to download, the download dialogue opens but it never starts to download. Just sits there. Any idea why?
Thanks
Click to expand...
Click to collapse
Yes. All you have to do is ignore the first download window and click on the file you want to download again and the second time it should come up.
alexenferman said:
Yes. All you have to do is ignore the first download window and click on the file you want to download again and the second time it should come up.
Click to expand...
Click to collapse
that worked. thanks
Hey this thing is awesome! I'm looking to build an app for the surface rt as well. What UWP SDK are you using to build this? Is there a specific process you needed to use in order for it to run on the tablet?
kmccmk9 said:
Hey this thing is awesome! I'm looking to build an app for the surface rt as well. What UWP SDK are you using to build this? Is there a specific process you needed to use in order for it to run on the tablet?
Click to expand...
Click to collapse
Thank you! No. You do not need any UWP sdk. I used the Visual Studio community edition (Free). If you know how to program in VB.net (Very easy), you can make programs that work on any platform by default. No need for additionnal SDks. As long as you have the .net runtime packages installed on your tablet (Comes installed by default), your program will run on any platform (Windows ARM, x86, even Linux!) If you do not know how to program on VB.net, it's actually VERY VERY easy! You design the program first by dragging buttons, textboxes, labels, etc... and then you do the programming. There are a lot of free resources available.
Hope this helps, PM me if you have more questions!
alexenferman said:
Thank you! No. You do not need any UWP sdk. I used the Visual Studio community edition (Free). If you know how to program in VB.net (Very easy), you can make programs that work on any platform by default. No need for additionnal SDks. As long as you have the .net runtime packages installed on your tablet (Comes installed by default), your program will run on any platform (Windows ARM, x86, even Linux!) If you do not know how to program on VB.net, it's actually VERY VERY easy! You design the program first by dragging buttons, textboxes, labels, etc... and then you do the programming. There are a lot of free resources available.
Hope this helps, PM me if you have more questions!
Click to expand...
Click to collapse
Ok thank you very much for responding. I'm very comfortable with C# so I'll go with Visual C#. I was trying UWP but getting a lot of annoying errors. I'll give standard C# ARM a shot. Maybe I'll use WPF to make it look nice
kmccmk9 said:
Ok thank you very much for responding. I'm very comfortable with C# so I'll go with Visual C#. I was trying UWP but getting a lot of annoying errors. I'll give standard C# ARM a shot. Maybe I'll use WPF to make it look nice
Click to expand...
Click to collapse
You actually don't need to touch anything. Leave everything by default. On the top, if it says any CPU, leave it as-is and it will work on your tablet and computer.
alexenferman said:
You actually don't need to touch anything. Leave everything by default. On the top, if it says any CPU, leave it as-is and it will work on your tablet and computer.
Click to expand...
Click to collapse
Darn it actually doesn't seem to be working. Maybe it is targeting too high of a .net framework?
---------- Post added at 03:18 AM ---------- Previous post was at 02:55 AM ----------
alexenferman said:
You actually don't need to touch anything. Leave everything by default. On the top, if it says any CPU, leave it as-is and it will work on your tablet and computer.
Click to expand...
Click to collapse
So did you do VB with Universal Windows?
Any workaround for this "Some apps, such as Microsoft games, do not open because they are not added to your account"? Like trying to register the game/app into a Windows 10 pc?
Thanks!
---------- Post added at 05:37 PM ---------- Previous post was at 05:37 PM ----------
Any workaround for this "Some apps, such as Microsoft games, do not open because they are not added to your account"? Like trying to register the game/app into a Windows 10 pc?
Thanks!
thanks for the appstore!
so i downloaded netflix 2.22.0.39arm and the required apps on surface rt with the windows 10 leaked build
installed without any problems
but when i launch it i closed right away
any idea whats wrong there?
p.s. i tried all arm version that i was able to install from the download list
but all of them install (once u install required libs) but when u start open and close
andPS2 said:
thanks for the appstore!
so i downloaded netflix 2.22.0.39arm and the required apps on surface rt with the windows 10 leaked build
installed without any problems
but when i launch it i closed right away
any idea whats wrong there?
p.s. i tried all arm version that i was able to install from the download list
but all of them install (once u install required libs) but when u start open and close
Click to expand...
Click to collapse
I assume you are connected to the internet so the app can acquire a license?
jwa4 said:
I assume you are connected to the internet so the app can acquire a license?
Click to expand...
Click to collapse
yes i'm connected
might be a general problem since all of the apps installed with the hack
Windows_10_15035_ARM32_AppUpdate do the same
P.S. fixed it by applying the Image again
Apps do work now!
andPS2 said:
yes i'm connected
might be a general problem since all of the apps installed with the hack
Windows_10_15035_ARM32_AppUpdate do the same
Click to expand...
Click to collapse
All the apps I tried from that pack so far worked fine. Longshot, but is your system time set right?
Edit: One thing I should mention is I'm not using the ready to go WIM, I got the untouched WIM from Beta Archive and applied fixes, drivers and finally apps myself.
jwa4 said:
All the apps I tried from that pack so far worked fine. Longshot, but is your system time set right?
Edit: One thing I should mention is I'm not using the ready to go WIM, I got the untouched WIM from Beta Archive and applied fixes, drivers and finally apps myself.
Click to expand...
Click to collapse
i would love to use that as well but not sure how to apply the drivers and fixes
would it be kinda like described here?
https://forums.mydigitallife.net/threads/download-windows-10-rs3-rtm-b16299-15-pe-arm32.75321/
p.s. i got it to work by applying the windows 10 image again!
i wonder what is causing the app activation to fail
applied windows 10 image again
installed apps -> all of them worked including skype and netflix
hours later after couple reboots and activating windows
i got more apps (adobe touch, microsoft reader, teamviewer and vlc)
all of these close right after i start them so again this problem that they cant
get the license...

[2022] HD2 Reborn pack

I am still using Legendary HTC HD2 in 2022. It was too hard to find all tools, utilites, ROMs, Recoveries etc... because of dead links, closed forums (Tytungs for example) etc... Also most of tools didnt work on Windows 10 and it was hard to run them on VM due USB/driver linking issues beetween main OS and VM. Finally I found solutions for all these problems and want to share these solutions with community.
I made 5 exe files to run Android 2.3.7 on Nand with Magldr and CWM recovery on HTC HD2.
- 1st; run "hd2driverinstaller.exe" both your Windows10/11 PC and VM Windows XP
- 2nd; run "HSPL.exe" on VM Windows XP to bypass SPL security mechanism
- 3rd; run "task29.exe" on VM Windows XP to erase NAND
- 4th; run "magldrinstaller.exe" on VM Windows XP to install aMagldr 1.13.08
- 5th; run "magldrwizard" on VM Windows XP to install Android and CWM on NAND
All tools except HSPL.exe modified or rewrited by me. Android ROM is based on Tytung's latest Gingerbread 2.3.7 - 3.3a. But heavily modified for remove not working apps etc. It has only 111 MB system partition size. If anyone wants its aroma flashable zip, I can upload it too.
Downloads: https://disk.yandex.com.tr/d/gySgVqkHx91loQ
The fact is I eventually found back my HD2s (one working great on Win Mobile, another one not working but used to work under Android and 2 others dead I bought years ago for parts and batteries) two days ago so I will try and report
I was thinking of doing that but found no time to do so. So thanks in advance !
It will be fun to try to use the legendary HD2 in 2022
BTW what is the size of the SD card you use ?
Howell said:
The fact is I eventually found back my HD2s (one working great on Win Mobile, another one not working but used to work under Android and 2 others dead I bought years ago for parts and batteries) two days ago so I will try and report
I was thinking of doing that but found no time to do so. So thanks in advance !
It will be fun to try to use the legendary HD2 in 2022
BTW what is the size of the SD card you use ?
Click to expand...
Click to collapse
Hi I use 16 gb class 10 sd card. I am working on tytung's 4.0.4 rom. Google Play Services and all google services works now. I will share when I finished it too.
I still have most tools backed up to a USB drive.
If you ever need anything you miss, let me know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any chances of reups of any newer roms? just to get the playstore and browers working. Would be much apreciated
symbuzzer said:
I am still using Legendary HTC HD2 in 2022. It was too hard to find all tools, utilites, ROMs, Recoveries etc... because of dead links, closed forums (Tytungs for example) etc... Also most of tools didnt work on Windows 10 and it was hard to run them on VM due USB/driver linking issues beetween main OS and VM. Finally I found solutions for all these problems and want to share these solutions with community.
I made 5 exe files to run Android 2.3.7 on Nand with Magldr and CWM recovery on HTC HD2.
- 1st; run "hd2driverinstaller.exe" both your Windows10/11 PC and VM Windows XP
- 2nd; run "HSPL.exe" on VM Windows XP to bypass SPL security mechanism
- 3rd; run "task29.exe" on VM Windows XP to erase NAND
- 4th; run "magldrinstaller.exe" on VM Windows XP to install aMagldr 1.13.08
- 5th; run "magldrwizard" on VM Windows XP to install Android and CWM on NAND
All tools except HSPL.exe modified or rewrited by me. Android ROM is based on Tytung's latest Gingerbread 2.3.7 - 3.3a. But heavily modified for remove not working apps etc. It has only 111 MB system partition size. If anyone wants its aroma flashable zip, I can upload it too.
Downloads: https://disk.yandex.com.tr/d/gySgVqkHx91loQ
Click to expand...
Click to collapse
Thank you, but I cannot for the life of me get HSPL to work.
It's taken me a while to get XP on a VM working, have tried all the steps here: https://forum.xda-developers.com/t/resolved-hspl2-and-hspl3-and-usb-connect-failed.731620/
Still HSPL just sits there, 'Waiting of a USB connection...'
grayme said:
Thank you, but I cannot for the life of me get HSPL to work.
It's taken me a while to get XP on a VM working, have tried all the steps here: https://forum.xda-developers.com/t/resolved-hspl2-and-hspl3-and-usb-connect-failed.731620/
Still HSPL just sits there, 'Waiting of a USB connection...'
Click to expand...
Click to collapse
On Virtual Machine app setting, enable usp ports when phone is plugged on usb
symbuzzer said:
On Virtual Machine app setting, enable usp ports when phone is plugged on usb
Click to expand...
Click to collapse
I believe I've done that. I can get activesync to connect up and sync.
Have tried putting the HD2 into bootloader and waiting for serial to become usb...
V1 of hspl says it's working and not to disconnect (then just sits doing nothing) but all other versions time out.
I'm wondering if these HD2s I have may have already been unlocked...
Finally got it working on one HD2, thanks.
Other seems bricked.
symbuzzer said:
I am still using Legendary HTC HD2 in 2022. It was too hard to find all tools, utilites, ROMs, Recoveries etc... because of dead links, closed forums (Tytungs for example) etc... Also most of tools didnt work on Windows 10 and it was hard to run them on VM due USB/driver linking issues beetween main OS and VM. Finally I found solutions for all these problems and want to share these solutions with community.
I made 5 exe files to run Android 2.3.7 on Nand with Magldr and CWM recovery on HTC HD2.
- 1st; run "hd2driverinstaller.exe" both your Windows10/11 PC and VM Windows XP
- 2nd; run "HSPL.exe" on VM Windows XP to bypass SPL security mechanism
- 3rd; run "task29.exe" on VM Windows XP to erase NAND
- 4th; run "magldrinstaller.exe" on VM Windows XP to install aMagldr 1.13.08
- 5th; run "magldrwizard" on VM Windows XP to install Android and CWM on NAND
All tools except HSPL.exe modified or rewrited by me. Android ROM is based on Tytung's latest Gingerbread 2.3.7 - 3.3a. But heavily modified for remove not working apps etc. It has only 111 MB system partition size. If anyone wants its aroma flashable zip, I can upload it too.
Downloads: https://disk.yandex.com.tr/d/gySgVqkHx91loQ
Click to expand...
Click to collapse
Is the Aroma flashable zip Android 3...?
grayme said:
Is the Aroma flashable zip Android 3...?
Click to expand...
Click to collapse
No, it is Magldr's DAF flasher.
I updated Tytung's lastest AOSP Gingerbread (2.3.7) rom to v1.02 today. You can download it's "5-magldrwizard.exe" file from https://disk.yandex.com.tr/d/gySgVqkHx91loQ
Code:
Changelog:
1.02:
- Only need 105 MB system partition now
- Removed all Google related apps (Except Framework due not working anymore)
- Removed default browser and downloads apps (due certificate errors)
- Added latest Opera Mini
- Removed Calendar app (due GAPPS not working anymore)
- Added original HTC Torch app
- Removed AOSP Launcher2
- Added Cyanogenmod 7's ADW Launcher
- Added Cyanogenmod 7's default file manager
- Rooted via latest SuperSU app
- Added soundrecord's icon to launcher
- Added Adguard DNS to buildprop
- Reverted Android's default host file
- Removed all TTS related items from system and Settings app
- Removed not working Dock option from Settings app
- Added proper version info to build.prop
- Removet startup animation
- Removed animated wallpapers (Animated Walpaper picker is still there, you can install any animated wallpaper)
- Added specific/modified ClockWorkMod recovery
1.01:
-early version
1.00:
-initial release
I made this rom for my 2nd daily phone, HTC HD2. I am open to comments and suggestions. I will regularly update this rom.
Code:
Planned v1.03 changes:
- Removing applicationprovider.apk (Search Application Provider)
- Modifying gps.conf
- Adding dark messages app
- Overclocking to 1190 Mhz
...
Thank you, works well.
I'm looking for a ROM that connects to Wi-Fi and I can install and run Tasker on. Unfortunately, 2.3.7 won't log in to Google or run Google Play...
I've found some ICS ROMs that should enable logging into Google, but Wi-Fi won't connect.
Is there a reason you stick with 2.3.7?
grayme said:
Thank you, works well.
I'm looking for a ROM that connects to Wi-Fi and I can install and run Tasker on. Unfortunately, 2.3.7 won't log in to Google or run Google Play...
I've found some ICS ROMs that should enable logging into Google, but Wi-Fi won't connect.
Is there a reason you stick with 2.3.7?
Click to expand...
Click to collapse
u can install tasker and tasker app factory on my rom, sir?
symbuzzer said:
u can install tasker and tasker app factory on my rom, sir?
Click to expand...
Click to collapse
I haven't been able to, at least not via Google Play Store (as I cannot install it nor log into my Google account on this ROM, nor via extracting the apk from my Android 12.1 phone and install on the HD2 due to the Android version being lower.
Tasker does allow you to download and buy a separate version for Gingerbread, but I may as well give up on the HD2 and buy another phone that will work with Google Play.
Am I missing a way to get it on and working?
u can find gingerbread compatible tasker's apk from internet, sir
I know, but I am not going to use an unofficial version of Tasker (would you trust something so powerful with your data from an unofficial source), and I am not going to buy a second version of Tasker given I have already bought it.
So I either find a later version of Android that connects to wifi, or give up completely and go with another phone.
Hey everyone. I would like to participate in this kind of topic, so I have compiled LineageOS 11 (basically CM11 with security updates up to February 2019) with 3.0 kernel for our device. But the zip file looks pretty raw compared to tytung's CM11 one. It needs some adaptation to the device, especially in part of bootloaders compatibility and ability to install using Data-on-EXT and NativeSD methods. And also the ROM needs to be tested after all these changes. I'll try to merge AROMA installer from tytung's ROM, but if you can help me in some way, it will be really appreciated, because there's no clean CM11 after all on our device. I'm going to upload the zip later to AFH and the edited device tree alongside with forked but unchanged kernel to my GitHub profile.
I'm pretty new to this topic, here's my thread
BloxmineXL said:
I still have most tools backed up to a USB drive.
If you ever need anything you miss, let me know
View attachment 5733029
Click to expand...
Click to collapse
I should've just posted my own zip of tools and roms here in the first place
So here you go

Categories

Resources