Print

[jxoxn21]

 I know there's a 1000 people probably posting the same sh*t but i really need someone to help me out here as i've been trying for WEEKS. I have 2 consoles one with a 47d and 1 ms25. 47d is fine works great f;ashed no problem. The ms25 wont get recognized with my mtkflash no matter what i do. My card is not on the compatibility list at all and i cant find any info on it. Maybe someone could tell me what values have to be hexedited in   . Your help is appreciated!!

My SATA PCI Card info:
-----
Name Initio inic1620 S-ATA Adapter
Manufacturer INITIO Corp.
Status OK
PNP Device ID PCI\VEN_1101&DEV_1622&SUBSYS_16221101&REV_02\1&2AF9ED5&D&60F0
I/O Port 0x0000D800-0x0000D8FF
I/O Port 0x0000D400-0x0000D4FF
I/O Port 0x0000D000-0x0000D0FF
I/O Port 0x0000DE00-0x0000DEFF
I/O Port 0x0000DD00-0x0000DDFF
-----
I can't see the difference of 7 in any of the lines??, Thanks all!

[Textbook]

I've never even seen that card before or heard of it.

Use the first and third I/O lines.

So it should be:

0111 2216 00D8 00D0

[jxoxn21]

QUOTE(Textbook @ Sep 24 2006, 04:56 PM)

I've never even seen that card before or heard of it.

Use the first and third I/O lines.

So it should be:

0111 2216 00D8 00D0

Thanks for the quick reply!! Before you replied i had put in just the value from the pnp devices line, and it SAW THE DRIVE!! So i dumped the firmware! even verified it in windows i went to flash back i got a bunch of errors and now my xbox has error code: E 65. (BAD FIRMWARE!!) is my drive bricked? anyway to fix this? I DO HAVE THE FIRMWARE ALREADY!

[angry_rabbit]

If you have the key from your original dump reflash the the drive. Make sure your bin file is the right size. Wrong size will give u this error.

[jxoxn21]

QUOTE(angry_rabbit @ Sep 24 2006, 05:54 PM)

If you have the key from your original dump reflash the the drive. Make sure your bin file is the right size. Wrong size will give u this error.

I do have the original firmware it did dump correctly. I followed the tutorial for bad flash recovery, i could get to the point where it says choose mast/slave SATA and every area it flashes it just says FAILED down the screen. It IS detecting the drive though! what would cause it to fail on every attempt??

[angry_rabbit]

Have seen this before, It looks like the file you hex edit is slightly larger or u made a mistake with the cut and paste in hex edit and copied bytes before 4000 'h. Ur now having a lockout condition similar to m28. There are two proceedures u may follow vcc trick or 19 & 20 data line trick. The timing to do a recovery flash is a bit tricky.  The best mobo is an nf3 to do this recovery easily. Do some research on this site and xboxhacker.net to find whats involved!

[Rymez]

QUOTE(jxoxn21 @ Sep 24 2006, 10:23 PM)

Thanks for the quick reply!! Before you replied i had put in just the value from the pnp devices line, and it SAW THE DRIVE!! So i dumped the firmware! even verified it in windows i went to flash back i got a bunch of errors and now my xbox has error code: E 65. (BAD FIRMWARE!!) is my drive bricked? anyway to fix this? I DO HAVE THE FIRMWARE ALREADY!

I had this same issue using X360SAM my brothers 360. It worked fine on my 360. I think there may be an issue with the patch command?
I got round it by reflashing with xtreme 3.3
Now working 100%

[jxoxn21]

If i do the timing right i could start my samhack.bat and it will begin flashing. Only problem is i have FAILED lined down the screen. is this a problem with the hex? The original firmware dumped fine. thanks all!

[angry_rabbit]

Try this mtkflash e /sata

[jxoxn21]

I tried the mtkflash e /sata; it says 100% successfully done! But whenever i try to write ANYTHING to the firmware i'm getting this:

-----
Updating..........00% www fail 1
www  Fail 2
www  Fail 3
www  Fail 4
www  Fail 5
www  Fail 6
www  Fail 7
www  Fail 8
www  Fail 9
www  Fail 10

ERR: fail to write flash!
-----

This is exactly what I got the first time I tried to do the flash and the drive gets a error 65 when booted in the 360. PLEASE someone tell me they've seen this before or know what this means! Thank for all your help!

[ash1471]

Ther is obviously somthing wrong here I think the mtkflash you are using is prt modified. Have a look at textbooks sig and download one of the guides there are links which provide fully modified mtkflash's. Within one of his exellent tutorials.

This post has been edited by ash1471: Sep 26 2006, 11:03 PM

[jxoxn21]

QUOTE(ash1471 @ Sep 26 2006, 06:02 PM)

Ther is obviously somthing wrong here I think the mtkflash you are using is prt modified. Have a look at textbooks sig and download one of the guides there are links which provide fully modified mtkflash's. Within one of his exellent tutorials.

I downloaded the official unmodified MTKflash and following the tutorials and people in the forum to hex my ports in; The drive is recognized and i dumped the firmware = 256k. No other drives were hooked up, so are you telling me the mtkflash is bad? or is it my sata card that nobody heard of?

If i do a mtkflash e itll say 100% completed perfectly immediately. I dunno if its really doing anything? is there any other reason why i could be getting these errors??

[Gazcoigne]

are you using an auto flasher app or doing it old school? i think old school floppy method is best hands down.

what commands are you using with the mtkflash?

sounds to me like you are getting hitachi and samsung mixed up

mtkflash r /m orig.bin          to read fw

mtkflash w /m xtreme.bin    to flash fw

there shouldnt be an e anywhere in the command, thats for hitachi flashing in windows.

This post has been edited by Gazcoigne: Sep 27 2006, 12:01 AM

[angry_rabbit]

After doing mtkflask e /sata cmd do the following mtkflask r /sata <filename> "not orig.bin". Next load this file into hex edit and see if the flash is erased ! U should see just ff's thru' out memory.  My guess it an't f/w screwed up no wonder e65 error!

This post has been edited by angry_rabbit: Sep 27 2006, 06:02 AM

[Textbook]

First of all, are you SURE your orig.bin is a good dump?  Have you checked it in hex or try opening it with 360 firmware toolbox?  If it is bad, it will be all FF's and won't even open up with 360fwtoolbox.  If it's good, it will look "weird".  If it is a good dump, you're fine, you just need to put your key into Xtreme and flash the drive.