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?
Related
Alright, since my google search returned the whole 2 (two!) relevant results, and the search here around 10 irrelevant, I thought I'd drop this on the community, in hope for some help.
I've upgraded my 64bit OpenSuSE to 11.2 the other day, downloaded the Android SDK, set up the environment variables, and fired up the "android" script that is supposed to download and install a platform, so I could access my device through adb shell.
Here I ran into a problem: Half of the buttons I click in the SDK updater don't seem to work, it will not save the settings, it will not remember the URL I type in (had to use http), and when it reads the http repo, it will not download and install what I have cheked! What happens is, I click the button, it appears to stick down for a while, then pops back up as if I never clicked it, and nothing happens.
My first question is, has anybody tried this on SuSE 11.2? I have had no problems on 11.1, for instance.
Second, does this need any "special" Java configuration to work properly? I have tried both the openJava (now built-in into SuSE), and Sun Java latest (SDK and JRE). I don't think so, but asking just in case...
I'm pretty much stuck. If anyone has this working, or better yet, if anyone knows where I could download platforms outside of the updater, please be so kind and share. Thank you!
P.S. Oh, and the optional third question: Is there a way to trigger the download from console? That would probably help to figure out what goes wrong...
EDIT: Not Java problem, but updater problem. It does not show any of the SDKs, it shows only APIs, which can only be added if a valid SDK exists.
Can anyone confirm this?
It seems I need an external link to SDK 1.6 for Linux (for example). Can't anyone share?
Thanks!
Still stuck...
EDIT2: Solved it, my adb works again. But the updater app is crap I installed the APIs, then shut it down, rebooted, then ran it again. Also, for some reason the buttons wouldn't respond to clicks, but if I click and then push Enter key, it works. Took me a while to figure this one out.
Hey, I'm getting ready to install Android SKD on openSUSE 11.2 from scratch. Could you list your steps and/or suggestions based on how you got it working? Thanks.
How did it go?? Sry, just saw this...
Don't have time to do the steps.. actually, everything works just as the standard procedure suggests, with the exception of button clicks - as I said, each time I clicked a button, I had to press the Enter key (as if the click was just giving it focus, but not the actual command)
Feel free to PM me (or any other user), especially if the thread is a bit old, like this one.
MountainX said:
Hey, I'm getting ready to install Android SKD on openSUSE 11.2 from scratch. Could you list your steps and/or suggestions based on how you got it working? Thanks.
Click to expand...
Click to collapse
Okay, so some of us were in this boat. You have to reinstall Windows on your nice little Surface Pro tablet. But sadly you don't have a recovery partition or a flash drive! So what are you supposed to do?
Well, first you ask Microsoft support. That does not go well: they tell you to send them your Surface. But that's not really a good option - to lose your tablet for two weeks over a software problem? That's just not fair!
So, next, you try googling for help. But all you ever find are similar unanswered pleas for help, which usually end up being either unanswered or closed by moderators.
But fear not, as you CAN solve this, and you don't even need to do crazy things like making your own recovery image, or downloading one from weird Chinese sites.
----
HOW TO REINSTALL WINDOWS 8.1 ON YOUR SURFACE PRO WITHOUT A RECOVERY PARTITION/USB
Step 1.
Obtain a Windows 8.1 ISO. I can't tell you where to obtain one, but it is not a hard task.
The flavor Surface Pro uses is Windows 8.1 Pro x64. I used the EN-US version, as I have an American Surface, so I can't verify how other languages will work.
Step 2.
Burn that ISO to a USB drive. I suggest using Rufus for that: http://rufus.akeo.ie/
Step 3.
Boot your Surface from the USB drive.
To do that, hold the volume down button when turning on your Surface
Step 4.
Install Windows 8.1.
Step 4.5.
It will ask you for an install key, and might not accept your real Surface key. The reason for that is that the installer for Windows 8.1 does not accept Windows 8.0 keys (and your Surface might have one of those).
To proceed with installation, you will need this install key:
XHQ8N-C3MCJ-RQXB6-WCHYG-C9WKB
Click to expand...
Click to collapse
This key is for installation only. IT DOES NOT ACTIVATE WINDOWS.
Step 5.
After installing the OS, you'll notice that it's not behaving quite right, for example, there are 4 rows of tiles on the start screen instead of three.
Go to Windows Update, and install everything.
Step 5.5.
If you installed with the install key, use this utility to get the original Windows key: http://forums.mydigitallife.info/threads/30363-Windows-8-Product-Key-Viewer
Choose the "MSDM" option, copy that key, and activate Windows with it.
Step 6.
Enjoy your happily recovered Surface.
----
So there. That was a little guide on how to recover a Surface Pro without a recovery drive. I was in this situation myself recently, and Microsoft offered me to send my Surface to them - which would've cost me $200, as I live in a different country from the one my Surface came from, and also would've meant living without my tablet for a month or even longer. So I just fixed it all myself.
A lot of people seem to be posting in that other recovery thread, so I'm just gonna make this visible again.
Only one question, do I need a keyboard or mouse for that?
Cause I've got only wireless mouse and original type cover, which does not work for some reason, and that's why I want reinstall windows.
I think it should pop up the on-screen keyboard if you use touch.
Anyone else did this process and got the Surface Pro 2 back to "out of the box" state?
touch screen
has anyone of you got the issue with the touch controller? and after the windows reinstall did it come back?
regards
Worked perfect
Worked perfect on a MS Surface Pro 1, with windows 8.1 Pro install USB, no keyboard or mouse needed.
Thank you! :good:
Thanks a heap for this guide, thought my Surface was done for.
For those unable to boot normally into Windows, holding VolKeyDown + Power while the unit is off will force the unit to boot from removable storage (doesn't have to be a USB Stick, you can plug in any kind of bootable media, including a USB DVD-ROM).
Have fun!
Can this works for Surface Pro 2
westjgames said:
Thanks a heap for this guide, thought my Surface was done for.
For those unable to boot normally into Windows, holding VolKeyDown + Power while the unit is off will force the unit to boot from removable storage (doesn't have to be a USB Stick, you can plug in any kind of bootable media, including a USB DVD-ROM).
Have fun!
Click to expand...
Click to collapse
Hi,
Can this method work for surface pro 2?
syahchrono said:
Hi,
Can this method work for surface pro 2?
Click to expand...
Click to collapse
I'm gonna try this now on my Surface Pro 2 because I got one with only scandinavian languages and I'm from Germany ^^ Will report back!
# UPDATE #
Worked perfectly fine
question
I just installed the latest Firmware / Drivers MS has pushed through Windows Update,
and i would like to refresh my Surface Pro 2 to get a clean install.
- First thing i did was create a bootable usb drive using Microsofts new 'Create Installation Media Tool'
. I selected 'Windows 8.1 Pro x64' in my native language which is Dutch.
The tool created a bootable USB stick, which i haven't tried yet.. before i continue i have some questions;
....
1. I copied my recovery image to a USB stick and deleted the recovery partition.
- If i reinstall Windows can i still use the recovery usb in case something goes wrong during the installation, or is it linked to your current installation?
2. Would Windows automatically recognize the serial number, which i believe is stored in the BIOS / UEFI, and activate Windows? I've written down the serial using the tool mentioned in the OP to be on the safe side.
3. Like i mentioned before, i installed the lastest driver / firmware package, will Windows automatically install the latest drivers after installation or first install more basic drivers to get WiFi up and running and then install the latest drivers?
4. When you install new driver / firmware software will Windows automatically update the then older drivers in the recovery image?
I've read the previous posts saying that everything went smoothly, but i just want to make sure i'm not forgetting anything..
i have a Surface Pro 2 btw!
koffiemelk said:
I just installed the latest Firmware / Drivers MS has pushed through Windows Update,
and i would like to refresh my Surface Pro 2 to get a clean install.
- First thing i did was create a bootable usb drive using Microsofts new 'Create Installation Media Tool'
. I selected 'Windows 8.1 Pro x64' in my native language which is Dutch.
The tool created a bootable USB stick, which i haven't tried yet.. before i continue i have some questions;
....
1. I copied my recovery image to a USB stick and deleted the recovery partition.
- If i reinstall Windows can i still use the recovery usb in case something goes wrong during the installation, or is it linked to your current installation?
2. Would Windows automatically recognize the serial number, which i believe is stored in the BIOS / UEFI, and activate Windows? I've written down the serial using the tool mentioned in the OP to be on the safe side.
3. Like i mentioned before, i installed the lastest driver / firmware package, will Windows automatically install the latest drivers after installation or first install more basic drivers to get WiFi up and running and then install the latest drivers?
4. When you install new driver / firmware software will Windows automatically update the then older drivers in the recovery image?
I've read the previous posts saying that everything went smoothly, but i just want to make sure i'm not forgetting anything..
i have a Surface Pro 2 btw!
Click to expand...
Click to collapse
1:I have no idea
2: Yes it will, I have a surface pro 1 and it was activated automatically, so i didnt had to do anything with my serial. (on a new windows 8.1 install)
3: Yes it will, but you can always install them manually (doesn't really matter unless there are issues with drivers).
4: Dont know (dont think so). (I havent ever uses a recovery installation ever, i always install everything manually back on .
Hi together,
I did the steps and everything went fine. But I had to disable secure boot at first.
Now, after the isntallation of Windows 8.1, I activated it again and reinstalled the default keys. Is this the way it is meant?
Or do I need to leave it disabled?
Thank you very much!
Best regards,
thrain2
So I have a question.
I removed my recovery partition to regain the space.
Does your method reformat the drive and repartition everything? Will it reinstall the recovery partition?
I remember all former windows os installations I've done allowed me to format the drive and clear the partitions and then either create new ones myself or use the blank disk. Win7 would (on a blank disk) create it's recovery partition.
So I went ahead and did it.
To anyone looking to do this, use the official media creation tool. It's free from Microsoft and extremely simple.
I didn't have to disable secure boot or anything, just hold down the volume and power button with the USB plugged in.
The installer let me delete all my existing partitions and it automatically created only the ones needed.
It never asked for a key and was activated correctly when I booted into widows.
I found the installer created 3 total partitions on it's own.
1st a 300mb empty partition which I believe is supposed to be for windows RE and required by bit locker.
2nd a 100mb partition containing an EFI folder.
Note: these two aren't supposed to be accessible, I did special mounting to check them out.
3rd the rest of my disk space was created for my system partition
I'm mostly happy with this.
The only issue I've had so far is I can't turn bit locker on, even though there is a 300mb partition, it's empty and bit locker complains about the widows recovery environment not being on the system dive.
iXNyNe said:
So I went ahead and did it.
To anyone looking to do this, use the official media creation tool. It's free from Microsoft and extremely simple.
I didn't have to disable secure boot or anything, just hold down the volume and power button with the USB plugged in.
The installer let me delete all my existing partitions and it automatically created only the ones needed.
It never asked for a key and was activated correctly when I booted into widows.
I found the installer created 3 total partitions on it's own.
1st a 300mb empty partition which I believe is supposed to be for windows RE and required by bit locker.
2nd a 100mb partition containing an EFI folder.
Note: these two aren't supposed to be accessible, I did special mounting to check them out.
3rd the rest of my disk space was created for my system partition
I'm mostly happy with this.
The only issue I've had so far is I can't turn bit locker on, even though there is a 300mb partition, it's empty and bit locker complains about the widows recovery environment not being on the system dive.
Click to expand...
Click to collapse
Thanks for sharing this.good
Anyone tested this yet with a surface 3 or surface 3 pro?
Tried this with my Surface 3, which is stuck currently on Win10 10074, and the install key didn't work.
It works
I used the freeware ISO2Disc to burn a Windows 10 ISO file to my USB drive and I can then reinstall successfully. Remember to choose GPT partition style as Surface Pro can boot in UEFI mode only.
iXNyNe said:
The only issue I've had so far is I can't turn bit locker on, even though there is a 300mb partition, it's empty and bit locker complains about the widows recovery environment not being on the system dive.
Click to expand...
Click to collapse
I did basically the same, reinstall a clean Windows on my Surface pro 3, but can not turn on bit locker, too. Have you figured out, how to solve this issue?
hello,
could it be possible, that someone ports the lenovo writeit software to the surface pro 3 ?
http://www.windowscentral.com/lenovos-unannounced-handwriting-tool-windows
it is new and currently blocks the installation/use of the software at other tablets except some lenovo modells.
WRITEit for non-Lenovo Devices
todarkness said:
hello,
could it be possible, that someone ports the lenovo writeit software to the surface pro 3 ?
http://www.windowscentral.com/lenovos-unannounced-handwriting-tool-windows
it is new and currently blocks the installation/use of the software at other tablets except some lenovo modells.
Click to expand...
Click to collapse
Here you go. Working on my Dell Venue 8 Pro
garybeaman said:
Here you go. Working on my Dell Venue 8 Pro
Click to expand...
Click to collapse
great! thanks.
it isn't really working well so far on surface 3, guess that is screen resolution related. the green box appears too far up in the screen, and box is too narrow to write in.
any idea how to change the config settings xml files to correspond to the surface screen resolution ?
leo
Works Great on Surface Pro 2
Has anyone considered privacy concerns regarding password input?
stormnl said:
great! thanks.
it isn't really working well so far on surface 3, guess that is screen resolution related. the green box appears too far up in the screen, and box is too narrow to write in.
any idea how to change the config settings xml files to correspond to the surface screen resolution ?
leo
Click to expand...
Click to collapse
Works great on my Surface Pro 2
Making the latest beta work on Surface or other tablets
I followed the following steps.
1. First you need to get the beta file from lenovo's site
2. Then, extract the msi file from the setup file.
To extract the msi file I opened command prompt, navigated to the folder where the setup exe is stored and ran this:
Code:
WRITEit-Setup.exe /A
This will prompt you to select a folder where all the contents will be extracted. You will find the msi file in that folder.
3. Then follow the instructions (use google translate for english) in the article by tabletpccorner to remove the Lenovo check from the msi file. (Steps 1 & 2 in the article are already covered above)
I can't paste the article link as I don't have enough rep, but you can find it by searching for 'comment essayer lenovo writeit' in google and go to the tabletpccorner dot net article
Basically, you need OCRA to be able to edit the MSI file and you delete the check for Lenovo devices and then proceed with the installation.
I used the latest beta and it works really well with Surface Pro 3. No scaling issues as mentioned above.
srikz said:
I followed the following steps.
1. First you need to get the beta file from lenovo's site
2. Then, extract the msi file from the setup file.
To extract the msi file I opened command prompt, navigated to the folder where the setup exe is stored and ran this:
Code:
WRITEit-Setup.exe /A
This will prompt you to select a folder where all the contents will be extracted. You will find the msi file in that folder.
3. Then follow the instructions (use google translate for english) in the article by tabletpccorner to remove the Lenovo check from the msi file. (Steps 1 & 2 in the article are already covered above)
I can't paste the article link as I don't have enough rep, but you can find it by searching for 'comment essayer lenovo writeit' in google and go to the tabletpccorner dot net article
Basically, you need OCRA to be able to edit the MSI file and you delete the check for Lenovo devices and then proceed with the installation.
I used the latest beta and it works really well with Surface Pro 3. No scaling issues as mentioned above.
Click to expand...
Click to collapse
does it still only work on modern apps (no desktop support) ?
todarkness said:
does it still only work on modern apps (no desktop support) ?
Click to expand...
Click to collapse
it works well for both, desktop and modern apps.
Dear Gary ans Srikz
I've tried many options but failed so far to extract the msi from the newest beta "writeit-setup.exe" let alone edit it.
the /A thing doesn't work on my windows 8.1.
can you please post an edited newest beta ?
thanks!
- update - i managed, solved
new version 1.043.0 now available!
Anyone got this working on the Surface Pro 3? I cannot believe Microsoft has not seen the value in this approach and added it to Windows 8.1.
Hello !
Someone can share the 1.2.7.0 WRITEit.msi version, because the last (1.3.29.0) doesn't look to be installable on Surface...
Thanks a lot !
Nobody ? ;-(
No Working
I follow the steps for the installation of the last version, and it has gone right.
But after the installation the software doesn't work and launches the message that it works only with lenovo.
Any idea?
srikz said:
I followed the following steps.
1. First you need to get the beta file from lenovo's site
2. Then, extract the msi file from the setup file.
To extract the msi file I opened command prompt, navigated to the folder where the setup exe is stored and ran this:
Code:
WRITEit-Setup.exe /A
This will prompt you to select a folder where all the contents will be extracted. You will find the msi file in that folder.
3. Then follow the instructions (use google translate for english) in the article by tabletpccorner to remove the Lenovo check from the msi file. (Steps 1 & 2 in the article are already covered above)
I can't paste the article link as I don't have enough rep, but you can find it by searching for 'comment essayer lenovo writeit' in google and go to the tabletpccorner dot net article
Basically, you need OCRA to be able to edit the MSI file and you delete the check for Lenovo devices and then proceed with the installation.
I used the latest beta and it works really well with Surface Pro 3. No scaling issues as mentioned above.
Click to expand...
Click to collapse
Lenovo added an extra layer of device control at loading of the app... maybe someone could look into this...
One more note: the app used MyScript software as OCR, and not Windows native character recognition... I really hope MS creates something similar to this app...
nicopizza said:
Lenovo added an extra layer of device control at loading of the app... maybe someone could look into this...
One more note: the app used MyScript software as OCR, and not Windows native character recognition... I really hope MS creates something similar to this app...
Click to expand...
Click to collapse
yeah so i got as far as installing it.
but now when I launch the app it *****es about it only running on a lenovo...
Any way to bypass this?
I installed the .msi file in this thread and it works without problems. It only asks to update whenever the app is started, but you can ignore that.
I did try to install the updated version from Lenovo site using the method suggested here, but it does not work, and I get the same warning as you do.So my suggestion is to use the older .msi version that you find in this post.
nicopizza said:
I installed the .msi file in this thread and it works without problems. It only asks to update whenever the app is started, but you can ignore that.
I did try to install the updated version from Lenovo site using the method suggested here, but it does not work, and I get the same warning as you do.So my suggestion is to use the older .msi version that you find in this post.
Click to expand...
Click to collapse
For me the .msi file in this thread is not working so good.
My name is James and I am the project manager for WRITEit. We will be launching our 2.0 beta at CES 2016 in a week. Before that, I wanted to share with you the code so that you could test it out for yourselves. No hack is required because we will be offering WRITEit on all OEMs going forward. We are radically changing the direction of WRITEit, but we still have the core handwriting -> text conversion that you all know from the 1.x builds. Going forward, we are putting more emphasis on annotating over the entire desktop screen. This can work on touch and pen machines, so you aren't limited to only having a pen equipped machine.
Remember that this is a beta... I welcome any feedback from the community. You can PM me on here or email me directly at [email protected]
Dropbox link (40MB exe): https://www.dropbox.com/s/y6ejtsibddukhdz/WRITEit-Setup CES BUILD.exe?dl=0
JAmerican said:
Has anyone considered privacy concerns regarding password input?
Click to expand...
Click to collapse
WRITEit does not allow the user to input passwords due to this reason.
Hello Everyone,
I've written a small tool that allows you to sign a single file or a complete folder. See attachments. It is quick and dirty. If someone wants to improve it, there is the source attached also.
Please note that this tool will sign every exe and dll files in all sub folders if you select "Sign folder"!
Best of all: It also runs on Windows RT directly
Have fun!
[Removed]
Hmm it seems to have some issues with signing some binary exe files that had been previously compiled and worked on RT 8.0. I'm guessing this has to do with Release vs Debug ARM binaries?
hi guys can some one help i cant find how to jailbreak my surface Windows 8.1 rt
hatekiller said:
hi guys can some one help i cant find how to jailbreak my surface Windows 8.1 rt
Click to expand...
Click to collapse
Follow the guide here: https://forum.xda-developers.com/wi...ent/windows-8-1-rt-jailbreak-exploit-t3226835
Hello, I know it's been a long time since this tool was made but would it be possible to add some kind of handler of errors to the signTool? It's becoming harder to use since programs are having more and more files and we have to close a little error message for every file otherwise the process is paused.
Even though this is pretty old post, thank you so much for this tool!
It took hours of trying to get .exes to work. The signtool.exe also didn't really work for me.
FINNAL IT WORKS!
There is an issue with this tool prompting you after every single file. I fixed it and also added some other minor things such as .sys file support. here it is
H, can anyone help me, I'm total noob, what is this signing? how do I sign this? I'm trying to have some apps works on the RT
starfrost013 said:
There is an issue with this tool prompting you after every single file. I fixed it and also added some other minor things such as .sys file support. here it is
Click to expand...
Click to collapse
Oh whoa thanks, this would help alot since this was updated recently
It looks like following the official instructions on wiki.lineageos . org/devices/I01WD/install can brick your device if you're unlucky - at least for me, the bootloader seems to have vanished; trying to boot will just return a black screen. So, I looked for unbricking instructions. Unfortunately, the only two I found were getdroidtips . com/unbrick-zenfone-6-asus-6z-qdloader-9008-mode/ and piunikaweb . com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/, which both use BAT scripts. I only use Linux, which doesn't support such scripts, and I'm not familiar with the Windows shell. I wondered whether anyone here could convert the instructions for Linux? The driver installation shouldn't be a problem, as Linux is monolithic and lsusb shows the Qualcomm modem being in QDL mode (I suppose that's the same as QDLoader 9008/EDL?). (remove the spaces from the links)
FantasyCookie17 said:
It looks like following the official instructions on wiki.lineageos . org/devices/I01WD/install can brick your device if you're unlucky - at least for me, the bootloader seems to have vanished; trying to boot will just return a black screen. So, I looked for unbricking instructions. Unfortunately, the only two I found were getdroidtips . com/unbrick-zenfone-6-asus-6z-qdloader-9008-mode/ and piunikaweb . com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/, which both use BAT scripts. I only use Linux, which doesn't support such scripts, and I'm not familiar with the Windows shell. I wondered whether anyone here could convert the instructions for Linux? The driver installation shouldn't be a problem, as Linux is monolithic and lsusb shows the Qualcomm modem being in QDL mode (I suppose that's the same as QDLoader 9008/EDL?). (remove the spaces from the links)
Click to expand...
Click to collapse
Would this help you?
https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Or this:
https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
I am sure you can easily read windows batch and convert them to your favorite shell language. I suppose it is simply a list of adb and fastboot commands. I don't know if I actually can help, but I'll be available for discussion, if you have any problems during your try with either of the two options above.
abprie said:
Would this help you?
https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Or this:
https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
I am sure you can easily read windows batch and convert them to your favorite shell language. I suppose it is simply a list of adb and fastboot commands. I don't know if I actually can help, but I'll be available for discussion, if you have any problems during your try with either of the two options above.
Click to expand...
Click to collapse
The first links seems to be basically the same as what I found. The last one only works if the bootloader is still there, which is not the case. That's also the reason why I think, while not actually had looked into them, that it's not just adb and fastboot commands (those won't work anymore with my device). ADB only works in Android, and fastboot only in the bootloader. But yes, I'll look into it and see if I can do anything.
So, after looking into it, I noticed I basically understand even less of that script than I do understand Unix shells. I guess I'll probably ask in that thread however, as this seems to be the original developer of the script(s). (actually, there's several scripts, XMLs and so on there)
I had a quick look at the update_image_EDL.bat file and noticed that the file itself calls an executable in Windows format. I guess this won't be easy to convert.
But did you try to run this in wine?
I believe the best solution to your problem would be a VM with Windows 10 installation and USB support.
aleksander002 said:
I believe the best solution to your problem would be a VM with Windows 10 installation and USB support.
Click to expand...
Click to collapse
This would require the OP to own a win10 version and if that was the case, (s)he could also boot from a installation disk and run the scripts on a live boot. But still, maybe a true Windows version is required.
As far as I know, Windows 10 is free to install without key and it will be legal as a short-period evaluation copy.
aleksander002 said:
As far as I know, Windows 10 is free to install without key and it will be legal as a short-period evaluation copy.
Click to expand...
Click to collapse
True, might work...
So, while QFIL.exe would start with wine and Mono (apparently it's a .NET application) installed, it wasn't actually able to connect to the phone (I think direct hardware access is one of the things WINE cannot really do anyway). Thus I tried the suggestion with Windows in a VM and USB redirection, however, I got `ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.` and some other errors after this which were apparently caused by the first error when executing the `update_img_EDL` script. I found another solution that may possibly work: Using https://www.96boards.org/documentation/consumer/guides/qdl.md.html, however I don't really know which partitions I need, and which XML files I should use from the many that are present in the zip file. The signed ELF programmer is apparently `prog_firehose_ddr.elf`, at least that's what the script seemed to use.
EDIT: Looks like some people in the original thread are having the same issue as I do.
FantasyCookie17 said:
So, while QFIL.exe would start with wine and Mono (apparently it's a .NET application) installed, it wasn't actually able to connect to the phone (I think direct hardware access is one of the things WINE cannot really do anyway). Thus I tried the suggestion with Windows in a VM and USB redirection, however, I got `ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.` and some other errors after this which were apparently caused by the first error when executing the `update_img_EDL` script. I found another solution that may possibly work: Using https://www.96boards.org/documentation/consumer/guides/qdl.md.html, however I don't really know which partitions I need, and which XML files I should use from the many that are present in the zip file. The signed ELF programmer is apparently `prog_firehose_ddr.elf`, at least that's what the script seemed to use.
EDIT: Looks like some people in the original thread are having the same issue as I do.
Click to expand...
Click to collapse
Sorry for the late reply. Could you find out what kind of dragonboard the zenfone 6 has? I guess that will give you a clue through the manual linked at the end of you referenced threat.
Oh, and did you try to just install a win10 version as suggested before?
abprie said:
Sorry for the late reply. Could you find out what kind of dragonboard the zenfone 6 has? I guess that will give you a clue through the manual linked at the end of you referenced threat.
Oh, and did you try to just install a win10 version as suggested before?
Click to expand...
Click to collapse
Afaik Dragonboard is just the name of that line of SBCs which also uses Qualcomm SoCs. So while the Zenfone very likely doesn't use a Dragonboard as PCB, the SoC modes and such should be similar. The device-specific instructions most likely won't work, however the software should work on all Qualcomm-based boards.
I didn't try to install Windows 10 on my PC, however I also tried it at a friend's PC with W10, where I got the same error.
FantasyCookie17 said:
I didn't try to install Windows 10 on my PC, however I also tried it at a friend's PC with W10, where I got the same error.
Click to expand...
Click to collapse
Meaning that even the Windows scripts that reflash the bootloader did not work?
Interesting. Looks like the issue was the cable; it worked with a different one (though both cables had both data and power lanes).
I'm in the same situation, with a dead Zenfone6 and only a Linux desktop.
Was there a way to bring it back to life?
Marlin79 said:
I'm in the same situation, with a dead Zenfone6 and only a Linux desktop.
Was there a way to bring it back to life?
Click to expand...
Click to collapse
See the original thread which was linked here. (the cable I originally used did not work, however it wasn't the original one that came with it) The only way I see is downloading the Windows installer and starting that in a VM with USB redirection (e.g. use QEMU/KVM and virt-manager). Then install Windows in that VM (if you don't want to create a Microsoft account, disconnect from the internet before it asks you to do so), and then follow all the instructions in the original thread.
FantasyCookie17 said:
See the original thread which was linked here. (the cable I originally used did not work, however it wasn't the original one that came with it) The only way I see is downloading the Windows installer and starting that in a VM with USB redirection (e.g. use QEMU/KVM and virt-manager). Then install Windows in that VM (if you don't want to create a Microsoft account, disconnect from the internet before it asks you to do so), and then follow all the instructions in the original thread.
Click to expand...
Click to collapse
My Asus brick has been lying in my drawer for a while but I had a bit of spare time so I thought to see what I could do with it. I have a bit of spare parts so I put together a bare bone computer and installed Windows 10 on it (the windows installer iso-file from microsoft.com)
I then tried to follow this guide https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
But when running the update_image_EDL.bat script I get "Environment variable _COM not defined". The USB cable I'm using is the one that came with the phone.
I know next to nothing about Windows. Somebody who has an idea what to do about that error message?
Marlin79 said:
My Asus brick has been lying in my drawer for a while but I had a bit of spare time so I thought to see what I could do with it. I have a bit of spare parts so I put together a bare bone computer and installed Windows 10 on it (the windows installer iso-file from microsoft.com)
I then tried to follow this guide https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
But when running the update_image_EDL.bat script I get "Environment variable _COM not defined". The USB cable I'm using is the one that came with the phone.
I know next to nothing about Windows. Somebody who has an idea what to do about that error message?
Click to expand...
Click to collapse
Yes. Happened to me, too. The problem was that the phone is not recognized as a Qualcomm device in Windows. I had to open it and bridge two points on the board. See this: https://forum.xda-developers.com/showpost.php?p=82965385&postcount=66
I finally got to the stage where i could execute update_image_EDL.bat script
It ran for a minute or so but then terminated in an error.
Code:
13: E:\firmware\prog_firehose_ddr.elf
06:28:01: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
06:28:01: ERROR: function: sahara_main:983 Sahara protocol error
06:28:01: ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'QMSL_MSVC10R.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at QC.QMSLPhone.Phone.QLIB_DisconnectAllServers()
at QC.QMSLPhone.Phone.DisconnectAllServers()
at QC.QMSLPhone.Phone.Finalize()
2020-07-11 06:28:02.931 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
press any key to continue . . .
Any ideas what that is about? The file it mentions QMSL_MSVC10R.dll does exist in the firmware directory