Print

[Greenvalor7]

QUOTE(TheSpecialist @ May 6 2007, 03:50 AM)

Well, to get a 20 gb WD BEVS recognized in xplorer360, you can edit sector 1024 (=0x400) = byte 0x80000. You need to make it look like:

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

  Thanks TS! I went ahead and followed your directions with the 120gb WD BEVS and xplorer sees the drive now!  So thats a step in the right direction.  THe only thing is, I think I now have the same problem that everyone does with their retail drives, only partitions 0 and 3 show up and neither have a plus sign next to them.  Hopefully Angerwound will point Roofus over to this thread

[TheSpecialist]

I did a little analysis of your xplorer360 tool, hope you don't mind (IMG:style_emoticons/default/wink.gif)

The problem with BEVS drives is twofold. First of all, your tool wants to see a FATX partition at 0x80000. This partition does not exist on WD BEVS drives, not even after it's formatted on the 360. It's probably created at the MS Headoffice (IMG:style_emoticons/default/smile.gif) Anyway, after adding the partition manually (like i posted), xplorer360 then will continue as normal.

However, the 2nd problem is that xplorer360 somehow thinks that the root directory cluster is at byte 0x131229000. While this holds indeed true for my 20 gb drive, it's not correct for my 120 gb drive. At byte 0x131229000 there's only a directory entry for the 'Cache' directory (and that's why xplorer360 only lists that 'cache' directory when i click on partition 3).

The 'true' root directory cluster for my 120 gb drive is at 0x132973000 (while the partition itself is unchanged of course, at 0x130EB0000)

I haven't done enough research yet to find out how your tool determines the root directory cluster (I scanned quickly for a hardcoded value, couldn't find it at first glance), but obviously that's where it goes wrong. I hope you guys have some time to release a fix, if not, let me know if it is ok if i would release a small patcher for your wonderful tool, to make it compatible with the WD BEVS series (IMG:style_emoticons/default/smile.gif)

kind regards,

TS

This post has been edited by TheSpecialist: May 10 2007, 01:22 AM

[TheSpecialist]

I did a little analysis of the xplorer360 tool and found a way to make it compatible with my 120 gb BEVS. Here's how to do it in 2 steps:


1) First add the missing partition manually starting at byte 0x80000 of your WD BEVS.  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 your WD BEVS 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 Beta 6 and the FATX error should be gone and you should see 2 partitions now. However, there'll be no data shown yet.



2) To get the data shown, exit xplorer360 and fire up your hexeditor again, but this time open the xplorer360.exe itself with it. Make sure you're using the beta v6 version. At offset 0xF0C2 you'll find:

68 77 03

You need to change these 3 bytes into:
00 C2 1A

Save it (make a backup !), restart it and you can now see the contents of the WD BEVS 120 gb, at least I can

BTW, this 'hack' won't work with the 20 gb version, so it's best to make a backup of the xplorer360.exe and use the 'unhacked' original version if you want to access a 20 gb hdd !

BTW2: There's no guarantee this will work, it worked for me, but it might not work for you. This xplorer360 hack might result in loss of data on your HDD, so make sure you're testing it on a clean WD BEVS and not one which contains a lot of important data

Please give me feedback on results

[TheSpecialist]

LOL, i just transferred the contents (music + save games) from my WD-BEVS-RST to the WD-BEVS-LAT drive and my x360 liked it ! Everything worked, music and save games

Best (and safest) way to do it, is (after you modded the xplorer360 like posted above) : right click on partition 3, extract it to some folder on your PC HDD, then load the modded/hacked xplorer360 and drag the contents that you saved to disk, to partition 3 again.

You might also use the 'image' function in xplorer360 but I don't know if that works ok with the modifications ... Only 1 way to find out

[TheSpecialist]

@ Angerwound:

The reading of the wrong directory cluster is indeed caused by the way you calculate it. You're calculating it like:

Root directory cluster = cluster chain start+ cluster chain length.

Cluster chain length = 4 byte entries * (partition size in bytes /$4000 bytes per cluster).

This of course is correct, but the problem is that you've hardcoded the partition size in your tool. If you correct that partition length for the 120 gb version (like i did in the small patch I suggested above), it all works I think you've just overlooked that partition size when you released beta v6.

BTW: tell Roofus that the tool was very well and 'clean' coded ! (allthough he probably knows that himself, hehe ) He sure knows what he's doing. Respect !

[Antman1]

QUOTE(TheSpecialist @ May 11 2007, 01:40 PM)

@ Angerwound:

The reading of the wrong directory cluster is indeed caused by the way you calculate it. You're calculating it like:

Root directory cluster = cluster chain start+ cluster chain length.

Cluster chain length = 4 byte entries * (partition size in bytes /$4000 bytes per cluster).

