yashsingh1/xdaforums huggingface dataset:
[Windows RT General] dalexop:
VivoTab RT Blue Screen of Death Post 8.1 Patching

+++++ This is for a VivoTab TF600T +++++

First off, major thanks to APATCAS for posting this thread, it is the best help for those of us with VIVOTABs I've found so far. Your Image was priceless in providing a Recovery environment for those of us that were foolish enough to avoid making a Recovery USB. :crying:

Also a big thanks to Chathu60, your article gelled the approach and helped get me closer than I've been since mid December.

I started with a Reboot in December after a regular Windows Update Patch pack for 8.1

This immediately resulted in the BSOD and " Error Code 0xc0000001 "

"You'll need to use the recovery tools on your installation media "

After several weeks I found the image that Apatcas posted and it provided me the ability to boot the device into the Windows Recovery Environment. !

Next I tried many command line executables and GUI repairs as well with no positive results.

Where am I at now ?

1) I used Chathu60's approach for DISM to apply the image to the C:|Windows Partition.

- When I reviewed the contents after the image was set, I notice that all files are dated 2012 therefore figured this is a Windows 8.0 image. Major difference ! When I tried the "Reset your PC" option in WinRE I noticed it was no longer a Win 8.1 image, and instead reads Windows RT ( Great News There )

2) Now that I know that it's a Windows 8 RT C:\Windows image, I tried the BootRec Options.

BOOTREC /FIXMBR

BOOTREC /FIXBOOT

BOOTREC /SCANOS

BOOTREC /REBUILDBCD

The first two always work. the Second two never do, they always result in 0 Windows Installations Found.

3) So I thought why not copy the BCD file from the newly imaged C:\Windows\Boot\DVD\EFI directory to the (Boot System Partition) \EFI\Microsoft\Boot directory.

Once I did this, I reran the Bootrec Commands and amazingly, the first three worked.

Yes, the SCANOS finally resulted in 1 Windows Installation Found C:\Windows

I then tried BOOTREC /REBUILDBCD , it came back:

It sees the 1 windows installation in c:\windows

Add the installation to the boot list ? Yes (Y) / No (N) / All (A): a

Which results with:

"The system cannot find the file specified ."

This is where I am stuck right now.

When I do this, ' Reset your PC + Fully clean the drive " now runs fine, Reboots, then results in the error:

Error Code 0xc0000001

Multiple tries, yada yada ...

What "File" does Bootrec / rebuildbcd look for ?

is there another spot on the Windows Partition where the BCD lives ?

Perhaps somewhere else on the System partition ?

I feel like I am soooooooo Cloooooose !!!!

*** Quick observation: If the image replaced the Windows Partition, how would the System Partition be reset back to the pre Win 8.1 environment ? Perhaps I need to replace more than just my BCD file on the EFI boot disk !

ps.

I left my Disk Partitions alone as they all seem OK ( See Disk Details in attachment )
[Windows RT General] fenohavana:
That s exactly what happened with me.
[Windows RT General] dalexop:
VivoTab RT Blue Screen of Death Post 8.1 Patching

I found the answer to my last question.

" What placed the files in the system partition ? "

This is what I ran for my Vivotab:

BCDBoot c:\Windows\Boot\EFI /s E: /f UEFI

( Note there are two things I had to do to make this work )

1) Assign a drive letter to the System Partition via DiskPart )

2) Copy the BCD file from the image to Windows\Boot\EFI

Once you delete the System Partition and recreate it, it will be empty. I executed BCDBoot and it populated all directories and files.

Now I always see "1 Windows installation" when I run Bootrec /scanos or Bootrec /RebuildBCD

My last isssue ?

Windows does not boot and remains with the same error code from the very beginning.

I continue to see the " The system cannot find the file specified" error when running Bootrec / RebuildBCD

In fact after that error occurs, the BCD file located on the System Partition becomes 8 K in size, which represents an empty store.

More testing....

One lesson that was surprising was:

I decrypted my Install.esd file on my Recovery partition, turned it into a Windows 8 RT ISO, put it on a USB stick and started the Windows 8 Setup.exe. It ran normally and immediately asked me for the Activation key.

