Related
Here we go!
3 Relevant partitions on the Zune HD:
ZBoot
NK
EXT
(there's actually a 4th partition, but it's a recovery partition for NK to facilitate fail-safe updating)
Enjoy
(a note: some files appear to be damaged, its my first time dumping a CE 7/Zune HD ROM )
(another note: thanks to nd4spd for getting the rom update to me, i don't have a zune hd )
wow I'll take a look.
Anything usable?
These executables are designed for CE 7 and more than likely will not work at all on CE 5 (although things coded for .NET might)
Really, you tell me, though, I haven't actually tried
Awesome! Subscribed...
Wait...so you're telling me it might be possible to create custom roms on the zune hd?!?! i need them to come out with a 128 gb model asap then...
WOW....they were trying to dump a zune rom for years.... so this means the protection on the zune HD is not nearly as strong as the regular zune...this is good news indeed...Mine is on backorder still =x
Another quick Q, did you dump that yourself or find it somewhere?
been trying to find this for a few weeks
looking forward to see what can be done!
are the keyboard files in a format that we can use on windows mobile phones?
votum said:
Another quick Q, did you dump that yourself or find it somewhere?
Click to expand...
Click to collapse
Actually, all I did was reset my Zune HD in recovery mode and plugged it in. When the Zune Software detected it, it downloaded the ROM from MS. When I was defragging my computer a few days earlier, I happened to find the folder where it saved all of the Firmware Updates. So I just looked in that folder and found the FirmwareUpdate.cab that had the .bin files in it.
after messing around with it, looks like nothing can really be recmoded to make dll files. it may need another way to rec mod than in the vk.
So does this mean that the Zune HD will be unlocked shortly?!
Blackwheel said:
So does this mean that the Zune HD will be unlocked shortly?!
Click to expand...
Click to collapse
and does this mean that we will have Zune GUI on winmo devices ?
benko286 said:
and does this mean that we will have Zune GUI on winmo devices ?
Click to expand...
Click to collapse
That could take some time, but once we are able to read the files, i will try to work on a keyboard
setix said:
That could take some time, but once we are able to read the files, i will try to work on a keyboard
Click to expand...
Click to collapse
How about unlocking the Zune HD? Or is that a completely different animal?
Somebody please sticky this thread immediately. This can only lead to great things!
Blackwheel said:
How about unlocking the Zune HD? Or is that a completely different animal?
Somebody please sticky this thread immediately. This can only lead to great things!
Click to expand...
Click to collapse
Err.. forgive my ignorance.. but is Zune HD locked?
In what way?
I think what he means by unlocking is to unlock for ROM modification and development.
ND4SPD said:
When I was defragging my computer a few days earlier, I happened to find the folder where it saved all of the Firmware Updates. So I just looked in that folder and found the FirmwareUpdate.cab that had the .bin files in it.
Click to expand...
Click to collapse
The ROM is saved in a .cab file to %HOMEPATH%\AppData\Local\Microsoft\Zune\Firmware Updates
7-Zip or another unzipping software can extract it out into the 4 .bin files, ext.bin, nk.bin, recovery.bin, and zboot.bin.
I have not yet succeeded to breaking it down into DLLs, it seems like there are multiple DLLs compiled into one .bin file.
Interestingly enough, some of the plaintext I saw in the recovery file was associated with camera/photography code (do a ctrl-f for "autofocus" or "lens" in the recovery.bin file in wordpad). However, I'm guessing it is the remnants of WinCE code, not for the Zune HD (or a successor?). It still begs the question of why it would be included in the recovery code though...
Hope that someone can use this for something...
hairchrm said:
The ROM is saved in a .cab file to %HOMEPATH%\AppData\Local\Microsoft\Zune\Firmware Updates
7-Zip or another unzipping software can extract it out into the 4 .bin files, ext.bin, nk.bin, recovery.bin, and zboot.bin.
I have not yet succeeded to breaking it down into DLLs, it seems like there are multiple DLLs compiled into one .bin file.
Interestingly enough, some of the plaintext I saw in the recovery file was associated with camera/photography code (do a ctrl-f for "autofocus" or "lens" in the recovery.bin file in wordpad). However, I'm guessing it is the remnants of WinCE code, not for the Zune HD (or a successor?). It still begs the question of why it would be included in the recovery code though...
Hope that someone can use this for something...
Click to expand...
Click to collapse
To break it down, you need to use cvrtbin.exe to convert it to the .nb0 format. Once you have that, as Da_G pointed out to me, you can use Xipport.exe's dump xip function to dump whichever converted file. Unfortunately, xipport has an error on the last file, so I'm going to try to fix that this evening.
You can also view the files in Da_G's first post
ND4SPD said:
To break it down, you need to use cvrtbin.exe to convert it to the .nb0 format. Once you have that, as Da_G pointed out to me, you can use Xipport.exe's dump xip function to dump whichever converted file. Unfortunately, xipport has an error on the last file, so I'm going to try to fix that this evening.
You can also view the files in Da_G's first post
Click to expand...
Click to collapse
Ahh... haha, I thought he linked to the raw .bin files and I figured that it would be easier to grab them from your own computer than download them. Whoooops!
I am curious, has anyone disected the Zune HD Hardware? I wonder what extra hardware got left behind that is not currently activated (and possilby not licensed). The core chipset can handle all of the common peripherals that you might find in a WM7 class phone chasis.
At the very least you should be able to see the sort of antenna and amps in there.
the Imageupdate system clearly works, so one approach to updating it (unlocking and or removing security) is to use the imageupdate system (on device or from your desktop, or possibly OTA). Although you would need to know a good bit about the NK and zloader for wm7. WM7 is a more streamlined, efficifient design, but - unfortunatey - there is a lot more in the kernel which makes updating individual bits more difficult without a full link.
It is a little bit more like the X360 design in this sense.
I believe that imageupdate is only known the to the end users as the engine for Windows Phone Update or -previously - FOTA (firmware over the air)
As Da_g mentioned, this is the first commercial device (to my knowledge) to use WCE7/WM7 (in general, WM is just a big OAK on WCE)
What certs are in the full CAB?
Windows Phone 7 has standardized the bootloader requirements for OEMs. No longer will an OEM be allowed to implement it's own design for ROM deployment (such as HTC with the .nbh/RUU system, .dz/LGMDP with LG, etc.)
The image format will be B000FF/.bin, which receives only minor changes from CE5, and so our current tools should work fine with this. The major change is in the way the bootloader handles image deployment. For Samsung and a handful of other manufacturers, this won't change too much, as they already utilize the B000FF system for deployment. The filesystem inside will be IMGFS - no longer will BinFS be used for NK/XIP section (now IMGFS will all partitions on device, NK and OS just being split by package rather than a seperate FS)
The physical flash layout will look as follows:
Reserved Regions, updateable only through a special oem-written driver to allow access to this area (size varies)
Partition Table (1KB)
BLDR (1MB)
DBSP (Device Boot State Partition, 256KB)
DPP (Device Provisioning Partition, 256KB)
USP (Update State Partition, 2MB)
ULDR1 (>=6MB)
ULDR2 (>=6MB)
NK (IMGFS, >=4.5MB) - At least 1MB free space for updates
OS (IMGFS, >=181MB) - At least 20% free space for updates
User Store (TexFAT)
Only the User Store (Which uses new Transaction-Safe ExFAT filesystem) will be user-writeable, all other areas will only be writable during an update operation. The Partition Table, DBSP, DPP, USP, and User Store are all not updateable during an update operation, only during a full-flash scenario. B00FF images are signed and checksummed, and passed through to the bootloader via ethernet over usb. The connection will most likely be encrypted, using the same flashing utility as Zune HD. (This is currently used to deploy images to the DevKits)
.ffu (Full Flash Update) file format (XML) will be used to pass information to the Zune software on which partitions are to be updated, etc. FFUs are signed just as .cabs are signed and only an .ffu which passes validation against the certificates on-device will be allowed to update a device.
Updates can also be done on a per-package basis, using the ImageUpdate process, which I have described in length @ the XDA WinMo Software Development forum. This process is largely unchanged from WinMo 6.x with the addition of a policy xml file containing security policy settings related to the .cab.pkg being deployed.
As such, I would recommend anyone interested in cracking the bootloader and creating a "HardSPL" take a good hard look at the Zune HD.
Similar to CE5/WinMo 6.x, There is a BLDR (Base Boot Loader) which makes the initial determination to boot up to the ULDR or to the WP7 OS. The OEM implements alternate boot parameters to trigger this and/or a button press combination. If ULDR is triggered, it checks the battery and power source to ensure that there is enough life remaining to successfully complete the flash, then awaits the flash download. There are redundant ULDR partitions (ULDR1/ULDR2) to facilitate failsafe recovery in the event of a failed ULDR flash (ULDR provides a basic level of functionality to enable a recovery flash even in the event of power failure during a flash)
MSFT is pushing it's Phone Update service much harder this time - it is intended to be used as the primary method for distributing phone updates. These can be deployed both over-the-air and through a USB connection with the Zune software.
subscribe to this......need to learn before my next device.
Thanks. I didn't see these threads before. Any chance you could share or point to the docs this info came from? It seems tweakers.net acquired it and I wouldn't mind looking through.
saved for future use! Da_G is the master of the roms!
As Usual Da_G you are cool..
Will you make this thread a Sticky for us? Thanks again G.
da_g said:
bump for visibility
Click to expand...
Click to collapse
bump! Bump! Bump!
Da_G you always rock, now we got a huge info.
thanks for your infos
that is some good news eventually have custom ROMs on wp7
thanks!!!!!
So you are saying that we will be able to cook for WM7, but wont be able to get a HSPL to flash it?
Well done Da_G.
Da_G said:
...
.ffu (Full Flash Update) file format (XML) will be used to pass information to the Zune software on which partitions are to be updated, etc. FFUs are signed just as .cabs are signed and only an .ffu which passes validation against the certificates on-device will be allowed to update a device.
Updates can also be done on a per-package basis, using the ImageUpdate process, which I have described in length @ the XDA WinMo Software Development forum. This process is largely unchanged from WinMo 6.x with the addition of a policy xml file containing security policy settings related to the .cab.pkg being deployed. As such, I would recommend anyone interested in cracking the bootloader and creating a "HardSPL" take a good hard look at the Zune HD...
Click to expand...
Click to collapse
Hi Da_G,
How can I get my hands on these files: not wp7 os but the other partition (dpp/bldr/uldr/imgfs/etc) contents? What IS known about wp7-fs? spl?
Do you have ANY dumps - even ZuneHD equiv? maybe the source of your .ffu info and an actual .ffu? Thanks there- pm me if you get the time. Yeah... I am noob here but interested in moving into rom-dev; used to do xbox-1+live and do have jtag, logic analyzers+trace, etc here. How would I begin? Once again: thanks and well done!
Edit/Update:
Perhaps with Cotulla's partition layout over 4 seperate nand areas it would be an option to modify this and his wp7 spl because the activation thing happened AFTER (live activation hack around etc) he had finished leo70 release and then..........
-whilst jtag/usb or eth/debug happening- (obviously you'd though of this b4- im just theorizing- let me know if way off)- to take a HTC HD2 (LEO70) that HAS BEEN ACTIVATED ON LIVE and see where/how/when/with/which partitions, filesys, regkeys, etc, have pvk for live or the ffu and then insert a test cert like ur own xbmod/chevron. or whatever is in sdk for 7 or ce. and then utilize this to diff and comp. I dont see why not. Then .ffu then self signature.
Now THAT'S cool! Thanks, Da_G!
This would mean, that we basically could get custom Rom's on WP7. Can't wait to see the first ones
Interesting info. Subscribing to it now....
Thanks or the info Da_G!!!
eh?
Did you look at the post dates before you all started subscribing? Almost a year now, doubt you'd see anything new ... but this and more 'subscribed' and a possible 'sod off' post.
Is this the only discussion on the topic? I'm sure im not the only one looking forward to having an unlocked bootloader. Any updates?
surrender420 said:
Is this the only discussion on the topic? I'm sure im not the only one looking forward to having an unlocked bootloader. Any updates?
Click to expand...
Click to collapse
See the first thread in this sub-forum.
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Anyone tried it yet? Looks like a risky process.
windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Thanks. Unfortunately, what I gather from what I'm reading is that that image does not contain drivers. You need to manually add the drivers to the image before you install. If you don't, you'll brick your tablet, according to WZT. People may want wait a little bit until there are clear directions and a few people who can verify that they worked (i.e. that they installed 8.1 without any problems).
Additional note: It sounds like the driver package is only for the Surface RT, so users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it. They'll have to wait until someone releases a driver package for their model (which WZT says might have to be taken from the Preview build).
Osprey00 said:
Even more unfortunately, while WZT has teased info about the driver package, they haven't actually leaked it yet.
Click to expand...
Click to collapse
This part isn't actually true, for what it's worth- it's included with the main download.
jhoff80 said:
This part isn't actually true, for what it's worth- it's included with the main download.
Click to expand...
Click to collapse
Oh, OK. I didn't catch that. They made it appear as though it was a separate download. Ah, you're right: there they are.
just run setup.exe
all drivers for surface are build in
BTW:I have rollback to 8.0 again
Osprey00 said:
...users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it.
Click to expand...
Click to collapse
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Unfortunatley I'm on a business trip and can't create an upgrade instruction for VivoTab users. But there is nothing difficult - as we already have all needed drivers on a recovery partition, and all you need - just insert them into WIM using the Wzor's instructions from his original post on ru-board.
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
mamaich said:
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Click to expand...
Click to collapse
I figured as much, but not everyone may have the recovery image or the knowledge, and, for them, a dead device that they're unable to recover is as good as a brick. Regardless, I just wanted to pass along the same language that WZT used so that I'm not guilty of misrepresenting the risks or responsible if someone can't fix what he got himself into.
derausgewanderte said:
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
Click to expand...
Click to collapse
Thanks for your instructions and verifying that it works. The original instructions don't mention writing down your current key first. While I likely would've done that anyways, it's re-assuring to see it in writing, just in case. I might give this a go tomorrow.
FYI, there's now an ISO with the Surface RT drivers baked in, so that users don't have to use DISM to add them manually. The release name is:
DRIVERS FOR SURFACE RT ONLY___MICROSOFT WINDOWS RT 8 1 WITH OFFICE 2013 RT RTM WOA ENGLISH DVD-WZT
Note that it's only for the Surface RT, not other RT tablets.
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Osprey00 said:
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Click to expand...
Click to collapse
and here is the direct link to Osprey00's post with a way of getting the key if you only have your RT.
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
huslterose said:
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
Click to expand...
Click to collapse
[EDIT: Never mind. I misunderstood.]
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Osprey00 said:
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Click to expand...
Click to collapse
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
SixSixSevenSeven said:
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
Click to expand...
Click to collapse
Ah! Gotcha. It slipped my mind that the jailbreak for unsigned apps not working in 8.1 is a valid reason for not upgrading, so I was thinking that he was waiting for something to make the upgrade, itself, even easier. Thanks for the clarification.
@Osprey00 - is there a direct link perhaps
aooga said:
Could someone please post instructions on how to decrypt the registry values? The link that was posted is down. Thanks.
Click to expand...
Click to collapse
Sure. There are a few different ways to do it. In order of simplest to most complicated...
METHOD 1 - Can be done solely from Windows RT (any version):
1. Follow these instructions to create a batch file.
2. Run the batch file on the tablet to get your key.
3. Either write the key down or right-click anywhere in the window, select Mark, highlight the key, right-click again (which will copy the key to the clipboard), paste the key into a text file and then copy that text file to another computer or backup drive.
4. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
METHOD 2 - Requires regular, non-RT Windows (XP/Vista/7/8):
1. In RT, open the charms bar, click Search, enter "Regedit" and run Regedit.
2. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
3. Copy that .reg file to your non-RT Windows.
4. On your non-RT Windows (all remaining steps will be done there), right-click the .reg file and choose Edit. Change "CurrentVersion" to "CurrentVersionRT". Re-save the file.
5. Double-click on the .reg file and import it.
6. Download and install WinTK.
7. Run WinTK, paste "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersionRT" (without quotes) into the field and press the Decrypt button.
*If, for some reason, WinTK won't run, you can try this: download and unzip Produkey, run Regedit, export your CurrentVersion key to a backup .reg file, change the key name in your RT .reg file from "CurrentVersionRT" back to "CurrentVersion", remove all values in your RT .reg file except for DigitalProductId and DigitalProductId4 (make sure that they're NOT the ones under the DefaultProductKey sub-branch), import that (thus overwriting your Windows key with your Windows RT key), run Produkey, write down the Product Key, then import the backup .reg file to restore your Windows key (important, obviously).
8. Write down the product key.
9. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
10. Optional: Open Regedit again and delete the CurrentVersionRT key, just to clean up.
METHOD 3 - Can be done solely from Windows RT, but only on 8.0 (won't work on 8.1 Preview or 8.1 RTM) and is more complicated than Method 1:
1. Download and unzip the RT jailbreak tool.
2. Run RunExploit.bat. Choose 'R' from the menu. Let it finish, then press any key when it asks you to.
3. Download and install Win86emu.
4. Download and unzip Produkey.
5. Open the charms bar, click Search, enter "Regedit" and run Regedit.
6. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
7. Find the Win86emu tile (icon is "x86") on your Start screen, flick down on it to bring up the options bar and tap Open File Location... or, at the Desktop, you can browse to C:\ProgramData\Microsoft\Windows\StartMenu\Programs\win86emu.
8. Double-tap the "x86 Registry Editor" shortcut.
9. In that registry editor, import the .reg file that you exported in step 4. This will import the settings into the special x86 registry that the emulator created when you installed it and which all x86 programs (including Produkey) will think is the real registry.
10. Double-tap the "Run x86 Program" shortcut.
11. Browse to and select the produkey.exe that you unzipped in step 2.
12. Find the Product Key listed for Windows in the window that appears and write it down. If nothing appears, click on Select Source and verify that it's searching the local computer (top-most radio button).
13. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
If one method doesn't seem to work for you, try one of the others.
Osprey00 said:
Sure. There are a few different ways to do it. I'll describe two...
...
Hopefully, I didn't forget any steps from either of those methods.
Click to expand...
Click to collapse
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
aooga said:
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
Click to expand...
Click to collapse
thanks for the info. was about to search for reasons. hacked by MS?
derausgewanderte said:
thanks for the info. was about to search for reasons. hacked by MS?
Click to expand...
Click to collapse
Yeah I was clueless why it wasn't working, so I just looked at their facebook page.
Would putting a link like this on XDA be considered warez? If not, can someone who has already downloaded the ISO with drivers upload it somewhere? There is no way I'm waiting till Oct. 16
Hello, I wonder if there is any way to run .exe on devices with Windows 10 Mobile.
If so, could you help with a tutorial? Thanks for the attention.
LuizWay said:
Hello, I wonder if there is any way to run .exe on devices with Windows 10 Mobile.
If so, could you help with a tutorial? Thanks for the attention.
Click to expand...
Click to collapse
exe is the native format of Windows and Windows Phone but it doesn't mean you can copy exe file from your pc and run it.
PC exe files are based on X86 and X64 but Mobile exe files are ARM and they are completely different
Windows CE .exes can be runned?
ARM compiled EXEs can run using my CMD in SSH solution (that @gus33000 automated in Interop Tools). Aside from that, you CAN run a .NET 4/4.5 Console app if it's named specific names (which I explain here: http://forum.xda-developers.com/showthread.php?t=3185766).
snickler said:
ARM compiled EXEs can run using my CMD in SSH solution (that @gus33000 automated in Interop Tools). Aside from that, you CAN run a .NET 4/4.5 Console app if it's named specific names (which I explain here: http://forum.xda-developers.com/showthread.php?t=3185766).
Click to expand...
Click to collapse
Weird... I made a custom C++ console app and it worked fine in console.
lukjok said:
Weird... I made a custom C++ console app and it worked fine in console.
Click to expand...
Click to collapse
Yes, it's supposed to. As long as it was compiled for ARM, it will run.
so...who can made arm exe files?
augustinionut said:
so...who can made arm exe files?
Click to expand...
Click to collapse
Anyone with VS installed and experience But arm-porting requires some additional skills - not all API's/functions are available on the arm platform.
I tried to build Far Manager for arm but still need to take care of about 54 issue (replace missing x86/64 functionality).
:silly: I.m still dreaming about mortscript.... imagine something like tasker on android
Do it. This was the exact reason I made sure to make a tutorial on how to get CMD running over SSH when I noticed it was possible. If you have the talent to, get your programming on.. Make apps and solutions that are useful for us. Let's get W10M on a better level and show everyone what we can do
@augustinionut, you don't need mortscript on windows, it has (suppose to but I haven't checked IoT system32 for it) own tools and services.
@snickler, have you experimented with the services like task scheduler etc.?
snickler said:
Do it. This was the exact reason I made sure to make a tutorial on how to get CMD running over SSH when I noticed it was possible. If you have the talent to, get your programming on.. Make apps and solutions that are useful for us. Let's get W10M on a better level and show everyone what we can do
Click to expand...
Click to collapse
Im a noob, i better do reverse engineering, i dont even have sufficient data do download visual studio
How high are the chances to get Office 2013 (from Windows RT) running on it?
Insignificant said:
How high are the chances to get Office 2013 (from Windows RT) running on it?
Click to expand...
Click to collapse
I think, zero.
I was able to dump the RDC that is provisioned to my 640 XL prototype. I dumped it and renamed it with a .bin extension. Have a couple of questions for those that know more about as I currently know little.
1. What is the RDC file, meaning what does it consist of? Or how is it used?
2. Where is it written when writing it from thor2? Or where is it stored on the phone?
3. Can it be re-used or is it good only for the one device it is provisioned to?
So, I am not sure if "dump" is the correct term to use here, as the command from thor2 would include the option -readrdc which sends it to a file that you choose...So it is reading something from the phone and generating a file...
I opened the file in hex editor but see little about its contents. It is small in size, about 804 bytes. I tried to write it to a different device same model but it failed with a specific error "Certificate error 25 (0x19) (0)"
Thanks.
Where to get prototypes phone?
nate0 said:
I was able to dump the RDC that is provisioned to my 640 XL prototype. I dumped it and renamed it with a .bin extension. Have a couple of questions for those that know more about as I currently know little.
1. What is the RDC file, meaning what does it consist of? Or how is it used?
2. Where is it written when writing it from thor2? Or where is it stored on the phone?
3. Can it be re-used or is it good only for the one device it is provisioned to?
So, I am not sure if "dump" is the correct term to use here, as the command from thor2 would include the option -readrdc which sends it to a file that you choose...So it is reading something from the phone and generating a file...
I opened the file in hex editor but see little about its contents. It is small in size, about 804 bytes. I tried to write it to a different device same model but it failed with a specific error "Certificate error 25 (0x19) (0)"
Thanks.
Click to expand...
Click to collapse
A RDC file is a research and development certificate tied to the device hardware it came with, it will only work on the device it was shipped with, having the same IMEI, hardware serial number and everything unique, you can't use them with other devices at all.
@gus33000
I was almost certain it was unique to the device it was installed in. Does it reside on the boot partition? Thanks for sharing.
nate0 said:
@gus33000
I was almost certain it was unique to the device it was installed in. Does it reside on the boot partition? Thanks for sharing.
Click to expand...
Click to collapse
It's in DPP along with all other provisioned data specific to the phone, you won't be able to do anything with it, just abort, you'll loose time and you'll most likely brick devices.
Was only wanting to know more about it. Thanks again.
nate0 said:
Was only wanting to know more about it. Thanks again.
Click to expand...
Click to collapse
Also as a tip, never overwrite MODEM*, SSD, and DPP with the ones from another phone, it will be destructive for prototypes. I advise you make a full backup of the prototype emmc first, before doing anything, (even if it's just reflashing with a ffu, it's very important to back everything up in mass storage using something like Win32 disk imager), if you however for some reason ever end up with wrong MODEM*, DPP and/or SSD, boot to flash app, switch to download mode, send the emergency payloads for that device RM, and write the rdc, writing it without DLOAD won't work.
DPP is the one nice to work with but never copy and replace, delete and eventually copy over onto it
I need this file
Can you help
Kidsnet said:
I need this file
Click to expand...
Click to collapse
I sold this phone along with dozens of other Lumias and Windows Phones over 2 years ago. I do not own the phone anymore, and I unlikely will find that RDC file if I even backed it up. It would be almost to you unless you are the new owner of this exact device that I dumped it from. Are you planning to use the file for any other reason?
I got a refurbished mobile came locked so i have to fl it since its demanding protection key so i need help
nate0 said:
I sold this phone along with dozens of other Lumias and Windows Phones over 2 years ago. I do not own the phone anymore, and I unlikely will find that RDC file if I even backed it up. It would be almost to you unless you are the new owner of this exact device that I dumped it from. Are you planning to use the file for any other reason
Click to expand...
Click to collapse
Kidsnet said:
I got a refurbished mobile came locked so i have to fl it since its demanding protection key so i need help
Click to expand...
Click to collapse
They are coming already locked, or if there's any tool i can download so that it will vo well with m
Sounds like the lock you are seeing is like a safety net lock. Someone must have had windows on it but had logged in with their account in Windows 10 mobile and set up the Reset protection with their Microsoft account. There is a method to remove that but it is quite dangerous and could ruin the phone.
There is a way to by pass it though as a work around so that you can use the phone but every time you hard reset it it will always lock back.
nate0 said:
Sounds like the lock you are seeing is like a safety net lock. Someone must have had windows on it but had logged in with their account in Windows 10 mobile and set up the Reset protection with their Microsoft account. There is a method to remove that but it is quite dangerous and could ruin the phone.
There is a way to by pass it though as a work around so that you can use the phone but every time you hard reset it it will always lock back.
Click to expand...
Click to collapse
@Kidsnet this is especially a problem for a lumia 640/640 xl. Because what happens is that if they upgraded it to Windows 10 mobile and enabled the protection but you reflash it back to Windows phone 8 you will unlikely set yourself up to not even get a workaround to get in the phone. Since the provisioning of W10M and WP8 are completely different.