How to repair lite-on pad 101

[iateshaggy]

there is, we look at what circuits you have busted and find a way to reroute them.

[chi3f]

I''m good at soldering but what I mean is there  should be a base line to start with !

That is one messed up board. I could just mail you one. Just pay for shipping.

[farntheplaya]

ive got a sept 2009 93450c drive

done a LOT of drives so its not wiring.

no matter what cant get proper status always 0x80. have tried switch and probe 2
using 22 ohm resistor/have tried from probe (18/22/20)

3.3 to ground has 1k Resistance

any ideas? drive still works when wired correctly

[chi3f]

ive got a sept 2009 93450c drive

done a LOT of drives so its not wiring.

no matter what cant get proper status always 0x80. have tried switch and probe 2
using 22 ohm resistor/have tried from probe (18/22/20)

3.3 to ground has 1k Resistance

any ideas? drive still works when wired correctly

I have had the same thing happen to me. It turned out that I had not properly cut a trace. You couldn't even tell by looking at it but after I had went back over with the razor it dumped just fine.

[farntheplaya]

nope my traces were fine checked with multimeter.

i just lowered the resistor to 17 and that fixed my problem.

[iateshaggy]

measure the resistance of the resistors, the results will surprise you.

[relltherell]

I'm having a problem I'm using the probe 2 and my pad 101 is damn there destroyed which fix do I use? Most of these I think are for users with made up probes I can get into vendor mode I just can't read the key. Where should I solder at? Thanks in advance pics coming soon

[iateshaggy]

if you got it into vendor mode, then you can read the key.  post your log.

[relltherell]

hey shaggy i just realized what you were talking about...we spoke thru email

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

there is my problem fully explained and threshed out...

when i go to read because of the destroyed pad i get x80 and x50 errors when i go to read after getting MXblahblah status - after getting x72 - it seems to me the problem is that i dont have enough pad contact to read the key. so im going to take a look at the thread you were talking about - if i can find it -


Edit: ok i see the post now this can be any wire...i just have to solder the points then click read? do i still have to use my probe 2 to read the key?

[Dream]

relltherell,

Post pictures here. I am banned from xecuter forum so can´t see the pictures.
Use easy probe2 to dump the drive.
We can help you here so don´t worry.

[relltherell]

Ok pics

http://i298.photobucket.com/albums/mm272/malconal2/100_0901.jpg

http://i298.photobucket.com/albums/mm272/malconal2/100_0900.jpg

My problem is i dont understand how just soldering that wire fix will give me the ability to read the firmware off.... i dont understand the process.

So would i solder the fix wire from the first pic and first post then try to get the key without the probe? or afterward do i still use my ck3 probe v2? do i remove it to flash it once im done do i remove it to repair the trace then pack it back up? can i spoof a samsung with that liteon if i destroyed the liteon?


Sorry for so many questions but this is sensitive stuff. i want to be 100 percent sure.

[Dream]

It is 3,3V DC line so we can jump 3,3V almost anywhere on the board.

Xecuter Probe2 Pad 122 Dump By: banned fool  
Use only one probe pin Green and dump it.

Fix like this and measure resistance 3,3V to GND 95 Kohm - 110 Kohm is good then dump it.


Green Green  Green!! Xecuter Probe2 it like this.


Stock Fix it like this

[relltherell]

Wow so i just solder a wire where the yellow is on top of the pcb (in the 2nd pic)...and thats it....just wow

and im just repairing the trace in the first pic with conductive glue when im done


PS correct me if im wrong

[Dream]

relltherell,

Do you have the FW?
That is stock fix @ working drive....

[relltherell]

No...i need to pull the original firmware off at this point. which is what im stuck at trying to do with the nearly fully broken pad101

[Dream]

No...i need to pull the original firmware off at this point. which is what im stuck at trying to do with the nearly fully broken pad101

First picture that i posted, is all you need probe pad 122!!!!
Only Xecuter Probe2 green pin in pad122 hole.
Wight button on top off the probe2 have to be pressed down. MRA mode on...

[relltherell]

if i probe that point dont i have to repair that cut on that line...i keep gettin x80 mra and white button down green pin side.

[Dream]

if i probe that point dont i have to repair that cut on that line...i keep gettin x80 mra and white button down green pin side.

You have tried 22/20/18 resistors on the Probe2?
If you have then make Easy Probe2 and use R15 ohm resistor.
Some drives need 15 ohm resistor to get status x72.

[304bgp]

Where can i send the board for key retrieval?
I just need my keys. I have a Samsung that i will be spoofing.

Please PM price and location.

[relltherell]

Where can i send the board for key retrieval?
I just need my keys. I have a Samsung that i will be spoofing.

Please PM price and location.

I am also about to go that route....


Heres My Log


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.75 Beta (152)
Session Started Fri Jul 23 10:14:51 2010

This is a 32 bit process running on 2 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 10 I/O Ports.
Found 2 Com Ports.
Found 3 windows drives C: D: E:
Found 1 CD/DVD drives D:

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

Sending Device ID request to port 0xE880
Manufacturer ID: 0x2A
Device ID: 0x2A
Flash Name:  Unknown type
Flash Size:  n/a


Serial flash found with Status 0x72

Sending Device ID request to port 0xE880
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name:  MXIC(MX25L2005)
Flash Size:  262144 bytes

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x80

Getting Status from port 0xE880
Invalid Status 0x80

Getting Status from port 0xE880
Invalid Status 0x80

Getting Status from port 0xE880
Invalid Status 0x80

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x0

Getting Status from port 0xE880
Invalid Status 0x50

Getting Status from port 0xE880
Invalid Status 0x50



More detailed pics in a second...thanks alot dream but im not getting any activity or response from pad 122 this is my current set up

* pic