Since I do not have a Software Hive from my original Windows 8 RT environment, I tried pulling the license key from the APATCAS image. ( Which I did ). I input this license and it did not work. I gather that each Vivotab has a separate license encrypted in the firmware. :(

So a clean install is out of the question...

The only thing left to try would be to completely wipe the Tablet and follow Chathu60's directions.

( Or become a BCD guru LOL )
[Windows RT General] dalexop:
VivoTab RT Blue Screen of Death Post 8.1 Patching

Hi Folks,

I looked deeper into mt BCD store and discovered the following:

1) When I toasted my C Partition and replaced it with the contents of the Apatcas Vivotab image, it overwrote my BCD file as well as the BCD-Template file. ( To be expected )

What I now realize is that this image is a WIN PE image and the contents of the BCD store within this image is solely Win PE. I now had no BCD Store info for Windows RT on the TF600T.

Luckily I saved all my versions of BCD stores on the System partition back to December.

( System hidden partition ) \EFI\Microsoft\Boot

The Apatcas Vivotab Image BCD store is around 230 k in size, which is odd given the relatively small content. My original BCD store was 56 k in December. When I looked at it via BCDEdit /Store PathtoBCD \Enum all, I immediately saw the references to my Boot Manager, Windows Loader, EMMC, etc etc. The issue with this BDC was that the Device definition was set to Unknown. Therefore it would never allow the system to boot.

For Example: the Boot Manager should have looked like this:

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

My Copy had the word " unknown " in the Device line.

( Exactly the same problem with the Windows Loader )

So I used the following command to fix it :

Bcdedit /set {bootmgr} partition=\Device\harddiskVolume2 ( I found this via DiskPart )

and

Bcdedit /set {Default} partition=C: ( Default is the header documented within the BCD File, seen via BCDEdit /Store C:\Windows\Boot\EFI\BCD /Enum all )

The following is what is should look like. ( My version had the word unknown instead of Partition=C: )

Windows Boot Loader

-------------------

identifier {9f25ee7a-e7b7-11db-94b5-f7e662935912}

device partition=C:

path \Windows\system32\winload.efi

description Microsoft Windows Server 8

locale en-US

inherit {bootloadersettings}

osdevice partition=C:

systemroot \Windows

Once I fixed this issue, I saved a copy of the new BCD file.

Then I ran : BCDEDIT /store c:\windows\boot\efi\bcd /enum to make sure it was still good.

I copied this version over to my System Partition under \EFI\Microsoft\Boot and now I had two BCD stores that matched.

I ran BootRec /Scanos and it was successful, seeing one Windows Installation in the C: drive.

I then ran Bootrec /RebuildBCD. it saw one Windows installation on the C Drive.

It finally ran successfully without the " Cannot Find the Specified File "

My BCD Store is now fixed.

When I reboot the Tablet, I am back to my very original issue, which is it boots to the Win 8 rotating circles then craps out with the 0xc0000001 generic error.

More on the testing of the Apatcas Recovery Image vs the Full German Image posted in this Thread.

*** Hi Folks, apologies for jumping around so much in this submission. I am going to re-write it tonight to describe the problem statement, what I did to find root cause, and what finally worked *** It's so important to help each other ! ****
[Windows RT General] fenohavana:
I spent many days on trying to resolve this issue and I used all recovery images that can be found on the Internet including for surface rt. I also bought an another vivotab with rt.8.1, captured its image, applied it after to the broken device but still no luck. I really hope you will go through to this issue because I gave up. Sorry for my bad English.

---------- Post added at 03:33 PM ---------- Previous post was at 03:28 PM ----------

http://xdaforums.com/showthread.php?t=2350875

disk wiped clean - won't allow me to recover

This thread contains also many information that can help.
[Windows RT General] dalexop:
Vivotab Recovery Image

Hi Folks,

I looked into the Windows Assessment and Deployment Kit for Windows 8.1

This kit publishes the following two tools for Image Management:

COPYPE and MakeWinPEMedia

These two tools are stated to work with the ARM architecture.

