I did a little analysis of your xplorer360 tool, hope you don't mind
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
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
kind regards,
TS
This was solved by the hddhacker tool creating partitions 0/2/3 so the above is resolved and was fine for those with official M$ drives.
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
Apparently we can get 60gb drives and 250gb drives to detect and show the data on partition 3 ifwe can hex edit this correctly but I am not sure what to change and such. May need a little assistance on this. I am sure a lot of people would like to fix this so we can transfer the data to our new 60gb and 250gb drives out there. I have confirmed that explorer360 extreme2 that thespecialist hooked us up with does not work with the oem 250gb drive. it shows the partitions but no data on partition3. same as the 60gb. (dont ask me for a hddss.bin)
@ 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 !
Would be great if the source code would be released so this could be resolved as well.
I figured I would bring this back up for discusion.
Author
Topic: Xplorer360 Adding Support For 250gb And 60gb (Read 104 times)