Print

[Antman1]

I just Jtaged my xbox and put XBReboot on my console.  After doing this I needed more space on my HDD then the 20gb so I pulled my 100gb Laptop HDD out and threw it in.  the 360 found it and formated it and is up and running.  However I would like to transfer all of my saves and content and such to it.  I tried Xplorer360 and Xport and they could not see it at first so I then ran HDD Hacker and had it create all 3 partitions so it would show up in Xplorer360 and Xport but it isnt able to read and write the data to partition 3.  Does anyone know what I would look for when Hex editing the Xplorer360 application to make it see the data were it actually begins?

This post has been edited by Antman1: Dec 16 2009, 05:47 PM

[xamphear]

QUOTE(Antman1 @ Dec 16 2009, 11:46 AM)

I just Jtaged my xbox and put XBReboot on my console.  After doing this I needed more space on my HDD then the 20gb so I pulled my 100gb Laptop HDD out and threw it in.  the 360 found it and formated it and is up and running.  However I would like to transfer all of my saves and content and such to it.  I tried Xplorer360 and Xport and they could not see it at first so I then ran HDD Hacker and had it create all 3 partitions so it would show up in Xplorer360 and Xport but it isnt able to read and write the data to partition 3.  Does anyone know what I would look for when Hex editing the Xplorer360 application to make it see the data were it actually begins?

If you open the drive in a hex editor and search for "name.txt" you can see where the root directory cluster is. From that hex value you can calculate the size of the cluster chain, by subtracting the location of the start of Partition 3, which is a constant among all drive sizes. This value is what you have to change inside Xplorer360.exe so it can see the contents of Partition 3.

A real fix would be for someone smarter than I am to make it dynamic, so that the root directory cluster is always located correctly, no matter the size of the drive.

[Antman1]

I am a little lost.  Not sure what Values I am looking for.  I found name.txt in my 100gb drive, here is a screen shot of what I found:


Then I was lost what am I subtracting and from what?

I also looked at my 20gb to do a comparison for Xplorer360 but again not sure what I am looking for.  here is what the 20gb looked like:


Does anyone have any ideas on were in the xplorer360 I would Hex edit these values or be looking for these values that need to be changed?  Maybe this can lead to a software that can do these calculations for all of us with different drives.  Unfortunatly I am ok with Hex editing but obviosly not as good as xamphear,  and TheSpecialist.  For all of those out there though that can not get Xplorer360 to even show your drive all you have to do is load the drive with hddhackr and use the option to create all 3 partitions and it will show up in xplorer360 but will not show partition3.  Hopefully we can figure something out on this.  

[Antman1]

ok little more progress is that on xplorer 360 you have to modify these offsets:   0xF0C2, 0xF0C3 and 0xF0C4

Noe I just gotta figure out what values to put in it.  Not sure if I understand what I am looking for for the location of partition3 and what I am to subtract from it.  It does seem like this would be a way of getting all of us with different drives closer.  if there was a way to figure this out maybe I can create a guide or something.  Anyone have any ideas?

[Antman1]

didnt realize it before but my images did not show the hex so here they are again.  here is the 20gb version of the above 20gb image but it is showing in hex now.

