Print

[Antman1]

any updates on this?

[coreyinoz]

Holy cow - me three!

Thinking I was all clever, I just ordered an external 360 to sata adapter so as to copy new files to my internal 360 HD without fuss - not realizing that xplore360 doesn't support 500GB hard drives!

Copying to DVD/USB, then to internal HD via Xexloader seems like a kluge, and I don't want an ugly external HD sitting beside my 360 either.

/prays for xplore360 update

coreyinoz

[Basin]

The magic number for 500gb is 00 40 73

See my post here http://www.xboxhacker.org/index.php?topic=...g95889#msg95889

[F1LTER]

QUOTE(Basin @ Jan 10 2010, 08:46 PM)

The magic number for 500gb is 00 40 73

See my post here http://www.xboxhacke...g95889#msg95889

Thanks so much! I can confirm access to my WD10EAVS  1TB WD Green drive with number 00 B0 E7.
This should tide me over until ftp access ...  


EDIT: I am getting about a 15 MBPS transfer rate and seems stable so far.

[bidrug]

QUOTE(Basin @ Jan 10 2010, 08:46 PM)

The magic number for 500gb is 00 40 73

See my post here http://www.xboxhacker.org/index.php?topic=...g95889#msg95889

I've already formatted the HDD, is a 320 GB Toshiba, but I don't really feel like zero filling the drive since I have put a lot of stuff in the drive....

I don't wan't to clone my disk, I have a 120 GB official drive (which BTW happens to be a Fujitsu) for use in my untouched console, I want this other 320 HDD just for the XBR'ed boxes I have...


I was following the guide OK, but I've got lost in the part where the 0x1381F0000 offset subtract 0x130eb1000 gets 0x7340000, having 734000(0) reversed to get a value to modify xplorer360 to see the drive.... I know if for a 500 GB drive...

So, if someone can explain in to me please, so I can get my 320 GB drive seen in xplorer360, I'll be so thankful and will even be in church every Sunday.

This post has been edited by bidrug: Jan 12 2010, 10:31 AM

[Basin]

QUOTE(bidrug @ Jan 12 2010, 08:58 AM)

I've already formatted the HDD, is a 320 GB Toshiba, but I don't really feel like zero filling the drive since I have put a lot of stuff in the drive....

I don't wan't to clone my disk, I have a 120 GB official drive (which BTW happens to be a Fujitsu) for use in my untouched console, I want this other 320 HDD just for the XBR'ed boxes I have...
I was following the guide OK, but I've got lost in the part where the 0x1381F0000 offset subtract 0x130eb1000 gets 0x7340000, having 734000(0) reversed to get a value to modify xplorer360 to see the drive.... I know if for a 500 GB drive...

So, if someone can explain in to me please, so I can get my 320 GB drive seen in xplorer360, I'll be so thankful and will even be in church every Sunday.

Copying everything between 0x80000 and 0x130eb1000 from your 120 to your 320 will put partition 1 and 2 onto the 320, if you haven't done that already, without affecting what's on the drive.

0x1381F0000 isn't correct for a 320GB drive, to find the right offset you need to find name.txt after giving your hard drive a label on the 360. The correct offset is at the multiple of 512 (0x200) below name.txt. e.g. my name.txt was found at 0x1381F0002, so the offset I need is at 0x1381F0000, because 0x1381F0000 is a multiple of 0x200.

0x means 'this is a hexadecimal number'. You can do hexadecimal calculations on windows calculator in 'programmer mode' which is in one of the menus, then you click the hex checkbox.

[bidrug]

QUOTE(Basin @ Jan 12 2010, 03:59 PM)

Copying everything between 0x80000 and 0x130eb1000 from your 120 to your 320 will put partition 1 and 2 onto the 320, if you haven't done that already, without affecting what's on the drive.

0x1381F0000 isn't correct for a 320GB drive, to find the right offset you need to find name.txt after giving your hard drive a label on the 360. The correct offset is at the multiple of 512 (0x200) below name.txt. e.g. my name.txt was found at 0x1381F0002, so the offset I need is at 0x1381F0000, because 0x1381F0000 is a multiple of 0x200.

0x means 'this is a hexadecimal number'. You can do hexadecimal calculations on windows calculator in 'programmer mode' which is in one of the menus, then you click the hex checkbox.

