System Error E200 000000EF 000000

[alexisblack]

I followed the methods on two videos I found on youtube except when placing the update files inside of folder A and B from my old hard drive I used the OSUDT3 download from the Microsoft support page. I tried to boot up the xbox and got the xbox logo and was immediately brought to something similar to the error code in the title. I tried all of the offline update tools and was given E101 errors. I made sure to format the thumb drive to ntfs if that was the issue and formatted each one. I can't get this thing working and I refuse to send it to Microsoft. Would it be possible to update your python script and make a clone of your xbox's System Update partition for us. I kept getting partition not found errors when running the script, yet they were still being created. I did have to reformat and manually rename some of them. Your input would be greatly appreciated.

[JW0914]

It's not the script, but the A & B folders.

It seems no one on any thread or forum listed the correct layout of the A & B folders .

• I forget to make a note of which folder needs what update files, so you may have to try this twice.
  My internal drive went kaput, so I didn't have the original files, and I was able to download the two missing files not included in the OSUDT updates (sosinit.xvd & sostmpl.xvd) from someone; however, I'm not sure if they're required for the OS rebuild.

If rebuilding using the OSUDT downloads from the Xbox Support site

• If utilizing a drive larger than 500GB, format the drive with the proper layout for a 500GB drive (this is necessary for the OS rebuild to occur and will be addressed at the end of this post)
  • Folder A should contain the following OSUDT 1 xvds (system is excluded):
    • I'm not sure if the sos* files are required for rebuild, so try without them first if you don't have them. I can provide sosinit.xvd & sostmpl.xvd should it prove they are required for the rebuild
      • SettingsTemplate.xvd
      • sosinit.xvd
      • sostmpl.xvd
      • systemaux.xvd
      • SystemTools.xvd
  • Folder B should contain all OSUDT 1 xvds:
    • SettingsTemplate.xvd
    • sosinit.xvd
    • sostmpl.xvd
    • system.vxd
    • systemaux.xvd
    • SystemTools.xvd
  • Xbox will boot, begin to update and fail about 25% of the way through
    • Ensure you shutdown the Xbox One correctly via pressing the power button until it turns off
      • Failure to do this prevents one from doing what's next
    • Replace OSUDT 1 files from Folder B with files from OSUDT 2 (copy and paste)
    • Reconnect drive to the Xbox One and boot up... It should continue the update and finish successfully.
• Do not forget to re-run the xboxonehdd python script prior to reinstalling into the Xbox One
• Again, I forgot to write down which folder is which, however I'm almost positive Folder B is the actual update folder, with Folder A containing files from the previous update (which is why folder A & B both need to have OSUDT 1 files if rebuilding the OS, excluding the system.xvd from Folder A).

If you are installing a drive larger than 500GB:

• Format with the proper layout of a 500GB drive (remaining free space after partition 5).
• Once the OS rebuild finalizes successfully and you're taken to the Xbox Home Screen,shut down the xbox completely via the menu (it needs to be fully shut down, not put into standby).
• Copy all files from all partitions into separate folders on a separate HDD
  • One could also use the WIM commands below to capture, then apply, a WIM to the applicable partitions
• Reformat the Xbox One internal drive & partition it via the the script provided
• Copy all files back to their respective partitions
• Once reconnected to the Xbox One, it should boot and display the correct size for free space.
  • If you receive an error after reinstalling, you need to rerun the xboxonehdd script, or use dd, to flip the HDD's 1st sector bits.

Xbox One Partition Layout (as of 2016.04.09; 1TB Seagate SSHD):

• Partition 1 (Temp Content):
  • $sosrst.xvd (50,596KB)
  • appswapfile.xvd (2,109,584KB)
  • ConnectedStorage-retail (9,548,892KB)
  • GDVRIndex.xvd (103,628KB)
  • ScreenShots.xvd (1,061,020KB)
  • temp00 (2,097,164KB)
  • temp01 (2,097,164KB)
  • temp02 (2,097,164KB)
• Partition 2 (User Content):
  • PLS (folder)
  • SharedStorage (folder)
