jjoubert327
New Member
- Joined
- Aug 29, 2016
- Messages
- 6
- Reaction score
- 0
I may have deleted the wrong partition I used partition-tool, tool said it was busy deleting partition I am now stuck on recovery page with error code 0xc0000225 any help please
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I may have deleted the wrong partition I used partition-tool, tool said it was busy deleting partition I am now stuck on recovery page with error code 0xc0000225 any help please
Does this mean that the tablet is now worthless or is there a way I could still fix it ?
There should be links on this thread where you can download the recovery drive, think it's a page or two back.
Ok, uploaded all the files from the recovery drive to http://1drv.ms/1N7VLM4
Work fibre ftw!!! Hope it can help
I'm being extra paranoid this time, going to Clonezilla the whole hdd to usb also just in case tonight before installing Win 10.
Device.Okay managed recovery, now I used my Windows credentials, is that Windows 10 update tied to the device or the account?
Bought a decent otg hub for R139 from Takealot btw
One in the titleDevice.
Tbh, I keep my tablet in the case and there isn't a scratch on it.
Very important do not keep the keyboard in the case with it, caused scuff marks on the screen when I had the screen protector on.
The one the tablet came with.Could you please post a pic of your case?
Touch has been a running issue for me and since I'm travelling more now would like to dev without taking my laptop.
The one the tablet came with.
Yeah the keyboard comes out.So you just removed the keyboard?
Turns out that the touchscreen driver installation process was slightly more involved than simply telling Windows to use a certain INF file. There's also "Touchsetting.gt" and "GT912_1040.BIN" that needs to be copied into your windows\INF folder.
I also don't think installing the drivers via the Device Manager works as it should, so you have to use something like devcon.exe.
I've managed to bundle all the original files and script this process, in case anyone still needs these drivers. Tested it on a squeaky clean Windows 10 Anniversary Edition install and it works on my machineTM. Obviously you'll still need a OTG/Bluetooth mouse/keyboard to be able to log in and run this batch file (install.bat).
https://1drv.ms/u/s!Atqf9izYEbXKh6soSvO0OgHn6rM04w
My Bluetooth keyboard that came with the device was stolen. I have wired keyboard, dodgy Bluetooth mouse. Is that adequate to regain touch after clean install of Win10?
Or else is it possible to upgrade from 8.1 to win 10 anniversary ( not clean install) to avoid losing touch?