Print

[randomguy98767]

So I got my newer 360 a couple days ago but before I got my new hdd.  I decided to do a backup of my hdd and then play around with it and try to install a dashboard and such.  I took it out of the housing, hooked it up via sata to my pc and then tried Xport and Xplorer.  They could both see the drive.  I dumped an image using Xport.  I played around with it a bit, and used it in the newer xbox to see the dashboard up and running.

My problem is that now, when I plug the hdd into my older xbox, it doesn't even see the drive.  Xport also doesn't see it so I can't use the backup that I made to restore it.  The new xbox sees it, Xplorer sees it, and various other tools see it, but neither of the things that I really WANT to see it can see it.  

So now I'm wondering if the image that was taken by Xport is just a raw binary dump, which I could then push back to the drive using dd.  Does anybody know if this is the case, or if there's any other way I can get this thing back working?

I appreciate any input.

[randomguy98767]

Very small update.

So I got the drive to be recognized by Xport and used that to restore from the image that I had taken earlier.  Unfortunately, I'm still getting the same results on the xboxes themselves.  My original xbox doesn't even show the drive as being attached and the new xbox (jtagged) shows the xbox but reports a few corrupted files.

[icepir8icepir8]

What size drive? Was the image made before you made any changes?

[randomguy98767]

It's a 120gb.  The image was made before I made any changes to the drive.  The older xbox is not jtagged and the newer one is.

[icepir8icepir8]

QUOTE(randomguy98767 @ Apr 10 2010, 01:33 PM)

It's a 120gb.  The image was made before I made any changes to the drive.  The older xbox is not jtagged and the newer one is.

Try opening the image you made to see if it is corrupted. Have you tried XBox 360 Commander yet?
I would like to see what results you get from it.

[randomguy98767]

Also, I've tried formatting the drive on the new xbox and that completed successfully.  Still couldn't see the drive on the old xbox though.

The image seems fine if I view it through Xplorer, Xport, or Xbox 360 Commander.  I can't tell if they still consider some of the profiles to be corrupted like the jtagged Xbox considers them to be, but they're definitely visible.

So current breakdown...

Xplorer, Xport, Xbox Commander:  Can see all files no problem

Old, banned, non-jtagged, falcon Xbox:  Can't even see the drive as being attached

Jtagged Jasper:  Sees drive as being attached, can see two profiles just fine but the other two are corrupted.  Haven't tried running anything yet to see if there are other corruption issues.  Browsing through the contents of the hdd on standard dash didn't report any other corruptions though.


This might sound stupid, but are there any little hardware triggers that might not be activated because I'm connecting it to the 360 by just plugging in the little sata adapter that's inside the housing and then connecting it straight to the 360?  Is there something like the system-closed switch that you get on some cellphones?

My idea now is that there might be an image of what the first few blocks on the hdd need to be for an xbox to recognize a drive and this one has those blocks improperly written.  If I can find such an image I can dd it to the drive and MAYBE the old xbox will see it.  Then I can format it on the old xbox, connect the formatted xbox to my pc, and then start trying to copy over files from the image that was taken.  

So, does anybody know anything about what needs to go on the hdd for an xbox to recognize it?  I think I heard something like that somewhere, but I really don't know.

Just tried to format the drive using xbox360 commander.  Got an null pointer error.  Anybody know anything else that might do the trick or if this is a fixable error?  Stack trace below.


************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at XBox360Commander.Form1.TSMenuFormatHardDrive_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
XBox360Commander
    Assembly Version: 0.1.0.1
    Win32 Version: 0.1.0.1
    CodeBase: file:///F:/leeeeeeeech/XBox360Commander/XBox360Commander.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll



This post has been edited by randomguy98767: Apr 10 2010, 09:52 PM

[randomguy98767]

UPDATE:

So the profiles are NOT corrupted.  The reason they were showing up as corrupted was that they were in use when the old console got banned.  I was able to uncorrupt them by clearing the CON flags and resigning them.

Unfortunately, I realized that I did something spectacularly stupid.  While browsing through the image I made, I realized that there was a C0DE9999 folder inside it.  Apparently I DID mess with the drive before I took the image.  I don't think I did very much though.  Even still, that doesn't explain why I was able to reformat the drive on my jtagged xbox and then it still not be visible on the old xbox.  

Hopefully I can figure this out and maybe save somebody else some trouble some day.

[icepir8icepir8]

QUOTE(randomguy98767 @ Apr 10 2010, 08:06 PM)

UPDATE:

So the profiles are NOT corrupted.  The reason they were showing up as corrupted was that they were in use when the old console got banned.  I was able to uncorrupt them by clearing the CON flags and resigning them.

Unfortunately, I realized that I did something spectacularly stupid.  While browsing through the image I made, I realized that there was a C0DE9999 folder inside it.  Apparently I DID mess with the drive before I took the image.  I don't think I did very much though.  Even still, that doesn't explain why I was able to reformat the drive on my jtagged xbox and then it still not be visible on the old xbox.  

Hopefully I can figure this out and maybe save somebody else some trouble some day.

I would check the HDDSS on the drive. maybe the jtagged system corrupted it. The jtag system does not verify the HDDSS while the unmodded checks it and if it is not correct it will not recconize the drive.
HDDHACKR can check the HDDSS to see if it matches the physical drive.

[randomguy98767]

Just ran HDDHACKR.  Got nothing.  The data that's on there is exactly what's supposed to be there.  

My new jtag xbox can see both this drive and the new drive that I got for it.  My old xbox can only see the new hard drive.

This makes no fucking sense.

[randomguy98767]

So I'm looking at a dd of the image that was taken by Xport and I can tell you right now that it doesn't conform to this standard:

Address  Length (bytes)  Contains
0x0000   8192    Null (0x00)
0x2000   68      Plain text hard disk info
0x2044   24      Static Binary Info (doesn't change console to console)
0x205C   256     Dynamic Binary Data (changes from console to console - possibly encrypted serial number of console)
0x2202   2       Size of following PNG file
0x2204   2754    MS logo in PNG format (aka hddss.bin), made with Macromedia Fireworks MX 2004 on the 19th of July 2005

There's a damned EFI header in the image within the first 0x200 bytes, which shouldn't be here.  At least I don't think so anyway.

My plan is to manually reconstruct the drive structure according to the standard and give it another go.

I hate to keep spamming this board with stupid status updates on such a small project, but there's always the chance that somebody will point me in the right direction like with HDDHACKR.  If I can figure out what went wrong I'll write up a bash script for dumping xbox hdd's for real.

[randomguy98767]

This is potentially GG, judging by this post:

http://www.xboxhacke...p;topic=13371.0

Looks like my problem was that plugging the drive directly into a pc results in the machine dicking with the LBA values in a way that xboxes do not like.  If this works I'll post and give the results.

[randomguy98767]

Yes, well that didn't work out.

Fuck it, I have a project due in a week.  I'll get back to this later.  Not like I don't have full disk dumps.