Related
Apologies to the mods if this belongs in the Raphael section.
I'm a software developer and I'm trying to find emulator images of the OS that ships with the HTC Touch Pro/Raphael in South Africa.
One of our clients is experiencing a problem running our software on his device. An error message pops up saying that our software was designed to run on a more recent compact framework than what he has installed. The target framework for our program is CF 3.5. I talked the customer through installing CF 3.5 on his device, but the error message persists. Following exactly the same steps, I experience no problems running our software on the emulator images in the following paragraph. This leads me to believe that there might be something odd in the particular build on the client's device.
He said that he hasn't done anything to his device with regards to upgrading or modifying his device apart from what I've talked him through. The specific build number of the OS on his device is 19965.1.2.3. I've downloaded the WM6.1 (build 19202.1.0.0) and 6.1.4 (build 20757.1.4.0) images from Microsoft, but I can't replicate the client's problem.
Where can I download images for build 19965.1.2.3? Do any of you have any other ideas of what might be causing this behavior?
Thank you very much.
*bump**bump*
This DOES belong either in the Raphael section or in the Q&A section.
I will move it to the Raphael section and if you wish, post it in the Q&A section as well.
GDILord said:
Apologies to the mods if this belongs in the Raphael section.
I'm a software developer and I'm trying to find emulator images of the OS that ships with the HTC Touch Pro/Raphael in South Africa.
One of our clients is experiencing a problem running our software on his device. An error message pops up saying that our software was designed to run on a more recent compact framework than what he has installed. The target framework for our program is CF 3.5. I talked the customer through installing CF 3.5 on his device, but the error message persists. Following exactly the same steps, I experience no problems running our software on the emulator images in the following paragraph. This leads me to believe that there might be something odd in the particular build on the client's device.
He said that he hasn't done anything to his device with regards to upgrading or modifying his device apart from what I've talked him through. The specific build number of the OS on his device is 19965.1.2.3. I've downloaded the WM6.1 (build 19202.1.0.0) and 6.1.4 (build 20757.1.4.0) images from Microsoft, but I can't replicate the client's problem.
Where can I download images for build 19965.1.2.3? Do any of you have any other ideas of what might be causing this behavior?
Thank you very much.
Click to expand...
Click to collapse
It might be worth getting them to install the .Net Configuration utility. That will tell them which versions of the Compact Framework are installed (to confirm that 3.5 is installed properly), and they can specify which applications use which version.
Cheers,
Steve
Thank you for moving this nir36. I would love to post it in the Q&A section too please. Should I do it, or will I get into trouble for posting the same request in multiple forums? If so, could you please do it for me?
Thanks for the upload Steve. I'll give it a try.
preface for the people not reading ... some quick answers:
- our page on this Hard-SPL is always here: http://rhodiumw.htc-unlocks.com/hard-spl.php
- license: you will just have to run the program on the PC with phone connected, normally you will not notice anything about the licensing, it is totally free for personal use!
- if you need help with license issues (when it says you already unlocked a device), you can send your message at: http://support.htc-unlocks.com
[SIZE=+2]Hard-SPL Release Time!!!! [/SIZE]
[SIZE=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/SIZE]
[SIZE=+2]NOW UPDATED -> if you already installed HardSPL, you will not need this update. but if you are going to HardSPL only now, it applies to you (package will lead you to update link anyway).[/SIZE]
Preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
Licensing information: it's like with previous Hard-SPL unlockers - every user gets one free use of the Hard-SPL, further use is subject to paying a small amount per device.
however, if you are a private user, you can have other uses free on request if needed, such as using it on a replacement device.
the license is valid forever and all this works as transparently as possible, so for normal users nothing is noticable; while businesses who need to unlock more devices than that, can use the link inside the program to send payment or contact cmonex or Olipro if you want to discuss bulk unlocking.
contact info is: via support link at our site
IMPORTANT: please do not use this contact info for asking help for problems unrelated to licensing unless you are a paying customer. other messages will not be answered - instead you can use this thread to post about your issues!!!
Preparations:
0) this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended.
Instructions: read this if unsure how to install Hard-SPL... if you are an experienced user then you'll probably not need to read most of this but if you are unsure or run into an issue, then you should read the following!
Steps:
1) download newest RhodiumW Hard-SPL package and extract this to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license.
4) run Rhodium-HardSPL.exe on your PC, make sure it's launched from a local drive (not through network drive, etc.). running it on XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, so allow it please.
important: if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it). if you encounter DEP errors, then add it to the exception list in DEP settings.
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below - any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
6) it will ask you to wait while it prepares for the flashing, press OK.
7) now it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the forums, but this should not ever occur (as this means a really fatal error occurred).
at this point the device did hopefully went to a black screen. this is the SSPL version, which is temporary. then RUU (Rom Update Utility) will instantly launch.
9) some notes: when RUU says it will perform a hard reset and cause data loss, do not worry, it is not going to do this. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
10) SPL flashes, device automatically reboots, job done.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.00.OliNex, which is the current Hard-SPL version.
More Notes:
NOTE 1: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, you need the following key combination: Power Button + Volume Down + Reset Button. means, do a soft reset while holding the "volume down" key and power key on the side of the device. hold these keys until you see a special tricolour screen which is the bootloader mode.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs (except of course some Radio roms). also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted on our site. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps in the next post about how to reflash stock SPL.
NOTE 3: anyone having USB connection problems with the device after it already entered SSPL mode, please copy SSPL-Manual-Rhodium.exe from SSPL-Manual-RhodiumW.zip (available on our site), copy it to the device and run it. then once the screen has gone black, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or a customRUU if you need to flash cooked ROMs.
NOTE 5: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. Windows 2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. also, the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS software.
Troubleshooting: and Step by Step on reflashing stock SPL: are in next post below!
Credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
[SIZE=+3]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you![/SIZE]
and now enjoy!
-continued from first post-
Manual SSPL download: (added soon)
Troubleshooting:
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
nothing happens on the device, does not enter black screen mode:
- anyone having problems with the device crashing instead of entering SSPL, make sure you've used Automatic flash mode before to put the device in SSPL (if you hard-reset your device, you have to repeat Automatic flash mode at least once).
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check, for example it can warn about model incompatibility).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems:
- if you get connection error in RUU after the device goes to black SSPL screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the black screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the USB connection is established in SSPL, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please make sure you are using the correct HardSPL package. currently this SSPL accepts only RHOD400, RHOD500 modelids i.e. the CDMA-GSM worldphone version, but if we get notified of another compatible RhodiumW version, we will instantly modify it to allow those models. check modelid by entering SPL tricolour screen manually and note what it says (RHOD400, RHOD500, or something else). note: RHOD1xx, 2xx, 3xx are not going to be compatible at all!
other issues:
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (black), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
how to reflash Stock/Shipped SPL: - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker by clicking here, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL made by us). the included one is the 0.63.0000 stock SPL. 3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 0.63.0000, not 1.00.OliNex.
About UPDATES:
-new release coming soon, fixes a specific problem for a small group of people-
-more troubleshooting tips soon-
Consider yourself... sticky
Thank you Olinex. Great WORK
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
buggs1a said:
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
Click to expand...
Click to collapse
In a nutshell, this basically will allow you to flash custom made roms and other assorted customizations.
Hey, thank you.
Does using this and then not putting a custom rom on it right away do anything bad? Like waiting for a 6.5.1 rom or something. Sorry if this isn't the right place. Forgive me please.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
You can wait as long as you want to flash another rom, custom or carrier. So no worries in holding off.
Thanks so much for answering.
Here's something.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
I just tried. I don't get it.
My mcafee doesn't have a trust app add feature that i can see so i turned off real time scanning to extract the file and then run it. Then the hard spl crashes when i try to run it. I hit auto flash and immediately it crashes.
What specific error message(s) are you getting?
Nothing specific. It just crashes and the windows app crash pops up. That's all that I can remember. Should I try again and look for something specific?
Also I would like to say that I connected the phone to my pc via usb cable and that's it. On phone opened the disk mode or active sync selection but I didn't touch anything in time then it disappeared. The phone showed up as a hard drive in explorer. I didn't do anything else when trying to run the hard-spl exe. Should I have?
Thanks a million.
You need to make sure you're connected to your computer and sync up with ActiveSync. Once that's all connected properly, then you can run hspl.
but how do i do that? i noticed just now i reconnected phone and active sync was selected on the phone, but nothing comes up on windows vista except the auto run and it says synch with media player or open to view files or do nothing.
Oh, Vista. Right. You'll need to use Windows Mobile Device Center then. Install that, reboot, then sync up with that (it's ActiveSync's replacment for Vista and Windows 7). Then you should be able to run hspl fine.
That you very much Oli, and to all the people who worked so hard on this! I just put it on my Verizon Touch Pro 2 and it went like a snap, but what software from you doesn't A nice donation is coming yer way me matey!
thanks. that did it.
i got to the part where it said make sure the battery has 50% or more. i said cancel and now my phone is off and won't come on. I disconnected usb and tried to turn it on and nothing happens. reconnected phone and tried to do this again and it told me i need to active synch again. but i can't turn on phone right now. I don't know what to do now.
Have you tried taking out the battery of the phone, reinserting it and turning it back on?
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
buggs1a said:
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
Click to expand...
Click to collapse
Glad you got it figured out. Have fun finding a good rom that suits you.
edit: since we don't really have much of a CDMA TP2 selection just yet, I'd recommend checking here. He makes a great ROM. Just be sure not to discuss ROMs in this thread.
I posted this at PPCGeeks also, but here is a problem I am having while trying to unlock in Windows 7 x64 using WMDC.
1. Ran the .exe
2. Screen pops up "Preparing to flash, press ok to wait. I press ok.
3. The screen goes black (like it's supposed to), Active Sync DISCONNECTS, and a box pops up: "Welcome to the ROM update utility...". I check the box "I understand the caution..." and click next.
4. The next box pops up "Follow the instructions..." and I check the box "I completed the steps..."
5. A box pops up: "Verifying the information on your PDA phone...please wait..."
6. About 30 seconds go by, and an error box pops up: Error [260]: Connection...
7. The screen remains black and the phone non-functional. I have to soft-reset the device at this point.
When I soft-reset in #7 above, the computer dink-donks like when you disconnect the UBS cable, so there's still some sort of connection the PC is recognizing. I tried a second time after installing the enablerapinew.cab (using auto mode) and got the exact same errors.
Any thoughts?
Computer Hardward: Windows Vista 32 Bit
Phone: HTC Hero-Sprint
Ultimate Goal: Putting Android 2.2 on my phone
I'm not a programmer or have any in-depth developing knowledge . However, I follow directions precisely. I feel like I've tried following several different directions on XDA and I start completely over each time trying a different one(uninstalling SDK and re-installing per particular directions) and they have all came to no avail.
The following link I will use as an example set of directions:
droidoholics.com/forum/viewtopic.php?f=20&t=187
BUT, when i get to this section in the directions:
" When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver"
I follow the directions and I've verified the folder and contents are there. I unfortunately ALWAYS get the following message:
"Windows was unable to install your ADB"
"Windows could not find driver software for your device"
I need help getting past this beginning step and feel like I've looked everywhere and followed all directions. Any help out there?? I'm drooling in anticipation of getting 2.2 for my device that the carrier will not be updating. This small step is stumping me severely.
Hey all- I been futzing around with BL, drivers, WMDC USB on/off, etc trying to get 6.5 on my Sprint Apache BL1.00. Gal on PPCG made me ROM that works fine, loads easy - bootloader, usb in, run!
See http://forum.ppcgeeks.com/htc-apach...tinkerbells-21916-apache-rom.html#post2058845
The user has been working on installing Windows Mobile 6.5 on their Sprint Apache device. After experimenting with various drivers and other configurations, the user was able to successfully load a ROM created by a member of the PPCG forum community. The link provided leads to the forum post where the ROM is available for download, along with instructions on how to install it.
it seems that the user has been trying to install Windows Mobile 6.5 on their Sprint Apache device. After some trial and error with different drivers and configurations, the user found success by using a custom ROM created by a member of the PPCG forum community. The link provided leads to the post where the user can download the ROM and get instructions on how to install it on their device.
Read carefully, this is about the installation of Windows 10 ARM32 on the Surface RT1. Previously tried the Elektrohax tutorial (video on youtube and also posted at Alexenferman.com) but I was unlucky on my attempts.
This is the mentioned tutorial:
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
I followed the instructions but failed twice. Now I know what was wrong. The tutorial IS FINE, it works. The thing is you have to first apply a patched version of Windows RT8.1 and run some scripts, that was fine, now the specifics:
Don't "RUN" the scripts, do not double click, this was the issue on my side. It doesn't matter if you run the script as "Administrator", I repeat, in my case this was the problem, DO NOT RUN or just double click.
INSTEAD, open a CMD window elevated to Administrator privileges. Move to the location of the scripts, this means get into the specific folder, only then run the script.
This means, if you placed the script on a folder named "whatever", right clicking with administrator rights and then execute does-NOT have the same effect as getting inside the folder as in "CD\whatever" and then "name-of-the-script".
I tried several times and I can confirm this is the thing that failed on my attempts.
- - - - - - - - - - - - -
Being that said, that website has all the instructions and links. Follow the tutorial carefully step by step. Keep the files on a safe place, who knows how long those will be kept on the web.
After my failed attempts I tried the chinese tutorial posted on Youtube by cong cheng on his channel. It worked, it even has some scripts working as installer, yes it works BUT after taking a deep look it's a method that applies a set of files made for some Nokia device, while it works, it is in chinese, has some broken things and it is SLOWER than Alexen Ferman method.
In short:
- Chinese - applies an already customized W10 version, way slower
- Alexen - it is an installer, you end up with a much better version
Good luck.
So what did you follow? The forums here seem to contain loads of broken links. Love to try W10 on my Surface since it's only collecting dust in my closet.
Thread edited and updated above and below.
Regarding Windows 10 on the Surface RT (CHINESE TUTORIAL)
I have no idea what's the risk on using a chinese modified pack. This one is different to the one at Alexen Ferman website, here I didn't need to apply all those patches (extras, after finishing the install), instead it worked out of the box. It's the same release as far as I know, but it's been customized.
My experience, what works:
o Edge works, better than IE11
o MyTube works (Youtube works amazingly well on this APP)
o System not as fast as W8.1
o I just clicked "Activate Windows" the usual way and it worked
o Cameras work out of the box (front and rear), no patches needed
o Can run ported apps (Paint.net, Halite, etc).
o YES, you gain access to some other apps on the STORE but hey, read below
X Office was in chinese (preinstalled) and slower, couldn't change it
X Removed it and installed the Office package provided by Alex Ferman
¬ After reinstalling, Office now is FASTER (tested and confirmed)
X No alternative browsers (just some but it's just IE with skin)
X Was kind of tricky to remove chinese (there are still some traces)
X Store doesn't fully work, just allows installing whatever is in my library (owned)
X VLC is way slower and ugly, worked way better on W8.1RT
- XX The Brightness control is kinda broken. You have to disable automatic changes and use only manual (via button), only there you can apply diff real levels of brightness to the screen, BUT, it won't work forever, after a while it will get stuck and you would have to reboot and set it right after going to the desktop.
- XX I'm still exploring this, I don't fully like it to be honest. The touch keyboard works, yes but in my case at times stops making sounds, and also stops working. Unplug and plug again fixes this but... meh.
It wasn't that great, I was actually considering going back to Windows 8.1 RT.
Now the final install I have (Alexen method):
Everything works, you just have to follow the tutorial and you will actually install W10, it's not an out of the box ready image, it is an installer. The only broken thing so far is the brightness control as explained above (it's an issue with the release so it won't go away), and the store didn't work for me, but there is an alternate method to install apps described at Alexen website.
Other than that EVERYTHING is better, it's fast, decent. I'm keeping my RT1 with Windows 10.
Read carefully, follow each step and don't give up. That's all I can say.
I did manage to get this working on my Surface 2 myself, was an interesting experience I don't really have any need for this thing anymore, but I have been pissed about buying a locked out piece of equipment for 8 years, so more just to principal of the thing! Thanks to Alex for all the work.
How do you install office from alexenferman? I tried running setup, but it says this app cant run on your pc. Also have you found a program to un pack .7z packages?
Has anyone written a guide on how to go back to windows rt 8.1?
Kolyei said:
Has anyone written a guide on how to go back to windows rt 8.1?
Click to expand...
Click to collapse
here you have
Alexenferman [OLD] - How to go back to Windows RT on the Surface RT
⚠ Warning:
old.alexenferman.com
does anyone knows if it is possible to put google chrome book on W RT?
Haven't visited the thread until today.
xnappo said:
I did manage to get this working on my Surface 2 myself, was an interesting experience I don't really have any need for this thing anymore, but I have been pissed about buying a locked out piece of equipment for 8 years, so more just to principal of the thing! Thanks to Alex for all the work.
Click to expand...
Click to collapse
Great that you got it working, now that you mention that you don't have any need for the Surface anymore, consider selling it to one of the member of the team working on modifications, unless you change your mind now that your surface works differently. In case you decide to move on, consider posting here on the Discord community
Join the Open RT Discord Server!
Check out the Open RT community on Discord - hang out with 5,903 other members and enjoy free voice and text chat.
discord.gg
mickeyx323 said:
How do you install office from alexenferman? I tried running setup, but it says this app cant run on your pc. Also have you found a program to un pack .7z packages?
Click to expand...
Click to collapse
I simply downloaded the package and ran the Office Installer on the Surface (now with Windows 10ARM), your comment makes me think perhaps, you don't actually have a Surface with Tegra processor, please check. .7z? search for 7zip, that's the program to extract the files from the compressed package .7z
Kolyei said:
Has anyone written a guide on how to go back to windows rt 8.1?
Click to expand...
Click to collapse
Yup, the link was posted by another forum member above.
bikrtoursportugal said:
does anyone knows if it is possible to put google chrome book on W RT?
Click to expand...
Click to collapse
Nope, impossible. They didn't create a binary (executable app) for the platform and the way it's built (the source code) seems unlikely for someone else to do it.
Anyone interested please check the Discord link posted on this message.
ricky4695 said:
here you have
Alexenferman [OLD] - How to go back to Windows RT on the Surface RT
⚠ Warning:
old.alexenferman.com
Click to expand...
Click to collapse
I just got around to reading this. Thank you so much! I'm back on windows rt 8.1. One problem: Secure Boot is still disabled. Is there a way to re-enable it?
Kolyei said:
I just got around to reading this. Thank you so much! I'm back on windows rt 8.1. One problem: Secure Boot is still disabled. Is there a way to re-enable it?
Click to expand...
Click to collapse
You should repart the drive using the official image downloaded from microsoft's site. If you want to come back to completely stock you have to re-install windows using the standard procedure, not the installation through wim file
im having an issue at the installing the wim using the dism. says system cant find the path specified. i verified the drive labels and all any ideas?
can some help me, after successful installed and load windows 10 on surface RT... when i want to run CMD as administrator. it gave an error "The Parameter is invalid".
Looking for some help, I got to the Win10 install stage and keep getting 0xc000000f blue screen error on Win10 boot. From the guide, it says I didn't choose to not copy system files when creating my recovery drive, but I didn't have any other options. I unchecked the only box available. Not sure what is wrong or how to fix. I can't reset, it asks me for my recovery drive, it doesn't accept the drive I created.
Edit: I ended up creating a new recovery drive from my Win10 PC, unchecked the box to copy system files, downloaded the Win RT recovery zip file from MS, copied the contents of that folder into the new recovery drive, copied the Win10 .wim from Alexen to the flash drive, and retried step 4 (I had already installed the hacked RT image and disabled secureboot, etc.). It is now booting, at least getting farther than it did before, after flashing the Win10 image.
Running into an issue right after the installing the patched image I get to the Region and Language select after the reboot and cannot select anything. After a bit the display just goes black. What can I do?