( http://https://technet.microsoft.com/en-us/library/hh825071.aspx )

However, they are missing the necessary Folder Structures to build the actual deployment package.

Has anyone found a version that works with ARM ??

Thanks

---------- Post added at 08:35 AM ---------- Previous post was at 08:27 AM ----------

Hi there Fenohavana,

Can you please send me or post your BCD file ?

( This is located in the C:\Windows\Boot\Microsoft\EFI Folder )

Also, in the C:\Windows|System32\LogFiles\ folder, you'll find a file called BCDinfo.txt. Can you please post that too ?

If you have an RT 8.1 working system, please use that one.

I've found that now that I have my system back to the original problem ( Windows 8.1 Patch 0cx0000001 error ) my BCD file has many iterations of "Unknown" device definitions.

I'd like to clean that up before making any further changes.

Thanks
[Windows RT General] fenohavana:
Hello,

These are the files that you asked,

Good luck
[Windows RT General] fenohavana:
This is the srtTrail.txt file after I tried autorepair

Startup Repair diagnosis and repair log

---------------------------

Number of repair attempts: 1

Session details

---------------------------

System Disk = \Device\Harddisk0

Windows directory = C:\windows

AutoChk Run = 0

Number of root causes = 1

Test Performed:

---------------------------

Name: Check for updates

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

---------------------------

Name: System disk test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

---------------------------

Name: Disk failure diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 15 ms

Test Performed:

---------------------------

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

---------------------------

Name: Target OS test

Result: Completed successfully. Error code = 0x0

Time taken = 16 ms

Test Performed:

---------------------------

Name: Volume content check

Result: Completed successfully. Error code = 0x0

Time taken = 109 ms

Test Performed:

---------------------------

Name: Boot manager diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 47 ms

Test Performed:

---------------------------

Name: System boot log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

---------------------------

Name: Event log diagnosis

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

---------------------------

Name: Internal state check

Result: Completed successfully. Error code = 0x0

Time taken = 0 ms

Test Performed:

---------------------------

Name: Boot status test

Result: Completed successfully. Error code = 0x0

Time taken = 16 ms

Test Performed:

---------------------------

Name: Setup state check

Result: Completed successfully. Error code = 0x0

Time taken = 297 ms

Root cause found:

---------------------------

Failure while setup is in progress.

---------------------------

---------------------------
[Windows RT General] dalexop:
Vivotab Recovery Image

Perfect !

Your 8.1 BCDInfo.txt file is much cleaner than mine.

Explains why I see what I do in my recovery console and why the recovery images are not working.

Once I make these changes, hopefully I'll see a significant difference.

If so, then we'll take a look at your dead VivoTab too.

Say, on that Tab, did you toast all the partitions ?

Is there any chance that you saved a BCD and BCDinfo.txt from that Tab before applying other images ?

Thanks

---------- Post added at 02:44 PM ---------- Previous post was at 02:34 PM ----------

Amazing, this is identical to mine !

I suspect that when your Tab boots, you see the rotating circles for a while correct ?

This aligns with what we see in the SRTTrail file, that is, the boot sequence doodles along...

Do you still have your recovery partitions on the wrecked Tab ?

I'm trying to get mine to work in order to re-link the boot process...

Thanks
[Windows RT General] fenohavana:
No. I don't have the original recovery partition anymore. I ve already cleaned all volume on the disk. I suspect problems of drivers but I don't know what to do.

---------- Post added at 10:05 PM ---------- Previous post was at 09:57 PM ----------

Yes. There is a rotating circle when it boots. Then it fails one time. Reboots again before displaying the error.

It worked well before the update to 8.1

---------- Post added at 10:23 PM ---------- Previous post was at 10:05 PM ----------

If you want to try others recovery images but they don't boot on your tab, just replace the boot.wim file with the file in the Atpactas recovery and it will boot. That was how I did to try many of them.

The boot.wim is hidden file in the sources folder.
[Windows RT General] dalexop:
Vivotab Recovery Image

Hey there Fenohavana.

Our SRTTrail.txt files are identical.

The error is " Failure while setup is in progress"

Which means " The computer does not start due to a failed Windows installation process."

I am completely confused how this is possible given the Windows partition has been blown away, recreated, then re-imaged using Windows RT. ( Along with the UEFI System Partition too )

So, there remains something from the 8.1 upgrade creating problems for us.

I am not finished cleaning up my BCD Store.

Last night I updated all Devices to point to the appropriate drives.

This has made no change in behavior.

The BCD Store is the main link between the UEFI system and the Windows Boot process. In fact it defines what happens and when it happens.

The sequence is struck in this file.

The fact that the BCD store is messed up in the Apatcas image is challenging.

Compounding this is the fact that I can't quickly whip up a bootable RE image using PE.

I still have my two in-tact Recovery Partitions so I really want to figure out how to get to Win RE from the Tab's disk partition.

You have a few interesting characters in your BCD file. I don't know whether they are due to the language ( You are running ja-jp ) or whether it's corrupted. Ir certainly helps to have a comparison.

:)
[Windows RT General] fenohavana:
The characters are probably due to Japanese language. The system is Japanese and English system language was added after update.

