MT1335 MX/WB unlocking

[unforgiven64]

well , here` the problem ,

first of all i hacked my 0225 slim with this new hack solution
everything was ok till i decide to write 0225 lt1.9 on drive with JF , i got "write verify failed" but it could play copy dvd .

so i locked my drive again , packed my whole xbox and after that!!!! when i turn it on again i got play DVD error with original or copy dvd ....
and even sometimes it gets stuck on booting up!
icant understand whats going on ... before packing up everything was fine but now ?!?!?
Any help appreciated....

well, if you get write verify failed, whyhave you packaged all? after that you have spi unlocked, it's just another try to write the firmware. so, what you have to do now is:

1- disassemble everything;
2- unlock the drive again (just put +5V in the hole with unlockspi launched);
3- rewrite firmware (until you get write verified SUCCESSFULLY)
4- package all

post feedback of your work.

i did all that u say ... but with Jungle flasher i got write verify failed again and again and again!
with dosflasher32 it`s ok ! without error ...
but as i said the first time that i unlock my drive i got "write verify failed "error but after that i test my copy DVD on Xbox ,that was ok and i could play copy on my xbox ... but after packing up everting gets reverse!....

could be the problem from DVDrom or laser or ... idon really know whats happend!:-??

[danthaman]

I'm pretty sure no-one has answered this question and apparently this problem occurred with tarablinda also,

When I do : UnlockSPI 3490

I get : WinIO error in writing to port 3493

