I have an old Surface 2 RT from my parents here, which I wanted to rejuvenate for my kids. I had reset it to the factory settings, but that process failed and the device ended up not booting anymore. Using some command line wizardry with dism, booted from USB, I was able to get Windows 8.1 back on the device. Because I was already working on it, I wanted the put Windows 10 on it, using this guide.
Step 1 went fine - I downloaded the recovery image
Step 2 - installing patched Windows RT image went fine too
Step 3 is where issues began
I was able to execute the "disabling UAC" step
When installing the secure boot policy and rebooting, I got an error that the secure boot policy could not be installed.
Because of this, I executed this step - by changing some files on the EFI partition
Now the device does not boot anymore because of error 0xc0000225 by which it cannot find "winload.efi" or it contains errors. Pressing the "WINDOWS KEY=recovery" it says the same error code but with a different description "A required device isn't connected or cannot be accessed". Eventually it reboots on its own and shows the error again, after the Surface boot logo.
I'm trying to follow the troubleshooting steps but the tablet does not boot from USB (anymore)
I properly safely eject the FAT32 formatted GPT partitioned USB drive of 4GB. I also tried a different USB stick of 8GB.
I use the volume down method in an attempt to get it booting, however, it always ends up at the same message. It does read the USB drive, because the light flickers a bit, but it doesn't act on it.
I cannot boot to UEFI either: I press power and volume up - it does not turn on. I am able to turn it on without the volume up button pressed however - but it does not boot of course.
My feeling is that it has forgotten that it needs to boot from USB, but I can't access the UEFI settings either. Besides, it often needs the "10 seconds power button" trick to even turn on.
What steps can I follow to at least get some more life out of it - or is it completely crapped out?
That EFI modification is for booting Windows 10 only, won't work if you have 8.1 installed instead of 10, to do the unlock you must not enter a Microsoft account or do any upgrade.
The Surface RT and 2 are very finicky about what USB they want to boot from power off, basically I have over 10 USB sticks, among which 4 are 4GB or smaller, the Surface RT and 2 only boot from one of them, which is a no brand Chinese one as well.
So basically just get the recovery image from Microsoft then try a lot of sticks till one boots.
Okay, I guess I need to scavenge some USB sticks
Use a SanDisk Ultra 3.0 drive. Worked best for me on my 1st and 2nd gen Surface RTs. Regular cruise gilded work fine, but the ultra 3.0 is better since it has better transfer rates and whatnot.
I only have three: a cheap marketing one of 4GB, a USB stick with SD card slot, and a 2GB one
But the weird thing is that I also had some connection issues in Windows itself, when it still was working. The USB sticks rapidly connected/disconnected sometimes - but I did not have this issue with the USB keyboard I plugged in. Still, perhaps the USB port is busted.
Related
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk
CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.
slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium
try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.
To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.
THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.
Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
In order to fix this soft-brick I first tried to use recovery by pressing VOL - & POWER. In the menu, I could select and confirm to recover to factory settings, but after some seconds the boot loop appeared again with (seemingly?) no change having been made. The error kept appeaing over and over again.
After trying recovery mode, I attempted to start the phone in download mode by pressing VOL + on the (switched off) phone and connecting a USB cable. The respective menu also opened, here, showing "Firmware Update" and "Do not unplug the USB connection until the process is complete". According to many tutorials I found on the internet, when having installed the required drivers (I used LG United Mobile drivers from here), this procedure should allow you to flash a recovery image through LG's flashing tool (which one can also find on that page).
However, when I connect the LG G3 (D855) to a computer the driver is installed on, there is no new device shown in the Device manager. I tried this out with Windows 10 x64 and Windows 7 x64 and disabled driver validation on both systems and enabled test signing on Windows 10, respectively. Additionally, I followed these instructions, but in this case the screen stays dark and the device is not detected either. It seems like there are not so many people experiencing this error, but I hope we can find a solution.
nVentis said:
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
Click to expand...
Click to collapse
This may sound like a dumb question, but have you tried a new battery yet? If it is one of the original batteries it could have gone bad & started bootlooping...like mine did a few months ago.
As far as the PC not recognizing the phone you can try downloading USBDeview and uninstall anything that has the vendor ID's of 1004 & 18d1(pretty much anything that says android or LGE in the description) & reboot the PC. Hopefully it'll recognize your device and install the drivers the next time you plug it in. If it doesn't find the drivers automatically for you then install LG drivers manually.
Link for usbdeview: http://www.nirsoft.net/utils/usb_devices_view.html
Link for LGE drivers: http://www.lg.com/us/support/software-firmware-drivers
Good luck :fingers-crossed:
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.
So I've recently experienced some problems booting with my Xtrons TQ709IPL, so I thought I would share the method I used to fix it. This will probably work with other Xtrons devices (especially TE706PL since it just seems to be a TQ709IPL that comes with Android 10-- which oddly my TQ709IPL did as well when it was supposed to come with 9.0) and possibly other non-physical/touch button head units with similiar setups. This method is based on a post by @marchnz found here: [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933[/URL] but fine-tuned to Xtrons unit.
To Preface this, I was unable to find the correct method to boot directly into recovery mode from RST. If anyone knows how on this unit, it'd be appreciated if they could share.
Beyond that, this also works if your device doesn't boot at all but the hardware buttons still react to RST being held in-- this will probably be due to a bad boot.img flash.
Required items:
Rockchip Head Unit with USB Port that can be recognized
Computer with Windows or Linux
USB-A to USB-A (or USB-C if your computer has the port)
Small pin, screwdriver-- something to push in the rst button
Rockchip Drivers and Android Tools: [url]https://github.com/rockchip-linux/tools[/URL]
ROM for your device in .img format: [url]https://yadi.sk/d/umCvHqCDzHccr[/URL]
Steps:
Install Rockchip Drivers and launch RKDevTool.
Plug Computer/Laptop into the Head Unit's Yellow USB-A port (this might be different on other models-- just try each out after doing the next step if it doesn't recognize your device)
Use a pin/small screw driver/etc to push in the RST button.
Hold button down until panel lights flash then stop pressing for about a second before pressing in again and holding (this should be done before the splash screen shows).
- If you did this successfully, your computer will now recognize your device in Maskrom mode. RKDevTool should show that a device is found.
Move over to the "Upgrade Firmware" tab and click firmware.
Select the .img file for your device.
Then click the "Upgrade" tab when the firmware has loaded.
- MAKE SURE YOU DO IT FROM HERE INSTEAD OF TRYING TO FLASH INDIVIDUAL IMGS IN THE "DOWNLOAD IMAGE" TAB! This caused my unit to not boot after I flashed the boot.img of my current firmware to it. Luckily, I was still able to get into Maskrom mode. So if you really want to try, make sure to use caution using that method!
It should now start flashing the firmware.
When it finishes, it should be recovered.
- Though, it failed and booted to recovery on mine once.
Done.
Hopefully, this will be of some use to some of you.
iamrance.asa said:
So I've recently experienced some problems booting with my Xtrons TQ709IPL, so I thought I would share the method I used to fix it. This will probably work with other Xtrons devices (especially TE706PL since it just seems to be a TQ709IPL that comes with Android 10-- which oddly my TQ709IPL did as well when it was supposed to come with 9.0) and possibly other non-physical/touch button head units with similiar setups. This method is based on a post by @marchnz found here: [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933[/URL] but fine-tuned to Xtrons unit.
To Preface this, I was unable to find the correct method to boot directly into recovery mode from RST. If anyone knows how on this unit, it'd be appreciated if they could share.
Beyond that, this also works if your device doesn't boot at all but the hardware buttons still react to RST being held in-- this will probably be due to a bad boot.img flash.
Required items:
Rockchip Head Unit with USB Port that can be recognized
Computer with Windows or Linux
USB-A to USB-A (or USB-C if your computer has the port)
Small pin, screwdriver-- something to push in the rst button
Rockchip Drivers and Android Tools: [url]https://github.com/rockchip-linux/tools[/URL]
ROM for your device in .img format: [url]https://yadi.sk/d/umCvHqCDzHccr[/URL]
Steps:
Install Rockchip Drivers and launch RKDevTool.
Plug Computer/Laptop into the Head Unit's Yellow USB-A port (this might be different on other models-- just try each out after doing the next step if it doesn't recognize your device)
Use a pin/small screw driver/etc to push in the RST button.
Hold button down until panel lights flash then stop pressing for about a second before pressing in again and holding (this should be done before the splash screen shows).
- If you did this successfully, your computer will now recognize your device in Maskrom mode. RKDevTool should show that a device is found.
Move over to the "Upgrade Firmware" tab and click firmware.
Select the .img file for your device.
Then click the "Upgrade" tab when the firmware has loaded.
- MAKE SURE YOU DO IT FROM HERE INSTEAD OF TRYING TO FLASH INDIVIDUAL IMGS IN THE "DOWNLOAD IMAGE" TAB! This caused my unit to not boot after I flashed the boot.img of my current firmware to it. Luckily, I was still able to get into Maskrom mode. So if you really want to try, make sure to use caution using that method!
It should now start flashing the firmware.
When it finishes, it should be recovered.
- Though, it failed and booted to recovery on mine once.
Done.
Hopefully, this will be of some use to some of you.
Click to expand...
Click to collapse
Please help, I'm about 2 seconds from getting a new HU...
I also have the Xtrons TQ709IPL. I installed the drivers, but no matter what I do, when I finally get the HU into the correct mode, the USB insertion noise happens but then windows tells me that the device failed to install correctly. I also am unable to manually install the driver. This was on Windows 10, but I also tried it on Windows 8.1 and Windows7 all with the same results.
I must be doing something different than you, but I followed your instructions?
Ok, my USB cable was too long, I was using an extender to get to my laptop on my workbench from my car. If anyone else has this problem, make sure your USB cable is short. I am in now!
Next question, I have the TQ709IPL just like you. So which ROM do I need from the link you provided?
Hello! Last week I bought used Surface RT 64 Gb Model: 1516 with next problem:
BSOD
RecoveryYour PC needs to be repaired.A required device isn't connected or can't be accessed.Error code: 0xc000000fYou'll need to use the recovery tools on your installation media. If you don't have anyinstallation media (like a disc or USB device), contact your system administrator or PC manufacturer.
If I try to press the Windows key to "try again", I get:
BSOD
RecoveryYour PC needs to be repaired.Windows cannot verify the digital signature for this file.File: \WINDOWS\System32\winload.efiError code: 0xc0000428
You'll need to use the recovery tools on your installation media. If you don't have any
installation media (like a disc or USB device), contact your system administrator or PC manufacturer.
I've tried download the Recovery Image from Microsoft for my Surface RT (using serial number). Use official manual for creating Recovery USB (format flash in FAT32 and copy files from downloaded archive, Press Volume- & Power Release & Release Volume- after Surface logo shown). Trying to boot from USB - nothing happen, I got BSOD! Trying to enter UEFI/BIOS (Press Volume+ & Power Release & Release Volume+ after UEFI/BIOS shown) - nothing happen, I got BSOD! Everytime I got same errors: first 0xc000000f and 0xc0000428 after pressing Win Key.
I use different Recovery Images for different regions with Win 8.0RT and Win 8.1RT, find & download ready custom images and trying to boot from... Use USB flash-drive 2.0 and 3.0 (different sizes 8 Gb, 32 Gb)
The tablet does not respond to connected USB flash-drive (but USB port is Ok). I've tried to boot from MicroSD :/ And nothing again!
I am tired please help me to solve this problem
silkway said:
Hello! Last week I bought used Surface RT 64 Gb Model: 1516 with next problem:
BSOD
RecoveryYour PC needs to be repaired.A required device isn't connected or can't be accessed.Error code: 0xc000000fYou'll need to use the recovery tools on your installation media. If you don't have anyinstallation media (like a disc or USB device), contact your system administrator or PC manufacturer.
If I try to press the Windows key to "try again", I get:
BSOD
RecoveryYour PC needs to be repaired.Windows cannot verify the digital signature for this file.File: \WINDOWS\System32\winload.efiError code: 0xc0000428
You'll need to use the recovery tools on your installation media. If you don't have any
installation media (like a disc or USB device), contact your system administrator or PC manufacturer.
I've tried download the Recovery Image from Microsoft for my Surface RT (using serial number). Use official manual for creating Recovery USB (format flash in FAT32 and copy files from downloaded archive, Press Volume- & Power Release & Release Volume- after Surface logo shown). Trying to boot from USB - nothing happen, I got BSOD! Trying to enter UEFI/BIOS (Press Volume+ & Power Release & Release Volume+ after UEFI/BIOS shown) - nothing happen, I got BSOD! Everytime I got same errors: first 0xc000000f and 0xc0000428 after pressing Win Key.
I use different Recovery Images for different regions with Win 8.0RT and Win 8.1RT, find & download ready custom images and trying to boot from... Use USB flash-drive 2.0 and 3.0 (different sizes 8 Gb, 32 Gb)
The tablet does not respond to connected USB flash-drive (but USB port is Ok). I've tried to boot from MicroSD :/ And nothing again!
I am tired please help me to solve this problem
Click to expand...
Click to collapse
Hi I have same problem and have tried everything you have did you fix it
There is a bare metal recovery guide here:
Bare Metal Recovery - Windows
Resetting a Windows RT device using a recovery image
jwa4.gitbook.io
The device is not bootable from SD and it will only boot from USB if holding volume - while powering on.
jwa4 said:
There is a bare metal recovery guide here:
Bare Metal Recovery - Windows
Resetting a Windows RT device using a recovery image
jwa4.gitbook.io
The device is not bootable from SD and it will only boot from USB if holding volume - while powering on.
Click to expand...
Click to collapse
Thanks buddy I will give it a go