• Partition 3 (System Support):
  • Controllers (folder)
    • cache0.cfg
  • cms.xvd
  • DataCollectionUploader_0
  • LastConsole
  • user.xvd
  • WER.xvd
• Partition 4 (System Update):
  • A (folder)
    • SettingsTemplate.xvd (37,144KB)
    • sosinit.xvd (11,964KB)
    • sostmpl.xvd (63,516KB)
    • systemaux.xvd (494,876KB)
    • SystemTools.xvd (466,44KB)
  • B (folder)
    • host.xvd (49,364KB)
    • SettingsTemplate.xvd (120,784KB)
    • sosinit.xvd (11,964KB)
    • sostmpl.xvd (63,516KB)
    • system.xvd (1,667,660KB)
    • systemaux.xvd (820,596KB)
    • systemmisc.xvd (748,192KB)
    • systemtools.xvd (38,484KB)
  • updater.xvd (63,644KB)
• Partition 5 (System Update 2):
  • no data, empty
• Items without sizes have no sizes listed as they will depend on the user specific files

[alexisblack]

Hey I thought you might find this interesting, I followed this tutorial http://www.ludvikjerabek.com/2014/07/14/xbox-one-fun-with-gpt-disk/ which runs terminal bash scripts not using python. through this method my partitions were created with no errors. I just got my xbox one to boot properly with no errors, now it looks like it goes to the dashboard but there are blue lines on the top and bottom of the screen. I just tried offline updating to OSUDT3 and it recognized it (first time ive gotten the update screen), but it looks like it just stalled. Im gonna try the factory reset now. I noticed the file format was off looking at your tree branch. Unfortunately I wiped my original drive so I dont have access to those files anymore.

[JW0914]

Please see my prior post... Again, the script is not the issue

[alexisblack]

awh thanks, sorry about that. Ill let you know if I need those files

[JW0914]

Also, in regards to the link in your prior post, the author of that script didn't write it properly, as it incorrectly formats a drive with the wrong sized system partitions (i.e. all partitions excluding partition 2). Unfortunately, they don't allow comments on their blog, so there's no way to inform them. I will guarantee that's why you had issues after using it.

• If you utilize that script and then verify the sizes of the partitions after they were created, you will see every partition is improperly sized.

Also, the reason why it stalled is if an offline update is performed, and the system sees any other partitioning than the default 500GB partition sizes, it will reformat the disk, thereby erasing all update files.

[alexisblack]

thanks for the information, I will go through it again with your script.

[alexisblack]

Question, when I run your script I get alot of errors saying that the resulting partition is not properly aligned for the best performance. I also get no access messages for each partition saying the file or directory doesn't exits. Is this to be ignored?

[JW0914]

It's not my script...

I also strongly encourage making a WIM backup of Partitions 1, 3, & 4 (using Windows) after you get the Xbox to successfully boot to the home screen without error and get all of your user content synced. This will prevent having to go through this again should you replace/upgrade a drive.

I've noticed the hex bits in the first sector weren't flipped when I went to make my WIMs after all content was synced, which allowed Windows to auto recognize it. If Windows doesn't recognize it however, you simply need to flip the 1st sector bits from 99CC to 55AA (see this write up)

• You also flip the bits using a nix OS (where */dev/sdc** is the disk, i.e. sdb, sdc, etc.):
  • echo -en '\x55\xAA' | dd conv=notrunc of=**/dev/sdc** bs=1 seek=510 2>/dev/null 1>&2
    • Then, prior to reinstalling the HDD:
  • echo -en '\x99\xCC' | dd conv=notrunc of=**/dev/sdc** bs=1 seek=510 2>/dev/null 1>&2