IF I try port 3480, it gives same error but with 3483, it seems to add 3 to the port each time? I know there is a range there, I've tried various driver states/versiosn etc.. all work fine for JF.
HELP!!! please!  This has got me stumped, and I don't have any other PC's I can use for flashing (Without drama, eg; 64bit win7 with SATA ports, non of which show in JF!

Oh yes, and BTW I am using 32 bit XP (VIA 6421) before you ask ..... I would try dos, but it wont boot from USB (Bloody IBM crap-ware BIOS!) and the floppy was removed ages ago to make room for everything else that's crammed-in there :p

Any help would be greatly appreciated.

first of all a clasic answer? did you install via's driver? if so, REMOVE IT!!! If you haven't instaled the driver, two suggestion:

1- try to change pci slot, maybe you have an issue on pci slot;
2- try to format your pc ( i know this is boring, but you have to try this solution too)

hope that this can help you. please post feedback of everything.

Thanx for the feedback,

Yes I know all about uninstalling drivers, hence the comment: 'I've tried various driver states/versions'  I have been at this for a while now ;-) I have even tried swapping different VIA card versions as that has help with other issues in the past...

There is only one PCI slot (It's SFF, annoying I know), I have read elsewhere that ppl have re-installed Window$ and it miraculously cleared-up their problem, First of all let me say this : If it comes to that I'll do it, but I'm just not that kind of guy, in that I need to know (or at least get a vague idea) what's causing this. I know the setup is overly complicated with tons of legacy crap (tied-in to old VIA drives and the like)etc.. and that all makes it difficult to diagnose but I think re-installing OS might be a clue. I would like to avoid this at all costs as I have tons of other work-horse type stuff layered installs and the like , I'm guessing If I backup and restore after I will just get the same problem back.... I have noticed that different VIA6421 card iterations respond differently to different drivers and perhaps that might have something to do with it also, The fact that Tara had the same problem hints something perhaps to do with the interaction of WinIO.sys and the drivers. I'm aware also that ppl often use different drivers for ripping/flashing & I'm curious what ver those who have success with VIA6421 and unlockSPI were using ??

I appreciate the suggestion(s) & the prompt response

Still looking for answers....

@the guy having the dvd-play issue, perhaps get the 1.9 re-pack (although I dont think it's called that ;-) and the absolute latest JF (I seem to remember something about a similar issue in the recent changelogs..)

[jackinthexbox]

Finally managed to flash the 0225 with JF. But one big problem now:

- backups work, so flashing was OK
- tray close works (albeit it closes very rapidly, in less than a second!)
- eject won't work, have to eject manually. It twitches just a bit and stops.

I don't think it's mechanics problem. Anyone hit that problem yet?

Its because you cut one wire too much with your dremel AFAIK
Probably cordinates were off and you cut to the right and down little bit. Or you just dug too deep.

[miskan]

Its because you cut one wire too much with your dremel AFAIK
Probably cordinates were off and you cut to the right and down little bit. Or you just dug too deep.

Darn, I hope that's not the case.. It's quite useless now.

UPDATE: Anyway, here is the pic of the drill. The correct wire is probably the one in upper left corner?
http://imageshack.us/f/88/drillzy.jpg/

I should probably drill this under microscope as my lines were drawn ok. 

[glaze83]

its a bug in 1.9 I believe -- try with stock firmware and see if you can eject.

[miskan]

its a bug in 1.9 I believe -- try with stock firmware and see if you can eject.

Had the same thought and tried that earlier, but no go, same problem.

[gavingt]

Its because you cut one wire too much with your dremel AFAIK
Probably cordinates were off and you cut to the right and down little bit. Or you just dug too deep.

Darn, I hope that's not the case.. It's quite useless now.

UPDATE: Anyway, here is the pic of the drill. The correct wire is probably the one in upper left corner?
http://imageshack.us/f/88/drillzy.jpg/

I should probably drill this under microscope as my lines were drawn ok. 

It looks like you only drew one line. Also, you should focus the dremel along the diagonal line, since that's the path along which the wire runs.

[Rogero]

Finally managed to flash the 0225 with JF. But one big problem now:

- backups work, so flashing was OK
- tray close works (albeit it closes very rapidly, in less than a second!)
- eject won't work, have to eject manually. It twitches just a bit and stops.

I don't think it's mechanics problem. Anyone hit that problem yet?

Sorry to let u know, but when the tray ejects or closes so fast then doesn't eject anymore, that's because you messed up the internal wires of the chip while drilling, u should have drilled more slowly and using steps, for example: drill a little....wait 1 second for unlock signal, then drill a very little more, wait another second...till u have the unlock signal.
And also sometimes this happens even if you did everything as it should, this method have almost 10% to 20% failure rate depending on each chip internal wiring, I have done myself around 20 chips with 5 failed, another friend of mine did today 60 chips with 10 of them dead ( that's when the drive behave with a strange eject/load tray manner ) like your case.

some chips have the WP wire close to the surface and needs very little drilling to get it done, other chips needs more depth to get it done, also something to note is that sometimes there is a small delay in the unlock message/sound, i have seen many times the "SPI Unlocked" message showing suddenly while the drill is not touching the chip (this happens while i'm stepping back for 1 second before the next drill attempt)

Cheers..

[miskan]

Yes, exactly. This happened to me, too. Took a few second pause from drilling and in that time the siren went off. Probably correct method is to take a pause every 1-2 seconds and then wait a few more.

So, the wires in chips are not always exactly in the same place and failure is just a matter of luck. Console is still usable, just a bit more work involved, eject will have to be done manually.

@gavingt

There's also a vertical line drawn, just that it's very faint.

[Riku]

Finally managed to flash the 0225 with JF. But one big problem now:

- backups work, so flashing was OK
- tray close works (albeit it closes very rapidly, in less than a second!)
- eject won't work, have to eject manually. It twitches just a bit and stops.

I don't think it's mechanics problem. Anyone hit that problem yet?

Try this, it helped some people to fix eject/closing problems.

[Blown240sx]

I guess the real question I have is how are they flashing the FW to the chip orginally then locking it? Is it flashed then the plastic casing cast over the chip?

Also would melting the plastic be a better option or would the heat be more of a danger to the internal chip?

[xbox360sexual]

I should imagine the chip is flashed then software locked

as we've seen with the 9504 series, even though a hardware pin is set, a software command must be issued to 'take notice' of that hw lock.

[Pacote-san]

Finally managed to flash the 0225 with JF. But one big problem now:

- backups work, so flashing was OK
- tray close works (albeit it closes very rapidly, in less than a second!)
- eject won't work, have to eject manually. It twitches just a bit and stops.

I don't think it's mechanics problem. Anyone hit that problem yet?

Try this, it helped some people to fix eject/closing problems.

Thanks a bunch Riku!

WOrking like a charm here (used a 68ohms resistor)

[Gazcoigne]

I'm pretty sure no-one has answered this question and apparently this problem occurred with tarablinda also,

When I do : UnlockSPI 3490

I get : WinIO error in writing to port 3493

IF I try port 3480, it gives same error but with 3483, it seems to add 3 to the port each time? I know there is a range there, I've tried various driver states/versiosn etc.. all work fine for JF.
HELP!!! please!  This has got me stumped, and I don't have any other PC's I can use for flashing (Without drama, eg; 64bit win7 with SATA ports, non of which show in JF!

Oh yes, and BTW I am using 32 bit XP (VIA 6421) before you ask ..... I would try dos, but it wont boot from USB (Bloody IBM crap-ware BIOS!) and the floppy was removed ages ago to make room for everything else that's crammed-in there :p

Any help would be greatly appreciated.

first of all a clasic answer? did you install via's driver? if so, REMOVE IT!!! If you haven't instaled the driver, two suggestion:

1- try to change pci slot, maybe you have an issue on pci slot;
2- try to format your pc ( i know this is boring, but you have to try this solution too)

hope that this can help you. please post feedback of everything.

Thanx for the feedback,

Yes I know all about uninstalling drivers, hence the comment: 'I've tried various driver states/versions'  I have been at this for a while now ;-) I have even tried swapping different VIA card versions as that has help with other issues in the past...

There is only one PCI slot (It's SFF, annoying I know), I have read elsewhere that ppl have re-installed Window$ and it miraculously cleared-up their problem, First of all let me say this : If it comes to that I'll do it, but I'm just not that kind of guy, in that I need to know (or at least get a vague idea) what's causing this. I know the setup is overly complicated with tons of legacy crap (tied-in to old VIA drives and the like)etc.. and that all makes it difficult to diagnose but I think re-installing OS might be a clue. I would like to avoid this at all costs as I have tons of other work-horse type stuff layered installs and the like , I'm guessing If I backup and restore after I will just get the same problem back.... I have noticed that different VIA6421 card iterations respond differently to different drivers and perhaps that might have something to do with it also, The fact that Tara had the same problem hints something perhaps to do with the interaction of WinIO.sys and the drivers. I'm aware also that ppl often use different drivers for ripping/flashing & I'm curious what ver those who have success with VIA6421 and unlockSPI were using ??

I appreciate the suggestion(s) & the prompt response

Still looking for answers....

@the guy having the dvd-play issue, perhaps get the 1.9 re-pack (although I dont think it's called that ;-) and the absolute latest JF (I seem to remember something about a similar issue in the recent changelogs..)

try this via driver - i had freezing issues etc with my 6421L even after successfully removing the drivers from my system

until i found this driver on another site and it works like a charm!! was amazed!!

http://www.sendspace.com/file/hkc2uz

let me know if it works for you

[128bit]

Thanks GEREMIA and MAXIMUS it's really so easy metod thanks so much i love it!

I make my video here also ^_^
http://www.youtube.com/watch?v=WqcF-MLPU0w

[dangal]

Riku,can you send me a better pic? i cant see very well!!!!
thanks a lot!!!

[modguru]

Its because you cut one wire too much with your dremel AFAIK
Probably cordinates were off and you cut to the right and down little bit. Or you just dug too deep.

Darn, I hope that's not the case.. It's quite useless now.

UPDATE: Anyway, here is the pic of the drill. The correct wire is probably the one in upper left corner?
http://imageshack.us/f/88/drillzy.jpg/

I should probably drill this under microscope as my lines were drawn ok. 

take a look the cable the right series is 
black
red
yelow
green
white
if you have mess with the two last wrong the drive only closed and not ejekt

[Blown240sx]

Did a little research and it seems that most of the chips are coated in the same plastic as a billiards ball is made of.

Found that sulfuric acid will dissolve this. (Dangerous)

I may run down to the local auto parts store and see if they still carry battery acid aka sulfuric acid on the shelf.

If they do I have an old xbox 360 mother board. Ill try dissolving a chip on it. I dont know what effects that might have on the internal chip if any but if it works it would be an alternative to drilling it and may make it possible to soilder to those traces to make it easy to unlock and lock in the future. Reason being that Microsoft may be able to detect if the chip is still locked.

[cyanarnofsky]

Did a little research and it seems that most of the chips are coated in the same plastic as a billiards ball is made of.

Found that sulfuric acid will dissolve this. (Dangerous)

I may run down to the local auto parts store and see if they still carry battery acid aka sulfuric acid on the shelf.

If they do I have an old xbox 360 mother board. Ill try dissolving a chip on it. I dont know what effects that might have on the internal chip if any but if it works it would be an alternative to drilling it and may make it possible to soilder to those traces to make it easy to unlock and lock in the future. Reason being that Microsoft may be able to detect if the chip is still locked.

Thats why you relock the chip after flashing.

[Oggy]

I'm pretty sure no-one has answered this question and apparently this problem occurred with tarablinda also,

When I do : UnlockSPI 3490

I get : WinIO error in writing to port 3493

IF I try port 3480, it gives same error but with 3483, it seems to add 3 to the port each time? I know there is a range there, I've tried various driver states/versiosn etc.. all work fine for JF.
HELP!!! please!  This has got me stumped, and I don't have any other PC's I can use for flashing (Without drama, eg; 64bit win7 with SATA ports, non of which show in JF!

Oh yes, and BTW I am using 32 bit XP (VIA 6421) before you ask ..... I would try dos, but it wont boot from USB (Bloody IBM crap-ware BIOS!) and the floppy was removed ages ago to make room for everything else that's crammed-in there :p

Any help would be greatly appreciated.

first of all a clasic answer? did you install via's driver? if so, REMOVE IT!!! If you haven't instaled the driver, two suggestion:

1- try to change pci slot, maybe you have an issue on pci slot;
2- try to format your pc ( i know this is boring, but you have to try this solution too)

hope that this can help you. please post feedback of everything.

Thanx for the feedback,

Yes I know all about uninstalling drivers, hence the comment: 'I've tried various driver states/versions'  I have been at this for a while now ;-) I have even tried swapping different VIA card versions as that has help with other issues in the past...

There is only one PCI slot (It's SFF, annoying I know), I have read elsewhere that ppl have re-installed Window$ and it miraculously cleared-up their problem, First of all let me say this : If it comes to that I'll do it, but I'm just not that kind of guy, in that I need to know (or at least get a vague idea) what's causing this. I know the setup is overly complicated with tons of legacy crap (tied-in to old VIA drives and the like)etc.. and that all makes it difficult to diagnose but I think re-installing OS might be a clue. I would like to avoid this at all costs as I have tons of other work-horse type stuff layered installs and the like , I'm guessing If I backup and restore after I will just get the same problem back.... I have noticed that different VIA6421 card iterations respond differently to different drivers and perhaps that might have something to do with it also, The fact that Tara had the same problem hints something perhaps to do with the interaction of WinIO.sys and the drivers. I'm aware also that ppl often use different drivers for ripping/flashing & I'm curious what ver those who have success with VIA6421 and unlockSPI were using ??

I appreciate the suggestion(s) & the prompt response

Still looking for answers....

@the guy having the dvd-play issue, perhaps get the 1.9 re-pack (although I dont think it's called that ;-) and the absolute latest JF (I seem to remember something about a similar issue in the recent changelogs..)

May be you should send to a pro?