My x360usb pro arrived and it flashed it without a single problem, Right into vendor mode
Very happy now
Thanks guys
Very happy now
Thanks guys
LITEON 9504 TX PCB Not Entering Vendor
- Thread starter ~Craig~
- Start date
x360ccm
BANNED
BraveH43
VIP Member
yes it does! (mainly to cover a very small number of drives that unique info is extended beyond normal region in the firmware)
So I agree - use latest JF on original PCB if that option is available to you
I created a new dummy file from my stock pcb with the new jf.
I thought I may aswell as the x360pro makes it so easy
I thought I may aswell as the x360pro makes it so easy
My x360usb pro should be here tomorrow, very excited that I found one in stock .
If it is as easy as everyone says it is I will probably be flashing away from home soon.
~Craig~: Congratulations
.If it is as easy as everyone says it is I will probably be flashing away from home soon.
~Craig~: Congratulations
I tried both methods and only the 2nd method worked. Now I got into vendor 0x72 but I could not read the FW. I clicked read and it said my SPI was locked.The fact that VIA doesn't work well with slim drives is well known - I presume your flash to 1.91 was its first use ?
You went from having a blank chip (works on almost any chipset)
Then you flashed it with locked slim drive (0272) fw -(after outro this is now essentially a slim drive - enter the VIA problems)
There is a work round for this but its a pita
IF you have a PMT set up (probe 3 style)
then
1. Click Intro
2. Power off on CK3
3. Click Yes
4. Hold in your Probe 3 Button (the one on your 3.3v Line on cable)
5. Power ON on CK3
6. a second after powering on - release the probe 3 Button.
This delays powering the SPi and allows drive to enter Vendor Mode!
failing this you could also use Badflash Method for Slims
during intro ........
1. Power off CK3
2. Probe MPX01 (with PMT)
3. Power ON CK3
4. As soon as you see status change lift the probe (DONT HOLD IT THERE)
So PLEASE STOP TRASHING THE T-X PCB - Its your Chipset! NOT the PCB
So then I pressed slimkey and when it came up to intro I did the same thing. Here is my log for the slim key and BTW I may have gotten my key but each time I do it it is different but I compared all 4 and typed my own key based on the percentage of each byte on the 4
Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.87 Beta (277)
Session Started Sun Sep 11 22:39:45 2011
This is a 32 bit process running on a 32 bit CPU
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 2 Com Ports.
Found 3 windows drives A: C: Z:
Found 0 CD/DVD drives
Drive is Slim Lite-On..
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 34 53 - 20 20 20 20 20 20 20 20 DG-16D4S
0020: 30 34 30 31 00 00 00 00 - 00 00 00 00 00 00 00 00 0401............
0030: 00 00 00 00 41 30 41 30 - 00 00 00 00 00 00 00 00 ....A0A0........
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0060: 44 37 31 36 43 47 31 31 - 32 38 30 33 30 30 44 57 D716CG11280300DW
0070: 4C 20 20 20 L
Sending Vendor Intro to port 0xFE20
Status 0x51
Re-sending Vendor Intro:
.............
Serial flash found with Status 0x72
Sending Device ID request to port 0xFE20
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
............
Stage 1 failed
Key: ****(blank'd out for obvious reasons)**** verification failed !
SlimKey extraction failed!
No Drive Detected! DVDkey files extraction aborted!
Drive is Slim Lite-On..
Drive is Slim Lite-On..
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 34 53 - 20 20 20 20 20 20 20 20 DG-16D4S
0020: 30 34 30 31 00 00 00 00 - 00 00 00 00 00 00 00 00 0401............
0030: 00 00 00 00 41 30 41 30 - 00 00 00 00 00 00 00 00 ....A0A0........
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0060: 44 37 31 36 43 47 31 31 - 32 38 30 33 30 30 44 57 D716CG11280300DW
0070: 4C 20 20 20 L
Sending Vendor Intro to port 0xFE20
Status 0x51
Re-sending Vendor Intro:
..................
Serial flash found with Status 0x72
Sending Device ID request to port 0xFE20
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
............
Stage 1 failed
Key: ****(blank'd out for obvious reasons)**** verification failed !
SlimKey extraction failed!
Drive is Slim Lite-On..
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 34 53 - 20 20 20 20 20 20 20 20 DG-16D4S
0020: 30 34 30 31 00 00 00 00 - 00 00 00 00 00 00 00 00 0401............
0030: 00 00 00 00 41 30 41 30 - 00 00 00 00 00 00 00 00 ....A0A0........
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0060: 44 37 31 36 43 47 31 31 - 32 38 30 33 30 30 44 57 D716CG11280300DW
0070: 4C 20 20 20 L
Sending Vendor Intro to port 0xFE20
Status 0x51
Re-sending Vendor Intro:
...........
Serial flash found with Status 0x72
Sending Device ID request to port 0xFE20
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
............
Stage 1 failed
Key: ****(blank'd out for obvious reasons)**** verification failed !
SlimKey extraction failed!
Drive is Slim Lite-On..
Drive is Slim Lite-On..
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 34 53 - 20 20 20 20 20 20 20 20 DG-16D4S
0020: 30 34 30 31 00 00 00 00 - 00 00 00 00 00 00 00 00 0401............
0030: 00 00 00 00 41 30 41 30 - 00 00 00 00 00 00 00 00 ....A0A0........
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0060: 44 37 31 36 43 47 31 31 - 32 38 30 33 30 30 44 57 D716CG11280300DW
0070: 4C 20 20 20 L
Sending Vendor Intro to port 0xFE20
Status 0x51
Re-sending Vendor Intro:
............
Serial flash found with Status 0x72
Sending Device ID request to port 0xFE20
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
............
Stage 1 failed
Key: ****(blank'd out for obvious reasons)**** verification failed !
SlimKey extraction failed!Have you followed the guide?
If all you're trying to get is the key:
1. Start JF
--a. DVDKey 32 Tab
--b. Check port is 0x000
--c. The drive should be detected as Liteon DG-16D4S
--d. Dummy.bin should be checked off. (upper right on JF)
--e. Start Slim Key
2. When the Slim Key prompt appears click No.
3. Then another prompt to cycle the drive appears, press yes, and power cycle.
4. You should now be in Vendor mode.
5. JF should do its thang to get some keys.
6. Save Dummy.
As the first thing you quoted says: VIA 6421 chipset has problems with slims, especially the latest firmwares. In my case 0272 would not get into vendor mode or even give me my dummy.bin with VIA 6421/nForce/Intel chipsets.
After using that trick to get into vendor mode, I was still unable to get my dummy.bin, I would always get extraction failed message. I asked some users why it was happening, and they would either respond:
X360USB PRO!!!
or
I have no idea.
So you're stuck in the same boat as everyone else without a x360usb pro.
So I had to buy a x360usb pro, which works wonderfully at a cost.
So are you trying to get the dummy.bin from your stock pcb? and have you read this thread?, you should. Apparently most 9504 > 0272 users can't do this without the right chipset/x360usb pro.
If all you're trying to get is the key:
1. Start JF
--a. DVDKey 32 Tab
--b. Check port is 0x000
--c. The drive should be detected as Liteon DG-16D4S
--d. Dummy.bin should be checked off. (upper right on JF)
--e. Start Slim Key
2. When the Slim Key prompt appears click No.
3. Then another prompt to cycle the drive appears, press yes, and power cycle.
4. You should now be in Vendor mode.
5. JF should do its thang to get some keys.
6. Save Dummy.
As the first thing you quoted says: VIA 6421 chipset has problems with slims, especially the latest firmwares. In my case 0272 would not get into vendor mode or even give me my dummy.bin with VIA 6421/nForce/Intel chipsets.
After using that trick to get into vendor mode, I was still unable to get my dummy.bin, I would always get extraction failed message. I asked some users why it was happening, and they would either respond:
X360USB PRO!!!
or
I have no idea.
So you're stuck in the same boat as everyone else without a x360usb pro.
So I had to buy a x360usb pro, which works wonderfully at a cost.
So are you trying to get the dummy.bin from your stock pcb? and have you read this thread?, you should. Apparently most 9504 > 0272 users can't do this without the right chipset/x360usb pro.
Last edited:
Hi all, I am in the process of trying to update from 0272 1.92 to 0272 2.0 on my team X replacement board (its working fine playing backups etc on 1.92 at the moment) anyway, I've encountered the unable to enter vendor mode as outlined in this thread and on reading it I realised my problem is my chipset. My plan is to buy a 360usb pro but my finances dictate that this cannot happen until next month. This leaves the probe option for now. I'm going to have to make a probe the way deadliner (above) did.
Can anyone point me to the correct guide to follow to both make and use the probe, Iunderstand that it is a needle and a length of wire but can some one advise me of the two points I need to make contact with and the process (at which point in the process do I use the probe)
Can anyone point me to the correct guide to follow to both make and use the probe, Iunderstand that it is a needle and a length of wire but can some one advise me of the two points I need to make contact with and the process (at which point in the process do I use the probe)