USB-to-SATA converter

nofx513

Noob Account
Dec 9, 2002
5
0
www.cincinnaticows.com
Hello,

Thanks 360mods for the great community and wealth of information... a couple of questions:

1. Can I use a USB-to-SATA converter cable to connect the Samsung and flash successfully?

2. If I can see the Samsung as a drive in Windows, does that mean the flashing will work correctly? (or in other terms, does the compatibility matrix in Textbook's v41 pdf mean that even though you may be able to see the drive in Windows, the flash may not work).

Finally, I have a ms25 sammy, my understanding of the overall process:

1. Download Xtreme5.2.
2. Use Xtreme Boot Maker to create bootable USB.
3. Copy updated x360sam & keycheck to USB.
4. Connect sammy to PC, boot up both.
5. Run SAMREAD to get orig.bin.
6. Use samtool with Xtreme5.2 and orig.bin.
7. Take resulting patched-hacked-fw (*)
and flash sammy with it (**).

* What will the resulting file be named?
** Do I use SAMHACK 1234567 12345 to flash sammy
with "patched-hacked-fw" from step 6? Where does
SAMHACK look for the patched-hacked-fw on the USB
directory? Can I just replace the MTKFlash-ed version?

Thanks!
 

Textbook

Console Master
Dec 6, 2002
1,333
36
1. No, a SATA>USB converter can only be used to flash the older Hitachi drives at this time. Samsung and Hitachi 78 will not work (currently).

2. You won't be able to see the Samsung drive until the drive has been flashed and the 0800 disc is used to put the drive into 0800 mode. Whether Windows sees your drive or not (it won't) would have nothing to do with SATA compatibility, as the flashing is done in DOS, using MTKFlash. MTKFlash cannot flash via USB and some SATA chipsets.

Your understanding of the process is mostly correct.

5. SAMREAD backs up the original firmware, runs x360sam to patch and create your hacked.bin hacked firmware, and it also will run keycheck to verify that a key exists in your orig.bin and hacked.bin and that they are correct.

6. SAMHACK 1234567 12345

* hacked.bin and it will be in the same directory as your orig.bin. -- Which is in /BACKUPS/1234567/12345/

** Yes , and second question answered already ^