LITEON 0225 New PCB not working?

G

gurch

Junior Member
Jun 23, 2011
11
0
hi guys, yesterday i recived my x360 pro usb and i saved the keys from the original PCB to my pc, and then installed my new PCB, i plugged everything backup and my laptop sees the x360 pro but does not detect it
also when i push the Eject button on the CK3 lite the tray does not open :s

I took the wires out of the solderless component and doubled up the wires (folding them in half to make them thicker) and it still does not work

could some1 please help me on this as i have been waiting ages to get this working!!

Thanks guys :cool:
 
D

diaboliq20

VIP Member
Jun 23, 2011
3,497
0
Scotland
Aw man - I actually fear the worst for u here - I saw another guy on this forum today with the same issue, and it turned out to be a faulty PCB - something about a cold solder joint somewhere...... - have a search through for his thread, there may be some suggestions in there that may help - If I spot the thread, I'll post back for ya

In fact - here it is I think
http://www.team-xecuter.com/forums/showthread.php?t=68095
 
M

mac0707

Junior Member
Feb 25, 2011
13
0
Try to go into recovery mode. I had the same problem, so I decided to go into recovery mode then pow the drive showed up for some reason. It might just jump into recovery mode but if it doesnt you have to play with it.
 
Last edited:
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
The PCB's are shipped blank. There is no firmware. of course they will not eject and don't detect in jungle flasher.

You have to follow the instructions - it clearly tells you what to do .
 
Ubergeek

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,259
0
California, USA
mac0707 said:
Try to go into recovery mode. I had the same problem, so I decided to go into recovery mode then pow the drive showed up for some reason. It might just jump into recovery mide but if it doesnt you have to play with it.
Click to expand...
You mean the badflash method - just like the instructions tell you to do ;)

http://team-xecuter.com/forums/showthread.php?t=67582

Point #10

If the PCB doesn't detect at all and you can't get into vendor mode with the above method simply click Intro/Device ID and power cycle - you should then get into vendor mode (0x72) with no problems
Click to expand...
 
G

gurch

Junior Member
Jun 23, 2011
11
0
thanks for that guys!!! i managed to put on the firmware, but one more Quick question, at the bottom it says
DVD Key: Not Found (grey key)

could i still proceed without the key verified?? if not how do i verify the key
 
Last edited:
Ubergeek

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,259
0
California, USA
gurch said:
thanks for that guys!!! i managed to put on the firmware, but one more Quick question, at the bottom it says
DVD Key: Not Found (grey key)

could i still proceed without the key verified?? if not how do i verify the key
Click to expand...
:rolleyes:

I hate it when people buy products then have absolutley no idea how to use them even though they are given simple step by step instructions

OF COURSE you have to take your DVD Key from your original PCB and copy to your Unlocked PCB. How else do you think its going to work ?
 
sherlock

sherlock

Troll Eating Dogs
May 24, 2009
1,926
78
Baker street, Stoke-on-Trent, England
gurch said:
thanks for that guys!!! i managed to put on the firmware, but one more Quick question, at the bottom it says
DVD Key: Not Found (grey key)

could i still proceed without the key verified?? if not how do i verify the key
Click to expand...

the key not verified is because it's the first time that drive has been read and the key extracted and it's not yet in the jungleflasher database, the next time you use that key it will be verified against the jungleflasher database.
 
H

had22

Full Member
Sep 24, 2010
57
0
Fl,USA
Ubergeek said:
in what way do you expect it to detect it ?

In jungle Flasher yes ?

read the instructions again. I just posted clearly on how to do that.
Click to expand...
you have point but no where on the steps does it say that
on step:9 it state this
2) Click the I/O refresh button and make sure that the drive properties show that its a PLDS DG-16D4S, how can it? if you already said there no software in it.
on (4) The PCB will detect as a Liteon Slim, how? if there is no past FW in it, so you see kinda confusing for someone new, I mean I had no problem with it is common sense that PCB come with no FW it even say it on the websites.
 
Last edited:
Z

ZALALEX

Noob Account
Jul 28, 2010
4
0
I've problems with TX PCB too. The vendor mode is ok. i've got 072 status. But then writing Bank 0 it's freezes.
I've Tried different jungle (v.0.1.85.Beta(257) and v0.1.84 Beta (250)). But there is no result for me. I also use TX USB PRO.


LOG
JungleFlasher 0.1.85 Beta (257)
Session Started Wed Jul 27 14:38:47 2011

This is a 32 bit process running on a 32 bit CPU
X360USB PRO detected, Version 0.18

portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 7 I/O Ports.
Found 1 Com Ports.
Found 7 windows drives C: F: G: H: K: V: W:
Found 0 CD/DVD drives

Sending Vendor Intro to port 0x0000
Status 0x80
Re-sending Vendor Intro:
......
Serial flash found with Status 0x72

Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes

Sending Spi Lock to Port 0x0000
Success !
Spi Status: 0x8C

Sending Spi UnLock to Port 0x0000
Success !
Spi Status: 0x00

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

Sending Chip Erase to Port 0x0000
Erasing:
Blank Test !

Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Blank verified OK !
Loading firmware file C:\JungleFlasher.0.1.84.Beta(250)\JungleFlasher v0.1.84 Beta (250)\firmware\Orig-0225.bin
MD5 hash: 3f6486dbafe586beca0cd98a6f93b525
Drive key @ n/a D53B9CA4511C9BCFA5C31123166A5829
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: Stock

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

Sending Chip Erase to Port 0x0000
Erasing:
Writing target buffer to flash
Writing Bank 0: .....XECUTER X360USB PRO removed
 
Z

ZALALEX

Noob Account
Jul 28, 2010
4
0
I've tried 2 different PC. tried with USB PRO and with PC SATA ports. The same problem. My USB PRO works fine with others DVD drives.
 
Z

ZALALEX

Noob Account
Jul 28, 2010
4
0
I don't think so - i've 4 PCB. And i can't write all of them with the same error. So, some people have the same problems. Maybe it is time to wait for new JF?

P.s. IF using the usb pro does writing may depend on PC (intel, AMD) or OS (Win XP, Win Vista, win7)?
 
P

PMX Tech

Noob Account
Aug 4, 2011
2
0
I just wanted to add that I have the same problem, almost two weeks now. Xconsoles been going back and forth with me trying to help, finally going to send board in.

Basically mine gets stuck on the "writing bank: . " 3 out of 10 liteon 73's used to do that too me and I would have to use a different controller on them, never did figure out. Im thinking chip compatibilities on the controller verse my motherboard etc. It's possibly Xconsoles will be able to flash it right away.

I will tell you this though, on my PCB, when you intro device and flip the ck3 it gets a 72 status and immediately pops up and says DEVICE ID FAILED and to "Return the MRA hack to the normal position" ?? If I click OK it just cycles and any commands produce unknown flash type. If I hit cancel it will let me erase successfully but not write. Mailing pcb back monday so if any has any suggestions i'm still open.

EDIT: oh and new jungleflasher or old, no difference.
 
Ubergeek

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,259
0
California, USA
ZALALEX said:
I don't think so - i've 4 PCB. And i can't write all of them with the same error. So, some people have the same problems. Maybe it is time to wait for new JF?

P.s. IF using the usb pro does writing may depend on PC (intel, AMD) or OS (Win XP, Win Vista, win7)?
Click to expand...
Definatley PEBKAC

Almost every single one that I have received back (except 2) have not been faulty at all - I could vendor and write to them straight away.

have you tried JF 1.86 ?
 
You must log in or register to reply here.