---------- Post added at 11:53 PM ---------- Previous post was at 11:40 PM ----------

I think that the process of upgrading rt 8.0 to 8.1, which has failed, has modified something stored in another memory than the hard-drive. I am not sure but it could be the bios for example. So if it can be reinitialized, it would solve the problem.
[Windows RT General] dalexop:
Vivotab Recovery Image

Hi there Fenohavana.

I've loaded Visual BCD onto one of my Win 7 machines to start looking deeper into the files.

It certainly provides a very different view into these binary files.

I have attached a Screenshot of your BCD.

You'll notice that your screenshot shows the only loader currently registered is Windows Setup.

That will certainly do it !

Visual BCD also proved that my own BCD is missing important linking information between objects.

I am going to try to build a new one, however, I don't think my BCD-Template file is good. ( The one from the Image )

Do you have a working copy ?

Also, did you post your good-known working copy of your BCD & BCDinfo.txt or the messed up one ?

I am now convinced this is our issue.

Does anyone out there have a BCD from a ASUS TF600T Win 8 RT system ???

Thanks

p.s. I did manage to delete one of 3 instances of the "NVidia EMMC Boot" recovery image from my BCD. I immediately noticed that the third emmc icon was no longer present in my Windows 8 Boot Manager GUI. ( Use a Device )
[Windows RT General] fenohavana:
Hello,

The files were from the working device running windows rt 8.1

I also searched all BCD file on that working device including on the EFI partition. Please find them here with the BCD-Template file (also from the windows rt 8.1)
[Windows RT General] fenohavana:
A very bad new for my broken device. I entered into recovery as usual, run the command diskpart and clean the disk 0. I didn't do the repartition before restarting and now it can t enter into recovery any more. I think this is the end for it. See attached the screen :(
[Windows RT General] bootleg16:
Anyone has a download for Windows RT 8.1 for VivoTab TF600TL?

hello, i have a bunch of VivoTab TF600TL that i need to be fixed, i was wondering if anyone has a image Recovery file that included the 8.1 update

thanks
[Windows RT General] dalexop:
Recovery Image for the VivoTAB RT

HI Fenohavana,

I double checked the Apatcas image and the BCD file only set's up a Windows RE boot.

That is, it first it creates a RAM drive, which is X by default, then it loads the contents of it's RE image there.

When you Boot from this USB drive, it never looks at the SSD at all.

The only thing it allows you to do is a thin set of executables in the Ram Drive and that's it.

So it should always boot regardless of what you have done to your SSD.

I am stripping the image down as much as I can so that it boots with a 4GB stick.

Once I've got that working, I'll post for you to try.
[Windows RT General] dalexop:
VivoTAB RT Recovery Image

Hi Fenohavana,

Can you please try the attached RE Image ?

It's small and fits easily on a 4 GB Stick.

I tested it tonight and it works well.

Just remember you need a bootable stick with a GPT partition, FAT32 FS.

https://drive.google.com/file/d/0B0c91zNa0RbqOWFzTENET2IwOGc/view?usp=sharing

** Note I edited my BCD file on the System Drive Partition and promptly killed the Tablet entirely. In fact, it hung on the ASUS Logo black screen ! I was still able to boot USB using this image. So the System Partition does not need to be there for a USB boot **
[Windows RT General] fenohavana:
Hello. I will try it when I arrive at home. I have a 4gb usb drive. I will format it to fat32 file system and copy your file into it. Thank you. I will report after.
[Windows RT General] fenohavana:
Hello, I ve tried the image file and it works fine. I can boot the device using it.