(IMG:http://img191.imageshack.us/img191/3964/20gbhdd.th.jpg)

And here is the image of my 100GB that I am trying to get partition 3 to show up in xplorer360:

(IMG:http://img19.imageshack.us/img19/705/hdd1o.th.jpg)

Hope this helps

**EDIT**  Also for those that might understand a little more about it, here are the notes from TheSpecialist when he explained the bug in xplorer360:  http://forums.xbox-scene.com/index.php?showtopic=694533

This post has been edited by Antman1: Dec 18 2009, 05:38 AM

[shinji257]

What capacity does the xbox 360 recognize it?  Is it showing as a 60GB would or as a 100GB?

[Antman1]

QUOTE(shinji257 @ Dec 18 2009, 08:09 PM)

What capacity does the xbox 360 recognize it?  Is it showing as a 60GB would or as a 100GB?

it sees it as a 100gb drive with 88.3 gb free.

[CoLD FiRE]

Erm.. just a suggestion and not particularly a very good one  (IMG:style_emoticons/default/dry.gif)
copy all your saves and content to an external HDD then use XeXLoader to copy over to your Xbox HDD, I know it's gonna be a real pain in the a$$ but you can use it as a last resort

or you might wanna wait for XeXLoader 0.17 to be released since it looks promising and more advanced than the current version  (IMG:style_emoticons/default/smile.gif)

[shinji257]

I don't think I'll be able to calculate the value you need.  Looks like it will get done in the same spot but I won't be of any help there.  Maybe one of the individuals that did it before can help you out?  Sorry.

[Antman1]

QUOTE(CoLD FiRE @ Dec 20 2009, 08:10 PM)

Erm.. just a suggestion and not particularly a very good one  
copy all your saves and content to an external HDD then use XeXLoader to copy over to your Xbox HDD, I know it's gonna be a real pain in the a$$ but you can use it as a last resort

or you might wanna wait for XeXLoader 0.17 to be released since it looks promising and more advanced than the current version  

Thanks a lot.  I didnt even realize I could do that.  I am transfering everything over now.  Hopefully someone will write an awesome program like xport that can transfer stuff to any size drive and will show the name of each save and piece of content.  

[CoLD FiRE]

QUOTE(Antman1 @ Dec 21 2009, 09:37 AM)

Thanks a lot.  I didnt even realize I could do that.  I am transfering everything over now.  Hopefully someone will write an awesome program like xport that can transfer stuff to any size drive and will show the name of each save and piece of content.   (IMG:style_emoticons/default/jester.gif)

Glad I could help.  (IMG:style_emoticons/default/smile.gif)

[Antman1]

Just an update...

ok here is why some are not able to use the hard drives in xplorer360, If you are using a non official M$ hard drive it is missing the official partitions for it to work properly. you will need to use a program like hddhacker and use the option to create the partitions or you will have to hex edit the drive like this:

add the missing partition manually starting at byte 0x80000 of your non M$ Drive. You need to make it look like:

58 54 41 46 00 00 00 00 00 00 00 10 00 00 00 01

So, the easy way to do this: open your drive with winhex( http://www.x-ways.net/winhex.zip ) by pressing F9, select yournon M$ drive, press <ALT>+G, use position 80000 (hexadec) and then edit these 16 bytes starting at 0x80000 to look like above. Save it, restart the xplorer360 Extreme 2 and the FATX error should be gone and you should see 2 partitions now.

This info came from thespecialist a while back when he discovered what xplorer360 is looking for. however your drive will not show the contents of partition 3 because xplorer360 cannot read it. it is not calculating the drive partition correctly without a little modification. I posted a thread a while back here: http://forums.xbox-s...howtopic=699395 for us to work on it but have been unsuccessful. I can however tell you my progress. I can get the drive detected in xplorer360 and I restored partition 2 successfully thus enabling xbox1 compatibility. Thats about it. I have been using xextool to transfer all my files back and forth.

[F1LTER]

QUOTE(Antman1 @ Dec 27 2009, 06:50 PM)

Just an update...

ok here is why some are not able to use the hard drives in xplorer360, If you are using a non official M$ hard drive it is missing the official partitions for it to work properly. you will need to use a program like hddhacker and use the option to create the partitions or you will have to hex edit the drive like this:

add the missing partition manually starting at byte 0x80000 of your non M$ Drive. You need to make it look like:

58 54 41 46 00 00 00 00 00 00 00 10 00 00 00 01

So, the easy way to do this: open your drive with winhex( http://www.x-ways.net/winhex.zip ) by pressing F9, select yournon M$ drive, press <ALT>+G, use position 80000 (hexadec) and then edit these 16 bytes starting at 0x80000 to look like above. Save it, restart the xplorer360 Extreme 2 and the FATX error should be gone and you should see 2 partitions now.

This info came from thespecialist a while back when he discovered what xplorer360 is looking for. however your drive will not show the contents of partition 3 because xplorer360 cannot read it. it is not calculating the drive partition correctly without a little modification. I posted a thread a while back here: http://forums.xbox-scene.com/index.php?showtopic=699395 for us to work on it but have been unsuccessful. I can however tell you my progress. I can get the drive detected in xplorer360 and I restored partition 2 successfully thus enabling xbox1 compatibility. Thats about it. I have been using xextool to transfer all my files back and forth.

I might have found info to help you on this task...Hope it helps, I might try messing with this tonight.

QUOTE

From http://www.xboxhacker.org/index.php?PHPSES...p;topic=13396.0

4. You need to find where the end of the FAT/start of the data on your new hard drive is. Open it up in a hex editor (I used the command line hexedit) and search for "name.txt". Find the offset 2 bytes before the "n" (hex: 6E) of "name" (on my 500GB drive this was 0x1381F1000). Now divide 0x1381F1000 by 512 to get 10227592. If you don't get an integer you may have done something wrong, or just round it off if its ~.99 or ~.01. (I used speedcrunch, but I think windows calculator in programmer mode can do mixed hex/decimal calculations too. Make sure 512 is entered as a decimal.) 10227592 is the starting sector for data on my 500GB drive. (On the 20GB drive it's 9998664)

[Antman1]

Well I did your like your post but not very good with math so I prolly screwed something up.  Here is what I got when trying to get into xplorer360 after I edited with my calculations.

[F1LTER]

Well I have been working on this and keep getting stuck at how they are doing the math.

68 77 03 @20GB       root directory cluster is at 0x131229000
00 C2 1A @120GB    root directory cluster is at 0x132973000
00 08 39 @250GB     Unknown to me

Part 3 is at  0x130EB0000

@xamphear can you tell us a little more about how you got the values for the offset 0xF0C2. A formula would be great