MXIC troubles, keep getting open trays

[ExBoxHax]

[SOLVED]MXIC troubles, keep getting open trays

Ok I've been getting open tray errors on a bunch of MXIC flashes recently. It's confusing because I have the drive key and I still can't seem to build a firmware that will work properly, I keep getting open trays and unrecognized disc errors. The only thing I can think that it could be is that I'm cutting the trace before I get a dump, and maybe that's affecting it somehow...could this be a problem? Shouldn't I still be able to build a working firmware with just the key? Or do I need some type of special information from the 3E000 sector from the original dump? I can't really figure this out...the other option I guess is that my trace cuts are too deep...but I've done them a bunch of times before and pretty much duplicated the process...It's happened on like 3 different boards...and I even got a new replacement board and flashed the firmware to it and I'm still having the same problem...Please, any info would help this is driving me crazy.

also, is it normal to get a blank 3E000 sector?

and what about locking the drive in jungle flasher before soldering the trace cut back...could that cause problems...or leaving the pcb unlocked???

 

[BL4K3Y]

Why aren't you using SlimKey before modding the drive?

SlimKey will give you dummy.bin which can be used to create an LT firmware.

After that, you can unlock the SPI and get a full firmware read which is recommended, but not a necessity.

Are you "fixing" the trace cut after writing firmware to the drive?

 

[Martin C]

I think images of what you're doing are needed, combined with logs.

 

[ExBoxHax]

Why aren't you using SlimKey before modding the drive?

SlimKey will give you dummy.bin which can be used to create an LT firmware.

After that, you can unlock the SPI and get a full firmware read which is recommended, but not a necessity.

Are you "fixing" the trace cut after writing firmware to the drive?

I was getting full reads after I unlocked it, I was simply cutting the trace first which really shouldn't make a difference...if I have the DVD key I should be able to make a working firmware by using a stock firmware file correct? or is it a must to get a full read of the original firmware? which I believe that I did get, but somehow it seems corrupted.

 

[ExBoxHax]

nevermind it was a bad laser LOL I'm retarded, it's always something simple I swear...I was having other problems with another MXIC but I'll look back into that later, they all start blending together after awhile and I was combining the problems I was having with 2 different systems into one problem, uggh ok solved. I still am curious if you need a verified original dump though or if you can simply use the DVD key...I say yes as long as you have the DVD key you can build a working firmware. That stupid 3E000 sector threw me for a loop, I though there was like hidden information on it or something and unless you read it then you couldn't make up your own firmware LOL I don't know.

 

[Martin C]

I say yes as long as you have the DVD key you can build a working firmware

Not in all cases you can't - don't make false, sweeping statements.

 

[ExBoxHax]

Not in all cases you can't - don't make false, sweeping statements.

that's what I'm trying to determine...in what cases can't you use the DVD key to make firmware?...and what other information is needed to make a working firmware?

 

[Martin C]

For phat drives, yes. For slim drives it depends on the firmware of the drive itself. DVD firmware isn't my forte, so someone else might be able to answer better.