LITEON 9504 Flash properties undetected

[Kratos8051]

Hi guys,

I hope you can help me with an issue I'm having. Last night I messed-up a Kamikaze (I am a bit out of practice). I was able to dump the firmware and flash the drive, but I get the infamous drive not opening. Luckily I had a 9504 replacement board. After installing the board, I connected JF and the drive was detected and the drive properties showing in the left-hand pane. However, JF tells me in the log, that it is an unrecognised drive. I thought maybe this is because the PCB is shipped without firmware.

Following the JF I clicked into to get the drive into vendor mode, since the board is unlocked according to my knowledge. Nothing happened. I then realized the radio button was on "slim", so I switched to "phat". Again nothing happened. I then saw that the drive was not detected in JF. I power cycled and got the drive detected. Again I tried intro-ing the drive, but still nothing. I then tried Slim Unlock, but I got an error message stating that no slim drive is connected. Now, I can't get the drive to detect in JF. Sometimes, if I am lucky, I can get the drive detected, but that is by pure luck. If I click on anything, the drive vanishes from JF. I tried the bad flash recovery in the tutorial, and am able to get it in vendor mode. However, no matter what I do, JF doesn't recognise the flash properties, hence I am unable to complete the flash.

I'm starting to think that maybe I should use Dosflash to erase the drive and then try again. However, I am using a X360usb Pro 2 and I am not sure how to format using the USB. I am also unsure if the process is the same as for the phat drives. I tried connecting the drive to onboard SATA, but because the drive is undetected, I don't want to flash erase on an unknown SATA port.

You guys have any advice on what to do? Is Dosflash the way to go? Is the replacement board bust?

 

[Kratos8051]

Thanks TombRaid. I wanted to try that trick last night, but didn't have the right resistors. Will see if I can get some today. Just in case I drilled way too deep and the trick doesn't work, anybody have an idea on die 9504 PCB?

 

[Kratos8051]

Thanks for the tip TombRaid. Unfortunately, I don't have any additional USB drives etc connected. Only my USB keyboard and mouse.

I did some reading and it would seem like X360USB Pro is not supported using doshflash (as I was suspecting). I found an older forum suggesting Lite-On Erase on a phat drive. If it doesn't work, continue erasing until it finishes. Might this trick also work on the slim drive?

 

[Kratos8051]

I will give it a shot when I get home tonight. I also read somthing about Ctrl + SHift + F9 before device intro. Will also try that.

 

[Martin C]

Your biggest mistake was clicking random options in JungleFlasher, rather than following the PDF.

Your PCB is probably ok.

 

[Kratos8051]

Thanks for reassuring me that the PCB is ok MartinC. I did follow the JF tut, but I should have read it properly. I should have gone for option 2 on page 104 and not option 1 first. Do you have any advice on what to try to get the drive into vendor mode?

 

[Martin C]

try setting it to phat, then choosing vendor mode.

 

[Kratos8051]

Ok, I'm able to get the drive in Vendor mode using both the slim and phat radion button. However, the flash properties stay undetected. Any other advice?

Edit: After a massive struggle I was able to get the drive into vendor mode. I spoofed the source firmware and clicked on write....only to have JF crash on me. Damn! Funny thing though. If the flash properties are detected incorrectly, the SPI shows as unlocked (0x00). However, then the flash properties were correctly detected, no SPI status was shown.

 

[Martin C]

Got a screenshot of what you mean?

 

[Kratos8051]

Will grab one as soon as I can repeat the results Martin C

Edit: Here are the screenshots Martin.

This is what I get most of the time, regardless of whether I select slim or phat before intro-ing the drive. As you can see, the SPI lock status is unlocked (0x00), but the flash is undetected.

After intro-ing the drive hundreds of times (literally), I am able to get the flash properties to show up. The process to get to this state is random. I into hundreds of times switching between phat and slim, using Ctrl + Shift + F9 and not, and power cycling the drive numerous times. However, look at the block indicating the SPI lock status. No status is indicated. If I spoof the drive and click Write in this state, I get a message stating that the drive in an invalid state.

Eventually I was able to get the flash properties to show up with the SPI lock status as unlocked. However, when I click write (after spoofing the drive), JF stops at writing bank 0.

Getting Status from port 0x0000
SPi flash found with Status 0x72

Sending Chip Erase to Port 0x0000
Writing target buffer to flash
Writing Bank 0: .

 

[OliIce]

Hi Ya

Had a similar problem of late, I had my X360USB PRO plugged into the usual USB 3 front port on my PC (always worked before!) but not this time.


However by chance I decided to plug the X360USB PRO into one of the USB 2 ports on the rear of the PC.


Hey Presto everything worked like a charm!
Hope this might help you.

 

[Kratos8051]

Thanks Olilce. I will give it a shot later today. I guess if this doesn't work, it is safe to assume the PCB is bust?

I also tried TombRaid's tip with the wire attached to POUT and it doesn't work. Guess I screwed up the Kamikaze big time.

 

[Antalpromille]

Thanks Olilce. I will give it a shot later today. I guess if this doesn't work, it is safe to assume the PCB is bust?

I also tried TombRaid's tip with the wire attached to POUT and it doesn't work. Guess I screwed up the Kamikaze big time.

I would assume the worst. But if you have the slimkey extract saved, just get a pro unlock kit and install on your pcb

 

[Kratos8051]

Yeah. I'm wasting a lot of time with this PCB. I am busy ordering a replacement. I have the slimkey dumps as well as the complete original firmware. I got the drive to unlock using Kamikaze. I think I drilled a bit off-center, so the drive doesn't open, but luckily I was able to fully dump the firmware.

I would still love to try and fix the 9504 board issue. What's the odds of it being the flash chip? Can I maybe tansplant this chip to the Kamikaze board to see if it works?

 

[Antalpromille]

Be aware that the full dump might be corrupt, not saying that it is but it might.

 

[Kratos8051]

Thanks for the tip! Could this maybe cause the weird crashes I have in JF when I try to write the firmware to the drive, or would corrupt firmware only cause the drive not to work?

 

[Antalpromille]

Hard to say but i think its a bigger chans it makes the drive not work properly in your xbox than making JF crash.

 

[Kratos8051]

Thanks Antalpromille. That would be my guess as well. Thanks for your help!

 

[prankster]

Thanks for the tip! Could this maybe cause the weird crashes I have in JF when I try to write the firmware to the drive, or would corrupt firmware only cause the drive not to work?

If the firmware were corrupt, it wouldn't parse in jungleflasher.

Sent from my Nexus 4 using Tapatalk 2

 

[Kratos8051]

Well, I am able to load the firmware in JF, so I would assume the firmware is dumped ok.