Install wm6 roms on vista 64bit - P3600 ROM Development

Hello, I tried updating my trinity on vista 64bit using a guide from trinityguides.info and the 64bit drivers I found there.
I just can get an further updating because my HTC usb sync driver says something about an error code 39
Is there any way to avoid this?
I've already tried updating wm6 trough a memory card "by renaming RUU_signed.nbh to TRINIMG.nbh
like described on Wiki Trinity SDCardFlashing" but i didn't worked
Btw. I've only got vista 64bit and OSX(using a macbook) so I hope i don't also have to install an windows 32bit version
Thanx in advance for any help or tips!

sorry you're having trouble.. if you have a problem it's better to post within the guide thread, than start a new one. Can you tell me what the error says exactly when it comes up?
have you disabled driver signing?
*update* i've been scouring the net for an answer, but only a handful of ppl have experienced this problem, and so far can't find any posts with the solution. There definitely are some ppl having trouble with the x64 driver. Post if you find anything, and i'll do the same

sspl
I had the same problem trying to install it with a sd-card.....
just download SSPL-TRIN.exe from this post http://forum.xda-developers.com/showthread.php?t=293632&highlight=sspl and put it in the root directory of your sd-card with the TRINIMG.nbh file....
i am hoping you stil have a wm5 or wm6 installed...when you insert your card go to the root directory of your card then dubble tap on the SSPL-TRIN.exe it wil pop up in installer mode and then press power to install......
Het heeft voor mij gewerkt......

Thanx for the info but i can't disabled driver signing on my Vista ultimate, seems like the guys from Microsoft disabled this funtion with their latest updates
Does somebody have any solution for this?
@TheBlackDragon:
Seems like this method doesn't work with wm6,I've got MuN 2.01.TE installed on my device.
The phone still works but I would like to put the official wm6 rom on it!
Btw. I've now got the follow SPL:
TRIN100
IPL-0.50
TRIN100
SPL-9.99.CP

