woaproject.net

Use Compact Deployment: will enable NTFS compression for a smaller deploy size. Clean Downloaded folder before deployment: Deletes cached driver and other files and redownloads them. Space allocation: Dropdown allows you to keep W10M or remove it. If you want to keep it, the slider shows how much sp...

Not quite the right subboard but lemme see if I can answer these:

I have not (yet) tried either of the opera dev builds. I do want to try running GX because of the performance sliders.

AdeltaX and woaproject are two completely different projects. They aren't even remotely related.

Should be fixed with the 2.5.1 release!

1. not quite the right section

2. All XLs are probably the best-compatible units for this project short of EB1 RX-130 development units.

This is both the wrong forum and wrong sub board for this thread.

Also, unless you do some weird partition hiding shenanigans, far as I know you can't dual boot two installations of Windows Mobile. [s]I have been horribly wrong before, though.[/s]

Please tell me you didn't install WoA to an SD card. I know that's nigh impossible with WoA Deployer, but just making sure.

I have successful Miracast connections on my phone (XL). If it fails, try to reconnect. If that's not working and you really need to blow up your phone (the display that is, don't actually make your phone explode) then Remote Desktop is a possibility.

Additionally, the folder names it generates are absurdly long, so try placing the working files into a directory closer to the root, such as C:\WoA lest you run into absolute file path limits.

iHeartRadio

I would definitely not recommend WoAoL as a daily driver ever-- it's really relegated to tinker status. If you want an Windows on ARM device to use as your daily, get a proper device.

Dual Boot is, far as I remember, in Advanced on WoA Deployer.

You'll have better luck by putting the scripts higher up in the directory tree, such as a folder on a drive root.

There is an absolute path limit as well.

vorobejsawka wrote: ↑

Thu Feb 07, 2019 6:24 pm

FFU flashing does not restore the partition EFIUEFI ?

It's not required for Windows 10 Mobile to function, if I remember correctly.

Currently, the only way is to reflash the stock FFU, or restore from a backup if you did so from WPInternals.

morethan24hourshaspassedsoimfreetodoublepost 3/2 [/s] - Copied this PowerShell script to a .ps1 and made a shortcut to it from the start menu. It takes about 15 seconds each run but it rotates the screen effectively until gyroscope/accelerometer support is implemented. - Made a small batch script th...

1/2 https://b.catgirlsare.sexy/3DAP.png https://b.catgirlsare.sexy/p8S9.png Interestingly, WSL runs in native arm64 rather than in x86 emulation. But I guess that would make sense since there are such packages available. Next: installing xfce on wsl on woa on lumia ----------------------------------...

Why does the error message even need to be in base64.... Here's the decoded result: Version: WkdNUFBgZWpYKSZdNSk4JjlUJioGAVc9Izg4Lm16eXx1MSIhPSIjSTk1TVd7cmB9YDlJe21yckEz ImageBase: 00400000 Eip: 9450009 Eax: 9450000 Ecx: 9B02331C Edx: 0 Ebx: 9350530 Esi: 9AC5143 Edi: 9B05DF52 Ebp: 19FE10 Esp: 19FDC...

Alternately, with Dual Boot enabled (I think it works disabled too but--):

1. Turn on the phone normally.
2. On the boot menu, select Developer Menu
* With dual boot disabled, the menu is still there, but you can't see it. Press volume down once, then press camera once.

Could you paste this as text? The error is very cut off in the screenshot.

Not currently. Charging is a separate thing from USB data.

I'm surprised that I'm both the first 'Merica post and of the amount of worldwide representation on this project.

There won't be another Windows Phone, not in the traditional sense. Ultramobile PCs that just so happen to have telephony support isn't out of the question, but it's highly doubtful or even torrential considering Android and iOS are working from the opposite side (they are trying to make their OSes ...

Yes, you should have updated W10M before even installing WoA. No, you cannot update W10M without removing WoA, the UEFI, and (optionally, but recommended) re-lock the bootloader; lest the install gets erased or worse (it could become a brick! but only a soft brick; you'll have to reflash the stock f...

I've run into this issue a couple of times. Skipping the faulty OOBE screen usually does no harm, and if it does go back to it retrying a few times will take care of it.

Also if you already have gone through OOBE once with one account, just kill OOBE from it and you get a desktop.

I've only had Windows Phones my entire life, and when the inevitable switch happens it'll be super jarring.

I still have my original 900. I hope to resurrect it at some point whenever I can get a hold of one of those jtag boxes.