Now I'm getting it...
I know 0x1381F0000 is not right for a 320 gb (the operation was for a 500 GB), so, I suppose,  0x1381F0000 is the begging of parttition3 (or the ending, getting lost again), and substracting the offset where partition2 ends, gives the magic number...

this means I have to format the drive... don't I?



.::Edit::.
Le Fluffie shows me only the Content Partition and allows me to injext/extract data, xplorer360 only shows Partition1 nad Partition3 but won't let me see anything



This post has been edited by bidrug: Jan 12 2010, 10:30 PM

[ccfman2004]

I hope an easy plug and play option comes along cause all this hex editing gives me a headache.

[bidrug]

I've found where name.txt is, in my drive, that would be 0x135806000 / 0x200 = 0x9AC030 (10141744).

I don't really want to format the drive, that would put my originals in risk of dying, my nephews know nothing else but playing like 3 hours after school, and they don't hesitate to switch games and throw'em like freezbe.
They have rendered batman useless in the console, i've made an image already and gonna polish the disk they scratched.

so, is there a way to modify xplorer360?

This post has been edited by bidrug: Jan 13 2010, 01:52 AM

[F1LTER]

QUOTE(bidrug @ Jan 13 2010, 01:33 AM)

I've found where name.txt is, in my drive, that would be 0x135806000 / 0x200 = 0x9AC030 (10141744).

I don't really want to format the drive, that would put my originals in risk of dying, my nephews know nothing else but playing like 3 hours after school, and they don't hesitate to switch games and throw'em like freezbe.
They have rendered batman useless in the console, i've made an image already and gonna polish the disk they scratched.

so, is there a way to modify xplorer360?

It should be 0x135806000 -  0x130eb1000 = 4955000 >(drop zero)495500 >
(group'and'reverse)00 55 49    

Hexedit that into your   xplorer360.exe @  offset 0xF0C0   that first line should read 00 00 00 55 49 00 00 00

This post has been edited by F1LTER: Jan 13 2010, 07:13 AM

[Antman1]

I tried these calculations with my 100gb and cant get it to work.  a picture of my drive pulled up in winhex is towards the top of this post.  Can some one help me?

[F1LTER]

QUOTE(Antman1 @ Jan 13 2010, 02:19 PM)

I tried these calculations with my 100gb and cant get it to work.  a picture of my drive pulled up in winhex is towards the top of this post.  Can some one help me?

It is still kinda early for me but I think your magic number should be:

1324CB000 - 130EB1000 = 161A000 > 161A00 > 00 1A 16  

[Antman1]

thank you.  that was it.  I had to put it at offset F0C2 though instead of offset F0C0.  Xplorer360 now working like a charm!  Thank you all very very much.  so far here are all the magic numbers I have seen done incase this helps others out.

20GB : 00 78 03 , 0x131229000
60GB : 00 C9 0C , 0x131B7A000
100GB : 00 1A 16 , 0x1324CB000
120GB : 00 C2 1A , 0x132973000
500GB : 00 40 73 , 0x1381F0000
1TB : 00 B0 E7 , 0x13f661000


These will only work for you if name.txt comes less than 512 bytes after the second number above.

[coreyinoz]

QUOTE(bidrug @ Jan 13 2010, 01:33 AM)

I've found where name.txt is, in my drive, that would be 0x135806000 / 0x200 = 0x9AC030 (10141744).

I got the same value on a WD Scorpio Black 320GB if anyone is interested.

[bidrug]

QUOTE(F1LTER @ Jan 13 2010, 07:08 AM)

It should be 0x135806000 -  0x130eb1000 = 4955000 >(drop zero)495500 >
(group'and'reverse)00 55 49    

Hexedit that into your   xplorer360.exe @  offset 0xF0C0   that first line should read 00 00 00 55 49 00 00 00

You are a capable guy and getting to know, I'm a complete dumb...

I was in the right spot, but like 2 offsets before expected.

So, you need to find where name.txt is and get 2 offsets berore the n, so you can get a 512 multiplier to get to know the magic number, but you need to add those 2 offsets in F0C0... maybe I'm nuts


Thanks a lot, worked at 1st try.

This post has been edited by bidrug: Jan 14 2010, 09:20 PM