Using the following script, I partitioned the ssd

select disk 0

convert gpt

create partition primary size=450

set id=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

gpt attributes=0x8000000000000001

format quick fs=ntfs label="Windows RE tools"

assign letter=T

create partition efi size=200

format quick fs=fat32 label="System"

assign letter=S

create partition msr size=128

create partition primary

shrink minimum=4200

gpt attributes=0x0000000000000000

format quick fs=ntfs label="Windows"

assign letter=W

create partition primary

set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

gpt attributes=0x8000000000000001

format quick fs=ntfs label="Recovery image"

assign letter=R

rescan

exit

I applied install.wim using dism

run bcdboot c:\windows and there was BFSVC warning

run the command bootrec /rebuildbcd but it didn t find any windows installation

When reboot, I found new error message 0x0000005C

Please find attached pictures of the process
[Windows RT General] dalexop:
Vivotab Recovery Image

Awesome, this is the error that I received as well thanks to the BCD in the image.

The reason is, we are not using the original BCD that was in the system with Windows 8 RT. ( I have remnants of a corrupted version that I am trying to re-build )

That's why is doesn't see any windows installations nor will it boot.

The fact that cinched it for me was that the Windows RE image should run when the Base RT Operating System fails. This never happens for us because the BCD file was corrupted thanks to the 8.1 upgrade. After that, the image we use only contains a RE boot, so Windows never starts.

I am now trying to build an original BCD file for the image you're laying out using the Partition Scripts.
[Windows RT General] tracins:
Hosting the Recovery Files soon!

Everything is great, just the download speed is awesome for me :D 400kb/s.

I live in Latvia, that's in Eastern Europe, i will host them too, for europeans when the download completes.

THANK YOU for the Files. Stupid W8.1 Doesn't support Jailbreak!
[Windows RT General] tracins:
Thank you, will try this one.
[Windows RT General] dalexop:
VivoTab Image Files

Wow !

Great stuff thanks.

I'll have a look through them.

I took a deeper look into the recent Tracin's post regarding the Egorblack image.

I hadn't noticed the MS One Drive link to his image.

I downloaded it and tested the image.

My tablet booted immediately into a BCD error ( 0cx000098 )

So I compared it to the Apatcas working image.

All files were identical except for the Boot.Wim file.

Here is the data:

Old File: Boot.Wim 20/05/2013 336,833

Gives a BCD error upon system Boot. ( 0xc0000098 ) /efi/microsoft/boot/bcd is missing or wrong

Copied over:

Boot.Wim 17/09/2012 182,756

The System immediately booted using the USB drive and the rest of the files.

The only difference was the addition of XML files for scripting, particularly the UEFI boot.

I was able to successfully boot into Windows RE, then choose Restore PC.

It went on to ask whether I wanted the Partitions restored, which in this case I do.

( I have saved all files on the original TAB off line )

I'll report back on status tonight since it was a long process to restore the system.

This is the first time that the Windows RE image worked right off the bat.

I read through the MS article on Boot.Wim or Wimboot, which completely explains the Partition Setup on our Tabs as well as the contents.

I'd like to understand why there are so many variations in the WimBoot file (Three in this thread alone ) for the exact same platform. Also, why does only one version of Winboot work on my Tablet, while other people work just fine with the others ???

If you have the time Fenohavana, give this a try:

Download this image from Egorblack:

1drv.ms/WhoB5B

Does it boot ?

If not replace the Win.Boot file with the one from Apatcas and then it should.

let me know how you do.
[Windows RT General] fenohavana:
Hello. It doesn't boot. I've changed the boot.wim with Apactas' and it booted. I run a reset, clean install, but it ends with the same error 0xc0000001 when restarting. I noticed that the installation process stopped suddenly at 98%. I think also that the boot.wim file is the problem. It can be edited with 7zip software or another one. May be driver or bcd files are needed to be inserted in it?
[Windows RT General] stolikat:
Has anyone been able to restore from USB to the Vivo RT? Reading through this thread it doesn't seem that anyone has had success?