let me look in to this.. can you please list the steps you tried to take to disable driver signing, so at least we know where you're stuck?
*edit*
ok, this is what i've got so far.. can you try these methods and let me know what works and what doesn't (i don't have x64). I guess we're looking for a permanent disabling of driver signing, cause some of these steps seem to only disable until reboot.
OPTION 1 - Bcedit
1. Create a shortcut on the desktop to cmd.exe
(this recipe explains how to create a shortcut if you don't know how)
Right click on an empty space on the desktop to open the context menu
Select New
Select Shortcut with a left-click
In the location box type cmd.exe
Select Next
Name your shortcut and push Finish
​
2. Right-click on the shortcut and select Run as administrator
3. When the command window opens, type or paste the following and press ENTER:
Bcdedit.exe /set nointegritychecks ON
4. Reboot and then try installing the driver​
some people listed some variations on this method, they are as follows:
​
if the "bcdedit /set nointegritychecks ON" does not work, try "bcdedit -set nointegritychecks ON"
or try bcdedit -set loadoptions \”DISABLE_INTEGRITY_CHECKS”
(this seems to be a more permanent fix i guess)
OPTION 2 - F8
An F8 boot option introduced with Windows Vista—“Disable Driver Signature Enforcement”—is available to disable the kernel-signing enforcement only for the current boot session. This setting does not persist across boot sessions.​
OPTION 3 - gpedit
open the command line again (i guess it wouldn't hurt to open with administrative priviledges as listed in option 1)
Navigate to User Configuration -> Administrative Templates -> System -> Driver Installation
enable the "Code signing for drivers" and then choose "Ignore".

Related

help!!! my htc 3300 won't start anymore!!!

Hello,
I have 3 month's ago flashed my htc 3300 with wm6 english (pdavliet).
I have used uspl and the wm6 rom.
Today i flashed my phone again but with wm6 dutch.
And now i can't start my phone.
When i push the startbutton the phone start in de startmenu with bleu screen wich is from 02 and the phone still hanging on that screen.
I think i broke my phone i must have do something wrong.
Is there anyone who can help to get my phone fixed without sending it to the manufacturier.
Please help me i turned my phone into a brick.
I am waiting for a response (i hope i get some)
I am from holland and my phone is from mda pro 3
Thank you all
try to hard reset, if not follow the instructions here http://forum.xda-developers.com/showthread.php?t=308242
HELP me please,
I've got the same problem... it was working perfectly but at same point it freezes!! I’ve tried a soft reset but didn’t work, then tried a hardware reset but it says “Format failed”. Really don’t know what to do!
Do I have to re-flash my artemis, can I do that even if it freezes at the splash screen?
P.S.: i have the B&B 4.2
Thx very much
follow the abovr link to reflash bricked devices
Is that meaning it is brikked?
But it worked for couple of months!
no it doesn't mean it's bricked but you can't hard reset.
Maybe you can try to use uspl on it and see if it succeds, if then try to reflash....
Thank you very much
Just a last question if you don't matter can I run the UPLS even if my PDA freezes when the Spalsh screen appears?
Thank you!
I think so as the phone stops to be flashed.
You can check if the activ sync icone is green.
On another forum a guy had a similar problem, he tried to hard reset about 20 times and it finaly passed
what if i would take off the battery for few hours?
Do you think it will erase everything like an hardware reset?
Act syn dosn't get green.... and 20 hardware reset are too much
Thank you!
removing the battery won't change anything, imagin if it goes down for a few days and you don't charge it.
It's a flash memory.
The only thing lesft may be to get into the bootloader and reflash
OK.... i connected my pda to my computer and i bootloaded! But my computer dosen't reconize it and so i cannot run the UPLS
Any idea?
Thank guys
No USPL, 1st reflash your p3000 with your ORIGINAL HTC orT-Mobile Rom and correct language. WM6 is just released officially so i should not be a problem to find your ROM. In the past this was the biggest problem (no way to get the original rom).
When this is done, then USPL and change to another rom (other language and extra cherrys!).
GL
edit: To do so, put the artemis in bootloader mode, connect to usb and start RUUGetInfo.exe. Wait and see what happens . Should work fine.
THANK!!!
i'll try!
yessssssssssssssssssss
Thank you all!!!
I solved my problem. I turned my brick into a phone hahahaahh
I am very happy
How to get in the bootloader menu?
Start your phone
hold speedialbutton and softreset but still holding the speeddial button and then the bootmenu will appair (dont forget the usb cable it must plugged in before you go in to the bootmenu)
How do i get the 'wceusbsh.inf' file?
On your cd from the phone.
Before starting: Your device needs to be connected to the PC, and in BOOTLOADER mode.
Step 1 of 16: Extract this zip file to a memorable location on your machine (e.g. the desktop). 'wceusbsh.inf' This is the Activesync 4.5 RTM USB driver.
[attachment=21151:VistaRUU.zip]
Step 2 of 16: Run 'Windows Mobile Device Center', and click 'Connection Settings'.
Step 3 of 16: Uncheck the 'Allow USB Connections' box, and select 'OK'.
Step 4 of 16: Run 'Services' by clicking the Start Orb and typing 'Services', and ensure the 'Windows Mobile-based connectivity' and Windows Mobile 2003-based connectivity' services are started. If they are not, click the service name and press the 'play' button on the top bar.
Step 5 of 16: Load 'Device Manager' by clicking the Start Orb and typing 'Device Manager'. Expand the 'Mobile devices' section and click the 'HTC USB Sync' (or similarly named) item.
Step 6 of 16: Click the 'Action' menu and select 'Update Driver Software'.
Step 7 of 16: Click 'Browse my computer for driver software'.
Step 8 of 16: Click 'Let me pick from a list of device drivers on my computer'.
Step 9 of 16: Click 'Have Disk'.
Step 10 of 16: Click 'Browse', and browse to the location where you extracted the ZIP' wceusbsh.inf' file in Step 1.
Step 11 of 16: Double click 'wceusbsh.inf'.
Step 12 of 16: Select 'HTC USB Sync' from the list, and click 'Next'.
Step 13 of 16: Wait while your driver is installed.
Step 14 of 16: Run 'Task Manager' by clicking the Start Orb and typing 'taskmgr'. Then find the 'WMDC.EXE' item, and click 'End Process'.
Step 15 of 16: Install your update! Everything should now run fine! You just need to bear in mind the final step when you want to start syncing normally again...
Step 16 of 16: In 'Windows Mobile Device Center', re-enable the 'allow USB connections' checkbox you disabled in Step 2.

[REF] The DEFINITIVE MTTY Thread!! - Diamond Edition

This is a friendly warning to people who are new to the site/new to the thread.
There has been a LOT of unnecessary posts recently from people who cannot be bothered searching starting HERE ON PAGE 59 POST 581 onwards.
I will simply not reply or reply with "Search". Why should I help when people cannot be bothered ATTEMPTING to help themselves?
Also anyone thinking of asking either of the following questions:
1: "After task 29, I get this output in MTTY: Total Bad Block in CE: x"
2: "After task 29, I get this output in MTTY:
ERASE block xxx FAIL !!!
ERASE block xxx FAIL !!!"
(where x is a random number)
This has been asked 100+ times in this thread so this is the final time I will answer:
IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!
There is a LOT of information in this thread. All you need is the first 4 posts or the search button OR if it is a GENUINE problem post it and I will help!
​
------------------------------------------------------------
Hi,
Over the last couple of weeks, as all of us flashing junkies are continuously flashing devices there has been an increase in "Strange Problems" which to all intents and purposes are just “clog ups” and “bad flashes”
As we all know MTTY is the key here, but I can say from personal experience that this small piece of software is a MASSIVE pain in the ass to get working, i must have tried 15-20 different “recommended” procedures to get it work and all failed.
But I managed to find a failsafe method of getting MTTY working on Vista AND Windows 7, also x86 AND x64!! (I have all 4 windows installations and the methods detailed below worked on all)
NOTE: WORKS WITHOUT DRIVER INSTALL ON XP
If for some reason you cannot got this to work on XP do the following: (Thanks kgerry!!)
kgerry said:
Hi,
if you run XP and you have Problems to connect to USB try following:
1. Launch ActiveSync on PC
2. Go to connection settings
3. Uncheck the Allow USB Connection
4. bring the device to bootloader.
5. Now, run mtty ...
... try again to switch from COM1 to USB and follow the instructions of perfect post 3
Hope it helps ... Kgerry
Click to expand...
Click to collapse
Here is how this thread works:
Post 1: Description
Post 2: Driver Installation
Post 3: MTTY Instructions For FLASHING FROM INTERNAL STORAGE
Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM
THANKS to:
Reb0rn - for pointing me to the light!
l2tp - for the images
lunasea - for providing me with working drivers
and of course to anyone else I forgot.
I hope this helps people!!
MG
Driver Installation
Pre-Cursor To Driver Installation – FOR EVERYONE (x64/x86 Vista/Win 7)
This will remove the need for users, x64 in particular, to use “Unsigned Drivers.” Also since in Vista SP2 (x64 & x86) they removed the “F8” options Completely!
Files Needed:
Driver Signature Enforcement Overrider
Remove Watermark V0.8
1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next
2: There will be a warning to REBOOT, Press “OK”
3: Go Back to Driver Signature Enforcement Overrider Select “Exit” then Click “Next”
4: Run the “Remove Watermark V0.8” for you OS type (x64 or x84)
5: In the Command Window type “Y” and wait for the process to complete
6: Once complete REBOOT your system and begin the driver install
NOTE: If you DO NOT complete the above, some users will need to press "F8" During Bootup - (ANOTHER NOTE FOR x64 USERS, EVERY TIME YOU NEED TO USE MTTY YOU MUST REBOOT YOUR COMPUTER, HIT F8 AND SELECT: "START WINDOWS WITHOUT DIGITALLY SIGNED DRIVER CHECK")
For Info See Post Below:
Reb0rn said:
I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
-----------------------------------------------------------------------
Big thanks to maybeme for providing a host for the images!!
1: Download the relevant drivers for your system attached to this post: these work for both Vista and Win7, all you have to choose is x86 or x64
EDIT: It has been found that with different versions of Windows 7 x64 need different Active Sync Drivers... If you are using Windows x64 please try x64 AS Drivers Win 7 Tested & Working.zip FIRST!!!
2: Connect Device to PC via Active Sync, Once Connected Uncheck USB Connections,DISCONNECT DEVICE then Reboot Computer
3: Bring device into bootloader (Reset + Hold Vol Down), This will show the Red, Blue, Green screen showing "Serial" - Once Computer booted, connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Go to "Control Panel -> System -> Device Manager" and select Microsoft Usb Sync in Mobile Devices section (NOTE: This MAY say HTC USB Sync but as long as you select your device!!):
5: Right Click and Select "Properties" then go to Driver tab, then Select "Update Driver"
6: Choose to "Browse Computer For Driver" (the second option):
7: Select "Let Me Pick From A List...." (the second option):
8: Click "Have Disk":
9: Select the folder with downloaded driver From Step 1 and select "wceusbsh.inf" (this is the same file for x86 & x64):
10: You will get back to previous screen, then click Install
10a: WINDOWS 7 ONLY - The Below Warning will appear, Select "Install anyway":
11: The drivers will be successfully installed:
12: When you get back to "Driver Properties" check driver version. If the "Driver Date" has changed from 2nd step (2003 instead of 2007), the installation has been a success:
13: Lastly leave the device connected and in "Bootloader" and reboot you system. Upon Rebooting an "Unknown Device" is installed, this is your HTC device.
Now the Active Sync Drivers are Installed
MTTY - Flashing From INTERNAL STORAGE
Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY
Before you start grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Download a ROM of your Choice, RENAME the *.nbh for your ROM to: DIAMIMG.nbh
2: Copy DIAMIMG.nbh to the "Internal Storage" of your Device.
3: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
4: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
5: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
6: Run following commands:
6a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
6c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
6d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
7: Immediately DISCONNECT your device and hold "Vol Down and Back" (Back = Small Arrow above "End Call" Button) to Initiate ROM Flash
8: After ROM flash Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) again, on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and allow the ROM to boot.
MTTY - Flashing From USB
Before you start:
a: FULLY COMPLETE POST 1
b: grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"
2: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1
3: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK
4: Run following commands:
5a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
5b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
5c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
5d: type "task 8" to ask your device reboot:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 8
Cmd>
---------------------
6: Immediately DISCONNECT your device then Press and Hold Vol Down to bring the device back to bootloader and connect to USB.
7: Run ROM Flasher and flash via USB. After rom flash is completed Hard-reset (Pen Reset, then Press and Hold Vol Down and Circle) then allow the ROM to boot.
Very good to have a MTTY thread that rounds everything up!
Good job and thanks for all the effort!
i must say this is the reason i got my old rom working and stuck with it without wanting to upgrade. this happened to me, and for about 4 days or more the phone kept crashing and needing a hard reset. even changing roms or reloading the same rom didnt fix.
i tried the MTTY thing and it was difficult to get going.
i personally really appreciate writing all this up, because now i will probably go and try another rom, with this thread in the back of my mind if things start acting up.
so thanks!
dieselboy said:
i must say this is the reason i got my old rom working and stuck with it without wanting to upgrade. this happened to me, and for about 4 days or more the phone kept crashing and needing a hard reset. even changing roms or reloading the same rom didnt fix.
i tried the MTTY thing and it was difficult to get going.
i personally really appreciate writing all this up, because now i will probably go and try another rom, with this thread in the back of my mind if things start acting up.
so thanks!
Click to expand...
Click to collapse
To be honest, i have NEVER experienced the issues that require MTTY! I have always just flashed from internal storage and never had an issue.
I wrote this because i just wanted to get MTTY working incase i ever do experience it!!
MG
pauldgroot said:
Very good to have a MTTY thread that rounds everything up!
Good job and thanks for all the effort!
Click to expand...
Click to collapse
No problem, I personally got sick of trying loads of instructions to have them fail!
Most of my failures were due to drivers and improper installation!
Glad you find this useful!!
MG
I must just say that u might have to watch the x64bit drivers if they are digitally signed... Cuz neither Vista 64 nor Windows 7 64 will let u load or start those drivers if they are not digitally signed.
IF that the case and if u have installed the driver but it says that it has stopped it due to the driver not been Digitally signed u have to start windows vista/7 in "ignore digitally signed drivers" mode.
When u start the computer, keep hitting F8 and it will prompt you if u want to start in safe mode bla bla and in the bottom of that list there is an option that goes something like this:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Reb0rn said:
Start Windows without Digitally signed Driver Check... or sumthing like that...
This is only if u have problems with the x64 driver... like i did...
BTW... u made a beautiful how-to man. Great job!
Click to expand...
Click to collapse
added this to the first post!!
thanks alot!
MG
well done
sticky!
benko286 said:
well done
sticky!
Click to expand...
Click to collapse
Agreed!!!
MG
MG, great thread thanks....
I am wondering whether you have any idea what happened to my Diamond, and what could I have done to save it (it is now with HTC).
http://forum.xda-developers.com/showthread.php?t=539958
I didn't do the "Driver Installation" part you described in your procedure, although I could still see the "USB" option in the dropdown, can that be where I went wrong?
Would also like to check how come recently there seems more flash problems reported? I myself have been flashing for some one year or so now... and never had a problem till now... I would like to get back to flashing again once my Diamond returns (hopefully), but now I am not sure I would since I am not sure what I did wrong to cause the problem to start in the first place.
epiphone said:
MG, great thread thanks....
I am wondering whether you have any idea what happened to my Diamond, and what could I have done to save it (it is now with HTC).
http://forum.xda-developers.com/showthread.php?t=539958
I didn't do the "Driver Installation" part you described in your procedure, although I could still see the "USB" option in the dropdown, can that be where I went wrong?
Click to expand...
Click to collapse
Possibly, i really would suggest running throught the entire thread if you have a brick.
reinstall the drivers, using the ones i have posted, also use the MTTY i have posted.
also USE the exact commands i have posted (i.e. not "task 28", use "task 28 55aa")
then after the MTTY format, HARD-RESET your device then to clear anything else off, then in your case, flash from the PC not internal storage.
epiphone said:
Would also like to check how come recently there seems more flash problems reported? I myself have been flashing for some one year or so now... and never had a problem till now... I would like to get back to flashing again once my Diamond returns (hopefully), but now I am not sure I would since I am not sure what I did wrong to cause the problem to start in the first place.
Click to expand...
Click to collapse
Personally i have never experienced (touch wood) these flashing problems, i have consistently flashed from internal storage and NEVER via USB.
personally this is where i think the problem resides, with leftover data from USB flashing logging up the devices.
as there are more "Bloated roms" (i.e. ones with loads of nice but useless software) this is also causing the problems.
having said that i use possibly the most bloated rom about, the NRGZ EnergyROM series!! i swap between this and the BSB, im more drawn to the BSB at the moment as there is more storage and ram free.
but as i said this is only my opinion and not verifiable facts! (i could be totally wrong!!)
MG, thanks for your replies... unfortunately I am not able to try the "task 28 55aa" now that I have booked my phone in This thread however, will no doubt be useful for more others in time to come!
Hmmm... the strange thing is that after ive had these problems i have to use MTTY as soon as i must flash another ROM then the one i already have in...
But as i said... no problems as long as it works
epiphone said:
MG, thanks for your replies... unfortunately I am not able to try the "task 29 55aa" now that I have booked my phone in This thread however, will no doubt be useful for more others in time to come!
Click to expand...
Click to collapse
MG, is it "task 29 55aa" or "task 28 55aa"?
sb0611 said:
MG, is it "task 29 55aa" or "task 28 55aa"?
Click to expand...
Click to collapse
sorry my error "task 28 55aa"
ill edit previous post
MG
sorry for the noob question, i'm on XP would I still need to run through the driver setup in the first post?
skilty said:
sorry for the noob question, i'm on XP would I still need to run through the driver setup in the first post?
Click to expand...
Click to collapse
I dont have XP, but i guess not, i have never heard of people having a problem with MTTY on XP.
Just disable USB connections in active sync, reboot your system and start MTTY.
If there s no USB option you may have to find the XP Active Sync Drivers and follow my method, but using the XP drivers.
MG

MTTY Problem (no response)

Hello Guys,
I have a big problem!
My Diamond is not working anymore,
sometimes it's not booting and if it boots it wants to reinstall windows.
when whindows is installed and i restart the device it is starting the installation again (Like there was a hard-reset).
So I want to flash it with MTTY
first i tried it in vista but it didnt work (I could choose usb from the list but MTTY did not response after i typed in "set 14 0" or anything else)
Now i installed XP and i can choose usb from the list:
1.JPG (Attachment)
if I click OK this window is opening:
2.JPG (Attachment)
I thik it should look like this, and it also looks good after i pressed enter:
3.JPG (Attachment)
But now the problem, i dont get a response after i type anything like "set 14 ":
4.JPG (Attachment)
i think there should be this response:
CMD>set 14 0
HTCST ÚÈHTCEUSB>
so what can i do?
where could be the problem?
Please help me, i need my Diamond!
Thank you for reading
31kcir
in windows vista there is a option to disable the driver enforcement...pressig f8 when the bios is displayed....in windows xp i don't know
have you installed the drivers that are provided in the mtty thread?
On vista I installed the drivers like in this thread: "[REF] The DEFINITIVE MTTY Thread!! - Diamond Edition" and on XP I just installed them like normal drivers. I have now vista and XP.
but with vista you have to use a special mode...when you open the pc press f8 and choose disable driver enforcement or something similar...
i did it like this..
I tried every description I could find.

[GUIDE] Crash Course in ADB/Unlocking on WINDOWS

Just wanted to try and put together something helpful for those who are unlocking their devices who might be doing this for the first time or just are having issues.
THIS GUIDE ONLY WORKS FOR WINDOWS FOLK, SORRY! IF YOU HAPPEN TO BREAK YOUR DEVICE OR DO ANYTHING TO IT THAT PREVENTS YOU FROM USING, I AM NOT RESPONSIBLE, CAVETE LIBERUM OPUS.
ADB
Download ADB from here: http://developer.android.com/sdk/index.html
Make sure you install it where ever you are comfortable with, I tend to keep mine in my main installation (C: )
HTC Sync
Download HTC Sync here - http://www.htc.com/www/software/htc-sync-manager/
Why download HTC Sync? For the drivers. After the installation is complete you can remove HTC Sync, just not the drivers.
Appropriate Drivers
In your Program Files (x86) folder, there should be an HTC Folder, with the drivers in it.
What you are going to need to do is make sure that your device has the HTC drivers installed.
You'll need to open Control Panel ----> Hardware and Sound ----> Device Manager
Your HTC One should be under portable device or android phone, or something similar to that. If it is telling you the current drivers are up to date, you may need to disable driver signature enforcement, and that method is different between Windows 7 and 8.
You'll want to update the driver software by right clicking ----> Update Driver Software ----> Browse my computer for driver software ----> Browse...; then select the HTC Driver folder from within the HTC folder (you'll have to navigate to it)
If you need to disable driver signature:
Windows 7 - http://bit.ly/1bE0jZT
Windows 8 - http://bit.ly/1bE0mF7
Trouble Shooting ADB and Rumrunner
I am, in no way, saying that I am an expert in running rumrunner. If you can use irc and contact beaups please do. However, just in general, here are tips I think might work -
Go to "System and Security" from Control Panel and click "Allow an app through Windows Firewall." Click "Change Settings" at the top and then click "Allow another app...". Navigate to your extracted rumrunner file and select the soju.exe to be allowed through. Why do this? Because I personally rather not take down my entire firewall to allow this program to run. No offense to beaups, just doesn't seem terribly practical to me.
In your ADB installation folder, go into SDK -----> platform tools ----> Hold down left shift and right click -----> Open command window here
type in adb devices; if you are not seeing
List of devices attached
XXXXXXXXXXXXXXXXXX device (read the X's as a string of numbers which are your device)
then it isn't ready to be use rumrunner. You'll have to go into Settings -----> About Phone -----> Software Information -----> Then click 7 times on Build Number to unlock developer options. Go into "Developer Options" and enable USB Debugging.
As mentioned in Rumrunner, please run soju.exe AS ADMINISTRATOR, to avoid permission issues on computer-side.
OEM Cables are also ideal in this situation. Also make sure you downloaded the right file (.8 version versus .10)
Last but not least, IT TAKES A WHILE FOR SOJU TO RUN. BE PATIENT Your phone will reboot A LOT during the entire process. It'll take awhile, but if you run into the (.........) problems or an error because your drivers aren't installed correctly be patient.
The guide isn't perfect, but hopefully it helps. I'll add advice if it comes in.
Great guide!
Make sure to remember to do a fastboot devices check too. that is my problem adb works great fastboot is another story
Sent from my HTC6500LVW using xda app-developers app
It also hates USB3
It also hates USB 3.0, had to use my fiances laptop todo it, but very straightforward.

[Tutorial] Install Windows 10 for ARM32 on your Lenovo Yoga 11

So my Yoga 11 has been laying around for some years now and usage has been getting worse mostly because of the included, no longer supported, Internet Explorer.
But when I found that a working release of Windows 10 ARM32 for the Surface RT was around, I decided to go rogue and install it on my Yoga 11.
I adapted the tutorial by @kephax and @Zaveraj to the needs of the Yoga and added own experiences https://forum.xda-developers.com/windows-8-rt/rt-general/tutorial-install-windows-10-arm32-t4052035 https://forum.xda-developers.com/showpost.php?p=82022643&postcount=41
Feedback and suggestions are always welcome
**WORKING** Windows 10 arm32 on Lenovo Yoga 11
As usual, disclaimer: For dead devices, the author is not responsible. Perform all actions at your own peril and risk. At the moment, the topic with flashing is young and everything is done manually. Perhaps later the process will be partially or fully automated. In the meantime ...
Let's go !!!
#
Documents and instructions
1. Firmware is a potentially dangerous process and requires some accuracy. Always have a recovery disc on hand created from the official kit from Microsoft!
2. In order to facilitate the installation process, in addition to the USB flash drive, you will need a USB keyboard and an USB bluetooth/wifi adapter.
3. Windows 10 on ARM is basically functional. The drivers for Surface 1 work fine, the Bluetooth driver for Surface 2 has some problems. The store mainly supports the installation of ARM applications. Office 2013 is fully operational and even has a Russian language pack.
4. The image is not meant for the Yoga 11, therefore Keyboard, Sound, Wifi, Bluetooth, camera, Touchscreen? are not working in the installation process. After a 'magic' windows update in the end, they do work.
DOWNLOADS:
Own collection of files on Mega, includes some scripts for easy installation and the steps numbered: https://mega.nz/folder/eB5zSRhS#r8pI0QtUPQUS4cXjMXmXRw
Mega: https://mega.nz/#F!2IJlDYSL!1pGKdtllvHCpgTKWRzrYsA
Yandex: disk https://yadi.sk/d/mnCUeGKWm1XTXA
Baidu: https://pan.baidu.com/s/12Uf6BQ_VFTCRKv_1GZgaYQ password:c7bf
Create recovery drive using the existing Windows RT 8.1 installation:
https://support.microsoft.com/en-us/help/17422/windows-8-create-usb-recovery-drive
1. Clear an USB drive (8gb+ advised)
2. Open 'Create a recovery drive' on the Windows RT installation
3. Follow the instructions on the screen
Restore the laptop to version 8.1 according to this instruction :
1. Ensure that the Yoga is completely turned off and connected to the charger. Connect the recovery disk to the USB port.
2. Press and hold the volume up and windows button on the screen. Press and release the power button.
3. Hold volume up and windows button until a black screen with a console like appearance appears, then you may release
4. When prompted, select English and a keyboard layout.
5. Select "Troubleshooting", then select "Recover from a Drive", in my case the last USB device was the correct one, It may take some tries which one you need. If you are prompted for a Bitlocker recovery key, select "Skip this drive" at the bottom of the screen. Next, select “Just remove my files” and the last “Reinstall”. The laptop will go into reboot and recovery of clean 8.1 will begin.
Hacking SecureBoot
1. Turn off UAC. Run the registry file - Disabling_UAC.reg and, after merging, restart the laptop.
2. Unmount the registry hive responsible for the BCD. Using a combination of win + R buttons, open the Run window and enter regedit to open the registry editor. Select HKEY_LOCAL_MACHINE \ BCD00000000, and click "File" - "Unload Hive" ("File" - "Uninstall Hive")
3. Run the SecureBootPatch patch
Open the "securebootpatch" directory. Run as administrator (right click) InstallPolicy.cmd, and then restart the laptop.
After the reboot, the secure boot debug policy interface will appear. Select "accept and install" to install the policy.
4. Turning on the test mode.
Run the command line and enter:
bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
If there are no errors, restart the laptop and enter the recovery mode command line. Check the lower right corner of the screen for the words "secureboot is not configured correctly". If the inscription is present - continue (At the start of the WinPE GUI boot, it will blink and disappear under the background, will appear again at the command prompt).
-- I have to admit that I didn't check the secureboot, but it went well
Deploying win10
1. From the last step, we are in WinPE recovery mode:
Go to the command line: Select "Troubleshooting", then "Advanced Options" - "Command Prompt". A request for a bitlocker recovery key should not appear.
2. Format drive C. Make sure that the commands are entered correctly and enter the next only if there are no errors in the previous one.
Enter
(a) diskpart
(b) list disk
(c) select disk 0
(d) list partition
(e) select partition 4
(f) format quick fs = ntfs override
(f) exit
3. Actually deploying win 10: The win10 deployment file suitable for your device (the surface RT one) should already be at the root of the flash drive. If not, rename it to "install.wim", and copy it to the root!
Enter:
dism /apply-image /imagefile:d:\install.wim /index:1 /ApplyDir:c:\
Where: "d: \ install.wim" is the location of the deployment file from Win 10, and "c:" is the system drive to which you are deploying.
Close the dialog after execution and restart the tablet.
4. When restarting you will get an error popup: Press SHIFT+F10
-- This is the moment the drivers are no longer present and you will need the USB keyboard
5. Type Regedit and go to KEY_Local machine/SYSTEM/Setup/Status/ChildCompletion > setup.exe > Modify the value to "3"
6. Restart
NOTE: I did not connect to wifi until sometime later, there is a firmware update that seems to mess up the ability to install appx files?
-- Dont connect, for the above reason, a connection is however needed later on for the drivers.
### 2.1. How to activate Windows
1. Powershell
slmgr.vbs /upk
slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
slmgr /skms kms.03k.org
slmgr /ato
slmgr /skms zhang.yt
### 2.2 Install runtime
If using my collection; it is possible to execute: Install.ps1 (may need to do so several times to make sure everything installs with the dependencies)
1. Copy APPX1 from Recovery USB to Desktop
2. Desktop\APPX1\APPX1.ps1 > Right click > Run as Administrator
3. Restart
--install appx files from framework folder
4. Desktop\APPX1\AppxBundle.ps1 > Right click > Run as Administrator
5. Restart
6. Install:
Microsoft.windowsStore.appxbundle
Microsoft.NET.Native.Framework.1.1.appx
Microsoft.NET.Native.Runtime.1.1.appx
## 3. After installation ##
1. install all apps/dependencies/framework you can that are included, at this stage the laptop accepts most.
2. insert USB Wifi adapter or USB Bluetooth adapter
3. Connect to Wifi or Bluetooth (I used Bluetooth Tethering on my phone)
4. Run Windows Update and hear all the devices get installed.
### How to remove Expired version popup ###
1. Go to C:\Windows\System32
2. Right click on LicensingUI.exe > Properties > Security > Advanced
-- Guys, the file you have to rename for getting rid of the warning IS NOT "LogonUI.exe", the guide is wrong. The right file is "LicensingUI.exe". -- Thanks Kiba85
3. Ower > Change
4. Enter your username > Check Names
5. Give the Group Users or Administrators Full control
6. Close all dialog boxes
7. Now rename the file to LogonUIbak.exe
If it doesn't work; boot using the USB Recovery, open command promt, navigate to C: Windows System32 and use the command "rename LicensingUI.exe LicensingUI.exe.bak
### How to change the language to English (and remove chinese) ###
Start > Settings > Time & Language > Region & Language
Remove chinese and set English as Default
### How to install uBlock Origin on Edge ###
-- not so sure this works at the moment
1. Download this: https://github.com/nikrolls/uBlock-Edge/releases (I was able to install 1.12.0, but It made my Edge unusable)
2. Edge > about:flags
3. Select: "Enable extensions developer features"
4. Select the "..." > Extensions > Load Extension
5. Select the folder with uBlock Origin (this should be on the Surface itself)
### How to install UWP applications - Manually ###
1. Find your application here:
https://www.microsoft.com/en-us/store/b/home
2. Copy the URL and copy it here:
https://store.rg-adguard.net/7
3. You will need to find here the .appxbundle ARM and sometimes also the dependencies. Sometimes when you download the file it does not have the extension, so rename the file to .appx in the end.
4. Install first the dependencies then the application on the Surface RT
### How to install UWP applications - Using ARM RT App-Store ###
https://forum.xda-developers.com/windows-8-rt/rt-general/arm-rt-app-store-windows-10-rt-t4067813
Thanks @alexenferman
### Install/modify appx files to work with version 15032 ###
Download: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
https://forum.xda-developers.com/showpost.php?p=82029699&postcount=50
After i install the "InstallPolicy.cmd" and accpet the policy after reboot i get an error in the testing mode... Look slike the cmd gets some errors.
Driv said:
After i install the "InstallPolicy.cmd" and accpet the policy after reboot i get an error in the testing mode... Look slike the cmd gets some errors.
Click to expand...
Click to collapse
Did you start with the clean recovered 8.1? And also rebooted after disabling the UAC? Did not connect the new installation to the internet? And run the InstallPolicy.cmd as administrator?
Could you please verify that you executed all these steps, and maybe re-run them?
tobiasvanc said:
Did you start with the clean recovered 8.1? And also rebooted after disabling the UAC? Did not connect the new installation to the internet? And run the InstallPolicy.cmd as administrator?
Could you please verify that you executed all these steps, and maybe re-run them?
Click to expand...
Click to collapse
Oh no. Everytime I go into recovery and try to recover from the USB it just restart into recovery Mode. I can choosen to recover from Disk and USB but i cant chose for example the D:/ drive..
I just "cleaned" Windows rt without wiping data.
Driv said:
Oh no. Everytime I go into recovery and try to recover from the USB it just restart into recovery Mode. I can choosen to recover from Disk and USB but i cant chose for example the D:/ drive..
I just "cleaned" Windows rt without wiping data.
Click to expand...
Click to collapse
I first had the same problem. I booted the recovery mode (starting while holding screen-windows-button, vol up and press power), then "Use a device" and tried all the USB devices showing up until I was lucky it rebooted to a different recovery screen. As far as I remember this recovery from the USB drive had less options in the menu. There were indeed no clear options to select like D:/ or USB drive, SD card, SSD partition 1. Would have made it easier. So I would suggest to try all the options in the "Use a device" menu with the recovery USB inserted.
Can you please post a Screenshot or a photo of the Yoga running Windows 10?
Microsoft says that "Use a Device" will only reboot into recovery again... ?
Driv said:
Can you please post a Screenshot or a photo of the Yoga running Windows 10?
Microsoft says that "Use a Device" will only reboot into recovery again...
Click to expand...
Click to collapse
Surely, I've opened up "About PC" and 'msinfo32' and made a picture of my device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Also I've rechecked the recovery booting of the device:
First picture, Booting the device using the 'onboard' recovery (got to this screen using the windows 10 installation and rebooted to recovery menu (advanced startup), not so sure using volume up/windows still goes into recovery):
Click to expand...
Click to collapse
Second and third picture, a prompt for a keyboard layout when booting from the USB drive. In my case the 'correct' USB Drive to use in the previous recovery menu 'Use a device' was the one at the bottom right.
I used a USB drive with an indication LED so I could see when it was being read (also booting to the recovery took significantly longer)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ok..
After I "install" the install.wim and restart the Tablet after a sucessful 100% execute it starts to do an automatic repair and diagnostic.
Driv said:
Ok..
After I "install" the install.wim and restart the Tablet after a sucessful 100% execute it starts to do an automatic repair and diagnostic.
Click to expand...
Click to collapse
Isn't this the moment to edit the register and reboot again?
4. When restarting you will get an error popup: Press SHIFT+F10
-- This is the moment the drivers are no longer present and you will need the USB keyboard
5. Type Regedit and go to KEY_Local machine/SYSTEM/Setup/Status/ChildCompletion > setup.exe > Modify the value to "3"
6. Restart
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This is so cool. Thanks for the guide man.
BobbyJohnson69 said:
This is so cool. Thanks for the guide man.
Click to expand...
Click to collapse
Glad to see it works
Quick question, what did you do exactly to get internet access to the yoga 11 while no drivers where installed(when keyboard, wifi drivers etc. don't work)? Because to use a usb wifi adapter you'd need to install it's setup, which doesn't work because it's rt and it doesn't support it. So how did you exactly get internet access? Did your usb bluetooth adapter not need a setup? And also, do you know why usb tethering doesn't work? My only usb wifi adapter doesn't work because of the above reasons, so I tried tethering trough usb with my phone, but it would just show up as an unkown device with RNDIS as the name, and it wouldn't work(still no internet). Could you please help me out?
Anyparktos said:
Quick question, what did you do exactly to get internet access to the yoga 11 while no drivers where installed(when keyboard, wifi drivers etc. don't work)? Because to use a usb wifi adapter you'd need to install it's setup, which doesn't work because it's rt and it doesn't support it. So how did you exactly get internet access? Did your usb bluetooth adapter not need a setup? And also, do you know why usb tethering doesn't work? My only usb wifi adapter doesn't work because of the above reasons, so I tried tethering trough usb with my phone, but it would just show up as an unkown device with RNDIS as the name, and it wouldn't work(still no internet). Could you please help me out?
Click to expand...
Click to collapse
In my case the USB Bluetooth adapter just worked. I think another wifi adapter should also work. You need a device which works with the generic drivers which are included. I think USB tethering requires some drivers that are not included by default and therefore need windows update/an internet connection.
I suggest you try another USB Bluetooth/wifi adapter and maybe borrow one somewhere. You can also try to force install the generic driver on the wifi adapter you have laying around, it may work.. I have no hopes for USB tethering.
Hi again,
Thanks for your answer last time.
If it's no bother, could I ask which bluetooth/wifi adapter you used?
Anyparktos said:
Hi again,
Thanks for your answer last time.
If it's no bother, could I ask which bluetooth/wifi adapter you used?
Click to expand...
Click to collapse
Hello, I found myself that it is not actually necessary to buy an adapter. The Windows 8.1 recovery USB drive contains a Wi-Fi driver which works under Windows 10. The hardest part is installing it, though it's easiy if you're familiar with installing drivers under Device Manager.
Do as follows:
- Plug your Windows 8.1 USB recovery drive into your Lenovo Yoga 11.
- Take note of the drive letter that the recovery USB appears under (for example D:\)
- Open Device Manager.
- Look under the 'Other devices' tab. Try to find a device with a name suggesting it is a Wi-Fi adapter. I do not have on hand what it is supposed to be called right now. If you get stuck at this stage, let me know and I'll look further.
- Right click the device and click 'Update Driver Software...'
- Click 'Browse my computer locally for driver software'.
- In the search location type the location of your USB drive. For example if your drive is letter D:\ than type in D:\. You must make sure 'Include subfolders' option is ticked.
- Click 'Next' and the driver for Wi-Fi should be installed successfully if you chose the right device. If you choose the wrong one it's fine, just try again with the correct one.
Let me know how it goes...
Добрый день всем. Попал данный ноутбук в руки. Подскажите как его можно использовать для серфинга в интернете и офисной работы? Надо ли его прошивать на windows 10?
tobiasvanc said:
so my yoga 11 has been laying around for some years now and usage has been getting worse mostly because of the included, no longer supported, internet explorer.
But when i found that a working release of windows 10 arm32 for the surface rt was around, i decided to go rogue and install it on my yoga 11.
I adapted the tutorial by @kephax and @zaveraj to the needs of the yoga and added own experiences https://forum.xda-developers.com/windows-8-rt/rt-general/tutorial-install-windows-10-arm32-t4052035 https://forum.xda-developers.com/showpost.php?p=82022643&postcount=41
feedback and suggestions are always welcome
**working** windows 10 arm32 on lenovo yoga 11
as usual, disclaimer: For dead devices, the author is not responsible. Perform all actions at your own peril and risk. At the moment, the topic with flashing is young and everything is done manually. Perhaps later the process will be partially or fully automated. In the meantime ...
Let's go !!!
#
documents and instructions
1. Firmware is a potentially dangerous process and requires some accuracy. Always have a recovery disc on hand created from the official kit from microsoft!
2. In order to facilitate the installation process, in addition to the usb flash drive, you will need a usb keyboard and an usb bluetooth/wifi adapter.
3. Windows 10 on arm is basically functional. The drivers for surface 1 work fine, the bluetooth driver for surface 2 has some problems. The store mainly supports the installation of arm applications. Office 2013 is fully operational and even has a russian language pack.
4. The image is not meant for the yoga 11, therefore keyboard, sound, wifi, bluetooth, camera, touchscreen? Are not working in the installation process. After a 'magic' windows update in the end, they do work.
Downloads:
Own collection of files on mega, includes some scripts for easy installation and the steps numbered: https://mega.nz/folder/eb5zsrhs#r8pi0qtupqus4cxjmxmxrw
mega: https://mega.nz/#f!2ijldysl!1pgkdtllvhcpgtkwrzrysa
yandex: Disk https://yadi.sk/d/mncuegkwm1xtxa
baidu: https://pan.baidu.com/s/12uf6bq_vftcrkv_1gzgayq password:c7bf
create recovery drive using the existing windows rt 8.1 installation:
https://support.microsoft.com/en-us/help/17422/windows-8-create-usb-recovery-drive
1. Clear an usb drive (8gb+ advised)
2. Open 'create a recovery drive' on the windows rt installation
3. Follow the instructions on the screen
restore the laptop to version 8.1 according to this instruction :
1. Ensure that the yoga is completely turned off and connected to the charger. Connect the recovery disk to the usb port.
2. Press and hold the volume up and windows button on the screen. Press and release the power button.
3. Hold volume up and windows button until a black screen with a console like appearance appears, then you may release
4. When prompted, select english and a keyboard layout.
5. Select "troubleshooting", then select "recover from a drive", in my case the last usb device was the correct one, it may take some tries which one you need. If you are prompted for a bitlocker recovery key, select "skip this drive" at the bottom of the screen. Next, select “just remove my files” and the last “reinstall”. The laptop will go into reboot and recovery of clean 8.1 will begin.
Hacking secureboot
1. Turn off uac. Run the registry file - disabling_uac.reg and, after merging, restart the laptop.
2. Unmount the registry hive responsible for the bcd. Using a combination of win + r buttons, open the run window and enter regedit to open the registry editor. Select hkey_local_machine \ bcd00000000, and click "file" - "unload hive" ("file" - "uninstall hive")
3. Run the securebootpatch patch
open the "securebootpatch" directory. Run as administrator (right click) installpolicy.cmd, and then restart the laptop.
After the reboot, the secure boot debug policy interface will appear. Select "accept and install" to install the policy.
4. Turning on the test mode.
Run the command line and enter:
Bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
if there are no errors, restart the laptop and enter the recovery mode command line. Check the lower right corner of the screen for the words "secureboot is not configured correctly". If the inscription is present - continue (at the start of the winpe gui boot, it will blink and disappear under the background, will appear again at the command prompt).
-- i have to admit that i didn't check the secureboot, but it went well
deploying win10
1. From the last step, we are in winpe recovery mode:
Go to the command line: Select "troubleshooting", then "advanced options" - "command prompt". A request for a bitlocker recovery key should not appear.
2. Format drive c. Make sure that the commands are entered correctly and enter the next only if there are no errors in the previous one.
Enter
(a) diskpart
(b) list disk
(c) select disk 0
(d) list partition
(e) select partition 4
(f) format quick fs = ntfs override
(f) exit
3. Actually deploying win 10: The win10 deployment file suitable for your device (the surface rt one) should already be at the root of the flash drive. If not, rename it to "install.wim", and copy it to the root!
Enter:
Dism /apply-image /imagefile:d:\install.wim /index:1 /applydir:c:\
where: "d: \ install.wim" is the location of the deployment file from win 10, and "c:" is the system drive to which you are deploying.
Close the dialog after execution and restart the tablet.
4. When restarting you will get an error popup: Press shift+f10
-- this is the moment the drivers are no longer present and you will need the usb keyboard
5. Type regedit and go to key_local machine/system/setup/status/childcompletion > setup.exe > modify the value to "3"
6. Restart
note: I did not connect to wifi until sometime later, there is a firmware update that seems to mess up the ability to install appx files?
-- dont connect, for the above reason, a connection is however needed later on for the drivers.
### 2.1. How to activate windows
1. Powershell
slmgr.vbs /upk
slmgr /ipk nppr9-fwdcx-d2c8j-h872k-2yt43
slmgr /skms kms.03k.org
slmgr /ato
slmgr /skms zhang.yt
### 2.2 install runtime
if using my collection; it is possible to execute: Install.ps1 (may need to do so several times to make sure everything installs with the dependencies)
1. Copy appx1 from recovery usb to desktop
2. Desktop\appx1\appx1.ps1 > right click > run as administrator
3. Restart
--install appx files from framework folder
4. Desktop\appx1\appxbundle.ps1 > right click > run as administrator
5. Restart
6. Install:
Microsoft.windowsstore.appxbundle
microsoft.net.native.framework.1.1.appx
microsoft.net.native.runtime.1.1.appx
## 3. After installation ##
1. Install all apps/dependencies/framework you can that are included, at this stage the laptop accepts most.
2. Insert usb wifi adapter or usb bluetooth adapter
3. Connect to wifi or bluetooth (i used bluetooth tethering on my phone)
4. Run windows update and hear all the devices get installed.
### how to remove expired version popup ###
1. Go to c:\windows\system32
2. Right click on licensingui.exe > properties > security > advanced
-- guys, the file you have to rename for getting rid of the warning is not "logonui.exe", the guide is wrong. The right file is "licensingui.exe". -- thanks kiba85
3. Ower > change
4. Enter your username > check names
5. Give the group users or administrators full control
6. Close all dialog boxes
7. Now rename the file to logonuibak.exe
if it doesn't work; boot using the usb recovery, open command promt, navigate to c: Windows system32 and use the command "rename licensingui.exe licensingui.exe.bak
### how to change the language to english (and remove chinese) ###
start > settings > time & language > region & language
remove chinese and set english as default
### how to install ublock origin on edge ###
-- not so sure this works at the moment
1. Download this: https://github.com/nikrolls/ublock-edge/releases (i was able to install 1.12.0, but it made my edge unusable)
2. Edge > about:flags
3. Select: "enable extensions developer features"
4. Select the "..." > extensions > load extension
5. Select the folder with ublock origin (this should be on the surface itself)
### how to install uwp applications - manually ###
1. Find your application here:
https://www.microsoft.com/en-us/store/b/home
2. Copy the url and copy it here:
https://store.rg-adguard.net/7
3. You will need to find here the .appxbundle arm and sometimes also the dependencies. Sometimes when you download the file it does not have the extension, so rename the file to .appx in the end.
4. Install first the dependencies then the application on the surface rt
### how to install uwp applications - using arm rt app-store ###
https://forum.xda-developers.com/windows-8-rt/rt-general/arm-rt-app-store-windows-10-rt-t4067813
thanks @alexenferman
### install/modify appx files to work with version 15032 ###
download: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
https://forum.xda-developers.com/showpost.php?p=82029699&postcount=50
Click to expand...
Click to collapse
подскажите,какие файлы восстановления вы использовали? потому что в леново 8.0, а не 8.1?
upd. всё получилось,чтобы поставить драйвер сети надо распаковать wim файл и установить по инструкции. Кстати надписи что secureboot отключен не было
Guys I don't get a lil which one of install.wim do I need to use - from Surface 1 or Surface 2? In archive it both present.
hooddy said:
Guys I don't get a lil which one of install.wim do I need to use - from Surface 1 or Surface 2? In archive it both present.
Click to expand...
Click to collapse
See https://mega.nz/folder/eB5zSRhS#r8pI0QtUPQUS4cXjMXmXRw
Surface 1
I dont get on which stage I need to doing Hack SecureBoot steps - after boot into Windows environment or within recovery environment?

Categories

Resources