This of course is correct, but the problem is that you've hardcoded the partition size in your tool. If you correct that partition length for the 120 gb version (like i did in the small patch I suggested above), it all works I think you've just overlooked that partition size when you released beta v6.

BTW: tell Roofus that the tool was very well and 'clean' coded ! (allthough he probably knows that himself, hehe ) He sure knows what he's doing. Respect !

Great Fix.  worked 100% and I was able to copy all data from 20GB drive over to my 120GB without M$ cable.

[TheSpecialist]

Good to hear it worked for you too, that kinda confirms that everything is ok (IMG:style_emoticons/default/smile.gif)

However, i would like to stress once more that people using this mod do NOT use the 'image' facilities of xplorer360. If you want to do that, do it on your own risk (IMG:style_emoticons/default/smile.gif) I haven't looked at it in detail, but there's a chance that this might mess up your data. If you want to use the image function, I suggest you just wait for a new official release from Angerwound/Roofus.

So in short: just extract the contents of partition 3 (which contains all your data like gamesaves, video and music) and copy it to another hdd. That works perfectly and is probably all you want anyway. Enjoy (IMG:style_emoticons/default/smile.gif)

This post has been edited by TheSpecialist: May 11 2007, 06:56 PM

[TheSpecialist]

I did some reverse engineering and hacking and here's a version I fixed to work with 120 gb:
http://rapidshare.co...rer360.rar.html
This particular version won't work with the 20 gb though.

I've also added an option to dump the hddss.bin with, it's under the 'edit menu'. You can currently only dump hddss.bin, not save it back yet, might add that next week if there's still no official release from the creators In that  case, I might also release a version that works for all hdd's (20gb + 120gb)

Image facilities work, but don't write a 20 gb version to a 120 gb hdd

I hope Angerwound/Roofus will release a fixed version within the next few days though, since it's way more work to create/add things without having the source code

[zikronix]

ok so how com backward compatibility doesnt work. with a 120 gig bevs drive yet it does on the retail drive.

[TheSpecialist]

BTW, I'm talking about a 'release' next week, but this is in no way a 'release' and I also dont' want it to be added to the main page of this site, it's just a temporarily version. This tool is from Angerwound and Roofus, and a release would seriously do not right to their work, I know they've put a lot of work into it and mine was just a few hours. (IMG:style_emoticons/default/smile.gif)

Just wanted to help out with a quick fix until they release their next version of this kickass tool (IMG:style_emoticons/default/smile.gif)

This post has been edited by TheSpecialist: May 12 2007, 10:15 PM

[bigmac_375]

well make sure you give some support for the emulation section.  If you dont add some kind of support for this in xplorer, then please tell us how to manually hex it into the hdd!

[Antman1]

I played Halo2 and some other games with my WD Drive.  sounds like you may want to reformat then and redownload the compatibility update and redo everything cause something is wrong on yer side.  drive is seen and works on the 360 as any other drive.

[bigmac_375]

well that wouldnt work because partition 2, where the emulator is, doesn't exsist on my drive. i would need to manually hex it in.

[gurry]

has anyone any guides to the fodlers structure so I know where to store/remove videos. My personal encodes not content off marketplace.

thanks

gurry

[Antman1]

QUOTE(bigmac_375 @ May 13 2007, 04:19 AM)

well that wouldnt work because partition 2, where the emulator is, doesn't exsist on my drive. i would need to manually hex it in.

OK I believe I have a work around for the BEVs drive and partition 2, but it is not simple.  I have been scratching my head wondering "What is everyone talking about?" Cause my partition2 is there and emulation works on my 120GB BEVs drive.  Well I figured out why it does for me and not others!  Here is what you would have to do.  Warning though you will lose your data on the drive!

OK First off run the undo.bin your drive.   Now use a hddss.bin from a 20GB drive with hddhacker v.91 and get it to be seen in explorer360 with the hex edit on the drive (Not xplorer360).  You will have to use a unedited version of explorer360 cause the drive will be like a 20GB drive not the 120GB cause of the 20GB hddss.bin.  Now restore your 120GB drive with a 20GB Drive image.  Then test it in the 360 it should show up as the 20GB drive with all the 20GB data.   Now your prolly saying this is pointless.  Well nope it created partition 2 for you.   now run the undo.bin once more and then use the hddss.bin from your 120GB drive!   Then put it back in your 360 and it will show the wrong size with corrupted data and you will have to reformat.  after you reformat the drive it will look normal.  Now load the drive back up on your PC with explorer360 and you will have partition 2 now and the ability to do xbox1 emulation.   Then just transfer your saves as previously stated by TheSpecialist from your 20GB drive to your PC and then from your PC to the 120GB drive.   I am sure that if anyone can find an easier way than my method it will be TheSpecialist.  If you have any questions feel free to ask.