• WIM Commands (Where *Z:* is the image save location, and **D:*, **E:*, & *F:* are the applicable drive letters for Xbox One partitions 1, 3, & 4):
  • Temp Content (Drive D)
    • DISM /Capture-Image /ImageFile:**Z:\TempContent.wim** /CaptureDir:**D:\** /name:**"Xbox One Partition 1"** /description:**"Temp Content"** /compress:**max** /CheckIntegrity /Verify
  • System Support (Drive E)
    • DISM /Capture-Image /ImageFile:**Z:\SystemSupport.wim** /CaptureDir:**E:\** /name:**"Xbox One Partition 3"** /description:**"System Support"** /compress:**max** /CheckIntegrity /Verify
  • System Update _(Drive F)`
    • DISM /Capture-Image /ImageFile:**Z:\SystemUpdate.wim** /CaptureDir:**F:\** /name:**"Xbox One Partition 4"** /description:**"System Update"** /compress:**max** /CheckIntegrity /Verify
  • While one could make a WIM backup of the User Content partition, I don't recommend it if you have broadband internet, as xvd storage is efficient and you'll have a resulting WIM image almost the exact same size as the used space on the User Content partition. Everything contained on the User Content partition is re-downloaded once you log in to your Xbox Live account and reinstall games/apps.
    • The only situation I could see this being beneficial is if one has spotty internet coverage where they live, have less than a 30mbps connection, and/or have a data cap on their home internet plan (TWC is currently trying out a cell carrier like pricing model per GB in select US Cities).

WIM sizes should be:

• Partition 1: TempContent.wim, 416,895KB
• Partition 3: SystemSupport.wim, 1,125,075KB
• Partition 4: SystemUpdate.wim, 4,175,222KB

Verify each WIM after capture:

• Very WIM File:
  • DISM /Get-WimInfo /WimFile:Z:\TempContent.wim
• Verify WIM File Index(es):
  • DISM /Get-WimInfo /WimFile:Z:\TempContent.wim /Index:1

Verify File Output:

Index : 1
Name : Xbox One Partition 1
Description : Temp Content
Size : 19,625,177,088 bytes

Verify Index Output:

Index : 1
Name : Xbox One Partition 1
Description : Temp Content
Size : 19,625,177,088 bytes
WIM Bootable : No
Architecture : <undefined>
Hal : <undefined>
Version : <undefined>
ServicePack Build : <undefined>
ServicePack Level : <undefined>
Edition : <undefined>
Installation : <undefined>
ProductType : <undefined>
ProductSuite : <undefined>
System Root : <undefined>
Directories : 1
Files : 8
Created : 2016.04.08 - 14:01:20
Modified : 2016.04.08 - 14:01:20
Languages : <undefined>

[alexisblack]

replacing files in folder B with OSUDT2 now

[alexisblack]

Error mounting /dev/sdc4 at /media/ubuntu/System Update: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=999,gid=999" "/dev/sdc4" "/media/ubuntu/System Update"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sdc4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
(udisks-error-quark, 0)

So when i try to remount the hard drive to replace files inside of folder B I get this information here.

[JW0914]

How did you shutdown the system prior to removing the hdd?

[alexisblack]

I held the xbox button until it shutdown. I accidentally turned it on again but repeated the same process of shutting it down by holding down the power button again

Is it a hard shutdown (holding down button) that im doing or just a regular one (tap)

[JW0914]

Reinstall the drive, wait for the error screen again, then hold down the controller xbox button to see if it provides a shutdown menu... if not, hold the power down again for 10 - 15 seconds for it to fully shut down, and ensure you do not re-power on the system again.

[JW0914]

If it will shut down by simply tapping the power button, try that first (It's one or the other, but for some reason I thought it I had to hold mine down, but I could be misremembering).

If the one tap shutdown still gives you a mount error, try it again with the hard shutdown and ensure not to power it backup again. Please let me know which one it is and I'll update my post above with the correct information.

EDIT:
I missed something in your prior post:

• "...when I run your script I get alot of errors saying that the resulting partition is not properly aligned for the best performance. "
  • I'm not sure why those messages occur, as the drive is 1MB offset, which is the recommended offset for 4k alignment in general. I tried various methods and various *nix partitioning programs, but was unable to get rid of the error. This seems to be specific to the formatting scripts for the xbox one, however someone with more experience than I using *nix cli partitioning will need to expand on the issue. At worst, it will result in non-optimal disk storage, but won't damage the drive or cause issues.

[alexisblack]

Awesome thanks for everything, I successfully booted the xbox and everything worked in the manner explained above. I'm glad that you were able to respond to my issue as well. There are only two tutorials that I have come across on youtube and neither one followed these steps (file structure for the A and B folders, and having to update folder B files with OSUDT2). Everyones been saying that this no longer works prior to the December update. Guess that can be put to rest. Have you thought about putting up a tutorial yourself?

[JW0914]

No problem at all =]

I'll be adding it to my GitHub Wikis section later today. I was in the exact same situation as you about a week ago and it took me ~8 hours of trial and error before I figured out how everything needs to come together.

My hunch about the December 2015 update is most were parroting what they'd heard from ths 3rd party or that 3rd party, with no one ever bothering to actually attempt the proper steps to restore. It appears this will always work, regardless of future updates, as all OSUDT updates contain the full OS in XVD disks (I assume it stands for Xbox Virtual Disk).The actual Win10 EFI bootloader resides on flash storage built into the MB, with the HDD only providing the OS files. It would be no different that utilizing an HDD on a PC for VHD/VHDX storage only and having Windows boot from the VHD/VHDX, similarly to how certain tablets utilize WIMboot.

BTW... which was the proper way to shut it down at the error screen: hard reboot or simple touch of the power button?

[alexisblack]

It was a simple touch. The console will shut off after a few seconds. You'll hear the power supply still going but you can simply unplug from the back. Can I get a link to your Wiki? I'm currently in college doing programming as my major so I've had some expirience with C++ Python and Java. I'm really interested in doing things like this as a hobby (reverse engineering?).

[JW0914]

Xbox One Wiki: https://github.com/JW0914/Wikis/tree/master/XboxOne

[westekgit]

@JW0914 After hours and hours of trying every combination of instructions I could find to replace the HDD, only this thread finally got me over the top. I was getting an E201 error when I would boot from the hard drive and E101 immediately every time I tried the OSUDT on USB. I tried every combination of OSUDT files on the hard drive and every version of OSUDT on the USB with no changes. I was basically in the exact same spot as @alexisblack was in. This thread saved me!

You are correct in that the xboxonehdd script creates the partitions of the wrong size and I believe that was 99% of my problem. I used your script https://github.com/JW0914/Wikis/blob/master/XboxOne/Scripts/mkxboxfs-500gb.sh to create the partitions instead and then ran the xboxonehdd script for the last time. I did have to modify that script to get it to run correctly the last time. It sees that the partitions are not the sizes it wants and then stops. I had to bypass that condition to get it to work, but after that the XBOX booted like a champ and behaved exactly as in the thread above.

Thanks so much!

[xibinx]

@JW0914
The mkxboxfs-500gb.sh script is giving the following errors...plz help me out
./mkxboxfs-500gb.sh: line 2: $'\r': command not found

• No such file or directory./dev/sdb
• No such file or directory./dev/sdb
• No such file or directory./dev/sdb
  1': No such file or directory
  The device doesn't exist; did you specify it correctly?
  ./mkxboxfs-500gb.sh: line 7: $'\r': command not found
• No such file or directory./dev/sdb
• No such file or directory./dev/sdb
  2': No such file or directory
  The device doesn't exist; did you specify it correctly?
  ./mkxboxfs-500gb.sh: line 11: $'\r': command not found
• No such file or directory./dev/sdb
• No such file or directory./dev/sdb
  3': No such file or directory
  The device doesn't exist; did you specify it correctly?
  ./mkxboxfs-500gb.sh: line 15: $'\r': command not found
• No such file or directory./dev/sdb
• No such file or directory./dev/sdb
  4': No such file or directory
  The device doesn't exist; did you specify it correctly?
  ./mkxboxfs-500gb.sh: line 19: $'\r': command not found
• No such file or directory./dev/sdb
• No such file or directory./dev/sdb
  5': No such file or directory
  The device doesn't exist; did you specify it correctly?